RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h50 Scan5 min
‹ All servers141.105.140.3:28015
Offline Full Queue Fresh wipe Wipe due No query

Solo Local Server

Offline 141.105.140.3:28015 checked 21d 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#14,631top 66%
Last wipe21d 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 Oct8 Oct10 Oct11 Oct13 Oct14 Oct

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

No hourly players around its wipes yet.

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, 09:13 UTC21d 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

Wipe schedule

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

An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 0 hours in.

What wipe timing does Solo Local Server follow?

The rhythm of Solo Local Server's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 21 days 9 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; mp1 (Max players): 1 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166652 (Build): Game build reading: 166652; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none 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. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player count

Where does Solo Local Server sit in the rankings?

Ranking for Solo Local Server: #14,631 on seven-day player hours, top 66% of all ranked servers.

What player count does Solo Local Server carry?

Solo Local Server is not responding; status offline, last seen 21 days 9 hours ago.

Operator and location

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. The endpoint you need is 141.105.140.3: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. To get in, your game needs the same protocol; Steam applies the update.

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

Check: connection. Solo Local Server is offline at this moment. Last contact was 21 days 9 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 7 October 2026.

Map and rules

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

Check: gather rate. The name Solo Local Server does not state one. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

How to join

What do you do to join Solo Local Server?

To join: start Rust, press F1 and type client.connect 141.105.140.3: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,cs166652,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp1
Max players 1 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166652
Build Game build reading: 166652.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none 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.