Station XX-10590 · no signal
MyServer (TEST)
Offline 138.16.248.206:28015 checked 2d ago
- Players now
- 1/ 100
- 1% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 1
- peak 1
- Rank
- #10,590
- top 48%
- Last wipe
- 2d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 100 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 48% 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
- 9.5 daysbetween real wipes
- wipe-day peak
- 1players, last three wipes
- crowd held
- 0%else halves by day 2
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 |
|---|---|---|---|---|---|---|
| Mon 26 Oct, 16:09 UTC2d ago | M0.0▲rising | 1 | – | running | 0 | |
| Sat 17 Oct, 04:52 UTC12d ago | M0.0▲rising | 1 | – | halved by day 2 | 9.5 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 MyServer (TEST)?
The name of MyServer (TEST) gives no gather rate. The group limit is 10 players. It plays in pve mode, no player-versus-player fighting. Listed as Modded in the server browser, it changes the game through plugins or settings. Oxide is the plugin framework it runs. Anti-cheat is off: VAC, from Valve.
Live population
How many players are recorded on MyServer (TEST) right now?
No players are recorded on MyServer (TEST) at this moment; it is offline, and the last sighting was 2 days 14 hours ago. The seven-day average is 1 players, with a peak of 1.
How does MyServer (TEST) rank against other Rust servers?
On player hours for the past week, MyServer (TEST) sits at #10,590, which puts it inside the top 48% of every ranked server.
Operator and location
How reliably does MyServer (TEST) stay online?
MyServer (TEST) is down at the moment; the last recorded contact was 2 days 14 hours ago. Of the 168 hours in the last 7 full days, it was up for 3, or 2% of the time. 15 October 2026 is when Rust Server Trends first recorded it.
Which region does MyServer (TEST) run from?
Nothing about a region comes from MyServer (TEST). Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 138.16.248.206:28015.
What build of Rust does MyServer (TEST) use?
Rust network protocol 2635 and build 168909 on Windows is what MyServer (TEST) runs. 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 MyServer (TEST)?
On average, the busiest point of its recent wipes drew 1 players. 1 hours after the latest wipe, the crowd peaked. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. By day 2 it fell below half in the wipes where it didn't hold.
On what timetable does MyServer (TEST) run its wipes?
Too few wipes of MyServer (TEST) are on record yet to show its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 2 days 17 hours is how long the current world has been running.
Tags
What do the server tags on MyServer (TEST) mean?
Tags published by MyServer (TEST) and read by the game's server browser include gmvanilla (Game mode): You'll find vanilla survival here; mp100 (Max players): 100 slots are available; ts10 (Group limit): Teams are capped at 10 players; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): The game build is 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; ^p (PvE): The danger comes from the world, not from other players; ^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 MyServer (TEST) appear?
These Rust Server Trends lists include MyServer (TEST): Modded Rust servers, tracked live and Rust PvE servers. You will find it under these filters on the server list: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
Connecting
What steps get you onto MyServer (TEST)?
To join, enter client.connect 138.16.248.206:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for 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.