RUST METRICSFlight deck · live data
Data live Servers11,686 Players34,855 Populated2,843 Fresh wipes 3 h96 Scan5 min
‹ All servers31.208.58.48:28031
Offline Full Queue Fresh wipe Wipe due No query

Local protocol reference

Offline 31.208.58.48:28031 checked 21d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 0 /1

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,966top 72%
Last wipe21d 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
15k10k15k20k6 Oct8 Oct9 Oct11 Oct12 Oct14 Oct

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

No hourly players around its wipes yet.

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 7 Oct, 08:28 UTC21d 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 happens on Local protocol reference when wipe day comes?

At their busiest, its recent wipes drew 0 players on average. After the latest wipe, numbers topped out at 0 hours.

When does Local protocol reference wipe?

To tell the rhythm of Local protocol reference, 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 21 days 18 hours ago.

Tag meanings

How should you read the tags on Local protocol reference?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp1 (Max players): 1 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166652 (Build): Build 166652; ptsw (Networking): It runs on the 'sw' network layer; $r? (Region code): The region field is empty from Local protocol reference. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show Local protocol reference?

On Rust Metrics, Local protocol reference sits in these lists: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player count

Where does Local protocol reference sit in the rankings?

Player hours over seven days put Local protocol reference at #15,966, in the top 72% of all ranked servers.

What is the population on Local protocol reference?

Local protocol reference is not responding; status offline, last seen 21 days 18 hours ago.

Operator and location

What location is Local protocol reference hosted in?

No region comes from Local protocol reference. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 31.208.58.48:28031.

What Rust version is Local protocol reference on?

Rust network protocol 2634 and build 166652 on Linux is the build Local protocol reference runs. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on Local protocol reference, and is it online?

Check: connection. Local protocol reference is offline at this moment. Last contact was 21 days 18 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 6 October 2026.

Settings and map

How is Local protocol reference configured, and what rules are in force?

Reading the name gives no gather rate for Local protocol reference. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is off.

Which map is live on Local protocol reference?

Procedural map on Local protocol reference, made by the game's generator.

Join

How can you get onto Local protocol reference?

To join: start Rust, press F1 and type client.connect 31.208.58.48:28031. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp1,ptsw,$r?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp1
Max players 1 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166652
Build Build 166652.
ptsw
Networking It runs on the 'sw' network layer.
$r?
Region code The region field is empty.

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.