RUST METRICSFlight deck · live data
Data live Servers11,834 Players76,849 Populated3,824 Fresh wipes 3 h147 Scan5 min
‹ All servers176.52.78.213:28015
Offline Full Queue Fresh wipe Wipe due No query

Devblog 260 Local

Offline 176.52.78.213:28015 checked 31d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 0 /50

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#16,730top 71%
Last wipe31d 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
15k10k15k20k26 Sep27 Sep29 Sep30 Sep2 Oct3 Oct

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

When does Devblog 260 Local wipe?

To tell the rhythm of Devblog 260 Local, too few of its wipes are on record. 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 31 days 7 hours ago.

Lists and filters

How should you read the tags on Devblog 260 Local?

Tags published by Devblog 260 Local, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): Build 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Devblog 260 Local appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Devblog 260 Local: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Player count

What position does Devblog 260 Local hold among Rust servers?

Ranking for Devblog 260 Local: #16,730 on seven-day player hours, top 71% of all ranked servers.

What is the population on Devblog 260 Local?

Status for Devblog 260 Local: offline. Last seen 31 days 7 hours ago.

Operator and location

Which location does Devblog 260 Local run from?

No region tag on Devblog 260 Local. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 176.52.78.213:28015.

What Rust version is Devblog 260 Local on?

Reading: Devblog 260 Local, Rust network protocol 2633 and build 165217, Windows. Matching protocol is required to join. Let Steam update your game.

What is the uptime on Devblog 260 Local, and is it online?

Reading: offline. Devblog 260 Local last answered 31 days 7 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 26 September 2026.

Settings and map

What settings and rules apply on Devblog 260 Local?

Check: gather rate. The name Devblog 260 Local does not state one. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Oxide of them. Anti-cheat reading: VAC on, Valve's system.

Which map is live on Devblog 260 Local?

Procedural map on Devblog 260 Local, made by the game's generator.

How to join

How do you connect to Devblog 260 Local?

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

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2633,gmrust,cs165217,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players The server holds 50 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Your game must run protocol 2633 to get in.
cs165217
Build Build 165217.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Check: category. Modded, because plugins or settings alter the game.

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.