Station XX-13609 · no signal
myserver
Offline 45.147.121.28:28015 checked 18d ago
- Players now
- 1/ 1
- 100% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #13,609
- top 61%
- Last wipe
- 25d 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 61% 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
- 1.1 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 2 Oct, 11:46 UTC25d ago | M0.0▲rising | 1 | – | running | 0 | |
| Thu 1 Oct, 02:06 UTC27d ago | M0.0▲rising | 1 | – | 1.4 days | 0 | |
| Wed 30 Sep, 08:33 UTC27d ago | M0.0▲rising | 1 | – | 0.7 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 map is running on myserver?
myserver uses a procedural map, which the game generates.
Which settings and rules apply on myserver?
You will find no gather rate in the name of myserver. Groups hold up to 8 players, which is the default for the game. It plays 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. The plugins run on Oxide. The server has VAC on, Valve's anti-cheat.
Population
What is the current population on myserver?
A reading taken now finds myserver offline; the most recent activity was 18 days 16 hours ago.
How does myserver rank against other Rust servers?
Over the last seven days, myserver recorded enough player hours to reach #13,609 worldwide, placing it in the top 61% of all ranked servers.
Operator and location
How reliably does myserver stay online?
As recorded now, myserver is not reachable, the last contact having been 18 days 16 hours 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 30 September 2026.
Which region does myserver run from?
Nothing about a region comes from myserver. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 45.147.121.28:28015 is the address it uses.
What build of Rust does myserver use?
Rust network protocol 2634 and build 166586 on Windows is what myserver runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe day
What does wipe day look like on myserver?
On average, the busiest point of its recent wipes drew 1 players. 1 hours after the latest wipe, the crowd peaked.
On what timetable does myserver run its wipes?
There is no next wipe to predict at myserver, since its wipes fall at irregular times. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 25 days 20 hours.
Server tags
What do the server tags on myserver mean?
The game's server browser reads the tags myserver publishes: gmrust (Game mode): The game mode is standard Rust survival; mp1 (Max players): 1 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs166586 (Build): It runs game build 166586; 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 myserver appear?
You will find myserver on the following Rust Server Trends lists: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Connecting
How do you connect to myserver?
You can connect by pressing F1 in Rust and typing client.connect 45.147.121.28: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.