RUST METRICSFlight deck · live data
Data live Servers11,847 Players92,510 Populated3,855 Fresh wipes 3 h385 Scan5 min
‹ All servers212.107.29.67:28015
Offline Full Queue Fresh wipe Wipe due No query

MonkeyCode Test Server

Offline 212.107.29.67:28015 checked 41d 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,398no 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 Sep23 Sep24 Sep25 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

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. 55 days 14 hours ago the current world was made.

Tags

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): The game mode is plain Rust survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Match the game version: protocol 2633 is required; cs162929 (Build): The server runs game build 162929; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Plugins or settings make this a modded 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?

On Rust Metrics, MonkeyCode Test Server sits in these lists: 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?

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

How full does MonkeyCode Test Server get?

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

Server

Which location does MonkeyCode Test Server run from?

Reading: location. MonkeyCode Test Server gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 212.107.29.67:28015.

What Rust version is MonkeyCode Test Server on?

Reading: MonkeyCode Test Server, Rust network protocol 2633 and build 162929, Linux. Check: protocol. To join, your game must match; Steam handles the update.

Is MonkeyCode Test Server up, and how often does it stay up?

Reading: offline. MonkeyCode Test Server last answered 41 days 2 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 17 September 2026, recorded by Rust Metrics.

Settings and map

What rules does MonkeyCode Test Server enforce, and what are its settings?

Check: gather rate. The name MonkeyCode Test Server does not state one. The group cap is 8 players, which is the default in the game. survival, the normal game: build, gather, raid — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Oxide of them. Anti-cheat reading: VAC on, Valve's system.

What map is MonkeyCode Test Server on?

The game generates a procedural map for MonkeyCode Test Server.

Join

How do you connect to MonkeyCode Test Server?

To join: start Rust, press F1 and type client.connect 212.107.29.67: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 The game mode is plain Rust survival.
mp10
Max players The server holds 10 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Match the game version: protocol 2633 is required.
cs162929
Build The server runs game build 162929.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Plugins or settings make this a modded server.

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.