Station XX-15400 · no signal
TEST
Offline 104.28.228.110:28015 checked 2d ago
- Players now
- 0/ 10
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,400
- top 69%
- Last wipe
- 3d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 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 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 5.4 daysbetween real wipes
- wipe-day peak
- 0players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 20 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Sat 24 Oct, 13:51 UTC3d ago | M0.0■steady | 0 | – | – | running | 0 |
| Mon 19 Oct, 04:27 UTC9d ago | M0.0■steady | 1 | – | 5.4 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 pageMap and rules
Which map is running on TEST?
A procedural map runs on TEST, generated by the game.
Which settings and rules apply on TEST?
No gather rate appears in the name of TEST. The group limit is 8 players, the game's default. It plays in survival mode, the usual game of gathering, building and raiding. You can raid and fight other players here. Plugins or settings alter the game here; the browser lists it as Modded. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched off.
Population
What is the current population on TEST?
TEST is not responding at this moment and is offline, last seen 2 days 23 hours ago. The population averaged 0 players over the past week.
How does TEST rank against other Rust servers?
The last seven days of player hours place TEST at #15,400, in the top 69% of all ranked servers.
Server details
How reliably does TEST stay online?
As recorded now, TEST is not reachable, the last contact having been 2 days 23 hours ago. Of the 168 hours in the last 7 full days, it was up for 1, or 1% of the time. Its earliest appearance in the records of Rust Server Trends dates to 4 October 2026.
Where in the world is TEST hosted?
A region is not published by TEST. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 104.28.228.110:28015.
Which Rust version is TEST running?
TEST is running Rust network protocol 2635 and build 168909 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.
Wipe day
What does wipe day look like on TEST?
On average, the busiest point of its recent wipes drew 0 players. 20 hours into the latest wipe, the crowd reached its peak.
On what timetable does TEST run its wipes?
The rhythm of TEST cannot yet be told: too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. It has run its current world for 3 days 18 hours.
Lists and tags
What do the server tags on TEST mean?
These are the tags TEST publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp10 (Max players): 10 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): Game build: 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. 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 TEST appear?
The Rust Server Trends lists that take in TEST are: 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.
Join the server
What steps get you onto TEST?
Enter client.connect 104.28.228.110: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.