RUST METRICSFlight deck · live data
Data live Servers11,830 Players85,544 Populated3,690 Fresh wipes 3 h401 Scan5 min
‹ All servers177.188.250.135:28015
Offline Full Queue Fresh wipe Wipe due No query

Test Server

Offline 177.188.250.135:28015 checked 27d ago

COM 1 · connect

Server instruments

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

Players now

no slots published 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#14,559top 63%
Last wipe27d agono schedule published
Next wipe–no rhythm it keeps
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
15k10k15k20k25 Sep28 Sep1 Oct3 Oct6 Oct9 Oct

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

PLAN

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap3.6 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Fri 2 OctWed 30 SepFri 25 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 07:38 UTC27d ago 1 – running 0
Wed 30 Sep, 02:43 UTC29d ago 0 – 2.2 days 1
Fri 25 Sep, 01:50 UTC34d ago 1 held half 5 days 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 timing

What happens on Test Server when wipe day comes?

At their busiest, its recent wipes drew 1 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.

What wipe timing does Test Server follow?

No next wipe can be predicted for Test Server, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 27 days 23 hours ago.

Tag meanings

Which tags does Test Server carry, and what do they mean?

These are the tags Test Server publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp0 (Max players): Slots: 0; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166586 (Build): Game build reading: 166586; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Test Server appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Test Server: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Occupancy

Where does Test Server sit in the rankings?

Ranking for Test Server: #14,559 on seven-day player hours, top 63% of all ranked servers.

How full does Test Server get?

Status for Test Server: offline. Last seen 27 days 13 hours ago.

Server details

Where does Test Server sit?

Reading: location. Test Server gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 177.188.250.135:28015.

What Rust version is Test Server on?

Rust network protocol 2634 and build 166586 on Windows is the build Test Server runs. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is Test Server, and is it online now?

Reading: offline. Test Server last answered 27 days 13 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 25 September 2026.

Rules and settings

What settings and rules apply on Test Server?

Reading the name gives no gather rate for Test Server. 8 players per group, the default value. The mode is survival. Note the following: standard play of gathering, building and raiding. Combat and raiding against other players are on. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.

Connection

What do you do to join Test Server?

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

PLACARDS

Server tags

what each one means

Published as mp0,ptrak,$r?,v2634,gmrust,cs166586,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp0
Max players Slots: 0.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166586
Build Game build reading: 166586.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.