Offline 77.50.255.146:28015 checked 3d ago
testbuild
Connect
srv = rust.server("77.50.255.146:28016")
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 69% 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 25 Oct, 12:16 UTC3d ago | 0 | NaN | running | 0 |
# 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, 12:16 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 · 149 on average | 167/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 123/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 192/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 67/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 12/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 17/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does testbuild rank?
Player hours over seven days put testbuild at #15,323, in the top 69% of the ranked set.
How many players does testbuild hold at once?
The current row shows testbuild offline; the last response was 3 days 23 hours ago. Over the last seven days it averaged 0 players.
Server facts
What is the Rust version on testbuild?
Rust network protocol 2635 and build 168909 on Windows is what testbuild runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is testbuild, and is it online now?
The latest sample has testbuild offline, with a last sighting 3 days 23 hours ago. Uptime of 0% across the last 3 full days: 0 hours of 72. Its earliest recorded date in Rust Data is 25 October 2026.
Which location does testbuild run from?
For testbuild, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 77.50.255.146:28015.
Rules, settings, map
Which rules apply on testbuild, and what settings?
You will not find a gather rate in the string testbuild. No custom cap; the default of 8 players per group stands. Recorded as survival, the usual game, with gathering, building and raiding. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.
What is the map on testbuild?
testbuild runs a procedural map, which the game generates.
Wipe data
When does testbuild wipe, and on what schedule?
The record for testbuild holds too few wipes to show a rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 3 days 23 hours ago.
On testbuild, what happens on wipe day?
Across recent wipes the busiest point averaged 0 players. The crowd on the latest wipe topped out 0 hours after it began.
Tags, lists
Which Rust Data filters and lists contain testbuild?
These Rust Data lists include testbuild: 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.
Which meanings do the tags on testbuild hold?
Read by the game's server browser, the tags testbuild publishes are: gmrust (Game mode): Rust survival in its standard form; mp15 (Max players): 15 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way into 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.