Server_217_DevBlog
Offline 5.227.44.219:28015 checked 29d 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 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
- 17/ 100
- 309/ 400
- 182/ 225
- 135/ 100
- 372/ 1000
- 31/ 700
Quick answers
Tags and search
Where does Server_217_DevBlog appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include Server_217_DevBlog: Modded Rust servers. The server list shows it under Type: Modded.
How should you read the tags on Server_217_DevBlog?
Server_217_DevBlog's game browser tags read: gmrust (Game mode): This is the standard Rust survival experience; mp10 (Max players): It holds 10 players; v2183 (Protocol): This server runs game protocol 2183, so your game must match that version to join; oxide (Oxide): This server uses Oxide (uMod) for plugins; modded (Modded): Plugins or settings make changes, so it's listed as Modded; h5e7466bf (Custom tag): A plugin or the owner set this tag; it's not one Facepunch provides; stok (Custom tag): A plugin or the owner set this tag; it's not one Facepunch provides. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
Server details
What's the location of Server_217_DevBlog?
There is no published region for Server_217_DevBlog. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. You can reach it at 5.227.44.219:28015.
How reliable is Server_217_DevBlog?
The server Server_217_DevBlog is not reachable at the moment; the last sighting was 29 days 23 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. Rust Going Deep has had it on record since 18 September 2026.
What is the Rust version for Server_217_DevBlog?
Rust network protocol 2183 is what Server_217_DevBlog runs, on Windows. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe schedule
How often does Server_217_DevBlog wipe?
Server_217_DevBlog's rhythm is unclear because not enough wipes are on record yet. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. The world you are on now was created 123 days 20 hours.
Map and rules
What settings and rules have been applied to Server_217_DevBlog?
The name of Server_217_DevBlog contains no gather rate. The group limit is not published. survival is the game mode, gather, build and raid, the standard game. PvP and raiding are enabled. Plugins or settings change the game, so the browser lists it as Modded. VAC is off: Valve's anti-cheat is not active.
What's the map on Server_217_DevBlog?
Server_217_DevBlog uses a game-generated procedural map.
Player count
Is Server_217_DevBlog busy?
Right now Server_217_DevBlog is offline, with its last appearance 29 days 23 hours ago.
Where does Server_217_DevBlog sit in the rankings?
For player hours in the last seven days, Server_217_DevBlog ranks #15,400, within the top – of ranked servers.
Getting in
What's the way to join Server_217_DevBlog?
Open Rust and press F1, then type client.connect 5.227.44.219:28015. Alternatively, click Launch Rust on this page to join via Steam.