RUST METRICSFlight deck · live data
Data live Servers11,672 Players34,284 Populated2,842 Fresh wipes 3 h85 Scan5 min
‹ All servers31.207.159.110:28015
Offline Full Queue Fresh wipe Wipe due No query

Solo Local Server

Offline 31.207.159.110:28015 checked 18d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 1.2 2.5 3.8 5 PAX 1 /5

Players now

20% 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,618top 62%
Last wipe19d 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
15k10k15k20k9 Oct11 Oct12 Oct14 Oct15 Oct17 Oct

Top 62% 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 9 Oct, 20:34 UTC19d 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 Solo 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.

When does Solo Local Server wipe?

The rhythm of Solo Local Server's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 19 days 6 hours ago the current world was made.

Tags

How should you read the tags on Solo Local Server?

Tags published by Solo Local Server, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp5 (Max players): 5 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167398 (Build): The server runs game build 167398; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

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

These Rust Metrics lists carry Solo 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.

Population

What position does Solo Local Server hold among Rust servers?

Ranking for Solo Local Server: #13,618 on seven-day player hours, top 62% of all ranked servers.

How full does Solo Local Server get?

Status for Solo Local Server: offline. Last seen 18 days 15 hours ago.

Server

Which location does Solo Local Server run from?

No region tag on Solo Local Server. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 31.207.159.110:28015.

What Rust version is Solo Local Server on?

Version check: Rust network protocol 2634 and build 167398 on Windows, run by Solo Local Server. To get in, your game needs the same protocol; Steam applies the update.

How reliable is Solo Local Server, and is it online now?

Check: connection. Solo Local Server is offline at this moment. Last contact was 18 days 15 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 9 October 2026.

Rules and settings

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

No gather rate appears in the name: Solo Local Server. The group cap is 8 players, which is the default in the game. Mode check gives survival; 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. Anti-cheat reading: VAC on, Valve's system.

Join

How can you get onto Solo Local Server?

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

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp5
Max players 5 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167398
Build The server runs game build 167398.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

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.