Codex Heap Crash Current Recheck
Offline 96.55.62.126:59626 checked 45d ago
Li2Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Li3Server 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.
Li4Rank
daily · 1 is bestBx1Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Bx2Wipes
newest first · each peak a flare-up, on one √ span to its biggest| 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.
Bx6Similar servers
the same kind of game, then region, group limit, rate and wipesLogQuick answers
from the figures on this pageWipe schedule
What is the wipe schedule on Codex Heap Crash Current Recheck?
Its rhythm cannot yet be told: too few of Codex Heap Crash Current Recheck's wipes are on record. Thursday 5 November at 19:00 UTC is the next monthly force wipe, when every Rust server wipes. 45 days ago the server made the world it is on now.
Player counts
How busy is Codex Heap Crash Current Recheck?
Codex Heap Crash Current Recheck went quiet 45 days ago and is offline right now.
Rules and settings
Which map does Codex Heap Crash Current Recheck run?
Codex Heap Crash Current Recheck runs a procedural map, which the game generates.
What are the rules and settings on Codex Heap Crash Current Recheck?
No gather rate appears in the name Codex Heap Crash Current Recheck. Groups can contain up to 8 players, the default in the game. The server runs survival, standard play: gathering, building and raiding. Combat between players and raiding are both possible. The server browser lists it under Community. Anti-cheat: Valve's VAC is on.
About the server
Which version of Rust does Codex Heap Crash Current Recheck run?
Rust network protocol 2633 and build 163696 on Windows is what Codex Heap Crash Current Recheck runs. Your game must run the same protocol to join, and Steam takes care of updating it.
Is Codex Heap Crash Current Recheck online, and how reliable is it?
Last seen 45 days ago, Codex Heap Crash Current Recheck is offline right now. 0 of 168 hours up over the last 7 full days, which is 0%. Rust Heatmap has had it on record since 13 September 2026.
Where is Codex Heap Crash Current Recheck located?
No region is published by Codex Heap Crash Current Recheck. A server says where it is, and Rust Heatmap shows that. The machine's actual location is not looked up. To connect, use 96.55.62.126:59626.
Tags
Which Rust Heatmap lists and filters include Codex Heap Crash Current Recheck?
Best Rust community servers are the Rust Heatmap lists that Codex Heap Crash Current Recheck fits. Filtering the list by Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more brings it up.
What do the server tags on Codex Heap Crash Current Recheck mean?
These are the tags Codex Heap Crash Current Recheck publishes for the game's server browser to read: gmrust (Game mode): Survival in the standard Rust form; mp4 (Max players): Slot count: 4; ts8 (Group limit): The game default applies: 8 per team at most; v2633 (Protocol): The server runs game protocol 2633, so your game has to match it; cs163696 (Build): The game build here is 163696; ptrak (Networking): Standard game networking here, which is RakNet; $r? (Region code): No region code is set. Also in the tags, shown at the top of this page: players now, the queue and the time the world was made.
Connect
How do I join Codex Heap Crash Current Recheck?
To join by console, open it with F1 in Rust and enter client.connect 96.55.62.126:59626. Or press Launch Rust on this page, which connects you through Steam.