RUST METRICSFlight deck · live data
Data live Servers11,765 Players73,690 Populated3,473 Fresh wipes 3 h229 Scan5 min
‹ All servers86.120.190.179:28015
Offline Full Queue Fresh wipe Wipe due No query

My Local Server

Offline 86.120.190.179:28015 checked 16d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.8 1.5 2.2 3 PAX 1 /3

Players now

33% 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#13,219top 61%
Last wipe17d 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
15k10k15k20k8 Oct10 Oct13 Oct15 Oct18 Oct20 Oct

Top 61% 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.

usual gap3.6 daysbetween real wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Mon 12 OctThu 8 Oct
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
Mon 12 Oct, 07:14 UTC17d ago 1 – running 1
Thu 8 Oct, 15:54 UTC21d ago 1 held half 3.6 days 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

Wipe schedule

What should you expect from wipe day on My Local Server?

At their busiest, its recent wipes drew 1 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.

How often does My Local Server wipe, and when?

Its rhythm cannot be told from the wipes of My Local Server on record: there are too few. 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 17 days 15 hours ago.

Tags

How should you read the tags on My Local Server?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp3 (Max players): 3 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167398 (Build): Build 167398; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty from My Local Server. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show My Local Server?

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.

Player count

What position does My Local Server hold among Rust servers?

Ranking for My Local Server: #13,219 on seven-day player hours, top 61% of all ranked servers.

What player count does My Local Server carry?

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

Server

Where does My Local Server sit?

No region tag on My Local Server. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 86.120.190.179:28015.

What Rust version is My Local Server on?

Reading: My Local Server, Rust network protocol 2634 and build 167398, Windows. Matching protocol is required to join. Let Steam update your game.

What is the uptime on My Local Server, and is it online?

Reading: offline. My Local Server last answered 16 days 12 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 8 October 2026, recorded by Rust Metrics.

Settings and map

What rules does My Local Server enforce, and what are its settings?

Reading the name gives no gather rate for My Local Server. 8 players per group, the default value. survival, gather, build and raid, as the game normally runs — that is the game mode. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Anti-cheat reading: VAC off, Valve's system.

Which map is live on My Local Server?

Check: map. Procedural, generated by the game, on My Local Server.

Connection

How do you connect to My Local Server?

Press F1 in Rust and enter client.connect 86.120.190.179:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp3,ptrak,$r?,v2634,gmrust,cs167398,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp3
Max players 3 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167398
Build Build 167398.
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.