StatusLive Servers online11,745 Players55,760 Populated3,187 Wiped · 3 h129 Interval5 min Date30 OCT 2026

DWG RG-S12162Server sheetchecked 9m ago

testing

Online 38.130.121.58:28055 checked 9m ago

Connect
Players now 0/ 10 0% full
7-day average0peak 1
Rank#12,162top 55%
Last wipe3h agono schedule published
Next wipe–no rhythm it keeps
Fig. 1

Players

AveragePeak
00.250.50.75102:0005:0008:0010:0021:0000:00

Hourly average and peak, UTC.

Fig. 1Players on testing
Fig. 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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k10 Oct14 Oct18 Oct22 Oct26 Oct30 Oct

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

Fig. 3Rank on player hours, daily
Schedule

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 gap9.6 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 2

The first 48 hours of its last wipes

Sun 11 OctSat 10 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 29 Oct, 21:35 UTC3h ago – – running 0
Sun 11 Oct, 12:33 UTC18d ago 1 halved by day 2 18.4 days 0
Sat 10 Oct, 15:45 UTC19d 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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 491 on average
72 / 250
02
Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average
106 / 200
03
Rusty Moose |EU Main|EU · groups of 12+ · weekly · 284 on average
335 / 350
04
Rustafied.com - EU FridayEU · groups of 16+ · weekly · 277 on average
20 / 100
05
Rustoria.co - EU MainEU · groups of 16+ · weekly · 266 on average
419 / 450
06
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 253 on average
304 / 325
Ref.Similar
General notes

Quick answers

from the figures on this page

Server details

What uptime is recorded for testing, and is it up?

Right now, testing is recorded as online. 73 of 168 hours up over the last 7 full days, which is 43% of the time. On 10 October 2026 is when Rust Graphs first saw it.

In which location is testing hosted?

A region is not published by testing. No lookup of the machine's location is done: Rust Graphs shows where a server says it is. You will find it at 38.130.121.58:28055.

On which Rust version is testing running?

On Windows, testing runs Rust network protocol 2636 and build 169702. Steam updates your game, which must be on the same protocol for you to join.

Population

How many players are plotted on testing?

0 of 10 slots on testing are taken at the latest refresh. The seven-day mean is 0 players; the peak over the same period is 1. The 48-hour peak falls at 21:00 UTC, averaging 1 players.

In the rankings, which position does testing hold?

Within the top 55% of all ranked servers: testing at #12,162 for player hours, seven days recorded.

Wipe times

On testing, what does the data show for wipe day?

The recent wipes averaged a busiest count of 1 players. At 0 hours after the latest wipe the crowd was at its peak. The crowd stayed above half the peak until the next wipe in 0% of its recent wipes. On the wipes where it did not hold, the crowd dropped below half by day 2.

On testing, when do wipes occur?

testing wipes at times that follow no pattern, so no next wipe can be predicted. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when all Rust servers wipe. The current world has been in use since 3 hours ago.

Settings

Which rules and settings are recorded for testing?

No gather rate is stated in the name of testing. No limit is published beyond the default: 8 players per group. survival, the standard game: gather, build, raid, is the game mode. PvP and raiding are on. It appears under Community in the server browser. VAC is on: that is Valve's anti-cheat.

What is the map for testing?

testing runs a procedural map, which the game generates.

Filters

On Rust Graphs, which lists and filters contain testing?

The Rust Graphs lists that carry testing are: Rust community servers, plotted. It is returned by these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 24 hours.

Which meaning is attached to each tag on testing?

gmvanilla (Game mode): The mode is vanilla survival; mp10 (Max players): 10 player slots; ts8 (Group limit): The team limit is 8, which is the game default; v2636 (Protocol): Your game must match protocol 2636 to join; cs169702 (Build): The game build is 169702; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The region code field is empty are the tags testing publishes; the game's server browser reads them. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.

Connect

How is testing joined?

Enter client.connect 38.130.121.58:28055 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you.

NotesAnswered from the figures
Key

Server tags

what each one means

Published as mp10,ptrak,$r?,v2636,gmvanilla,cs169702,ts8

Game

gmvanilla
Game mode The mode is vanilla survival.
mp10
Max players 10 player slots.
ts8
Group limit The team limit is 8, which is the game default.
v2636
Protocol Your game must match protocol 2636 to join.
cs169702
Build The game build is 169702.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code The region code 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.

KeyTag string decoded