Offline 212.107.28.50:28015 checked 39d ago
MonkeyCode Test Server
Connect
srv = rust.server("212.107.28.50: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
Wipe schedule
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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
- 212.107.28.50:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 4 Sep 2026, 01:16 UTC
- hostname
- –
- first seen
- 20 Sep 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 · 151 on average | 17/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 · 122 on average | 36/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 97 on average | 6/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 94 on average | 20/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 112/200 |
Quick answers
From the figures on this page.
Player counts
What position does MonkeyCode Test Server take in the server rankings?
Player hours over seven days put MonkeyCode Test Server at #15,481, in the top – of the ranked set.
How full does MonkeyCode Test Server run?
MonkeyCode Test Server returns no live count at this refresh, having last been seen 39 days 18 hours ago.
Server facts
What Rust version does MonkeyCode Test Server run?
The build is Rust network protocol 2633 and build 162929 on Linux, run by MonkeyCode Test Server. The protocol has to match before you can join, and Steam does the updating.
How reliable is MonkeyCode Test Server, and is it online now?
MonkeyCode Test Server is offline at this refresh; the last response came 39 days 18 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 20 September 2026.
Where does MonkeyCode Test Server sit?
For MonkeyCode Test Server, 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. 212.107.28.50:28015 is its address.
Map and rules
Which settings and rules does MonkeyCode Test Server run?
You will not find a gather rate in the string MonkeyCode Test Server. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
Which map has MonkeyCode Test Server loaded?
A procedural map runs on MonkeyCode Test Server, generated by the game.
Wipe schedule
On what schedule does MonkeyCode Test Server wipe?
The record for MonkeyCode Test Server holds too few wipes to show a rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 56 days 2 hours ago.
Tags, lists
Which lists on Rust Data hold MonkeyCode Test Server, and which filters?
The Rust Data lists that MonkeyCode Test Server fits are: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on MonkeyCode Test Server?
These tags are published by MonkeyCode Test Server and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): To join, your game must run protocol 2633; cs162929 (Build): The server runs build 162929; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
What is the way into MonkeyCode Test Server?
In Rust, F1 opens the console: type client.connect 212.107.28.50:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.