RUST METRICSFlight deck · live data
Data live Servers11,644 Players43,541 Populated3,049 Fresh wipes 3 h97 Scan5 min
‹ All servers38.130.121.58:28055
Offline Full Queue Fresh wipe Wipe due No query

testing

Offline 38.130.121.58:28055 checked 19h ago

COM 1 · connect

Server instruments

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

Players now

0% full 7-day avg7-day peak
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 1
Rank#14,834top 67%
Last wipe17d agono schedule published
Next wipe–too few wipes seen yet
Memory–at the last reading
REC 1

Players

AveragePeak
0123409:0014:0020:0001:0007:0012:00

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
15k10k15k20k10 Oct14 Oct18 Oct21 Oct25 Oct29 Oct

Top 67% 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.

usual gap0.9 daysbetween real wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Sun 11 OctSat 10 Oct
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
Sun 11 Oct, 12:33 UTC17d ago 1 – running 0
Sat 10 Oct, 15:45 UTC18d ago 1 – 0.9 days 0

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 should you expect from wipe day on testing?

The busiest point of its recent wipes drew 1 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

When does testing wipe?

Its rhythm cannot be told from the wipes of testing 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 it runs now was made 17 days 19 hours ago.

Tags

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

These are the tags testing publishes, and the server browser reads them: gmvanilla (Game mode): The mode is vanilla survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show testing?

On Rust Metrics, testing sits in these lists: 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.

Player count

Where does testing sit in the rankings?

Ranking for testing: #14,834 on seven-day player hours, top 67% of all ranked servers.

What is the population on testing?

Status for testing: offline. Last seen 19 hours ago. Seven-day check: 0 players on average. Peak reading: 1.

Server details

What location is testing hosted in?

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

What Rust version is testing on?

Reading: testing, Rust network protocol 2635 and build 168909, Windows. Matching protocol is required to join. Let Steam update your game.

How reliable is testing, and is it online now?

Check: connection. testing is offline at this moment. Last contact was 19 hours ago. Reading: 42% uptime over the last 7 full days. It was up 70 of 168 hours. Reading: first seen 10 October 2026, recorded by Rust Metrics.

Settings and map

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

No gather rate appears in the name: testing. 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 testing on?

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

Connection

How do you connect to testing?

To join: start Rust, press F1 and type client.connect 38.130.121.58:28055. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2635,gmvanilla,cs168909,ts8

Game

gmvanilla
Game mode The mode is vanilla survival.
mp10
Max players 10 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none 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.