Station XX-15330 · no signal
<SERVER_NAME>
Offline 24.171.68.3:28015 checked 10d ago
- Players now
- 0/ ?
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,330
- top 70%
- Last wipe
- 26d ago
- no schedule published
- Next wipe
- 8d 8h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of ? 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
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 8d 8h. The force wipe · high confidence
- wipe-day peak
- 0players, last three wipes
Coming wipes
- 8d 8hThu 5 Nov, 19:00 UTCFW
- 36d 8hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 1 Oct, 23:20 UTC FW26d ago | M0.0■steady | 0 | – | running | 0 |
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 map is running on <SERVER_NAME>?
A procedural map runs on <SERVER_NAME>, generated by the game.
Which settings and rules apply on <SERVER_NAME>?
The name of <SERVER_NAME> gives no gather rate. Groups hold up to 8 players, which is the default for the game. In survival mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. VAC, Valve's anti-cheat, is switched on.
Population
What is the current population on <SERVER_NAME>?
<SERVER_NAME> is not responding at this moment and is offline, last seen 10 days 10 hours ago.
How does <SERVER_NAME> rank against other Rust servers?
Over the last seven days, <SERVER_NAME> recorded enough player hours to reach #15,330 worldwide, placing it in the top 70% of all ranked servers.
Operator and location
How reliably does <SERVER_NAME> stay online?
<SERVER_NAME> is down at the moment; the last recorded contact was 10 days 10 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. Its earliest appearance in the records of Rust Server Trends dates to 13 September 2026.
Where in the world is <SERVER_NAME> hosted?
Nothing about a region comes from <SERVER_NAME>. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 24.171.68.3:28015 is the address it uses.
Which Rust version is <SERVER_NAME> running?
On Linux, <SERVER_NAME> runs Rust network protocol 2634 and build 167781. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe pattern
What does wipe day look like on <SERVER_NAME>?
On average, the busiest point of its recent wipes drew 0 players. 0 hours after the latest wipe, the crowd peaked.
How often does <SERVER_NAME> wipe, and on which days?
Once a month <SERVER_NAME> wipes, at the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. 26 days 11 hours is how long the current world has been running.
Server tags
What do the server tags on <SERVER_NAME> mean?
These are the tags <SERVER_NAME> publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp0 (Max players): 0 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set. 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 <SERVER_NAME> appear?
You will find <SERVER_NAME> on the following Rust Server Trends lists: Rust community servers without the side modes. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How to join
What steps get you onto <SERVER_NAME>?
To join, enter client.connect 24.171.68.3: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.