Offline 103.156.242.197:28015 checked 42d ago
MonkeyCode Test Server
Connect
srv = rust.server("103.156.242.197: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
- 103.156.242.197: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 · 151 on average | 35/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 130/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 123 on average | 38/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 97 on average | 14/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 94 on average | 35/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 47/200 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does MonkeyCode Test Server rank?
Player hours over seven days put MonkeyCode Test Server at #15,502, in the top – of the ranked set.
How full does MonkeyCode Test Server run?
The current row shows MonkeyCode Test Server offline; the last response was 42 days 22 hours ago.
Server facts
What is the Rust version on MonkeyCode Test Server?
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.
Is MonkeyCode Test Server up, and what does its uptime show?
The latest sample has MonkeyCode Test Server offline, with a last sighting 42 days 22 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 17 September 2026.
Which location does MonkeyCode Test Server run from?
There is no region published for MonkeyCode Test Server. 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 103.156.242.197:28015.
Map and rules
What rules and settings are recorded for MonkeyCode Test Server?
The name MonkeyCode Test Server carries no gather rate. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: gather, build, raid: the standard loop. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. Anti-cheat status: VAC on.
Which map has MonkeyCode Test Server selected?
MonkeyCode Test Server runs a procedural map, which the game generates.
Wipe data
When does MonkeyCode Test Server wipe, and how often?
Too few wipes are on record for MonkeyCode Test Server to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 56 days 4 hours ago.
Tags, lists
Which lists on Rust Data hold MonkeyCode Test Server, and which filters?
These Rust Data lists include MonkeyCode Test Server: 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): Survival play, standard Rust; 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): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^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.
Join steps
What is the way into MonkeyCode Test Server?
In Rust, F1 opens the console: type client.connect 103.156.242.197:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.