RUST METRICSFlight deck · live data
Data live Servers11,744 Players73,772 Populated3,676 Fresh wipes 3 h140 Scan5 min
‹ All servers188.26.76.159:28015
Offline Full Queue Fresh wipe Wipe due No query

My Local Server

Offline 188.26.76.159:28015 checked 29d ago

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#16,921top 71%
Last wipe32d 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
15k10k15k20k25 Sep27 Sep29 Sep1 Oct3 Oct5 Oct

Top 71% 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 peak1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 25 Sep, 22:47 UTC32d ago 1 – running 1

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 should you expect from wipe day on My Local Server?

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

When does My Local Server wipe?

To tell the rhythm of My Local Server, 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 in play was created 32 days 14 hours ago.

Tag meanings

Which tags does My Local Server carry, and what do they mean?

These are the tags My Local Server publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): 10 slots in total; 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): The server runs game build 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does My Local Server appear in Rust Metrics lists and filters?

These Rust Metrics lists carry My Local Server: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Occupancy

What position does My Local Server hold among Rust servers?

Player hours over seven days put My Local Server at #16,921, in the top 71% of all ranked servers.

What is the population on My Local Server?

Status for My Local Server: offline. Last seen 29 days 12 hours ago.

Operator and location

Where does My Local Server sit?

No region tag on My Local Server. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 188.26.76.159:28015.

What Rust version is My Local Server on?

Rust network protocol 2633 and build 165217 on Windows is the build My Local Server runs. Check: protocol. To join, your game must match; Steam handles the update.

Is My Local Server up, and how often does it stay up?

My Local Server reports offline. The last reading came 29 days 12 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 25 September 2026.

Settings and map

What settings and rules apply on My Local Server?

Check: gather rate. The name My Local Server does not state one. The group cap is 8 players, which is the default in the game. survival, the normal game: build, gather, raid — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. VAC is off. That is Valve's anti-cheat.

What map is My Local Server on?

The game generates a procedural map for My Local Server.

How to join

How do you connect to My Local Server?

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

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players 10 slots in total.
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 The server runs game build 165217.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.