RUST METRICSFlight deck · live data
Data live Servers11,811 Players72,496 Populated3,745 Fresh wipes 3 h137 Scan5 min
‹ All servers158.46.51.68:28015
Offline Full Queue Fresh wipe Wipe due No query

My Local Server

Offline 158.46.51.68:28015 checked 7d 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,340top 69%
Last wipe7d 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
15k10k15k20k20 Oct21 Oct23 Oct24 Oct26 Oct27 Oct

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

01234+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
Tue 20 Oct, 00:34 UTC7d 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 happens on My Local Server when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 0 hours.

How often does My Local Server wipe, and when?

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 7 days 21 hours ago.

Tag meanings

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

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): Slots: 1; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): The server runs game build 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty from My Local Server. 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 My Local Server?

On Rust Metrics, My Local Server 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; Last wipe: In the last 2 weeks.

Population

What position does My Local Server hold among Rust servers?

Player hours over seven days put My Local Server at #15,340, in the top 69% of all ranked servers.

What player count does My Local Server carry?

Reading for My Local Server: offline at this moment; last seen 7 days 18 hours ago. Seven-day reading: 0 players on average.

Operator and location

What location is My Local Server hosted in?

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

What Rust version is My Local Server on?

Rust network protocol 2634 and build 167781 on Windows is the build My Local Server runs. To get in, your game needs the same protocol; Steam applies the update.

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

Check: connection. My Local Server is offline at this moment. Last contact was 7 days 18 hours ago. Reading: 0% uptime over the last 6 full days. It was up 0 of 144 hours. Reading: first seen 20 October 2026, recorded by Rust Metrics.

Settings and map

How is My Local Server configured, and what rules are in force?

Reading the name gives no gather rate for My Local Server. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.

Which map is live on My Local Server?

The game generates a procedural map for My Local Server.

Join

What do you do to join My Local Server?

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

PLACARDS

Server tags

what each one means

Published as mp1,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1
Max players Slots: 1.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167781
Build The server runs game build 167781.
ptrak
Networking This is RakNet, Rust's usual 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.