RUST METRICSFlight deck · live data
Data live Servers11,826 Players82,123 Populated3,756 Fresh wipes 3 h273 Scan5 min
‹ All servers194.48.218.124:28015
Offline Full Queue Fresh wipe Wipe due No query

Server_210_DevBlog

Offline 194.48.218.124:28015 checked 13d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#14,600top 68%
Last wipe13d agono schedule published
Next wipe–too few wipes seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

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.

REC 3

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.

PLAN

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 peak1players, 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.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 15 Oct, 15:05 UTC13d ago 1 – running 1

Peak: the most players in the first 48 hours. 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What should you expect from wipe day on Server_210_DevBlog?

The busiest point of its recent wipes drew 1 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

When does Server_210_DevBlog wipe?

To tell the rhythm of Server_210_DevBlog, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 13 days 23 hours ago.

Tags

Which tags does Server_210_DevBlog carry, and what do they mean?

These are the tags Server_210_DevBlog publishes, and the server browser reads them: mp10 (Max players): Slots: 10; v2153 (Protocol): Match the game version: protocol 2153 is required; h29248c67 (Custom tag): This tag is non-standard, added by the owner or a plugin; stok (Custom tag): This tag is non-standard, added by the owner or a plugin. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show Server_210_DevBlog?

These Rust Metrics lists carry Server_210_DevBlog: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Last wipe: In the last 2 weeks.

Occupancy

Where does Server_210_DevBlog sit in the rankings?

Ranking for Server_210_DevBlog: #14,600 on seven-day player hours, top 68% of all ranked servers.

What player count does Server_210_DevBlog carry?

Status for Server_210_DevBlog: offline. Last seen 13 days 22 hours ago.

Server

Where does Server_210_DevBlog sit?

No region comes from Server_210_DevBlog. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 194.48.218.124:28015.

What Rust version is Server_210_DevBlog on?

Version check: Rust network protocol 2153 on Windows, run by Server_210_DevBlog. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is Server_210_DevBlog, and is it online now?

Server_210_DevBlog reports offline. The last reading came 13 days 22 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 14 October 2026.

Map and rules

What rules does Server_210_DevBlog enforce, and what are its settings?

Reading the name gives no gather rate for Server_210_DevBlog. No group limit is published. The mode is survival. Note the following: standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Anti-cheat reading: VAC off, Valve's system.

What map is Server_210_DevBlog on?

Check: map. Procedural, generated by the game, on Server_210_DevBlog.

How to join

How can you get onto Server_210_DevBlog?

Press F1 in Rust and enter client.connect 194.48.218.124:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp10,v2153,h29248c67,stok

Game

mp10
Max players Slots: 10.
v2153
Protocol Match the game version: protocol 2153 is required.

Other

h29248c67
Custom tag This tag is non-standard, added by the owner or a plugin.
stok
Custom tag This tag is non-standard, added by the owner or a plugin.

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.