RUST METRICSFlight deck · live data
Data live Servers11,841 Players77,907 Populated3,836 Fresh wipes 3 h157 Scan5 min
‹ All servers153.66.255.60:28015
Offline Full Queue Fresh wipe Wipe due No query

RustDockerServer

Offline 153.66.255.60:28015 checked 37d ago

COM 1 · connect

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,495no region published
Last wipe336d 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
15k10k15k20k20 Sep21 Sep23 Sep24 Sep26 Sep27 Sep
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 RustDockerServer follow?

Its rhythm cannot be told from the wipes of RustDockerServer on record: there are too few. 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 336 days 18 hours ago.

Tags

How should you read the tags on RustDockerServer?

These are the tags RustDockerServer publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2604 (Protocol): Your game must run protocol 2604 to get in; cs136664 (Build): Game build reading: 136664; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does RustDockerServer appear in Rust Metrics lists and filters?

These Rust Metrics lists carry RustDockerServer: 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

Where does RustDockerServer sit in the rankings?

Player hours over seven days put RustDockerServer at #15,495, in the top – of all ranked servers.

What is the population on RustDockerServer?

Reading for RustDockerServer: offline at this moment; last seen 37 days 19 hours ago.

Server details

Where does RustDockerServer sit?

Reading: location. RustDockerServer 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 153.66.255.60:28015.

What Rust version is RustDockerServer on?

Rust network protocol 2604 and build 136664 on Linux is the build RustDockerServer runs. To get in, your game needs the same protocol; Steam applies the update.

How reliable is RustDockerServer, and is it online now?

Check: connection. RustDockerServer is offline at this moment. Last contact was 37 days 19 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 19 September 2026.

Settings and map

How is RustDockerServer configured, and what rules are in force?

Reading the name gives no gather rate for RustDockerServer. 8 players per group, the default value. The mode is survival. Note the following: standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

Which map is live on RustDockerServer?

Check: map. Procedural, generated by the game, on RustDockerServer.

Join

What do you do to join RustDockerServer?

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

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2604,gmrust,cs136664,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players 10 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2604
Protocol Your game must run protocol 2604 to get in.
cs136664
Build Game build reading: 136664.
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.