Station XX-15513 · no signal
Server_217_DevBlog
Offline 45.88.12.13:28015 checked 12d ago
- Players now
- 0/ 10
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,513
- top 71%
- Last wipe
- 12d 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 71% 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.1 daysbetween real wipes
- on rhythm
- 100%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, 20 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Sun 8 Nov, 16:06 UTC12d ago | M0.0■steady | 0 | – | – | running | 0 |
| Sat 7 Nov, 14:44 UTC13d ago | M0.0■steady | 0 | – | 1.1 days | 0 | |
| Fri 6 Nov, 13:06 UTC14d ago | M0.0■steady | 0 | – | 1.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 pageServer rules
Which map is running on Server_217_DevBlog?
The map on Server_217_DevBlog is procedural, produced by the game.
Which settings and rules apply on Server_217_DevBlog?
No gather rate appears in the name of Server_217_DevBlog. The group limit is not published. It plays in survival mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. The server browser lists it under Modded, where plugins or settings change the game. Anti-cheat is off: VAC, from Valve.
Population
What is the current population on Server_217_DevBlog?
Server_217_DevBlog is not responding at this moment and is offline, last seen 12 days 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,513 worldwide, placing it in the top 71% of all ranked servers.
Operator and location
How reliably does Server_217_DevBlog stay online?
Server_217_DevBlog is down at the moment; the last recorded contact was 12 days ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. On 6 November 2026 it was recorded for the first time by Rust Server Trends.
Where in the world is Server_217_DevBlog hosted?
Nothing about a region comes from Server_217_DevBlog. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 45.88.12.13:28015 is the address it uses.
Which Rust version is Server_217_DevBlog running?
On Windows, Server_217_DevBlog runs Rust network protocol 2183. 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?
0 players, on average, was the busiest crowd at its recent wipes. 20 hours into the latest wipe, the crowd reached its peak.
On what timetable does Server_217_DevBlog run its wipes?
There is no next wipe to predict at Server_217_DevBlog, since its wipes fall at irregular times. On Thursday 3 December at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 12 days 20 hours is how long the current world has been running.
Server 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): The game mode is standard Rust survival; mp10 (Max players): Slots: 10; v2183 (Protocol): Game protocol 2183: to join, your game must match this version; oxide (Oxide): Oxide (uMod) is the plugin framework running here; modded (Modded): Plugins or settings alter the game, so it's listed under Modded; h5e7466bf (Custom tag): The owner or a plugin applied this tag, which isn't part of standard Rust; stok (Custom tag): The owner or a plugin applied this tag, which isn't part of standard Rust. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does Server_217_DevBlog appear?
The Rust Server Trends lists that take in Server_217_DevBlog are: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Last wipe: In the last 2 weeks.
Join the server
How do you connect to Server_217_DevBlog?
Enter client.connect 45.88.12.13:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects 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.