Station XX-15344 · no signal
myserver
Offline 188.163.20.214:28015 checked 6d ago
- Players now
- 0/ 1
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,344
- top 69%
- Last wipe
- 6d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 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 69% 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
- 3.8 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 0, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Fri 23 Oct, 02:13 UTC6d ago | M0.0▼falling | 0 | – | – | running | 1 |
| Thu 15 Oct, 18:15 UTC13d ago | M0.0▲rising | 1 | – | 7.3 days | 0 | |
| Thu 15 Oct, 11:03 UTC14d ago | M0.0■steady | 1 | – | 0.3 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 myserver?
myserver uses a procedural map, which the game generates.
Which settings and rules apply on myserver?
The name of myserver gives no gather rate. The group limit is 8 players, the game's default. It plays in survival mode, the usual game of 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. Anti-cheat is on: VAC, from Valve.
Live population
What is the current population on myserver?
A reading taken now finds myserver offline; the most recent activity was 6 days 13 hours ago. Averaged across the last seven days, the population was 0 players.
How does myserver rank against other Rust servers?
Over the last seven days, myserver recorded enough player hours to reach #15,344 worldwide, placing it in the top 69% of all ranked servers.
Server details
How reliably does myserver stay online?
No contact with myserver right now, and the last recorded contact was 6 days 13 hours ago. It was up 1% of the time across the last 7 full days: 1 of 168 hours. 14 October 2026 is when Rust Server Trends first recorded it.
Where in the world is myserver hosted?
No region is published by myserver. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 188.163.20.214:28015.
What build of Rust does myserver use?
On Windows, myserver runs Rust network protocol 2634 and build 167781. The protocol must match for you to join, and Steam takes care of updating it.
Wipe pattern
What does wipe day look like on myserver?
The recent wipes averaged a busiest count of 1 players. The peak on the most recent wipe came 0 hours after the wipe.
How often does myserver wipe, and on which days?
There is no next wipe to predict at myserver, since its wipes fall at irregular times. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. It has run its current world for 6 days 13 hours.
Lists and tags
What do the server tags on myserver mean?
These are the tags myserver publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp1 (Max players): The server has 1 slots; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167781 (Build): The game build is 167781; 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; ^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. 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.
Connecting
How do you connect to myserver?
To join, enter client.connect 188.163.20.214: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.