RUST METRICSFlight deck · live data
Data live Servers11,617 Players35,650 Populated2,906 Fresh wipes 3 h67 Scan5 min
‹ All servers147.92.98.181:28015
Offline Full Queue Fresh wipe Wipe due No query

Local Test Server

Offline 147.92.98.181:28015 checked 44d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 1 /10

Players now

10% 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,550no region published
Last wipe50d 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
No rank history yet.
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

What wipe timing does Local Test Server follow?

Its rhythm cannot be told from the wipes of Local Test Server 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. 50 days 5 hours ago the current world was made.

Lists and filters

How should you read the tags on Local Test Server?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163794 (Build): Build 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set from Local Test Server. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

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

Rust Metrics lists featuring Local Test 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

Where does Local Test Server sit in the rankings?

Player hours over seven days put Local Test Server at #14,550, in the top – of all ranked servers.

What is the population on Local Test Server?

Reading for Local Test Server: offline at this moment; last seen 44 days 12 hours ago.

Server details

Which location does Local Test Server run from?

No region comes from Local Test Server. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 147.92.98.181:28015.

What Rust version is Local Test Server on?

Version check: Rust network protocol 2633 and build 163794 on Windows, run by Local Test Server. Check: protocol. To join, your game must match; Steam handles the update.

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

Local Test Server reports offline. The last reading came 44 days 12 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Settings and map

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

No gather rate appears in the name: Local Test Server. 8 players per group, the default value. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is off.

What map is Local Test Server on?

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

Join

What do you do to join Local Test Server?

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

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2633,gmrust,cs163794,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players 10 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Match the game version: protocol 2633 is required.
cs163794
Build Build 163794.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.