RUST METRICSFlight deck · live data
Data live Servers11,727 Players59,874 Populated3,366 Fresh wipes 3 h179 Scan5 min
‹ All servers31.135.199.171:28015
Offline Full Queue Fresh wipe Wipe due No query

Server_216_DevBlog

Offline 31.135.199.171:28015 checked 3d ago

modded
COM 1 · connect
Launch Rust and join

Server instruments

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

Players now

10% full 7-day avg7-day peak
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 average1peak 1
Rank#11,513top 52%
Last wipe46d agono schedule published
Next wipe–no wipe 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
15k10k15k20k20 Sep28 Sep3 Oct7 Oct12 Oct29 Oct

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

PLAN

Wipe schedule

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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 wipe timing does Server_216_DevBlog follow?

Its rhythm cannot be told from the wipes of Server_216_DevBlog on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 46 days 16 hours ago the current world was made.

Tag meanings

How should you read the tags on Server_216_DevBlog?

Tags published by Server_216_DevBlog, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): 10 slots in total; v2180 (Protocol): Match the game version: protocol 2180 is required; oxide (Oxide): It runs Oxide, also known as uMod; modded (Modded): Modded: plugins or settings depart from the stock game; hdf93daba (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. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does Server_216_DevBlog appear in Rust Metrics lists and filters?

On Rust Metrics, Server_216_DevBlog sits in these lists: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded.

Player count

What position does Server_216_DevBlog hold among Rust servers?

Ranking for Server_216_DevBlog: #11,513 on seven-day player hours, top 52% of all ranked servers.

What player count does Server_216_DevBlog carry?

Status for Server_216_DevBlog: offline. Last seen 3 days 22 hours ago. Seven-day check: 1 players on average. Peak reading: 1.

Server

Which location does Server_216_DevBlog run from?

No region comes from Server_216_DevBlog. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 31.135.199.171:28015.

What Rust version is Server_216_DevBlog on?

Rust network protocol 2180 on Windows is the build Server_216_DevBlog runs. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on Server_216_DevBlog, and is it online?

Check: connection. Server_216_DevBlog is offline at this moment. Last contact was 3 days 22 hours ago. Reading: 1% uptime over the last 7 full days. It was up 2 of 168 hours. Reading: first seen 15 September 2026, recorded by Rust Metrics.

Settings and map

How is Server_216_DevBlog configured, and what rules are in force?

Check: gather rate. The name Server_216_DevBlog does not state one. The group limit is not published. survival, gather, build and raid, as the game normally runs — that is the game mode. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Check: anti-cheat. VAC, Valve's system, is off.

Which map is live on Server_216_DevBlog?

Procedural map on Server_216_DevBlog, made by the game's generator.

How to join

What do you do to join Server_216_DevBlog?

To join: start Rust, press F1 and type client.connect 31.135.199.171:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players 10 slots in total.
v2180
Protocol Match the game version: protocol 2180 is required.

Mods and access

oxide
Oxide It runs Oxide, also known as uMod.
modded
Modded Modded: plugins or settings depart from the stock game.

Other

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