RUST METRICSFlight deck · live data
Data live Servers11,621 Players32,314 Populated2,788 Fresh wipes 3 h65 Scan5 min
‹ All servers109.41.179.12:28035
Offline Full Queue Fresh wipe Wipe due No query

Metro v3 test (local)

Offline 109.41.179.12:28035 checked 18d ago

COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 1 2 3 4 PAX 0 /4

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,883top 72%
Last wipe18d 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
15k10k15k20k10 Oct11 Oct13 Oct14 Oct16 Oct17 Oct

Top 72% 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 peak0players, last three wipes

The first 48 hours of its last wipes

No hourly players around its wipes yet.

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 10 Oct, 17:33 UTC18d ago 0 – running 0

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 Metro v3 test (local)?

At their busiest, its recent wipes drew 0 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

When does Metro v3 test (local) wipe?

To tell the rhythm of Metro v3 test (local), too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 18 days 11 hours ago.

Tags

Which tags does Metro v3 test (local) carry, and what do they mean?

Tags published by Metro v3 test (local), read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp4 (Max players): 4 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167398 (Build): Build 167398; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Metro v3 test (local) appear in Rust Metrics lists and filters?

These Rust Metrics lists carry Metro v3 test (local): 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.

Population

Where does Metro v3 test (local) sit in the rankings?

Player hours over seven days put Metro v3 test (local) at #15,883, in the top 72% of all ranked servers.

What player count does Metro v3 test (local) carry?

Metro v3 test (local) is not responding; status offline, last seen 18 days 11 hours ago.

Operator and location

Where does Metro v3 test (local) sit?

No region comes from Metro v3 test (local). Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 109.41.179.12:28035.

What Rust version is Metro v3 test (local) on?

Reading: Metro v3 test (local), Rust network protocol 2634 and build 167398, Windows. Check: protocol. To join, your game must match; Steam handles the update.

Is Metro v3 test (local) up, and how often does it stay up?

Metro v3 test (local) reports offline. The last reading came 18 days 11 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 10 October 2026, recorded by Rust Metrics.

Map and rules

What settings and rules apply on Metro v3 test (local)?

No gather rate appears in the name: Metro v3 test (local). 8 players per group, the default value. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.

Connection

What do you do to join Metro v3 test (local)?

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

PLACARDS

Server tags

what each one means

Published as mp4,ptrak,$r?,v2634,gmrust,cs167398,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp4
Max players 4 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167398
Build Build 167398.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.