RUST METRICSFlight deck · live data
Data live Servers11,656 Players41,553 Populated2,988 Fresh wipes 3 h90 Scan5 min
‹ All servers24.71.188.185:28015
Offline Full Queue Fresh wipe Wipe due No query

Local Test Server

Offline 24.71.188.185:28015 checked 41d ago

moddedoxide
COM 1 · connect
Launch Rust and join

Server instruments

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

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,514no region published
Last wipe69d 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 Sep23 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 schedule

What wipe timing does Local Test Server follow?

The rhythm of Local Test 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. 69 days 1 hours ago the current world was made.

Tags

How should you read the tags on Local Test Server?

These are the tags Local Test Server publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): Slots: 10; ts8 (Group limit): Default limit in force: 8 per team; v2632 (Protocol): Protocol 2632: join only on the same game version; cs161125 (Build): Build 161125; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. 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 Local Test Server?

Rust Metrics lists featuring Local Test Server: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Population

What position does Local Test Server hold among Rust servers?

Ranking for Local Test Server: #15,514 on seven-day player hours, top – of all ranked servers.

What player count does Local Test Server carry?

Status for Local Test Server: offline. Last seen 41 days 4 hours ago.

Operator and location

What location is Local Test Server hosted in?

Reading: location. Local Test Server gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 24.71.188.185:28015.

What Rust version is Local Test Server on?

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

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

Check: connection. Local Test Server is offline at this moment. Last contact was 41 days 4 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 16 September 2026.

Settings and map

What settings and rules apply on Local Test Server?

Check: gather rate. The name Local Test Server does not state one. 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. The server browser lists it as Modded, where plugins or settings change how the game plays. Oxide plugins are running. VAC is on. That is Valve's anti-cheat.

What map is Local Test Server on?

Procedural map on Local Test Server, made by the game's generator.

Connection

What do you do to join Local Test Server?

To join: start Rust, press F1 and type client.connect 24.71.188.185: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?,v2632,gmrust,cs161125,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players Slots: 10.
ts8
Group limit Default limit in force: 8 per team.
v2632
Protocol Protocol 2632: join only on the same game version.
cs161125
Build Build 161125.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Check: category. Modded, because plugins or settings alter the game.

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.