RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h83 Scan5 min
‹ All servers158.120.182.9:28015
Offline Full Queue Fresh wipe Wipe due No query

Justin+mctester's Rust

Offline 158.120.182.9:28015 checked 35d ago

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,473top 67%
Last wipe36d 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
15k10k15k20k22 Sep23 Sep25 Sep26 Sep28 Sep29 Sep

Top 67% 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

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 22 Sep, 19:50 UTC35d 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 timing

What happens on Justin+mctester's Rust when wipe day comes?

An average of 0 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 0 hours in.

How often does Justin+mctester's Rust wipe, and when?

The rhythm of Justin+mctester's Rust'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. The world it runs now was made 36 days 3 hours ago.

Tags

Which tags does Justin+mctester's Rust carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): Game build reading: 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set from Justin+mctester's Rust. 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 Justin+mctester's Rust?

Rust Metrics lists featuring Justin+mctester's Rust: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player count

Where does Justin+mctester's Rust sit in the rankings?

Ranking for Justin+mctester's Rust: #15,473 on seven-day player hours, top 67% of all ranked servers.

What is the population on Justin+mctester's Rust?

Reading for Justin+mctester's Rust: offline at this moment; last seen 35 days 19 hours ago.

Operator and location

What location is Justin+mctester's Rust hosted in?

No region comes from Justin+mctester's Rust. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 158.120.182.9:28015.

What Rust version is Justin+mctester's Rust on?

Rust network protocol 2633 and build 165217 on Windows is the build Justin+mctester's Rust runs. To get in, your game needs the same protocol; Steam applies the update.

How reliable is Justin+mctester's Rust, and is it online now?

Justin+mctester's Rust reports offline. The last reading came 35 days 19 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 22 September 2026, recorded by Rust Metrics.

Rules and settings

How is Justin+mctester's Rust configured, and what rules are in force?

Reading the name gives no gather rate for Justin+mctester's Rust. No limit is set beyond the default. Groups take up to 8 players. 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. Check: anti-cheat. VAC, Valve's system, is on.

What map is Justin+mctester's Rust on?

Check: map. Procedural, generated by the game, on Justin+mctester's Rust.

How to join

How can you get onto Justin+mctester's Rust?

To join: start Rust, press F1 and type client.connect 158.120.182.9: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?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players 10 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Your game must run protocol 2633 to get in.
cs165217
Build Game build reading: 165217.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.