RUST METRICSFlight deck · live data
Data live Servers11,685 Players51,425 Populated3,180 Fresh wipes 3 h127 Scan5 min
‹ All servers212.107.29.75:28015
Offline Full Queue Fresh wipe Wipe due No query

MonkeyCode Test Server

Offline 212.107.29.75:28015 checked 44d ago

moddedoxide
COM 1 · connect
Launch Rust and join

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,049no 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 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

Reset cycle

When does MonkeyCode Test Server wipe?

To tell the rhythm of MonkeyCode Test Server, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 55 days 8 hours ago.

Lists and filters

How should you read the tags on MonkeyCode Test Server?

These are the tags MonkeyCode Test Server publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Your game must run protocol 2633 to get in; cs162929 (Build): Build 162929; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. 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. Reading: server list filters. It comes up under 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,049 on seven-day player hours, top – of all ranked servers.

What player count does MonkeyCode Test Server carry?

Status for MonkeyCode Test Server: offline. Last seen 44 days 22 hours ago.

Server

Where does MonkeyCode Test Server sit?

Reading: location. MonkeyCode Test Server gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 212.107.29.75:28015.

What Rust version is MonkeyCode Test Server on?

Reading: MonkeyCode Test Server, Rust network protocol 2633 and build 162929, Linux. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on MonkeyCode Test Server, and is it online?

Check: connection. MonkeyCode Test Server is offline at this moment. Last contact was 44 days 22 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 13 September 2026.

Settings and map

What settings and rules apply on MonkeyCode Test Server?

No gather rate appears in the name: MonkeyCode Test Server. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Oxide plugins are running. VAC is on. That is Valve's anti-cheat.

What map is MonkeyCode Test Server on?

Procedural map on MonkeyCode Test Server, made by the game's generator.

Connection

How can you get onto MonkeyCode Test Server?

To join: start Rust, press F1 and type client.connect 212.107.29.75:28015. Or press Launch Rust here and Steam opens the game 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 Survival, as standard Rust plays it.
mp10
Max players The server holds 10 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Your game must run protocol 2633 to get in.
cs162929
Build Build 162929.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Check: category. Modded, because plugins or settings alter the 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.