Server_216_DevBlog
Offline 213.5.195.22:28015 checked 25d ago
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 67% of all ranked servers. Ranked on player hours over the last seven days.
Wipe 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
- 17/ 100
- 310/ 400
- 182/ 225
- 129/ 100
- 381/ 1000
- 31/ 700
Quick answers
Tags and filters
Where does Server_216_DevBlog appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry Server_216_DevBlog are: Modded Rust servers. Its entry appears under the filters Type: Modded.
How should you read the tags on Server_216_DevBlog?
Server_216_DevBlog's game browser tags read: gmrust (Game mode): This is the standard Rust survival experience; mp10 (Max players): There are 10 slots on this server; v2180 (Protocol): The protocol is 2180; a different version won't get you in; oxide (Oxide): This server uses Oxide (uMod) for plugins; modded (Modded): The Modded category fits: plugins or settings are in play; hdf93daba (Custom tag): The owner or a plugin created this tag, so it's not standard Rust; stok (Custom tag): The owner or a plugin created this tag, so it's not standard Rust. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
Server info
Where can you find Server_216_DevBlog?
Server_216_DevBlog does not put out a region. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. The endpoint is 213.5.195.22:28015.
How reliable is Server_216_DevBlog?
Server_216_DevBlog is down at the moment; it was last up 25 days 18 hours ago. Over the past full 7 days it stayed up for 0 of 168 hours, or 0%. 22 September 2026 is when Rust Going Deep first saw it.
What Rust version is Server_216_DevBlog on?
On Windows, Server_216_DevBlog runs Rust network protocol 2180. Steam handles the update; you just need your game on the matching protocol to join.
Wipe details
What schedule does Server_216_DevBlog follow for wipes?
Too few wipes are on record for Server_216_DevBlog to show its rhythm. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. 25 days 18 hours is how long ago this world came into being.
Settings and map
What settings and rules have been applied to Server_216_DevBlog?
The name of Server_216_DevBlog contains no gather rate. No group limit is published. It runs survival, gather, build and raid, the standard game. PvP and raiding are enabled. In the server browser it sits under Modded, where plugins or settings change the game. VAC is off: Valve's anti-cheat is not active.
Which map is active on Server_216_DevBlog?
Server_216_DevBlog uses a game-generated procedural map.
Player stats
Is Server_216_DevBlog busy?
Server_216_DevBlog was last seen 25 days 18 hours ago and is offline as you read this.
Where does Server_216_DevBlog sit in the rankings?
For player hours in the last seven days, Server_216_DevBlog ranks #15,460, within the top 67% of ranked servers.
Getting in
What's the process to join Server_216_DevBlog?
Open Rust and press F1, then type client.connect 213.5.195.22:28015. Alternatively, click Launch Rust on this page to join via Steam.