StatusLive Servers online11,830 Players75,280 Populated3,722 Wiped · 3 h228 Interval5 min Date29 OCT 2026

DWG RG-S15335Server sheetchecked 10m ago

Test Server

Online 216.245.177.46:28015 checked 10m ago

solo
Connect
Players now 0/ 30 0% full
7-day average0peak –
Rank#15,335top 69%
Last wipe23d agono schedule published
Next wipe–no rhythm it keeps
Fig. 1

Players

AveragePeak
0123415:0000:0009:0017:0003:0012:00

Hourly average and peak, UTC.

Fig. 1Players on Test Server
Fig. 2

Server performance

05010015020015:0000:0009:0017:0003:0012:00

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, measured since 17 Sep. 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
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 69% of all ranked servers, and #199 of the solo servers (top 90%). 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 gap10.7 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held50%else halves by day 2

The first 48 hours of its last wipes

Tue 6 OctThu 17 SepTue 15 Sep
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, 28 hours in.

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 6 Oct, 10:53 UTC23d ago 1 – running 0
Thu 17 Sep, 10:39 UTC42d ago 1 halved by day 2 19 days 0
Tue 15 Sep, 00:57 UTC44d ago 1 held half 2.4 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
Rustafied.com - EU SoloEU · solo · weekly · 120 on average
92 / 100
02
Rustafied.com - US SoloNA · solo · weekly · 104 on average
19 / 100
03
RustForNoobs.com | Mondays | SOLO ONLY | EUEU · solo · weekly · 54 on average
61 / 100
04
RustForNoobs.com | SOLO ONLY | Weekly | EUEU · solo · weekly · 48 on average
13 / 100
05
Lone Wolf Rust | Solo Only, Monthly, Vanilla, No BP WipesNA · solo · monthly · 35 on average
22 / 100
06 8 / 100
Ref.Similar
General notes

Quick answers

from the figures on this page

Server data

What uptime is recorded for Test Server, and is it up?

Test Server is up at this moment. Counted from its reported uptime, the last restart was about 13 hours ago. 167 of 168 hours up over the last 7 full days, which is 99% of the time. The first sighting of it by Rust Graphs was on 13 September 2026.

How does Test Server perform, as measured?

The last 48 hours give an average of 96 server fps and a floor of 76. Counted at its highest: 88,251 entities, buildings, deployables and the rest of the world included. 5,624 MB is the memory peak. What players feel as lag is low fps together with a climbing entity count.

What location is recorded for Test Server?

No region is published by Test Server. No lookup of the machine's location is done: Rust Graphs shows where a server says it is. You will find it at 216.245.177.46:28015.

On which Rust version is Test Server running?

Rust network protocol 2634 and build 166652 on Windows: that is what Test Server runs. The same protocol is required for joining, and Steam updates your game to it.

Counts

How many players are plotted on Test Server?

At the last refresh, Test Server recorded 0 players across 30 slots. Averaged across seven days, the player count is 0.

What rank has been recorded for Test Server?

Over the last seven days, Test Server records #15,335 for player hours: the top 69% of all ranked servers. Within the solo group it places #199.

Wipe data

What happens on Test Server on the day of a wipe?

An average of 1 players was recorded at the busiest point of its recent wipes. At 28 hours after the latest wipe the crowd was at its peak. Up to the next wipe, the crowd in 50% of its recent wipes stayed above half that peak. By day 2 the crowd had fallen below half on the wipes where it did not hold.

Which times and days are wipes plotted at on Test Server?

No next wipe can be predicted for Test Server: its wipes fall at irregular times. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when all Rust servers wipe. The world it runs now was made 23 days 3 hours ago.

Settings

Which settings does Test Server run, and what rules?

No gather rate is stated in the name of Test Server. Solo play only: teams are not allowed. It runs the survival game mode, the standard game: gather, build, raid. Fighting and raiding between players are enabled. The server browser lists it under Community. VAC is on: that is Valve's anti-cheat.

Which map has Test Server loaded?

Test Server runs a procedural map of size 4,000 with seed 3513435846, generated by the game. Size and seed fix the map, so this page links it on RustMaps for viewing.

Lists and filters

Where does Test Server appear among the Rust Graphs lists and filters?

On Rust Graphs, Test Server is placed in these lists: Rust community servers, plotted and Solo Rust servers: group limit 1. It is returned by these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: Solo.

On Test Server, what is meant by each tag?

gmrust (Game mode): Standard survival, as Rust plays; mp30 (Max players): Slots: 30; ts1 (Group limit): The team limit is 1; v2634 (Protocol): Your game must match protocol 2634 to join; cs166652 (Build): The game build is 166652; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is recorded are the tags Test Server publishes; the game's server browser reads them. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.

Connect

By what method do you join Test Server?

In Rust, press F1 and type client.connect 216.245.177.46:28015 in the console. Launch Rust on this page also works: Rust opens through Steam and connects you.

NotesAnswered from the figures
Key

Server tags

what each one means

Published as mp30,ptrak,$r?,v2634,gmrust,cs166652,ts1

Game

gmrust
Game mode Standard survival, as Rust plays.
mp30
Max players Slots: 30.
ts1
Group limit The team limit is 1.
v2634
Protocol Your game must match protocol 2634 to join.
cs166652
Build The game build is 166652.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code No region code is recorded.

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