Slid3rverse
Offline 50.53.26.23:28015 checked 44d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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 bestWipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
Peak: the most players in the first 48 hours. 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 wipes- 271/250
- 223/225
- 17/250
- 22/250
- 25/100
- 92/200
Quick answers
from the figures on this pageWipe schedule
How often does Slid3rverse wipe, and when?
Its rhythm cannot be told from the wipes of Slid3rverse on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 52 days 2 hours ago.
Lists and filters
How should you read the tags on Slid3rverse?
These are the tags Slid3rverse publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp4 (Max players): The server holds 4 slots; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163207 (Build): Build 163207; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Which lists and filters on Rust Metrics show Slid3rverse?
On Rust Metrics, Slid3rverse sits in these lists: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Player count
Where does Slid3rverse sit in the rankings?
Player hours over seven days put Slid3rverse at #15,025, in the top – of all ranked servers.
How full does Slid3rverse get?
Status for Slid3rverse: offline. Last seen 44 days 15 hours ago.
Operator and location
Where does Slid3rverse sit?
No region comes from Slid3rverse. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 50.53.26.23:28015.
What Rust version is Slid3rverse on?
Version check: Rust network protocol 2633 and build 163207 on Linux, run by Slid3rverse. Check: protocol. To join, your game must match; Steam handles the update.
Is Slid3rverse up, and how often does it stay up?
Reading: offline. Slid3rverse last answered 44 days 15 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 13 September 2026, recorded by Rust Metrics.
Map and rules
How is Slid3rverse configured, and what rules are in force?
Reading the name gives no gather rate for Slid3rverse. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.
What map is Slid3rverse on?
Procedural map on Slid3rverse, made by the game's generator.
Connection
What do you do to join Slid3rverse?
To join: start Rust, press F1 and type client.connect 50.53.26.23:28015. Or press Launch Rust here and Steam opens the game and connects you.