RUST METRICSFlight deck · live data
Data live Servers11,680 Players52,558 Populated3,201 Fresh wipes 3 h137 Scan5 min
‹ All servers149.202.227.169:28015
Offline Full Queue Fresh wipe Wipe due No query

TestServer

Offline 149.202.227.169:28015 checked 43d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.8 1.5 2.2 3 PAX 0 /3

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,464no region published
Last wipe55d 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 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 TestServer follow?

Its rhythm cannot be told from the wipes of TestServer on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 55 days 16 hours ago.

Tag meanings

How should you read the tags on TestServer?

Check: tags. The game's server browser reads gmvanilla (Game mode): Check: mode. Vanilla survival; mp3 (Max players): Slots: 3; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163794 (Build): Build 163794; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty from TestServer. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show TestServer?

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.

Population

What position does TestServer hold among Rust servers?

Player hours over seven days put TestServer at #15,464, in the top – of all ranked servers.

What player count does TestServer carry?

TestServer is not responding; status offline, last seen 43 days 13 hours ago.

Server details

What location is TestServer hosted in?

No region comes from TestServer. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 149.202.227.169:28015.

What Rust version is TestServer on?

Version check: Rust network protocol 2633 and build 163794 on Linux, run by TestServer. To get in, your game needs the same protocol; Steam applies the update.

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

Reading: offline. TestServer last answered 43 days 13 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.

Settings and map

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

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. Anti-cheat reading: VAC on, Valve's system.

What map is TestServer on?

Check: map. Procedural, generated by the game, on TestServer.

Join

What do you do to join TestServer?

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

PLACARDS

Server tags

what each one means

Published as mp3,ptrak,$r?,v2633,gmvanilla,cs163794,ts8

Game

gmvanilla
Game mode Check: mode. Vanilla survival.
mp3
Max players Slots: 3.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Match the game version: protocol 2633 is required.
cs163794
Build Build 163794.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

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.