Codex Heap Crash Current Recheck
Key statistics
the figures behind the quote- Players now
- 0/ 4 0% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 0 peak –
- Rank
- – score 0
- Rank · 7d ago
- – not ranked a week ago
- Last wipe
- 30d ago no schedule published
- Next wipe
- – no wipe seen yet
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 0 player hours, last seven days
- Map
- – Procedural Map
- First seen
- 13 Sep 2026 no hostname published
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
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
the same kind of game, then region, group limit, rate and wipes| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | Rustoria.co - EU East LongEU · groups of 12+ · monthly · 410 on average | 309/325 | ▲+31+11.2% | |
| 2 | Rusty Moose |EU Monthly|EU · groups of 12+ · monthly · 361 on average | 288/325 | ▲+52+21.9% | |
| 3 | Rusty Moose |US Monthly|NA · groups of 12+ · monthly · 346 on average | 323/350 | ▼−63−16.2% | |
| 4 | Rustoria.co - EU LongEU · groups of 14+ · monthly · 337 on average | 264/300 | ▲+61+29.8% | |
| 5 | Rustoria.co - EU MainEU · groups of 16+ · weekly · 299 on average | 49/250 | ▼−12−19.8% | |
| 6 | Rustafied.com - EU Long - LargeEU · groups of 16+ · monthly · 283 on average | 245/350 | ▲+26+11.9% |
Quick answers
from the figures on this pageRules & Settings
What settings and rules are in place on Codex Heap Crash Current Recheck?
No gather rate appears in the name of Codex Heap Crash Current Recheck. Groups can contain a maximum of 8 players, the default for the game. survival is the mode, gather, build and raid in the standard game. PvP and raiding are enabled. You will find it under Community in the server browser: it is a community server. The server has VAC, Valve's anti-cheat, switched on.
What is the current map on Codex Heap Crash Current Recheck?
The game generates the procedural map on Codex Heap Crash Current Recheck.
Population
How full is Codex Heap Crash Current Recheck?
Right now, Codex Heap Crash Current Recheck is offline; the last sighting was 30 days 9 hours ago.
Wipe Schedule
When does Codex Heap Crash Current Recheck schedule its wipes?
The record holds too few of Codex Heap Crash Current Recheck's wipes to establish its rhythm. The monthly force wipe takes every Rust server. Next: Thursday 5 November at 19:00 UTC. 30 days 9 hours ago the current world was created.
Server Overview
Where can Codex Heap Crash Current Recheck be found?
No region is published by Codex Heap Crash Current Recheck. Where a server says it is, Rust Analytics shows; where the machine stands, it does not look up. You can reach it at 96.55.62.126:59626.
What Rust version is Codex Heap Crash Current Recheck running?
The build is Rust network protocol 2633 and build 163696 on Windows, running on Codex Heap Crash Current Recheck. The protocol has to match for you to join, and Steam applies that update.
How reliable is Codex Heap Crash Current Recheck and is it currently online?
No response from Codex Heap Crash Current Recheck. It was last seen 30 days 9 hours ago. 7 full days have passed with 0% uptime, 0 of 168 hours. 13 September 2026 is when Rust Analytics first saw it.
Tags and Rankings
What is the meaning of the tags on Codex Heap Crash Current Recheck?
These tags are published by Codex Heap Crash Current Recheck and read by the game's server browser: gmrust (Game mode): Survival in the standard Rust format; mp4 (Max players): Capacity: 4 slots; ts8 (Group limit): Team size stays at the game default of 8; v2633 (Protocol): To join, your game needs protocol 2633; cs163696 (Build): Build 163696; ptrak (Networking): RakNet, the network layer the game ships with; $r? (Region code): The region code is absent. Also in the tags and at the top of this page: current players, queue and world creation time.
Codex Heap Crash Current Recheck appears in which of the lists and filters on Rust Analytics?
On Rust Analytics, Codex Heap Crash Current Recheck matches these lists: Rust community servers. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How to Join
What steps do I take to join Codex Heap Crash Current Recheck?
The console route: start Rust, press F1, enter client.connect 96.55.62.126:59626. The page's Launch Rust button opens Rust through Steam and connects you instead.
Server tags
what each one meansPublished as mp4,ptrak,$r?,v2633,gmrust,cs163696,ts8
Game
gmrust
mp4
ts8
v2633
cs163696
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.