RUST METRICSFlight deck · live data
Data live Servers11,645 Players42,938 Populated3,029 Fresh wipes 3 h91 Scan5 min
‹ All servers211.106.63.210:28015
Online Full Queue Fresh wipe Wipe due No query

Rust TestServer

Online 211.106.63.210:28015 checked 11m ago

oxide
COM 1 · connect

Server instruments

last reading Thu 06:00 UTC
0 12 25 38 50 PAX 2 /50

Players now

4% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 109 SERVER FPS

Server fps

48 h low 60 · below 20 is lag, below 10 is bad
0 100 200 300 400 ENT 187,889 ×1000

Entities

48 h range 172,178–188,809 · memory 3,866 MB
1239 ET SINCE RESTART 07:05

Uptime

7 h 5 min since its last restart, at the last reading
7-day average0peak 2
Rank#7,290top 33%
Last wipe9h agono schedule published
Next wipe–too few wipes seen yet
Memory3,866MB48 h peak 2 players
REC 1

Players

AveragePeakWipe
00.511.5209:0018:0003:0011:0021:0006:00Wiped Wed 28 Oct, 22:59 UTCWIPE

Hourly average and peak, UTC.

REC 2

Server performance

Server fpsWipe
05010015020009:0018:0003:0011:0021:0006:00Wiped Wed 28 Oct, 22:59 UTCWIPE

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, measured since 14 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k14 Oct17 Oct20 Oct23 Oct26 Oct29 Oct

Top 33% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

too few wipes seen yet

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
Wed 28 Oct, 22:59 UTC9h ago – – running 1

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 Rust TestServer follow?

The rhythm of Rust TestServer'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. 9 hours ago the current world was made.

Lists and filters

How should you read the tags on Rust TestServer?

Tags published by Rust TestServer, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Match the game version: protocol 2635 is required; cs167781 (Build): Game build reading: 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Rust TestServer appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Rust TestServer: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and Plugins, not modded; Server tag: Oxide ^o; Group limit: 5 or more; Last wipe: In the last 24 hours.

Player count

What position does Rust TestServer hold among Rust servers?

Player hours over seven days put Rust TestServer at #7,290, in the top 33% of all ranked servers.

What is the population on Rust TestServer?

Current headcount on Rust TestServer: 2 players, 50 slots available. Check: players over seven days. Average 0, peak 2. The last 48 hours peaked at 02:00 UTC, averaging 2 players at that hour.

Operator and location

Where does Rust TestServer sit?

No region comes from Rust TestServer. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 211.106.63.210:28015.

What Rust version is Rust TestServer on?

Reading: Rust TestServer, Rust network protocol 2635 and build 167781, Windows. To get in, your game needs the same protocol; Steam applies the update.

Is performance on Rust TestServer within range?

Check: fps. Average 101 server fps over the last 48 hours, low of 60. Within range. Check: entities. The peak was 188,809, counting buildings, deployables and the rest of the world. Reading: 8,408 MB of memory at the highest. Expect lag when fps falls and entities climb.

What is the uptime on Rust TestServer, and is it online?

Rust TestServer reports online. Status: normal. Check: restart. The uptime it reports puts the last restart about 7 hours ago. Uptime for the last 7 full days: 167 of 168 hours, or 99%. Reading: first seen 14 October 2026, recorded by Rust Metrics.

Map and rules

How is Rust TestServer configured, and what rules are in force?

Check: gather rate. The name Rust TestServer does not state one. The group cap is 8 players, which is the default in the game. survival, standard play of gathering, building and raiding — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on Rust TestServer?

From seed 856364890, the game generates the procedural map on Rust TestServer. Its size is 4,250. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

Join

How do you connect to Rust TestServer?

Check: join. Open Rust, press F1, then enter client.connect 211.106.63.210:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,gmrust,cs167781,ts8,^o

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players The server holds 50 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Match the game version: protocol 2635 is required.
cs167781
Build Game build reading: 167781.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.

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.