RUST METRICSFlight deck · live data
Data live Servers11,626 Players40,285 Populated2,838 Fresh wipes 3 h132 Scan5 min
‹ All servers119.228.206.30:28015
Offline Full Queue Fresh wipe Wipe due No query

TestServer

Offline 119.228.206.30:28015 checked 26d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 1 /1

Players now

100% 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,909top 61%
Last wipe28d 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
15k10k15k20k2 Oct4 Oct5 Oct7 Oct8 Oct10 Oct

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

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

When does TestServer wipe?

Its rhythm cannot be told from the wipes of TestServer 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. The world it runs now was made 28 days 6 hours ago.

Lists and filters

Which tags does TestServer carry, and what do they mean?

These are the tags TestServer publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): Slots: 1; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166494 (Build): The server runs game build 166494; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does TestServer appear in Rust Metrics lists and filters?

Rust Metrics lists featuring TestServer: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Occupancy

What position does TestServer hold among Rust servers?

Player hours over seven days put TestServer at #13,909, in the top 61% of all ranked servers.

How full does TestServer get?

TestServer is not responding; status offline, last seen 26 days 14 hours ago.

Server

Where does TestServer sit?

Reading: location. TestServer gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 119.228.206.30:28015.

What Rust version is TestServer on?

Reading: TestServer, Rust network protocol 2634 and build 166494, Windows. Check: protocol. To join, your game must match; Steam handles the update.

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

TestServer reports offline. The last reading came 26 days 14 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 2 October 2026.

Settings and map

What rules does TestServer enforce, and what are its settings?

Check: gather rate. The name TestServer does not state one. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on TestServer?

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

Join

How do you connect to TestServer?

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

PLACARDS

Server tags

what each one means

Published as mp1,ptrak,$r?,v2634,gmrust,cs166494,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1
Max players Slots: 1.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166494
Build The server runs game build 166494.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

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.