Station XX-11848 · no signal
TestServer
Offline 124.170.92.249:28015 checked 5d ago
- Players now
- 1/ 10
- 10% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 1
- peak 1
- Rank
- #11,848
- top 54%
- Last wipe
- 5d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 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 54% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
- usual gap
- 8.3 daysbetween real wipes
- on rhythm
- 0%of its recent 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 |
|---|---|---|---|---|---|---|
| Fri 23 Oct, 03:20 UTC5d ago | M0.0■steady | 1 | – | running | 1 | |
| Sun 18 Oct, 12:50 UTC10d ago | M0.0▲rising | 1 | – | 4.6 days | 0 | |
| Tue 6 Oct, 13:06 UTC22d ago | M0.0■steady | 1 | – | 12 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 pageServer rules
Which settings and rules apply on TestServer?
The name of TestServer gives no gather rate. Up to 32 players can be in a group. In survival mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Oxide. Anti-cheat is on: VAC, from Valve.
Player counts
How many players are recorded on TestServer right now?
A reading taken now finds TestServer offline; the most recent activity was 5 days 15 hours ago. The seven-day average is 1 players, with a peak of 1.
How does TestServer rank against other Rust servers?
Over the last seven days, TestServer recorded enough player hours to reach #11,848 worldwide, placing it in the top 54% of all ranked servers.
Operator and location
How reliably does TestServer stay online?
TestServer is down at the moment; the last recorded contact was 5 days 15 hours ago. It was up 2% of the time across the last 7 full days: 3 of 168 hours. 6 October 2026 is when Rust Server Trends first recorded it.
Where in the world is TestServer hosted?
A region is not published by TestServer. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 124.170.92.249:28015 is the address it uses.
What build of Rust does TestServer use?
Rust network protocol 2635 and build 168909 on Windows is what TestServer runs. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe schedule
What does wipe day look like on TestServer?
The recent wipes averaged a busiest count of 1 players. 1 hours into the latest wipe, the crowd reached its peak.
How often does TestServer wipe, and on which days?
There is no next wipe to predict at TestServer, since its wipes fall at irregular times. 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 5 days 16 hours.
Lists and tags
What do the server tags on TestServer mean?
The game's server browser reads the tags TestServer publishes: gmrust (Game mode): You'll find standard Rust survival here; mp10 (Max players): 10 slots are available; ts32 (Group limit): Each team can hold up to 32; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): Game build: 168909; 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; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. 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 TestServer appear?
You will find TestServer on the following Rust Server Trends lists: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Connecting
What steps get you onto TestServer?
Enter client.connect 124.170.92.249:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust 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.