Station XX-13604 · no signal
Test
Offline 188.19.102.77:28015 checked 19d ago
- Players now
- 1/ 200
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #13,604
- top 61%
- Last wipe
- 27d ago
- biweekly schedule
- Next wipe
- 7d 23h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 200 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 61% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Thursday 5 November, 19:00 UTC, in 7d 23h. The force wipe · high confidence
- usual gap
- 2.2 daysbetween real wipes
- wipe-day peak
- 1players, last three wipes
Coming wipes
- 7d 23hThu 5 Nov, 19:00 UTCFW
- 22d 1hThu 19 Nov, 20:52 UTC
- 35d 23hThu 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 1, 1 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 8 Oct, 20:52 UTC19d ago | M0.0▲rising | 1 | – | running | 0 | |
| Tue 6 Oct, 16:00 UTC22d ago | M0.0▲rising | 1 | – | 2.2 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 pageServer rules
Which settings and rules apply on Test?
No gather rate appears in the name of Test. 10 players is the most a group can hold. pve is the game mode, no player-versus-player fighting. The server browser lists it under Modded, where plugins or settings change the game. Its plugins are run through Oxide. VAC, Valve's anti-cheat, is switched on.
Live population
How many players are recorded on Test right now?
Test is not responding at this moment and is offline, last seen 19 days ago.
How does Test rank against other Rust servers?
Over the last seven days, Test recorded enough player hours to reach #13,604 worldwide, placing it in the top 61% of all ranked servers.
Server details
How reliably does Test stay online?
No contact with Test right now, and the last recorded contact was 19 days 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 6 October 2026.
Which region does Test run from?
Nothing about a region comes from Test. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 188.19.102.77:28015 is the address it uses.
Which Rust version is Test running?
Rust network protocol 2634 and build 167398 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?
On average, the busiest point of its recent wipes drew 1 players. 1 hours after the latest wipe, the crowd peaked.
How often does Test wipe, and on which days?
The prediction is taken from its tag, since Test has too few wipes on record to confirm the schedule. On Thursday 5 November at 19:00 UTC the force wipe arrives: that is its next wipe, and every Rust server wipes then. 27 days 1 hours is how long the current world has been running. Its tags state that it wipes every two weeks.
Server tags
What do the server tags on Test mean?
Tags published by Test and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp200 (Max players): Slots: 200; ts10 (Group limit): Teams are capped at 10 players; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs167398 (Build): The game build is 167398; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^b (Biweekly): A wipe comes every second week; ^p (PvE): There's no player combat; the world provides the threat; ^o (Oxide): A plugin framework, Oxide (uMod), runs 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 Test appear?
These Rust Server Trends lists include Test: Modded Rust servers, tracked live and Rust PvE servers. These filters bring it up on the server list: Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.
Join the server
How do you connect to Test?
You can connect by pressing F1 in Rust and typing client.connect 188.19.102.77: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.