Station XX-10138 · no signal
Test
Offline 94.228.171.183:28015 checked 3d ago
- Players now
- 1/ 1
- 100% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 1
- peak 1
- Rank
- #10,138
- top 46%
- Last wipe
- 6d ago
- weekly schedule
- Next wipe
- 5h
- Thu 29 Oct, 12:38 UTC
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 46% of all ranked servers, and #452 of the trio servers (top 72%). Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Thursday 29 October, 12:38 UTC, in 5h. Its weekly schedule tag · low confidence
- wipe-day peak
- 1players, last three wipes
Coming wipes
- 5hThu 29 Oct, 12:38 UTC
- 7d 12hThu 5 Nov, 19:00 UTCFW
- 14d 5hThu 12 Nov, 12:38 UTC
- 21d 5hThu 19 Nov, 12:38 UTC
- 28d 5hThu 26 Nov, 12:38 UTC
- 35d 12hThu 3 Dec, 19:00 UTCFW
- 42d 5hThu 10 Dec, 12:38 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 22 Oct, 12:38 UTC6d ago | M0.0■steady | 1 | – | running | 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 map is running on Test?
Test uses a procedural map, which the game generates.
Which settings and rules apply on Test?
No gather rate appears in the name of Test. 3 players is the most a group can hold (trio). In survival mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. Plugins or settings alter the game here; the browser lists it as Modded. Oxide is the plugin framework it runs. Vanilla is the label it uses for itself: no changed rates, kits or rules: this is the game as Facepunch ships it. VAC, Valve's anti-cheat, is switched on.
Player counts
What is the current population on Test?
No players are recorded on Test at this moment; it is offline, and the last sighting was 3 days 19 hours ago. Averaged across the last seven days the population was 1 players, reaching a peak of 1.
How does Test rank against other Rust servers?
Over the last seven days, Test recorded enough player hours to reach #10,138 worldwide, placing it in the top 46% of all ranked servers. Within trio, it places #452.
Server facts
How reliably does Test stay online?
No contact with Test right now, and the last recorded contact was 3 days 19 hours ago. Of the 168 hours in the last 7 full days, it was up for 4, or 2% of the time. 14 October 2026 is when Rust Server Trends first recorded it.
Where in the world is Test hosted?
No region is published by Test. 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 94.228.171.183:28015.
What build of Rust does Test use?
On Windows, Test runs Rust network protocol 2635 and build 168909. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe schedule
What does wipe day look like on Test?
On average, the busiest point of its recent wipes drew 1 players. 0 hours into the latest wipe, the crowd reached its peak.
On what timetable does Test run its wipes?
The prediction follows its tag, because too few of Test's wipes are on record to confirm its schedule. The date of its next wipe is Thursday 29 October at 12:38 UTC. 6 days 18 hours is how long the current world has been running. A weekly wipe schedule is published in its tags.
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): You'll find standard Rust survival here; mp1 (Max players): Slots: 1; ts3 (Group limit): The team limit is 3; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): The game build is 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^w (Weekly): The server wipes every week; ^v (Vanilla): No changed rates, kits or rules: this is the game as Facepunch ships it; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it 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?
You will find Test on the following Rust Server Trends lists: Modded Rust servers, tracked live and Best trio Rust servers. These filters bring it up on the server list: Type: Vanilla and Modded; Server tag: Weekly ^w, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: Trio; Wipe schedule: Weekly; Last wipe: In the last week.
How to join
How do you connect to Test?
You can connect by pressing F1 in Rust and typing client.connect 94.228.171.183: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.