RUST METRICSFlight deck · live data
Data live Servers11,657 Players49,583 Populated3,193 Fresh wipes 3 h104 Scan5 min
‹ All servers80.187.74.12:28015
Offline Full Queue Fresh wipe Wipe due No query

Local Test

Offline 80.187.74.12:28015 checked 39d ago

moddedcarbon
COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.5 1 1.5 2 PAX 0 /2

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,382no region published
Last wipe39d 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 Sep24 Sep25 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 Local Test wipe, and when?

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

Lists and filters

How should you read the tags on Local Test?

These are the tags Local Test publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp2 (Max players): Slots: 2; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs164530 (Build): Game build reading: 164530; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; ^y (Carbon): Plugin framework in use: Carbon. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

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

These Rust Metrics lists carry Local Test: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Occupancy

Where does Local Test sit in the rankings?

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

How full does Local Test get?

Local Test is not responding; status offline, last seen 39 days 19 hours ago.

Server details

Where does Local Test sit?

No region tag on Local Test. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 80.187.74.12:28015.

What Rust version is Local Test on?

Reading: Local Test, Rust network protocol 2633 and build 164530, Windows. Matching protocol is required to join. Let Steam update your game.

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

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

Map and rules

What rules does Local Test enforce, and what are its settings?

Reading the name gives no gather rate for Local Test. 8 players per group, the default value. 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. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Carbon of them. Anti-cheat reading: VAC on, Valve's system.

What map is Local Test on?

The game generates a procedural map for Local Test.

Join

How do you connect to Local Test?

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

PLACARDS

Server tags

what each one means

Published as mp2,ptrak,$r?,v2633,gmrust,cs164530,ts8,^z,^y

Game

gmrust
Game mode The game mode is plain Rust survival.
mp2
Max players Slots: 2.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Protocol 2633: join only on the same game version.
cs164530
Build Game build reading: 164530.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

Mods and access

^z
Modded Check: category. Modded, because plugins or settings alter the game.
^y
Carbon Plugin framework in use: Carbon.

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.