RUST METRICSFlight deck · live data
Data live Servers11,846 Players84,816 Populated3,802 Fresh wipes 3 h288 Scan5 min
‹ All servers193.232.161.40:28015
Offline Full Queue Fresh wipe Wipe due No query

Server_217_DevBlog

Offline 193.232.161.40:28015 checked 12d 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,090top 70%
Last wipe12d 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
15k10k15k20k16 Oct17 Oct19 Oct20 Oct22 Oct23 Oct

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

Wipe timing

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. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 12 days 21 hours ago the current world was made.

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): Survival, as standard Rust plays it; mp10 (Max players): The server holds 10 slots; v2183 (Protocol): Match the game version: protocol 2183 is required; oxide (Oxide): Plugin framework in use: Oxide (uMod); modded (Modded): Modded: plugins or settings depart from the stock game; h5e7466bf (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.

Where does Server_217_DevBlog appear in Rust Metrics lists and filters?

Rust Metrics lists featuring 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,090 on seven-day player hours, top 70% of all ranked servers.

What player count does Server_217_DevBlog carry?

Status for Server_217_DevBlog: offline. Last seen 12 days 21 hours ago.

Operator and location

Where does Server_217_DevBlog sit?

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

What Rust version is Server_217_DevBlog on?

Rust network protocol 2183 on Windows is the build Server_217_DevBlog runs. Matching protocol is required to join. Let Steam update your game.

How reliable is Server_217_DevBlog, and is it online now?

Server_217_DevBlog reports offline. The last reading came 12 days 21 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 16 October 2026.

Rules and settings

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

Reading the name gives no gather rate for Server_217_DevBlog. No group limit is published. The mode is survival. Note the following: 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. Anti-cheat reading: VAC off, Valve's system.

Which map is live on Server_217_DevBlog?

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

Connection

How do you connect to Server_217_DevBlog?

Press F1 in Rust and enter client.connect 193.232.161.40: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 Survival, as standard Rust plays it.
mp10
Max players The server holds 10 slots.
v2183
Protocol Match the game version: protocol 2183 is required.

Mods and access

oxide
Oxide Plugin framework in use: Oxide (uMod).
modded
Modded Modded: plugins or settings depart from the stock game.

Other

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