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

Server_217_DevBlog

Offline 5.227.44.219:28015 checked 40d 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,400no region published
Last wipe134d 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 Sep23 Sep24 Sep25 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

What wipe timing does Server_217_DevBlog follow?

The rhythm of Server_217_DevBlog's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 134 days 6 hours ago.

Tag meanings

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

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; v2183 (Protocol): Your game must run protocol 2183 to get in; oxide (Oxide): Check: framework. Oxide (uMod) handles plugins; modded (Modded): Check: category. Modded, because plugins or settings alter the 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 from Server_217_DevBlog. 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?

These Rust Metrics lists carry Server_217_DevBlog: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded.

Population

Where does Server_217_DevBlog sit in the rankings?

Player hours over seven days put Server_217_DevBlog at #15,400, in the top – of all ranked servers.

How full does Server_217_DevBlog get?

Server_217_DevBlog is not responding; status offline, last seen 40 days 8 hours ago.

Server

Where does Server_217_DevBlog sit?

Reading: location. Server_217_DevBlog gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 5.227.44.219: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.

Is Server_217_DevBlog up, and how often does it stay up?

Reading: offline. Server_217_DevBlog last answered 40 days 8 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 18 September 2026, recorded by Rust Metrics.

Map and rules

What settings and rules apply on Server_217_DevBlog?

Reading the name gives no gather rate for Server_217_DevBlog. No group limit is published. The mode is survival. Note the following: the normal game: build, gather, raid. 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?

The game generates a procedural map for Server_217_DevBlog.

Connection

What do you do to join Server_217_DevBlog?

To join: start Rust, press F1 and type client.connect 5.227.44.219:28015. Or press Launch Rust here and Steam opens the game 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 10 slots in total.
v2183
Protocol Your game must run protocol 2183 to get in.

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