MonkeyCode Test Server
Offline 212.107.28.58:28015 checked 42d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
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- 41/500
- 135/100
- 59/225
- 19/700
- 3/200
- 5/1000
Quick answers
from the figures on this pageReset cycle
How often does MonkeyCode Test Server wipe, and when?
To tell the rhythm of MonkeyCode Test Server, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 55 days 4 hours ago.
Lists and filters
Which tags does MonkeyCode Test Server carry, and what do they mean?
Tags published by MonkeyCode Test Server, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): Slots: 10; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Protocol 2633: join only on the same game version; cs162929 (Build): Build 162929; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Which lists and filters on Rust Metrics show MonkeyCode Test Server?
On Rust Metrics, MonkeyCode Test Server sits in these lists: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Occupancy
Where does MonkeyCode Test Server sit in the rankings?
Ranking for MonkeyCode Test Server: #15,502 on seven-day player hours, top – of all ranked servers.
How full does MonkeyCode Test Server get?
Status for MonkeyCode Test Server: offline. Last seen 42 days 12 hours ago.
Server
Where does MonkeyCode Test Server sit?
No region comes from MonkeyCode Test Server. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 212.107.28.58:28015.
What Rust version is MonkeyCode Test Server on?
Reading: MonkeyCode Test Server, Rust network protocol 2633 and build 162929, Linux. Matching protocol is required to join. Let Steam update your game.
What is the uptime on MonkeyCode Test Server, and is it online?
Reading: offline. MonkeyCode Test Server last answered 42 days 12 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 14 September 2026.
Rules and settings
How is MonkeyCode Test Server configured, and what rules are in force?
Reading the name gives no gather rate for MonkeyCode Test Server. No limit is set beyond the default. Groups take up to 8 players. survival, gather, build and raid, as the game normally runs — that is the game mode. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Oxide of them. Check: anti-cheat. VAC, Valve's system, is on.
What map is MonkeyCode Test Server on?
The game generates a procedural map for MonkeyCode Test Server.
How to join
How do you connect to MonkeyCode Test Server?
Press F1 in Rust and enter client.connect 212.107.28.58:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.