RUST METRICSFlight deck · live data
Data live Servers11,795 Players71,386 Populated3,684 Fresh wipes 3 h118 Scan5 min
‹ All servers82.67.176.179:28015
Offline Full Queue Fresh wipe Wipe due No query

test | SOLO ONLY | VANILLA

Offline 82.67.176.179:28015 checked 22d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 50 100 150 200 PAX 0 /200

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,998top 71%
Last wipe22d 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
15k10k15k20k6 Oct7 Oct9 Oct10 Oct12 Oct13 Oct

Top 71% of all ranked servers. Ranked on player hours over the last seven days.

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 schedule

What wipe timing does test | SOLO ONLY | VANILLA follow?

To tell the rhythm of test | SOLO ONLY | VANILLA, 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. 22 days 4 hours ago the current world was made.

Tags

Which tags does test | SOLO ONLY | VANILLA carry, and what do they mean?

Tags published by test | SOLO ONLY | VANILLA, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp200 (Max players): The server holds 200 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166652 (Build): Game build reading: 166652; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $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 test | SOLO ONLY | VANILLA appear in Rust Metrics lists and filters?

Rust Metrics lists featuring test | SOLO ONLY | VANILLA: 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 test | SOLO ONLY | VANILLA sit in the rankings?

Ranking for test | SOLO ONLY | VANILLA: #15,998 on seven-day player hours, top 71% of all ranked servers.

What player count does test | SOLO ONLY | VANILLA carry?

Reading for test | SOLO ONLY | VANILLA: offline at this moment; last seen 22 days 4 hours ago.

Operator and location

Where does test | SOLO ONLY | VANILLA sit?

Reading: location. test | SOLO ONLY | VANILLA gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 82.67.176.179:28015.

What Rust version is test | SOLO ONLY | VANILLA on?

Rust network protocol 2634 and build 166652 on Windows is the build test | SOLO ONLY | VANILLA runs. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on test | SOLO ONLY | VANILLA, and is it online?

Check: connection. test | SOLO ONLY | VANILLA is offline at this moment. Last contact was 22 days 4 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 6 October 2026.

Settings and map

How is test | SOLO ONLY | VANILLA configured, and what rules are in force?

Reading the name gives no gather rate for test | SOLO ONLY | VANILLA. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.

Which map is live on test | SOLO ONLY | VANILLA?

Check: map. Procedural, generated by the game, on test | SOLO ONLY | VANILLA.

Connection

How do you connect to test | SOLO ONLY | VANILLA?

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

PLACARDS

Server tags

what each one means

Published as mp200,ptrak,$r?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp200
Max players The server holds 200 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166652
Build Game build reading: 166652.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.