Offline 77.50.255.146:28015 checked 1d ago
testbuild
Connect
srv = rust.server("77.50.255.146:28017")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
48 hours: hourly readings. 30 to 90 days: one point a day, with the day's average and lowest fps, most entities and most memory. From asking the server directly; low fps and a climbing entity count mean lag.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is best
Top 40% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 10 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 25 Oct, 13:12 UTC3d ago | 2 | NaN | running | 1 |
# Peak: the most players in the first 48 hours. Crowd: whether every day of the wipe kept at least half that peak, or the day it fell below. A new world less than six hours after a wipe is a restart, not a wipe of its own.
display(srv.map, srv.info())
Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 77.50.255.146:28015
- region
- –
- max players
- 15
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 25 Oct 2026, 13:12 UTC
- hostname
- –
- first seen
- 25 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 155 on average | 28/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 131/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 33/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 13/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 4/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 1/1000 |
Quick answers
From the figures on this page.
Player counts
How does testbuild compare in the rankings?
Over the last seven days testbuild sits at #8,927 on player hours, in the top 40% of ranked servers.
What population does testbuild carry?
testbuild returns no live count at this refresh, having last been seen 30 hours ago. Over the last seven days it averaged 1 players and peaked at 2. Averaged by hour over 48 hours, 19:00 UTC is the busiest, at 1 players.
About the server
Which Rust version is testbuild on?
Version Rust network protocol 2635 and build 168909 on Windows is reported by testbuild. The protocol has to match before you can join, and Steam does the updating.
How reliable is testbuild, and is it up?
The latest sample has testbuild offline, with a last sighting 30 hours ago. 2 of 72 hours up over the last 3 full days, or 3%. Its earliest recorded date in Rust Data is 25 October 2026.
In which location is testbuild hosted?
There is no region published for testbuild. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 77.50.255.146:28015.
Map and rules
Which settings and rules does testbuild run?
No gather rate appears in the name: testbuild. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. Anti-cheat status: VAC on.
Which map has testbuild selected?
A procedural map runs on testbuild, generated by the game.
Wipe data
When does testbuild wipe, and on what schedule?
A rhythm cannot be read from the wipes of testbuild on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 3 days 13 hours ago, and that is the one in play.
What is wipe day on testbuild like?
Across recent wipes the busiest point averaged 2 players. Peak population on the latest wipe came 10 hours in.
Lists and tags
Which lists on Rust Data hold testbuild, and which filters?
The Rust Data lists that testbuild fits are: Modded Rust servers and Servers with build or creative tags. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
How should you read the server tags on testbuild?
These tags are published by testbuild and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp15 (Max players): Slot count: 15; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
How to join
How can I connect to testbuild?
The manual route: launch Rust, F1, then client.connect 77.50.255.146:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.