Offline 212.107.29.67:28015 checked 40d ago
MonkeyCode Test Server
Connect
srv = rust.server("212.107.29.67: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.29.67:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 4 Sep 2026, 01:16 UTC
- hostname
- –
- first seen
- 17 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 · 149 on average | 159/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 132/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 189/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 78/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 10/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 23/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does MonkeyCode Test Server rank?
Over the last seven days MonkeyCode Test Server sits at #15,398 on player hours, in the top – of ranked servers.
How many players does MonkeyCode Test Server hold at once?
The current row shows MonkeyCode Test Server offline; the last response was 40 days 22 hours ago.
About the server
Which Rust version is MonkeyCode Test Server on?
The build is Rust network protocol 2633 and build 162929 on Linux, run by MonkeyCode Test Server. Joining needs the same protocol on your game; Steam handles the update.
Is MonkeyCode Test Server up, and what does its uptime show?
MonkeyCode Test Server is offline at this refresh; the last response came 40 days 22 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 17 September 2026.
Where does MonkeyCode Test Server sit?
For MonkeyCode Test Server, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 212.107.29.67:28015 is its address.
Settings and map
Which settings and rules does MonkeyCode Test Server run?
No gather rate appears in the name: MonkeyCode Test Server. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
Which map has MonkeyCode Test Server selected?
MonkeyCode Test Server runs a procedural map, which the game generates.
Wipes and dates
When does MonkeyCode Test Server wipe, and on what schedule?
The record for MonkeyCode Test Server holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 55 days 10 hours ago.
Tags and filters
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. Under these filters on the server list, it is listed: 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?
The game's server browser reads these tags from MonkeyCode Test Server: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): To join, your game must run protocol 2633; cs162929 (Build): Recorded game build: 162929; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way to join MonkeyCode Test Server?
In Rust, F1 opens the console: type client.connect 212.107.29.67:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.