RUST METRICSFlight deck · live data
Data live Servers11,735 Players53,534 Populated3,365 Fresh wipes 3 h127 Scan5 min
‹ All servers112.213.162.243:28015
Offline Full Queue Fresh wipe Wipe due No query

Solo Local Test

Offline 112.213.162.243:28015 checked 43d 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,416no region published
Last wipe43d agono schedule published
Next wipe–no wipe 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 Sep21 Sep22 Sep
PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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

How often does Solo Local Test wipe, and when?

Its rhythm cannot be told from the wipes of Solo Local Test on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 43 days 11 hours ago the current world was made.

Tag meanings

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

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp1 (Max players): Slots: 1; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163794 (Build): Game build reading: 163794; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set from Solo Local Test. 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 Test?

These Rust Metrics lists carry Solo Local Test: 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

What position does Solo Local Test hold among Rust servers?

Player hours over seven days put Solo Local Test at #15,416, in the top – of all ranked servers.

How full does Solo Local Test get?

Reading for Solo Local Test: offline at this moment; last seen 43 days 9 hours ago.

Server

Which location does Solo Local Test run from?

Reading: location. Solo Local Test gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 112.213.162.243:28015.

What Rust version is Solo Local Test on?

Rust network protocol 2633 and build 163794 on Windows is the build Solo Local Test runs. Check: protocol. To join, your game must match; Steam handles the update.

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

Solo Local Test reports offline. The last reading came 43 days 9 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 15 September 2026, recorded by Rust Metrics.

Settings and map

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

Reading the name gives no gather rate for Solo Local Test. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on Solo Local Test?

Check: map. Procedural, generated by the game, on Solo Local Test.

Join

How do you connect to Solo Local Test?

To join: start Rust, press F1 and type client.connect 112.213.162.243: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?,v2633,gmrust,cs163794,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp1
Max players Slots: 1.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Protocol 2633: join only on the same game version.
cs163794
Build Game build reading: 163794.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.