RUST METRICSFlight deck · live data
Data live Servers11,869 Players103,347 Populated3,962 Fresh wipes 3 h552 Scan5 min
‹ All servers81.200.11.214:28015
Offline Full Queue Fresh wipe Wipe due No query

TEST

Offline 81.200.11.214:28015 checked 39d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 1 /10

Players now

10% 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#13,307no region published
Last wipe39d 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

Reset cycle

What wipe timing does TEST follow?

Its rhythm cannot be told from the wipes of TEST on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 39 days 21 hours ago the current world was made.

Lists and filters

How should you read the tags on TEST?

Check: tags. The game's server browser reads 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; cs164530 (Build): Build 164530; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game from TEST. 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 TEST?

These Rust Metrics lists carry TEST: 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

What position does TEST hold among Rust servers?

Ranking for TEST: #13,307 on seven-day player hours, top – of all ranked servers.

How full does TEST get?

TEST is not responding; status offline, last seen 39 days 5 hours ago.

Server details

What location is TEST hosted in?

No region tag on TEST. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 81.200.11.214:28015.

What Rust version is TEST on?

Version check: Rust network protocol 2633 and build 164530 on Windows, run by TEST. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is TEST, and is it online now?

Reading: offline. TEST last answered 39 days 5 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 19 September 2026, recorded by Rust Metrics.

Settings and map

How is TEST configured, and what rules are in force?

Reading the name gives no gather rate for TEST. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: standard play of gathering, building and raiding. 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 TEST on?

Procedural map on TEST, made by the game's generator.

How to join

How do you connect to TEST?

Check: join. Open Rust, press F1, then enter client.connect 81.200.11.214: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,cs164530,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.
cs164530
Build Build 164530.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Check: category. Modded, because plugins or settings alter the 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.