MonkeyCode Test Server
Key statistics
the figures behind the quote- Players now
- 0/ 10 0% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 0 peak –
- Rank
- #15,481 no region published
- Rank · 7d ago
- #15,134 ▼347 places down
- Last wipe
- 40d ago no schedule published
- Next wipe
- – no wipe seen yet
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 0 player hours, last seven days
- Map
- – Procedural Map
- First seen
- 20 Sep 2026 no hostname published
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestWipe schedule
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | ShockRust | Blue | NoLimitno group limit · 126 on average | 200/300 | ▲+9+4.8% | |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 13.10EU · groups of 16+ · weekly · 106 on average | 193/225 | ▼−5−2.4% | |
| 3 | МИНИ-КАРТА 2Х | STORM | FPS+ 10.10EU · groups of 8+ · weekly · 90 on average | 88/100 | ▼−3−3.1% | |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 10.10EU · groups of 16+ · monthly · 86 on average | 49/1000 | ▼−54−52.5% | |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 08.10EU · groups of 16+ · monthly · 76 on average | 11/1000 | ▼−22−66.2% | |
| 6 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 11.10EU · groups of 16+ · monthly · 72 on average | 54/700 | ▼−76−58.5% |
Quick answers
from the figures on this pageServer Rules
How is MonkeyCode Test Server configured in terms of rules and settings?
No gather rate appears in the name of MonkeyCode Test Server. The default group size of 8 players applies here. survival is the mode, gather, build and raid in the standard game. Combat and raiding between players are allowed. Modded is its category in the server browser; plugins or settings modify the game. Oxide plugins are in use. The server has VAC, Valve's anti-cheat, switched on.
Which map is played on MonkeyCode Test Server?
The game generates the procedural map on MonkeyCode Test Server.
Activity
What is the rank of MonkeyCode Test Server?
For the last seven days, MonkeyCode Test Server holds rank #15,481 on player hours, in the top – of all ranked servers.
What is the population on MonkeyCode Test Server?
At present, MonkeyCode Test Server is offline; the last sighting was 24 days 4 hours ago.
Wipe Cycle
How often does MonkeyCode Test Server wipe?
There are too few wipes on record for MonkeyCode Test Server to reveal its rhythm. At the monthly force wipe, every Rust server wipes. That happens next on Thursday 5 November at 19:00 UTC. 40 days 12 hours ago the current world was created.
Server Overview
Where can MonkeyCode Test Server be found?
No region is published by MonkeyCode Test Server. Where a server says it is, Rust Analytics shows; where the machine stands, it does not look up. 212.107.28.50:28015 is its address.
MonkeyCode Test Server is on which Rust version?
Rust network protocol 2633 and build 162929 on Linux is what MonkeyCode Test Server runs. Joining requires the same protocol on your game, which Steam updates.
Is MonkeyCode Test Server up, and how consistent is its uptime?
MonkeyCode Test Server is down. The last time we saw it was 24 days 4 hours ago. 7 full days have passed with 0% uptime, 0 of 168 hours. 20 September 2026 is when Rust Analytics first saw it.
Tags & Filters
How should you interpret the tags on MonkeyCode Test Server?
The game's server browser reads gmrust (Game mode): Survival in the standard Rust format; mp10 (Max players): Slot count: 10; ts8 (Group limit): Team size stays at the game default of 8; v2633 (Protocol): Your game must run protocol 2633 to connect; cs162929 (Build): Game build: 162929; ptrak (Networking): RakNet, the network layer the game ships with; $r? (Region code): No region code has been set; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The Modded listing applies: plugins or settings change play, which MonkeyCode Test Server publishes. Also in the tags and at the top of this page: current players, queue and world creation time.
On Rust Analytics, which lists and filters feature MonkeyCode Test Server?
On Rust Analytics, MonkeyCode Test Server matches these lists: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Connection
What is the process to join MonkeyCode Test Server?
The console route: start Rust, press F1, enter client.connect 212.107.28.50:28015. The page's Launch Rust button opens Rust through Steam and connects you instead.
Server tags
what each one meansPublished as mp10,ptrak,$r?,v2633,gmrust,cs162929,ts8,^o^z
Game
gmrust
mp10
ts8
v2633
cs162929
ptrak
$r?
Mods and access
^o
^z
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.