Chris Was Here
163.123.239.18:25998 checked 24d ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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.
Rank
daily · 1 is bestWipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players 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.
Similar servers
Quick answers
Map and rules
What is the setup on Chris Was Here when it comes to rules and settings?
You will not find a gather rate in the name Chris Was Here. That is the game's default: groups of up to 8 players. survival is the game mode, gather, build and raid: the standard game. Raiding and fighting other players are allowed. You will find it under Community in the server browser. VAC, Valve's anti-cheat, is switched on.
Which map is active on Chris Was Here?
The game generates the procedural map Chris Was Here runs.
Population
How many players are on Chris Was Here?
Last seen 24 days 13 hours ago, Chris Was Here is offline at the moment.
What position does Chris Was Here hold in the server rankings?
In the top – of ranked servers, Chris Was Here holds #13,305 for player hours over the last seven days.
Lists and tags
What do Chris Was Here's tags indicate?
For the game's server browser, Chris Was Here publishes these tags: gmrust (Game mode): Standard survival gameplay; mp50 (Max players): It holds 50 players; ts8 (Group limit): This uses the standard team limit of 8; v2633 (Protocol): To join, your game must match protocol 2633; cs164924 (Build): It runs build 164924; ptrak (Networking): Standard RakNet networking is in use here; $r? (Region code): Region code left unset. The tags carry its players now, its queue and the time its world was made as well, and the top of this page displays them.
Which Rust Zerg Life filters and lists cover Chris Was Here?
The Rust Zerg Life lists that include Chris Was Here are Rust community servers for clans. 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.
About the server
What is the uptime and reliability of Chris Was Here?
No sign of Chris Was Here at present: it was last seen 24 days 13 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. Rust Zerg Life has been tracking it since 18 September 2026.
Which Rust build does Chris Was Here use?
On Linux, Chris Was Here runs Rust network protocol 2633 and build 164924. The protocol must match for you to join, and Steam will update your game to that protocol.
Where can you find Chris Was Here?
No region is published by Chris Was Here. The location shown by Rust Zerg Life is what a server says; it does not check where the machine stands. You can reach it at 163.123.239.18:25998.
Wipe schedule
When does Chris Was Here wipe?
With so few wipes on record for Chris Was Here, its pattern is not yet clear. Come Thursday 5 November at 19:00 UTC, the monthly force wipe arrives for every Rust server. The world in play right now was made 26 days 15 hours ago.
Connect
How can I connect to Chris Was Here?
Enter client.connect 163.123.239.18:25998 in the F1 console. Another way: use Launch Rust on this page, which opens Rust through Steam and connects you.
Server tags
Published as mp50,ptrak,$r?,v2633,gmrust,cs164924,ts8
Game
gmrust
mp50
ts8
v2633
cs164924
ptrak
$r?
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.