Codex Heap Crash Current Recheck
Offline 96.55.62.126:59626 checked 34d 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
the same kind of game, then region, group limit, rate and wipes
- 120/ 200
- 311/ 300
- 237/ 275
- 748/ 800
- 111/ 200
- 257/ 300
Quick answers
Tags and search
Where does Codex Heap Crash Current Recheck appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry Codex Heap Crash Current Recheck are: Rust community servers, going deep. Its entry appears under the filters Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the tags on Codex Heap Crash Current Recheck?
The server browser shows these tags for Codex Heap Crash Current Recheck: gmrust (Game mode): Survival, as standard Rust does it; mp4 (Max players): It holds 4 players; ts8 (Group limit): Teams cap at 8, which is the game default; v2633 (Protocol): To join, your game has to be on protocol 2633; cs163696 (Build): The build number is 163696; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): The region field is empty. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
Server info
Where can you find Codex Heap Crash Current Recheck?
There is no published region for Codex Heap Crash Current Recheck. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. To connect, use 96.55.62.126:59626.
What's the uptime like for Codex Heap Crash Current Recheck?
Right now Codex Heap Crash Current Recheck is offline, having last been seen 34 days 16 hours ago. Over the past full 7 days it stayed up for 0 of 168 hours, or 0%. The first sighting by Rust Going Deep was on 13 September 2026.
What is the Rust version for Codex Heap Crash Current Recheck?
On Windows, Codex Heap Crash Current Recheck runs Rust network protocol 2633 and build 163696. The protocol must match to join; Steam will update your game.
Wipe details
What schedule does Codex Heap Crash Current Recheck follow for wipes?
Codex Heap Crash Current Recheck's rhythm is unclear because not enough wipes are on record yet. All Rust servers wipe at the monthly force wipe, with Thursday 5 November at 19:00 UTC as the next date. The world you are on now was created 34 days 16 hours.
Rules and settings
What settings are in place on Codex Heap Crash Current Recheck?
The name of Codex Heap Crash Current Recheck contains no gather rate. The group limit is the game's default of 8 players. survival is the game mode, gather, build and raid, the standard game. PvP and raiding are enabled. Community is where the server browser puts it, as a community server. The server runs Valve's anti-cheat, VAC.
What's the map on Codex Heap Crash Current Recheck?
Codex Heap Crash Current Recheck uses a game-generated procedural map.
Player stats
How many players are on Codex Heap Crash Current Recheck?
Codex Heap Crash Current Recheck was last seen 34 days 16 hours ago and is offline as you read this.
Join info
What's the way to join Codex Heap Crash Current Recheck?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 96.55.62.126:59626.