Rust Server TrendsSeismic network · station log
Recording Stations11,720 Players57,954 Active3,334 Wipes · 3 h174 48 h

Station XX-15966 · no signal

Local protocol reference

Offline 31.208.58.48:28031 checked 22d ago

Connect
Players now
0/ 1
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,966
top 72%
Last wipe
22d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15966 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 1 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

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.

Channel 3 · rank movement

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.

Expected events

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 peak
0players, 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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Wed 7 Oct, 08:28 UTC22d ago M0.0steady 0 – – running 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 519 on average
421/ 400
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 319 on average
339/ 350
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 291 on average
34/ 250
Rustoria.co - EU Main EU · groups of 16+ · weekly · 276 on average
29/ 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 275 on average
51/ 100
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 244 on average
145/ 200
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on Local protocol reference?

Local protocol reference uses a procedural map, which the game generates.

Which settings and rules apply on Local protocol reference?

The name of Local protocol reference gives no gather rate. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. It is a community server, and the browser lists it under Community. Anti-cheat is off: VAC, from Valve.

Population

How many players are recorded on Local protocol reference right now?

No players are recorded on Local protocol reference at this moment; it is offline, and the last sighting was 22 days 1 hours ago.

How does Local protocol reference rank against other Rust servers?

The last seven days of player hours place Local protocol reference at #15,966, in the top 72% of all ranked servers.

Operator and location

How reliably does Local protocol reference stay online?

As recorded now, Local protocol reference is not reachable, the last contact having been 22 days 1 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. On 6 October 2026 it was recorded for the first time by Rust Server Trends.

Which region does Local protocol reference run from?

Nothing about a region comes from Local protocol reference. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 31.208.58.48:28031.

What build of Rust does Local protocol reference use?

Local protocol reference is running Rust network protocol 2634 and build 166652 on a machine with Linux. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe day

What does wipe day look like on Local protocol reference?

The recent wipes averaged a busiest count of 0 players. 0 hours after the latest wipe, the crowd peaked.

How often does Local protocol reference wipe, and on which days?

On record so far are too few of Local protocol reference's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. It has run its current world for 22 days 1 hours.

Server tags

What do the server tags on Local protocol reference mean?

Tags published by Local protocol reference and read by the game's server browser include gmrust (Game mode): The game mode is standard Rust survival; mp1 (Max players): The server has 1 slots; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs166652 (Build): The game build is 166652; ptsw (Networking): You'll see 'sw' as the network layer; $r? (Region code): The server has no region code. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does Local protocol reference appear?

The Rust Server Trends lists that take in Local protocol reference are: Rust community servers without the side modes. You will find it under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Join the server

How do you connect to Local protocol reference?

You can connect by pressing F1 in Rust and typing client.connect 31.208.58.48:28031 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is standard Rust survival.
mp1
Max players The server has 1 slots.
ts8
Group limit Teams max out at 8, the default set by the game.
v2634
Protocol Game protocol 2634: to join, your game must match this version.
cs166652
Build The game build is 166652.
ptsw
Networking You'll see 'sw' as the network layer.
$r?
Region code The server has no region code.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.