RUST METRICSFlight deck · live data
Data live Servers11,756 Players64,636 Populated3,440 Fresh wipes 3 h196 Scan5 min
‹ All servers188.169.142.192:28015
Offline Full Queue Fresh wipe Wipe due No query

0x666

Offline 188.169.142.192:28015 checked 15d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 25 50 75 100 PAX 1 /100

Players now

1% 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#13,136top 61%
Last wipe27d 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 21 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
15k10k15k20k20 Sep26 Sep2 Oct8 Oct14 Oct20 Oct

Top 61% 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.

usual gap10.1 daysbetween real wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Thu 1 OctMon 21 Sep
00.511.52+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 20:38 UTC FW27d ago 1 – running 0
Mon 21 Sep, 18:42 UTC37d ago 2 halved by day 1 10.1 days 1

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 0x666?

An average of 2 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 0 hours. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. It fell below half by day 1 when it didn't.

What wipe timing does 0x666 follow?

To tell the rhythm of 0x666, 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. The world in play was created 27 days 15 hours ago.

Tag meanings

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

Tags published by 0x666, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): The server runs game build 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does 0x666 appear in Rust Metrics lists and filters?

On Rust Metrics, 0x666 sits in these lists: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Occupancy

What position does 0x666 hold among Rust servers?

Ranking for 0x666: #13,136 on seven-day player hours, top 61% of all ranked servers.

What is the population on 0x666?

Status for 0x666: offline. Last seen 15 days 18 hours ago.

Server

Where does 0x666 sit?

No region comes from 0x666. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 188.169.142.192:28015.

What Rust version is 0x666 on?

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

How reliable is 0x666, and is it online now?

Reading: offline. 0x666 last answered 15 days 18 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 17 September 2026.

Settings and map

What rules does 0x666 enforce, and what are its settings?

Reading the name gives no gather rate for 0x666. The group cap is 8 players, which is the default in the game. Mode check gives survival; the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Anti-cheat reading: VAC off, Valve's system.

Which map is live on 0x666?

Size 4,000 and seed 12345: the game generates the procedural map on 0x666 from them. View it on RustMaps from this page: matching size and seed give an identical map.

Join

How can you get onto 0x666?

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

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players The server holds 100 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167781
Build The server runs game build 167781.
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.