RUST METRICSFlight deck · live data
Data live Servers11,722 Players61,093 Populated3,368 Fresh wipes 3 h184 Scan5 min
‹ All servers212.107.28.57:28015
Offline Full Queue Fresh wipe Wipe due No query

MonkeyCode Test Server

Offline 212.107.28.57:28015 checked 39d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,391no region published
Last wipe55d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep21 Sep22 Sep24 Sep25 Sep26 Sep
PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

How often does MonkeyCode Test Server wipe, and when?

The rhythm of MonkeyCode Test Server's wipes cannot be told yet: too few 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 it runs now was made 55 days 9 hours ago.

Lists and filters

How should you read the tags on MonkeyCode Test Server?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs162929 (Build): Game build reading: 162929; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Modded: plugins or settings depart from the stock game from MonkeyCode Test Server. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does MonkeyCode Test Server appear in Rust Metrics lists and filters?

These Rust Metrics lists carry MonkeyCode Test Server: 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.

Population

Where does MonkeyCode Test Server sit in the rankings?

Player hours over seven days put MonkeyCode Test Server at #15,391, in the top – of all ranked servers.

What is the population on MonkeyCode Test Server?

MonkeyCode Test Server is not responding; status offline, last seen 39 days 16 hours ago.

Operator and location

What location is MonkeyCode Test Server hosted in?

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.57:28015.

What Rust version is MonkeyCode Test Server on?

Rust network protocol 2633 and build 162929 on Linux is the build MonkeyCode Test Server runs. 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 39 days 16 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 16 September 2026, recorded by Rust Metrics.

Settings and map

How is MonkeyCode Test Server configured, and what rules are in force?

Check: gather rate. The name MonkeyCode Test Server does not state one. 8 players per group, the default value. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. The server browser lists it as Modded, where plugins or settings change how the game plays. Oxide plugins are running. Anti-cheat reading: VAC on, Valve's system.

What map is MonkeyCode Test Server on?

Check: map. Procedural, generated by the game, on MonkeyCode Test Server.

Connection

What do you do to join MonkeyCode Test Server?

Check: join. Open Rust, press F1, then enter client.connect 212.107.28.57:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2633,gmrust,cs162929,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players The server holds 10 slots.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Match the game version: protocol 2633 is required.
cs162929
Build Game build reading: 162929.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Modded: plugins or settings depart from the stock game.

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.