RUST METRICSFlight deck · live data
Data live Servers11,699 Players65,959 Populated3,548 Fresh wipes 3 h117 Scan5 min
‹ All servers45.62.172.81:28015
Offline Full Queue Fresh wipe Wipe due No query

MonkeyCode Test Server

Offline 45.62.172.81: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,428no region published
Last wipe54d 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 timing

How often does MonkeyCode Test Server wipe, and when?

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

Tag meanings

Which tags does MonkeyCode Test Server carry, and what do they mean?

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

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.

Population

What position does MonkeyCode Test Server hold among Rust servers?

Ranking for MonkeyCode Test Server: #15,428 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 39 days 15 hours ago.

Operator and location

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

What Rust version is MonkeyCode Test Server on?

Version check: Rust network protocol 2633 and build 162929 on Linux, run by MonkeyCode Test Server. 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 39 days 15 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 18 September 2026.

Map and rules

What settings and rules apply on MonkeyCode Test Server?

Reading the name gives no gather rate for MonkeyCode Test Server. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.

What map is MonkeyCode Test Server on?

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

How to join

How do you connect to MonkeyCode Test Server?

Press F1 in Rust and enter client.connect 45.62.172.81: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 The game mode is plain Rust survival.
mp10
Max players 10 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Match the game version: protocol 2633 is required.
cs162929
Build Game build reading: 162929.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

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.