RUST METRICSFlight deck · live data
Data live Servers11,749 Players65,278 Populated3,453 Fresh wipes 3 h195 Scan5 min
‹ All servers176.119.169.227:28015
Offline Full Queue Fresh wipe Wipe due No query

Server_217_DevBlog

Offline 176.119.169.227:28015 checked 43d 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,404no region published
Last wipe43d 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 Sep21 Sep22 Sep
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

When does Server_217_DevBlog wipe?

The rhythm of Server_217_DevBlog's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 43 days 23 hours ago.

Tag meanings

How should you read the tags on Server_217_DevBlog?

These are the tags Server_217_DevBlog publishes, and the server browser reads them: 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): Check: framework. Oxide (uMod) handles plugins; modded (Modded): Check: category. Modded, because plugins or settings alter the game; 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, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does Server_217_DevBlog appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Server_217_DevBlog: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded.

Player count

What position does Server_217_DevBlog hold among Rust servers?

Ranking for Server_217_DevBlog: #15,404 on seven-day player hours, top – of all ranked servers.

How full does Server_217_DevBlog get?

Status for Server_217_DevBlog: offline. Last seen 43 days 18 hours ago.

Server details

Which location does Server_217_DevBlog run from?

No region comes from Server_217_DevBlog. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 176.119.169.227:28015.

What Rust version is Server_217_DevBlog on?

Reading: Server_217_DevBlog, Rust network protocol 2183, Windows. Matching protocol is required to join. Let Steam update your game.

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 43 days 18 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 15 September 2026.

Settings and map

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

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

Connection

How do you connect to Server_217_DevBlog?

Check: join. Open Rust, press F1, then enter client.connect 176.119.169.227:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

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 Check: framework. Oxide (uMod) handles plugins.
modded
Modded Check: category. Modded, because plugins or settings alter the game.

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.