Rust Server TrendsSeismic network · station log
Recording Stations11,802 Players70,703 Active3,677 Wipes · 3 h121 48 h

Station XX-10084 · no signal

Server_210_DevBlog

Offline 89.105.199.147:28015 checked 5d ago

modded
Connect
Players now
1/ 10
10% full
Motion · 24 h
M –
too few hourly readings
7-day average
1
peak 1
Rank
#10,084
top 45%
Last wipe
6d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-10084 · 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
1of 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 Oct23 Oct24 Oct26 Oct27 Oct28 Oct

Top 45% 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 · 157 on average
105/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
129/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 116 on average
119/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 91 on average
90/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average
25/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
24/ 1000
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on Server_210_DevBlog?

The map on Server_210_DevBlog is procedural, produced by the game.

Which settings and rules apply on Server_210_DevBlog?

No gather rate appears in the name of Server_210_DevBlog. The group limit is not published. In survival mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. The server browser lists it under Modded, where plugins or settings change the game. VAC, Valve's anti-cheat, is switched off.

Player counts

What is the current population on Server_210_DevBlog?

No players are recorded on Server_210_DevBlog at this moment; it is offline, and the last sighting was 5 days 1 hours ago. Averaged across the last seven days the population was 1 players, reaching a peak of 1.

How does Server_210_DevBlog rank against other Rust servers?

On player hours for the past week, Server_210_DevBlog sits at #10,084, which puts it inside the top 45% of every ranked server.

Server details

How reliably does Server_210_DevBlog stay online?

No contact with Server_210_DevBlog right now, and the last recorded contact was 5 days 1 hours ago. 2 of 120 hours in the last 5 full days were up time, 2% of the total. On 22 October 2026 it was recorded for the first time by Rust Server Trends.

Where in the world is Server_210_DevBlog hosted?

A region is not published by Server_210_DevBlog. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 89.105.199.147:28015.

What build of Rust does Server_210_DevBlog use?

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

Wipe schedule

On what timetable does Server_210_DevBlog run its wipes?

The rhythm of Server_210_DevBlog cannot yet be told: too few of its wipes are on record. 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 6 days 6 hours.

Tags

What do the server tags on Server_210_DevBlog mean?

These are the tags Server_210_DevBlog publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp10 (Max players): Slots: 10; v2201 (Protocol): Game protocol 2201: 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; hd910d3d2 (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: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Last wipe: In the last week.

Connecting

How do you connect to Server_210_DevBlog?

You can connect by pressing F1 in Rust and typing client.connect 89.105.199.147:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp10,v2201,hd910d3d2,stok,gmrust,oxide,modded

Game

gmrust
Game mode The game mode is standard Rust survival.
mp10
Max players Slots: 10.
v2201
Protocol Game protocol 2201: to join, your game must match this version.

Mods and access

oxide
Oxide Oxide (uMod) is the plugin framework running here.
modded
Modded Plugins or settings alter the game, so it's listed under Modded.

Other

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