Station XX-13771 · no signal
Test
Offline 93.148.96.124:28015 checked 11d ago
- Players now
- 1/ 1
- 100% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #13,771
- top 64%
- Last wipe
- 11d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 1 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 64% 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
- 0.6 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 16 Oct, 08:17 UTC11d ago | M0.0▲rising | 1 | – | running | 0 | |
| Thu 15 Oct, 08:41 UTC12d ago | M0.0■steady | 1 | – | 1 days | 1 | |
| Wed 14 Oct, 14:29 UTC13d ago | M0.0▲rising | 1 | – | 0.8 days | 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 settings and rules apply on Test?
You will find no gather rate in the name of Test. At the game's default, groups can have up to 8 players. In survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. Listed as Modded in the server browser, it changes the game through plugins or settings. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.
Population
What is the current population on Test?
Test is not responding at this moment and is offline, last seen 11 days 21 hours ago.
How does Test rank against other Rust servers?
Over the last seven days, Test recorded enough player hours to reach #13,771 worldwide, placing it in the top 64% of all ranked servers.
Server facts
How reliably does Test stay online?
As recorded now, Test is not reachable, the last contact having been 11 days 21 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 28 September 2026.
Where in the world is Test hosted?
No region is published by Test. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 93.148.96.124:28015.
What build of Rust does Test use?
Rust network protocol 2634 and build 167781 on Windows is what Test runs. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe pattern
What does wipe day look like on Test?
1 players, on average, was the busiest crowd at its recent wipes. 1 hours after the latest wipe, the crowd peaked.
How often does Test wipe, and on which days?
There is no next wipe to predict at Test, since its wipes fall at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The present world dates from 11 days 21 hours.
Lists and tags
What do the server tags on Test mean?
The game's server browser reads the tags Test publishes: gmvanilla (Game mode): Survival in vanilla mode; mp1 (Max players): Slots: 1; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167781 (Build): It runs game build 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; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does Test appear?
The Rust Server Trends lists that take in Test are: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Join the server
What steps get you onto Test?
You can connect by pressing F1 in Rust and typing client.connect 93.148.96.124:28015 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.