RUST METRICSFlight deck · live data
Data live Servers11,749 Players55,156 Populated3,381 Fresh wipes 3 h134 Scan5 min
‹ All servers70.237.29.165:28015
Online Full Queue Fresh wipe Wipe due No query

RustDockerServer

Online 70.237.29.165:28015 checked 8m ago

COM 1 · connect

Server instruments

last reading Wed 21:00 UTC
0 0.2 0.5 0.8 1 PAX 0 /1

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS 112 SERVER FPS

Server fps

48 h low 95 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 121,231 ×1000

Entities

48 h range 118,870–121,769 · memory 3,053 MB
1239 ET SINCE RESTART 11:55

Uptime

11 h 55 min since its last restart, at the last reading
7-day average0peak –
Rank#15,344top 69%
Last wipe26d agono schedule published
Next wipe–too few wipes seen yet
Memory3,053MBat the last reading
REC 1

Players

AveragePeak
0123400:0009:0018:0002:0011:0021:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020000:0009:0018:0002:0011:0021:00

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 17 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 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 69% 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
Fri 2 Oct, 09:14 UTC26d 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

Reset cycle

What should you expect from wipe day on RustDockerServer?

The busiest point of its recent wipes drew 0 players on average. Peak crowd on the latest wipe: 0 hours in.

What wipe timing does RustDockerServer follow?

Its rhythm cannot be told from the wipes of RustDockerServer on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 26 days 13 hours ago.

Tag meanings

How should you read the tags on RustDockerServer?

Tags published by RustDockerServer, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): 1 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Build 168909; 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.

Which lists and filters on Rust Metrics show RustDockerServer?

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

Population

Where does RustDockerServer sit in the rankings?

Player hours over seven days put RustDockerServer at #15,344, in the top 69% of all ranked servers.

How full does RustDockerServer get?

Current headcount on RustDockerServer: 0 players, 1 slots available. A seven-day average of 0 players is the reading.

Server

Where does RustDockerServer sit?

No region tag on RustDockerServer. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 70.237.29.165:28015.

What Rust version is RustDockerServer on?

Rust network protocol 2635 and build 168909 on Linux is the build RustDockerServer runs. Matching protocol is required to join. Let Steam update your game.

Is performance on RustDockerServer within range?

Reading: 129 server fps on average across the last 48 hours. It never dropped below 95. Peak entity count: 121,769. Buildings, deployables and all else included. Check: memory. Peak use was 3,506 MB. Expect lag when fps falls and entities climb.

How reliable is RustDockerServer, and is it online now?

Check: connection. RustDockerServer is online at this moment. By its reported uptime, the last restart was roughly 11 hours ago. Uptime for the last 7 full days: 168 of 168 hours, or 100%. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Settings and map

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

Check: gather rate. The name RustDockerServer does not state one. No limit is set beyond the default. Groups take up to 8 players. survival, gather, build and raid, as the game normally runs — that is the game mode. 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.

Which map is live on RustDockerServer?

Check: map. Procedural, size 4,500, seed 1337, generated by the game on RustDockerServer. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

Join

How do you connect to RustDockerServer?

Press F1 in Rust and enter client.connect 70.237.29.165:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp1,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1
Max players 1 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Build 168909.
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.