Rust Server TrendsSeismic network · station log
Recording Stations11,525 Players85,836 Active3,992 Wipes · 3 h134 48 h

Station XX-15141 · no signal

Server_217_DevBlog

Offline 83.99.204.200:28015 checked 10d ago

moddedcarbon
Connect
Players now
0/ 10
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,141
top 69%
Last wipe
14d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15141 · 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
15k10k15k20k6 Nov8 Nov11 Nov13 Nov16 Nov18 Nov

Top 69% 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

00.250.50.751+0h+9h+19h+28h+38h+47h

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
Fri 6 Nov, 17:07 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
МИНИ-КАРТА 2Х | STORM | FPS+ 18.11 EU · groups of 8+ · weekly · 128 on average
123/ 100
ShockRust | Blue | NoLimit no group limit · 110 on average
299/ 400
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT GLOBAL 20.11 EU · groups of 16+ · weekly · 98 on average
188/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 17.11 EU · groups of 16+ · monthly · 79 on average
60/ 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 19.11 EU · groups of 16+ · monthly · 69 on average
115/ 1000
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 14.11 EU · groups of 16+ · monthly · 66 on average
14/ 1000
Readings, in words

Quick answers

from the figures on this page

Map and 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?

You will find no gather rate in the name of Server_217_DevBlog. The group limit is 8 players, the game's default. In survival mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. Plugins or settings alter the game here; the browser lists it as Modded. Its plugins are run through Carbon. The server has VAC off, Valve's anti-cheat.

Player counts

How many players are recorded on Server_217_DevBlog right now?

A reading taken now finds Server_217_DevBlog offline; the most recent activity was 10 days 7 hours ago.

How does Server_217_DevBlog rank against other Rust servers?

On player hours for the past week, Server_217_DevBlog sits at #15,141, which puts it inside the top 69% of every ranked server.

Server facts

How reliably does Server_217_DevBlog stay online?

As recorded now, Server_217_DevBlog is not reachable, the last contact having been 10 days 7 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. 6 November 2026 is when Rust Server Trends first recorded it.

Which region does Server_217_DevBlog run from?

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. 83.99.204.200:28015 is the address it uses.

What build of Rust does Server_217_DevBlog use?

Rust network protocol 2636 and build 170460 on Windows is what Server_217_DevBlog runs. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe schedule

What does wipe day look like on Server_217_DevBlog?

The recent wipes averaged a busiest count of 1 players. 0 hours into the latest wipe, the crowd reached its peak.

How often does Server_217_DevBlog wipe, and on which days?

Too few wipes of Server_217_DevBlog are on record yet to show its rhythm. On Thursday 3 December at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The present world dates from 14 days 19 hours.

Tags

What do the server tags on Server_217_DevBlog mean?

The game's server browser reads the tags Server_217_DevBlog publishes: gmrust (Game mode): The game mode is standard Rust survival; mp10 (Max players): The server has 10 slots; ts8 (Group limit): This uses the game default of 8 per team; v2636 (Protocol): To connect, your game must be on the same protocol, 2636; cs170460 (Build): It runs game build 170460; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): A plugin framework, Carbon, runs here. 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?

These Rust Server Trends lists include Server_217_DevBlog: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Connecting

What steps get you onto Server_217_DevBlog?

You can connect by pressing F1 in Rust and typing client.connect 83.99.204.200: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,ptrak,$r?,v2636,gmrust,cs170460,ts8,^z,^y

Game

gmrust
Game mode The game mode is standard Rust survival.
mp10
Max players The server has 10 slots.
ts8
Group limit This uses the game default of 8 per team.
v2636
Protocol To connect, your game must be on the same protocol, 2636.
cs170460
Build It runs game build 170460.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code The server has no region code.

Mods and access

^z
Modded Plugins or settings alter the game, so it's listed under Modded.
^y
Carbon A plugin framework, Carbon, runs here.

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.