RUST METRICSFlight deck · live data
Data live Servers11,737 Players52,840 Populated3,354 Fresh wipes 3 h124 Scan5 min
‹ All servers67.255.194.124:28015
Offline Full Queue Fresh wipe Wipe due No query

12Gauge_Test

Offline 67.255.194.124:28015 checked 26d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 1.2 2.5 3.8 5 PAX 1 /5

Players now

20% 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,353top 63%
Last wipe26d 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
15k10k15k20k2 Oct3 Oct5 Oct6 Oct8 Oct9 Oct

Top 63% 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 peak2players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 2, 2 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 20:45 UTC26d ago 2 – 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 12Gauge_Test?

At their busiest, its recent wipes drew 2 players on average. Peak crowd on the latest wipe: 2 hours in.

How often does 12Gauge_Test wipe, and when?

Its rhythm cannot be told from the wipes of 12Gauge_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. The world in play was created 26 days 2 hours ago.

Tag meanings

How should you read the tags on 12Gauge_Test?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp5 (Max players): The server holds 5 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166586 (Build): Game build reading: 166586; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set from 12Gauge_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 12Gauge_Test?

Rust Metrics lists featuring 12Gauge_Test: 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 12Gauge_Test sit in the rankings?

Player hours over seven days put 12Gauge_Test at #14,353, in the top 63% of all ranked servers.

What is the population on 12Gauge_Test?

Reading for 12Gauge_Test: offline at this moment; last seen 26 days ago.

Operator and location

Where does 12Gauge_Test sit?

Reading: location. 12Gauge_Test gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 67.255.194.124:28015.

What Rust version is 12Gauge_Test on?

Version check: Rust network protocol 2634 and build 166586 on Windows, run by 12Gauge_Test. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on 12Gauge_Test, and is it online?

12Gauge_Test reports offline. The last reading came 26 days ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 2 October 2026.

Settings and map

What rules does 12Gauge_Test enforce, and what are its settings?

Check: gather rate. The name 12Gauge_Test does not state one. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.

Which map is live on 12Gauge_Test?

Check: map. Procedural, generated by the game, on 12Gauge_Test.

Connection

What do you do to join 12Gauge_Test?

Check: join. Open Rust, press F1, then enter client.connect 67.255.194.124:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp5,ptrak,$r?,v2634,gmrust,cs166586,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp5
Max players The server holds 5 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166586
Build Game build reading: 166586.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.