RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h7 Scan5 min
‹ All servers45.62.172.83:28015
Offline Full Queue Fresh wipe Wipe due No query

MonkeyCode Test Server

Offline 45.62.172.83:28015 checked 38d 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,467no 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 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

How often does MonkeyCode Test Server wipe, and when?

Its rhythm cannot be told from the wipes of MonkeyCode Test Server on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 54 days 18 hours ago the current world was made.

Tag meanings

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): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; 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): Game build reading: 162929; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^o (Oxide): It runs Oxide, also known as 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.

Which lists and filters on Rust Metrics show MonkeyCode Test Server?

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

Population

Where does MonkeyCode Test Server sit in the rankings?

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

How full does MonkeyCode Test Server get?

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

Server

Which location does MonkeyCode Test Server run from?

No region comes from MonkeyCode Test Server. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 45.62.172.83: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. Check: protocol. To join, your game must match; Steam handles the update.

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

Check: connection. MonkeyCode Test Server is offline at this moment. Last contact was 38 days 11 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.

Rules and settings

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

No gather rate appears in the name: MonkeyCode Test Server. No limit is set beyond the default. Groups take up to 8 players. survival, the normal game: build, gather, raid — that is the game mode. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Oxide of them. VAC is on. That is Valve's anti-cheat.

What map is MonkeyCode Test Server on?

The game generates a procedural map for MonkeyCode Test Server.

Connection

How do you connect to MonkeyCode Test Server?

Check: join. Open Rust, press F1, then enter client.connect 45.62.172.83:28015. Alternatively, use Launch Rust on this page: Steam opens Rust 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 10 slots in total.
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 Game build reading: 162929.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide It runs Oxide, also known as 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.