Off air
Codex Heap Crash Current Recheck
Offline 96.55.62.126:59626 checked 45d ago
Players
Codex Heap Crash Current Recheck
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
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
| 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
Server details
Is Codex Heap Crash Current Recheck online, and how reliable is it?
Codex Heap Crash Current Recheck is down at the moment, having last been seen 45 days 7 hours ago. 0 of 168 hours is what it managed over the past 7 full days, 0% of the time. Its earliest entry with Rust Charts dates from 13 September 2026.
Where is Codex Heap Crash Current Recheck located?
From Codex Heap Crash Current Recheck, no region is published. Rust Charts doesn't look up where the machine stands; it shows where the server says it is. Connect at 96.55.62.126:59626.
Which version of Rust does Codex Heap Crash Current Recheck run?
Rust network protocol 2633 and build 163696 on Windows is the version Codex Heap Crash Current Recheck runs. Your game must match the protocol to get in, and Steam keeps it updated for you.
Population
How busy is Codex Heap Crash Current Recheck?
Codex Heap Crash Current Recheck shows as offline now, with its last appearance 45 days 7 hours ago.
Wipe days
What is the wipe schedule on Codex Heap Crash Current Recheck?
Too few wipes on record for Codex Heap Crash Current Recheck to show its rhythm. Thursday 5 November at 19:00 UTC brings the next monthly force wipe, which reaches every Rust server. 45 days 7 hours is how long ago its current world was made.
How it is set up
What are the rules and settings on Codex Heap Crash Current Recheck?
You will not find a gather rate in the name Codex Heap Crash Current Recheck. Up to 8 players per group, as the game sets by default. survival is the game mode, raid, build and gather: the standard game. Fighting and raiding between players is allowed. In the server browser it is under Community, being a community server. Valve's VAC anti-cheat is active.
Which map does Codex Heap Crash Current Recheck run?
A procedural map, generated by the game, is what Codex Heap Crash Current Recheck runs.
Tag guide
Which Rust Charts lists and filters include Codex Heap Crash Current Recheck?
The Rust Charts lists that carry Codex Heap Crash Current Recheck are: Rust community servers, unmodded. 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.
What do the server tags on Codex Heap Crash Current Recheck mean?
gmrust (Game mode): The game mode is standard Rust survival; mp4 (Max players): The server holds 4 slots; ts8 (Group limit): 8 per team, as the game ships it; v2633 (Protocol): The server speaks protocol 2633, so your game needs the same version; cs163696 (Build): This server reports build 163696; ptrak (Networking): RakNet handles the network, as standard for the game; $r? (Region code): The region code is unset — that's the set of tags Codex Heap Crash Current Recheck publishes for the server browser. At the top of this page you'll see the tags' extra details: players now, the queue, and the age of the world.
How to join
How do I join Codex Heap Crash Current Recheck?
Press F1 in Rust to open the console and type client.connect 96.55.62.126:59626. Joining on this page with Launch Rust works too, opening Rust through Steam and connecting you.