RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h41 Scan5 min
‹ All servers46.172.84.193:28015
Offline Full Queue Fresh wipe Wipe due No query

Server_217_DevBlog

Offline 46.172.84.193:28015 checked 9d ago

modded
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#15,291top 69%
Last wipe11d 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
15k10k15k20k20 Sep27 Sep3 Oct13 Oct19 Oct26 Oct

Top 69% 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 peak0players, last three wipes

The first 48 hours of its last wipes

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 21 Sep, 06:00 UTC37d ago 0 – running 0

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

Wipe schedule

What should you expect from wipe day on Server_217_DevBlog?

An average of 0 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 0 hours.

What wipe timing does Server_217_DevBlog follow?

Its rhythm cannot be told from the wipes of Server_217_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. The world it runs now was made 11 days 12 hours ago.

Tags

How should you read the tags on Server_217_DevBlog?

Tags published by Server_217_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; v2183 (Protocol): Your game must run protocol 2183 to get in; oxide (Oxide): It runs Oxide, also known as uMod; modded (Modded): Plugins or settings make this a modded server; h5e7466bf (Custom tag): A plugin or the owner set this tag; Rust does not ship it; stok (Custom tag): A plugin or the owner set this tag; Rust does not ship it. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does Server_217_DevBlog appear in Rust Metrics lists and filters?

These Rust Metrics lists carry Server_217_DevBlog: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Last wipe: In the last 2 weeks.

Player count

Where does Server_217_DevBlog sit in the rankings?

Ranking for Server_217_DevBlog: #15,291 on seven-day player hours, top 69% of all ranked servers.

What player count does Server_217_DevBlog carry?

Reading for Server_217_DevBlog: offline at this moment; last seen 9 days 12 hours ago.

Operator and location

Where does Server_217_DevBlog sit?

No region tag on Server_217_DevBlog. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 46.172.84.193:28015.

What Rust version is Server_217_DevBlog on?

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

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

Check: connection. Server_217_DevBlog is offline at this moment. Last contact was 9 days 12 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 13 September 2026.

Settings and map

What settings and rules apply on Server_217_DevBlog?

Check: gather rate. The name Server_217_DevBlog does not state one. No group limit is published. Mode check gives survival; gather, build and raid, as the game normally runs. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. VAC is off. That is Valve's anti-cheat.

Which map is live on Server_217_DevBlog?

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

How to join

How can you get onto Server_217_DevBlog?

Press F1 in Rust and enter client.connect 46.172.84.193: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,v2183,h5e7466bf,stok,gmrust,oxide,modded

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players 10 slots in total.
v2183
Protocol Your game must run protocol 2183 to get in.

Mods and access

oxide
Oxide It runs Oxide, also known as uMod.
modded
Modded Plugins or settings make this a modded server.

Other

h5e7466bf
Custom tag A plugin or the owner set this tag; Rust does not ship it.
stok
Custom tag A plugin or the owner set this tag; Rust does not ship it.

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.