RUST METRICSFlight deck · live data
Data live Servers11,652 Players47,233 Populated3,140 Fresh wipes 3 h109 Scan5 min
‹ All servers194.9.118.64:28015
Offline Full Queue Fresh wipe Wipe due No query

MY RUST STAGING TEST

Offline 194.9.118.64:28015 checked 30d ago

COM 1 · connect
Launch Rust and join

Server instruments

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

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#16,970top 71%
Last wipe30d 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
15k10k15k20k24 Sep26 Sep28 Sep1 Oct3 Oct5 Oct

Top 71% 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 peak1players, 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 1, 1 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 28 Sep, 14:58 UTC30d ago 1 – 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

Reset cycle

What happens on MY RUST STAGING TEST when wipe day comes?

At their busiest, its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 1 hours.

How often does MY RUST STAGING TEST wipe, and when?

To tell the rhythm of MY RUST STAGING TEST, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 30 days 18 hours ago the current world was made.

Tags

How should you read the tags on MY RUST STAGING TEST?

These are the tags MY RUST STAGING TEST publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp5 (Max players): The server holds 5 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166040 (Build): Build 166040; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show MY RUST STAGING TEST?

Rust Metrics lists featuring MY RUST STAGING 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.

Occupancy

Where does MY RUST STAGING TEST sit in the rankings?

Ranking for MY RUST STAGING TEST: #16,970 on seven-day player hours, top 71% of all ranked servers.

What player count does MY RUST STAGING TEST carry?

MY RUST STAGING TEST is not responding; status offline, last seen 30 days 16 hours ago.

Operator and location

What location is MY RUST STAGING TEST hosted in?

Reading: location. MY RUST STAGING TEST gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 194.9.118.64:28015.

What Rust version is MY RUST STAGING TEST on?

Version check: Rust network protocol 2634 and build 166040 on Windows, run by MY RUST STAGING TEST. To get in, your game needs the same protocol; Steam applies the update.

How reliable is MY RUST STAGING TEST, and is it online now?

Check: connection. MY RUST STAGING TEST is offline at this moment. Last contact was 30 days 16 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 24 September 2026, recorded by Rust Metrics.

Rules and settings

How is MY RUST STAGING TEST configured, and what rules are in force?

No gather rate appears in the name: MY RUST STAGING TEST. 8 players per group, the default value. Mode check gives survival; gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.

What map is MY RUST STAGING TEST on?

Procedural map on MY RUST STAGING TEST, made by the game's generator.

Connection

What do you do to join MY RUST STAGING TEST?

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

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp5
Max players The server holds 5 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166040
Build Build 166040.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.