Station XX-14455 · no signal
Test Server
Offline 5.3.229.55:28015 checked 36d ago
- Players now
- 1/ 50
- 2% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #14,455
- top 63%
- Last wipe
- 36d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 50 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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.
Rank
daily · 1 is bestTop 63% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 0.7 daysbetween real wipes
- wipe-day peak
- 1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Mon 21 Sep, 20:58 UTC36d ago | M0.0▲rising | 1 | – | running | 0 | |
| Mon 21 Sep, 05:19 UTC37d ago | M0.0■steady | 1 | – | 0.7 days | 1 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageMap and rules
Which settings and rules apply on Test Server?
You will find no gather rate in the name of Test Server. The group limit is 8 players, the game's default. It plays in survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Carbon. VAC, Valve's anti-cheat, is switched on.
Live population
How many players are recorded on Test Server right now?
No players are recorded on Test Server at this moment; it is offline, and the last sighting was 36 days 9 hours ago.
How does Test Server rank against other Rust servers?
Over the last seven days, Test Server recorded enough player hours to reach #14,455 worldwide, placing it in the top 63% of all ranked servers.
Server details
How reliably does Test Server stay online?
As recorded now, Test Server is not reachable, the last contact having been 36 days 9 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. 21 September 2026 is when Rust Server Trends first recorded it.
Which region does Test Server run from?
Nothing about a region comes from Test Server. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 5.3.229.55:28015 is the address it uses.
Which Rust version is Test Server running?
Rust network protocol 2633 and build 164530 on Windows is what Test Server runs. The protocol must match for you to join, and Steam takes care of updating it.
Wipe day
What does wipe day look like on Test Server?
On average, the busiest point of its recent wipes drew 1 players. The peak on the most recent wipe came 1 hours after the wipe.
How often does Test Server wipe, and on which days?
Too few wipes of Test Server are on record yet to show its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 36 days 9 hours is how long the current world has been running.
Tags
What do the server tags on Test Server mean?
These are the tags Test Server publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp50 (Max players): 50 slots are available; ts8 (Group limit): Teams max out at 8, the default set by the game; v2633 (Protocol): Your game needs to be on protocol 2633 to join; cs164530 (Build): Game build: 164530; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): Carbon is the plugin framework running here. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does Test Server appear?
These Rust Server Trends lists include Test Server: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Connecting
How do you connect to Test Server?
To join, enter client.connect 5.3.229.55:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.