RUST METRICSFlight deck · live data
Data live Servers11,800 Players69,961 Populated3,675 Fresh wipes 3 h123 Scan5 min
‹ All servers5.167.146.254:28015
Offline Full Queue Fresh wipe Wipe due No query

0x666

Offline 5.167.146.254:28015 checked 26d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 0 /50

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#14,555top 64%
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, measured since 29 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k29 Sep1 Oct3 Oct5 Oct7 Oct9 Oct

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

No hourly players around its wipes yet.

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 16:21 UTC26d 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 0x666 when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does 0x666 follow?

The rhythm of 0x666'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. 26 days 5 hours ago the current world was made.

Lists and filters

Which tags does 0x666 carry, and what do they mean?

These are the tags 0x666 publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166586 (Build): The server runs game build 166586; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. 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 0x666?

On Rust Metrics, 0x666 sits in these lists: 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.

Population

What position does 0x666 hold among Rust servers?

Player hours over seven days put 0x666 at #14,555, in the top 64% of all ranked servers.

What is the population on 0x666?

Status for 0x666: offline. Last seen 26 days 4 hours ago.

Server details

What location is 0x666 hosted in?

Reading: location. 0x666 gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 5.167.146.254:28015.

What Rust version is 0x666 on?

Rust network protocol 2634 and build 166586 on Windows is the build 0x666 runs. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on 0x666, and is it online?

Reading: offline. 0x666 last answered 26 days 4 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 29 September 2026.

Rules and settings

What settings and rules apply on 0x666?

Check: gather rate. The name 0x666 does not state one. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. VAC is off. That is Valve's anti-cheat.

Which map is live on 0x666?

Check: map. Procedural, size 4,500, seed 1073017936, generated by the game on 0x666. View it on RustMaps from this page: matching size and seed give an identical map.

Connection

What do you do to join 0x666?

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

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players The server holds 50 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166586
Build The server runs game build 166586.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

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.