Rust Server TrendsSeismic network · station log
Recording Stations11,831 Players94,092 Active3,830 Wipes · 3 h517 48 h

Station XX-14600 · no signal

Server_210_DevBlog

Offline 194.48.218.124:28015 checked 14d ago

Connect
Players now
0/ 10
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#14,600
top 68%
Last wipe
14d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-14600 · 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
15k10k15k20k14 Oct16 Oct17 Oct19 Oct20 Oct22 Oct

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

Expected events

Wipe schedule

too few wipes seen yet

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

wipe-day peak
1players, last three wipes

The first 48 hours of its last wipes

No hourly players around its wipes yet.

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Thu 15 Oct, 15:05 UTC14d ago M0.0steady 1 – – running 1

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
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 508 on average
236/ 275
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 318 on average
316/ 350
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 282 on average
771/ 1000
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 277 on average
47/ 100
Rustoria.co - EU Main EU · groups of 16+ · weekly · 266 on average
894/ 950
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 240 on average
744/ 800
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on Server_210_DevBlog?

Server_210_DevBlog uses a procedural map, which the game generates.

Which settings and rules apply on Server_210_DevBlog?

The name of Server_210_DevBlog gives no gather rate. It gives no group limit in its listing. survival is the game mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Under Community in the server browser, it runs as a community server. The server has VAC off, Valve's anti-cheat.

Live population

How many players are recorded on Server_210_DevBlog right now?

Server_210_DevBlog is not responding at this moment and is offline, last seen 14 days 5 hours ago.

How does Server_210_DevBlog rank against other Rust servers?

The last seven days of player hours place Server_210_DevBlog at #14,600, in the top 68% of all ranked servers.

Server details

How reliably does Server_210_DevBlog stay online?

Server_210_DevBlog is down at the moment; the last recorded contact was 14 days 5 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. On 14 October 2026 it was recorded for the first time by Rust Server Trends.

Which region does Server_210_DevBlog run from?

No region is published by Server_210_DevBlog. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 194.48.218.124:28015.

What build of Rust does Server_210_DevBlog use?

Rust network protocol 2153 on Windows is what Server_210_DevBlog runs. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe day

What does wipe day look like on Server_210_DevBlog?

The recent wipes averaged a busiest count of 1 players. 0 hours after the latest wipe, the crowd peaked.

How often does Server_210_DevBlog wipe, and on which days?

Too few wipes of Server_210_DevBlog are on record yet to show its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The present world dates from 14 days 5 hours.

Lists and tags

What do the server tags on Server_210_DevBlog mean?

Tags published by Server_210_DevBlog and read by the game's server browser include mp10 (Max players): 10 slots are available; v2153 (Protocol): Game protocol 2153: to join, your game must match this version; h29248c67 (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. 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_210_DevBlog appear?

You will find Server_210_DevBlog on the following Rust Server Trends lists: Rust community servers without the side modes. You will find it under these filters on the server list: Type: Community (not modded, not official) and No plugins at all.

Connecting

What steps get you onto Server_210_DevBlog?

To join, enter client.connect 194.48.218.124: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,v2153,h29248c67,stok

Game

mp10
Max players 10 slots are available.
v2153
Protocol Game protocol 2153: to join, your game must match this version.

Other

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

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.