Rust Player Stats
Live UTC 50,302 playing

Online 103.236.54.209:28015 checked 12m ago

TestServer

Players now0
Slots1000
Full0%
7-day average0peak –
Rank#15,335top 69%
Last wipe14d agono schedule published
Next wipe–no rhythm it keeps
Launch Rust and join

By the numbersMatch stats

against its 1,000 slots
Players now0
0% of the slots taken
7-day average0
players on an average hour this week
7-day peak–
the fullest it got this week
48-hour peak0
the busiest hour of the last two days
On the list46 of 48 hours
hours it answered in the last two days
Server fps242
average over 48 hours; 60 or more is smooth
Standingtop 69%
of all ranked servers, on player hours over seven days
Replay

The story of the match

Players, performance and rank, hour by hour and day by day.

CrowdPlayers

AveragePeak
0123410:0019:0004:0013:0023:0008:00

Hourly average and peak, UTC.

FitnessServer performance

010020030040010:0019:0004:0013:0023:0008: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 14 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

FormRank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep11 Oct15 Oct20 Oct24 Oct29 Oct

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

FixturesWipe 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.5 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Fri 16 OctWed 14 OctSun 11 Oct
01234+0h+9h+19h+28h+38h+47h

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

ResultsWipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 16 Oct, 08:36 UTC13d ago 0 – running 0
Wed 14 Oct, 19:15 UTC14d ago 0 – 1.6 days 0
Sun 11 Oct, 08:18 UTC18d ago 0 – 3.5 days 0
Wed 16 Sep, 19:41 UTC42d ago 0 – 24.5 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.

Other matches on now

Similar servers

The same kind of game, then region, group limit, rate and wipes.

The pundits

Quick answers

From the figures on this page.

Server details

Is TestServer online, and how reliable is it?

Online now, TestServer is up. Going by the uptime it reports, the last restart came about 14 days 12 hours ago. 99% of the time over the last 7 full days, which is 167 of 168 hours up. On 14 September 2026, Rust Player Stats saw it for the first time.

Does TestServer run smoothly?

Averaging 242 server fps across the last 48 hours, it held a floor of 224. Up to 22,207 entities sat in the world, buildings and deployables included. 2,936 MB of memory was the high point. Lag, to a player, is these two together: low fps and a rising entity count.

Which Rust version is TestServer on?

Rust network protocol 2633 and build 163794 on Linux: that is the setup at TestServer. Same protocol or no entry: your game must match, and Steam keeps it updated for you.

Where is TestServer located?

No region is published by TestServer. Rust Player Stats takes the server's word on where it is and does not look up the machine's real location. You will find it at 103.236.54.209:28015.

Server tags

What do the server tags on TestServer mean?

gmrust (Game mode): The standard Rust survival rules apply here; mp1000 (Max players): The cap is 1,000 slots; ts8 (Group limit): Teams cap at 8, the game default; v2633 (Protocol): To join, your game has to run protocol 2633; cs163794 (Build): The game build here is 163794; ptrak (Networking): RakNet handles the network here, the game's standard layer; $r? (Region code): There's no region code on this one are the tags TestServer publishes, and the game's server browser reads them. The tags carry more besides: present players, queue length and when the world was made, all displayed at the top of this page.

Which Rust Player Stats lists and filters include TestServer?

These Rust Player Stats lists take TestServer: Community servers, ranked live. Searching the server list with these filters returns it: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Map and rules

Which map is running on TestServer?

TestServer runs a game-generated procedural map: size 2,300, seed 12345. The map repeats with that size and seed, and you can view it on RustMaps from here.

What are the rules and settings on TestServer?

No gather rate appears in the name of TestServer. The cap is 8 players per group, the game's default. It plays as survival, gather, build, raid: the standard game. You can fight and raid other players here. The server browser lists it under Community. Anti-cheat is on: VAC.

Player counts

What is the population on TestServer at the moment?

0 of 1,000 slots are filled on TestServer right now. Averaged out across the past week, the count is 0 players.

Where does TestServer sit in the rankings?

Player hours over seven days place TestServer at #15,335, among the top 69% of ranked servers.

Wipe days

What is the wipe schedule on TestServer?

No next wipe can be predicted for TestServer, because it wipes at irregular times. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. 14 days 14 hours ago is when its current world was made.

What does wipe day look like on TestServer?

At their busiest, its recent wipes drew 0 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

Joining the server

How do I join TestServer?

Console route: F1 in Rust, then client.connect 103.236.54.209:28015. Or use Launch Rust here, which opens Rust through Steam and connects you.

GlossaryServer tags

what each one means

Published as mp1000,ptrak,$r?,v2633,gmrust,cs163794,ts8

Game

gmrust
Game mode The standard Rust survival rules apply here.
mp1000
Max players The cap is 1,000 slots.
ts8
Group limit Teams cap at 8, the game default.
v2633
Protocol To join, your game has to run protocol 2633.
cs163794
Build The game build here is 163794.
ptrak
Networking RakNet handles the network here, the game's standard layer.
$r?
Region code There's no region code on this one.

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.