RUST METRICSFlight deck · live data
Data live Servers11,644 Players37,516 Populated2,896 Fresh wipes 3 h65 Scan5 min
‹ All servers95.24.22.105:28015
Offline Full Queue Fresh wipe Wipe due No query

Solo Local Server

Offline 95.24.22.105:28015 checked 7d ago

COM 1 · connect

Server instruments

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

Players now

100% 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,059top 59%
Last wipe20d 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
15k10k15k20k7 Oct11 Oct15 Oct19 Oct23 Oct27 Oct

Top 59% 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
Wed 7 Oct, 08:42 UTC20d ago 1 – 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 timing

What happens on Solo Local Server when wipe day comes?

The busiest point of its recent wipes drew 1 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does Solo Local Server follow?

Its rhythm cannot be told from the wipes of Solo Local Server on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 20 days 18 hours ago.

Lists and filters

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

Tags published by Solo Local Server, read by the game's server browser: 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; cs166652 (Build): Build 166652; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. 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 Solo Local Server?

On Rust Metrics, Solo 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.

Population

Where does Solo Local Server sit in the rankings?

Player hours over seven days put Solo Local Server at #13,059, in the top 59% of all ranked servers.

How full does Solo Local Server get?

Status for Solo Local Server: offline. Last seen 7 days 16 hours ago.

Operator and location

Which location does Solo Local Server run from?

No region comes from Solo Local Server. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 95.24.22.105:28015.

What Rust version is Solo Local Server on?

Version check: Rust network protocol 2634 and build 166652 on Windows, run by Solo Local Server. Matching protocol is required to join. Let Steam update your game.

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

Solo Local Server reports offline. The last reading came 7 days 16 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 7 October 2026.

Map and rules

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

Reading the name gives no gather rate for Solo Local Server. The group cap is 8 players, which is the default in the game. survival, gather, build and raid, as the game normally runs — that is the game mode. 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.

Connection

How can you get onto Solo Local Server?

Press F1 in Rust and enter client.connect 95.24.22.105: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 mp1,ptrak,$r?,v2634,gmrust,cs166652,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.
cs166652
Build Build 166652.
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.