Station XX-15478 · no signal
testserver
Offline 162.19.204.31:25745 checked 36d ago
- Players now
- 0/ 10
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,478
- top 70%
- 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
- 0of 10 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 70% 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.3 daysbetween real wipes
- wipe-day peak
- 4players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 4, 3 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Tue 22 Sep, 18:55 UTC36d ago | M0.5▲rising | 4 | – | running | 1 | |
| Tue 22 Sep, 10:58 UTC37d ago | M0.5▲rising | 4 | – | 0.3 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 pageRules and settings
Which map is running on testserver?
testserver uses a procedural map, which the game generates.
Which settings and rules apply on testserver?
No gather rate appears in the name of testserver. Up to 6 players can be in a group. survival is the game mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. The server browser lists it under Modded, where plugins or settings change the game. The plugins run on Carbon. The server has VAC on, Valve's anti-cheat.
Player counts
How many players are recorded on testserver right now?
testserver is not responding at this moment and is offline, last seen 36 days 2 hours ago.
How does testserver rank against other Rust servers?
The last seven days of player hours place testserver at #15,478, in the top 70% of all ranked servers.
Server facts
How reliably does testserver stay online?
As recorded now, testserver is not reachable, the last contact having been 36 days 2 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. On 21 September 2026 it was recorded for the first time by Rust Server Trends.
Which region does testserver run from?
Nothing about a region comes from testserver. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 162.19.204.31:25745.
Which Rust version is testserver running?
On Linux, testserver runs Rust network protocol 2633 and build 165217. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe day
What does wipe day look like on testserver?
The recent wipes averaged a busiest count of 4 players. The peak on the most recent wipe came 3 hours after the wipe.
How often does testserver wipe, and on which days?
On record so far are too few of testserver's wipes to tell its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 36 days 21 hours.
Server tags
What do the server tags on testserver mean?
These are the tags testserver publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp10 (Max players): The server has 10 slots; ts6 (Group limit): Each team can hold up to 6; v2633 (Protocol): Game protocol 2633: to join, your game must match this version; cs165217 (Build): Game build: 165217; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): No region code is set for this server; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): Carbon is the plugin framework running here. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does testserver appear?
You will find testserver on the following Rust Server Trends lists: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How to join
How do you connect to testserver?
You can connect by pressing F1 in Rust and typing client.connect 162.19.204.31:25745 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects 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.