RUST METRICSFlight deck · live data
Data live Servers11,690 Players52,970 Populated3,210 Fresh wipes 3 h138 Scan5 min
‹ All servers212.107.28.50:28015
Offline Full Queue Fresh wipe Wipe due No query

MonkeyCode Test Server

Offline 212.107.28.50:28015 checked 39d 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,481no 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 Sep23 Sep24 Sep26 Sep27 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

What wipe timing does MonkeyCode Test Server follow?

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

Tag meanings

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): 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): Protocol 2633: join only on the same game version; cs162929 (Build): The server runs game build 162929; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock 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?

Rust Metrics lists featuring MonkeyCode Test Server: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Occupancy

What position does MonkeyCode Test Server hold among Rust servers?

Player hours over seven days put MonkeyCode Test Server at #15,481, 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 39 days ago.

Server

What location is MonkeyCode Test Server hosted in?

No region comes from MonkeyCode Test Server. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 212.107.28.50: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 ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 20 September 2026.

Settings and map

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

Reading the name gives no gather rate for MonkeyCode Test Server. The group cap is 8 players, which is the default in the game. survival, gather, build and raid, as the game normally runs — 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. Oxide plugins are running. Anti-cheat reading: VAC on, Valve's system.

What map is MonkeyCode Test Server on?

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

Join

What do you do to join MonkeyCode Test Server?

To join: start Rust, press F1 and type client.connect 212.107.28.50: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 Default limit in force: 8 per team.
v2633
Protocol Protocol 2633: join only on the same game version.
cs162929
Build The server runs game build 162929.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^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.