Station XX-15347 · no signal
Server_217_DevBlog
Offline 212.110.152.61:28015 checked 9d ago
- Players now
- 0/ 10
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,347
- top 70%
- Last wipe
- 30d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 10 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 70% 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
- 1.5 daysbetween real wipes
- on rhythm
- 0%of its recent wipes
- wipe-day peak
- 0players, 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 |
|---|---|---|---|---|---|---|
| Tue 29 Sep, 11:00 UTC30d ago | M0.0■steady | 0 | – | running | 0 | |
| Sun 27 Sep, 14:27 UTC32d ago | M0.0■steady | 0 | – | 1.9 days | 0 | |
| Sat 26 Sep, 13:24 UTC33d ago | M0.0■steady | 0 | – | 1 days | 0 |
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 Server_217_DevBlog?
A procedural map runs on Server_217_DevBlog, generated by the game.
Which settings and rules apply on Server_217_DevBlog?
You will find no gather rate in the name of Server_217_DevBlog. It gives no group limit in its listing. It plays in survival mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. Listed as Modded in the server browser, it changes the game through plugins or settings. Anti-cheat is off: VAC, from Valve.
Player counts
What is the current population on Server_217_DevBlog?
A reading taken now finds Server_217_DevBlog offline; the most recent activity was 9 days 12 hours ago.
How does Server_217_DevBlog rank against other Rust servers?
Over the last seven days, Server_217_DevBlog recorded enough player hours to reach #15,347 worldwide, placing it in the top 70% of all ranked servers.
Server details
How reliably does Server_217_DevBlog stay online?
No contact with Server_217_DevBlog right now, and the last recorded contact was 9 days 12 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. On 26 September 2026 it was recorded for the first time by Rust Server Trends.
Which region does Server_217_DevBlog run from?
Nothing about a region comes from Server_217_DevBlog. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 212.110.152.61:28015 is the address it uses.
What build of Rust does Server_217_DevBlog use?
Server_217_DevBlog is running Rust network protocol 2183 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.
Wipe pattern
What does wipe day look like on Server_217_DevBlog?
The recent wipes averaged a busiest count of 0 players. 0 hours into the latest wipe, the crowd reached its peak.
On what timetable does Server_217_DevBlog run its wipes?
No next wipe can be predicted for Server_217_DevBlog, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. It has run its current world for 30 days 12 hours.
Tags
What do the server tags on Server_217_DevBlog mean?
These are the tags Server_217_DevBlog publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp10 (Max players): Slots: 10; v2183 (Protocol): To connect, your game must be on the same protocol, 2183; oxide (Oxide): A plugin framework, Oxide (uMod), runs here; modded (Modded): Plugins or settings alter the game, so it's listed under Modded; h5e7466bf (Custom tag): The owner or a plugin set this tag, and it's not one of Rust's standard tags; stok (Custom tag): The owner or a plugin set this tag, and it's not one of Rust's standard tags. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does Server_217_DevBlog appear?
You will find Server_217_DevBlog on the following Rust Server Trends lists: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded.
Join the server
How do you connect to Server_217_DevBlog?
To join, enter client.connect 212.110.152.61: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.