RUST METRICSFlight deck · live data
Data live Servers11,704 Players60,571 Populated3,281 Fresh wipes 3 h172 Scan5 min
‹ All servers103.156.242.197:28015
Offline Full Queue Fresh wipe Wipe due No query

MonkeyCode Test Server

Offline 103.156.242.197:28015 checked 42d 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,502no 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 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

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 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 23 hours ago.

Tag meanings

How should you read the tags on MonkeyCode Test Server?

Check: tags. The game's server browser reads 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): The server runs game 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): Plugins or settings make this a modded server from MonkeyCode Test Server. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

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

Rust Metrics lists featuring 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.

Player count

Where does MonkeyCode Test Server sit in the rankings?

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

What player count does MonkeyCode Test Server carry?

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

Operator and location

Where does MonkeyCode Test Server sit?

No region comes from MonkeyCode Test Server. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 103.156.242.197: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.

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 42 days 17 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 17 September 2026.

Settings and map

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

Reading the name gives no gather rate for MonkeyCode Test Server. 8 players per group, the default value. Mode check gives survival; gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.

Which map is live on MonkeyCode Test Server?

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

How to join

What do you do to join MonkeyCode Test Server?

Press F1 in Rust and enter client.connect 103.156.242.197:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

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 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 The server runs game 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 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.