Server_217_DevBlog
Offline 193.107.108.174:28015 checked 13d 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 71% 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
- 286/ 400
- 199/ 225
- 131/ 100
- 400/ 1000
- 37/ 700
Quick answers
Tags and listings
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. Its entry appears under the filters 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): There are 10 slots on this server; 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): 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. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
Server info
What's the location of Server_217_DevBlog?
Server_217_DevBlog does not put out a region. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. The endpoint is 193.107.108.174:28015.
How reliable is Server_217_DevBlog?
Right now Server_217_DevBlog is offline, having last been seen 13 days ago. In the last full 7 days, 0 of 168 hours were online, 0% uptime. 1 October 2026 is when Rust Going Deep first saw it.
What Rust version is Server_217_DevBlog on?
Rust network protocol 2183 is what Server_217_DevBlog runs, on Windows. Steam handles the update; you just need your game on the matching protocol to join.
Wipe info
What schedule does Server_217_DevBlog follow for wipes?
Server_217_DevBlog's rhythm is unclear because not enough wipes are on record yet. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. This world has been running since 16 days 19 hours ago.
Rules and settings
What settings are in place on Server_217_DevBlog?
The name of Server_217_DevBlog contains no gather rate. There is no published group limit. It runs survival, gather, build and raid, the standard game. You can fight and raid other players. In the server browser it sits under Modded, where plugins or settings change the game. The server does not run Valve's anti-cheat, VAC.
Which map is active on Server_217_DevBlog?
The map on Server_217_DevBlog is procedural, made by the game.
Player stats
What's the population like on Server_217_DevBlog?
Server_217_DevBlog was last seen 13 days ago and is offline as you read this.
What position does Server_217_DevBlog hold in the server rankings?
Over the last seven days, Server_217_DevBlog is #15,980 by player hours, among the top 71% of all ranked servers.
How to join
What's the way to join Server_217_DevBlog?
Open Rust and press F1, then type client.connect 193.107.108.174:28015. Alternatively, click Launch Rust on this page to join via Steam.