Rust Server TrendsSeismic network · station log
Recording Stations11,703 Players49,472 Active2,998 Wipes · 3 h104 48 h

Station XX-15460 · no signal

Server_216_DevBlog

Offline 213.5.195.22:28015 checked 37d ago

modded
Connect
Players now
0/ 10
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,460
top 67%
Last wipe
37d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-15460 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 10 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k22 Sep23 Sep25 Sep26 Sep28 Sep29 Sep

Top 67% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit no group limit · 151 on average
15/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
132/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 122 on average
34/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 97 on average
2/ 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 94 on average
6/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 86 on average
127/ 200
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on Server_216_DevBlog?

Server_216_DevBlog uses a procedural map, which the game generates.

Which settings and rules apply on Server_216_DevBlog?

You will find no gather rate in the name of Server_216_DevBlog. No group limit is published. It plays in survival mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Modded, where plugins or settings change the game. VAC, Valve's anti-cheat, is switched off.

Live population

What is the current population on Server_216_DevBlog?

A reading taken now finds Server_216_DevBlog offline; the most recent activity was 37 days 9 hours ago.

How does Server_216_DevBlog rank against other Rust servers?

On player hours for the past week, Server_216_DevBlog sits at #15,460, which puts it inside the top 67% of every ranked server.

Server details

How reliably does Server_216_DevBlog stay online?

No contact with Server_216_DevBlog right now, and the last recorded contact was 37 days 9 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 22 September 2026 it was recorded for the first time by Rust Server Trends.

Which region does Server_216_DevBlog run from?

Nothing about a region comes from Server_216_DevBlog. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 213.5.195.22:28015.

Which Rust version is Server_216_DevBlog running?

Rust network protocol 2180 on Windows is what Server_216_DevBlog runs. The protocol must match for you to join, and Steam takes care of updating it.

Wipe schedule

How often does Server_216_DevBlog wipe, and on which days?

On record so far are too few of Server_216_DevBlog's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. It has run its current world for 37 days 9 hours.

Server tags

What do the server tags on Server_216_DevBlog mean?

The game's server browser reads the tags Server_216_DevBlog publishes: gmrust (Game mode): Survival in standard Rust; mp10 (Max players): The server has 10 slots; v2180 (Protocol): Your game needs to be on protocol 2180 to join; oxide (Oxide): A plugin framework, Oxide (uMod), runs here; modded (Modded): The game is changed by plugins or settings, placing it under Modded; hdf93daba (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. 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_216_DevBlog appear?

The Rust Server Trends lists that take in Server_216_DevBlog are: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded.

Connecting

What steps get you onto Server_216_DevBlog?

To join, enter client.connect 213.5.195.22: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.

Instrument codes

Server tags

what each one means

Published as mp10,v2180,hdf93daba,stok,gmrust,oxide,modded

Game

gmrust
Game mode Survival in standard Rust.
mp10
Max players The server has 10 slots.
v2180
Protocol Your game needs to be on protocol 2180 to join.

Mods and access

oxide
Oxide A plugin framework, Oxide (uMod), runs here.
modded
Modded The game is changed by plugins or settings, placing it under Modded.

Other

hdf93daba
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.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.

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.