RUST METRICSFlight deck · live data
Data live Servers11,869 Players97,045 Populated3,902 Fresh wipes 3 h396 Scan5 min
‹ All servers163.123.239.18:25998
Offline Full Queue Fresh wipe Wipe due No query

Chris Was Here

Offline 163.123.239.18:25998 checked 39d ago

COM 1 · connect

Server instruments

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

Players now

2% 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,305no region published
Last wipe41d 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 Chris Was Here follow?

To tell the rhythm of Chris Was Here, 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 41 days 3 hours ago.

Lists and filters

How should you read the tags on Chris Was Here?

These are the tags Chris Was Here 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): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs164924 (Build): Game build reading: 164924; ptrak (Networking): This is RakNet, Rust's usual network layer; $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 Chris Was Here?

Rust Metrics lists featuring Chris Was Here: 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.

Occupancy

What position does Chris Was Here hold among Rust servers?

Ranking for Chris Was Here: #13,305 on seven-day player hours, top – of all ranked servers.

How full does Chris Was Here get?

Status for Chris Was Here: offline. Last seen 39 days 1 hours ago.

Operator and location

Where does Chris Was Here sit?

No region comes from Chris Was Here. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 163.123.239.18:25998.

What Rust version is Chris Was Here on?

Reading: Chris Was Here, Rust network protocol 2633 and build 164924, Linux. Matching protocol is required to join. Let Steam update your game.

Is Chris Was Here up, and how often does it stay up?

Chris Was Here reports offline. The last reading came 39 days 1 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 18 September 2026.

Settings and map

How is Chris Was Here configured, and what rules are in force?

Check: gather rate. The name Chris Was Here does not state one. 8 players per group, the default value. Mode check gives survival; 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.

What map is Chris Was Here on?

The game generates a procedural map for Chris Was Here.

Join

How do you connect to Chris Was Here?

Check: join. Open Rust, press F1, then enter client.connect 163.123.239.18:25998. 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?,v2633,gmrust,cs164924,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players The server holds 50 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Your game must run protocol 2633 to get in.
cs164924
Build Game build reading: 164924.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.