Codex Heap Crash Current Recheck
Offline 96.55.62.126:59626 checked 44d ago
- Wipedunder 6 hours
- Fillingthe first day
- Peakthe first days
- Settledlater on
- Due againnext wipe close
Players, performance and rank
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
every wipe as a delivery, newest first- 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.
- Rusty Moose |EU Mondays| 410 / 350
- Rustoria.co - EU East Long 206 / 225
- Rustoria.co - EU Main 24 / 250
- Rusty Moose |EU Main| 21 / 250
- Rustoria.co - EU East Medium 126 / 225
- Rustafied.com - EU Friday 42 / 100
Quick answers
From the figures on this page.
Player count
What is the current population on Codex Heap Crash Current Recheck?
At the moment Codex Heap Crash Current Recheck is offline, having last been seen 44 days 20 hours ago.
Rules and settings
Which map is active on Codex Heap Crash Current Recheck?
The map on Codex Heap Crash Current Recheck is procedural, produced by the game.
What settings and rules should you know for Codex Heap Crash Current Recheck?
The name of Codex Heap Crash Current Recheck gives no gather rate. 8 players is the group limit, since the game's default applies. survival is the mode, gather and build and raid: the standard game. You can raid and fight other players. You will find it listed under Community in the server browser: it is a community server. VAC, Valve's anti-cheat, is switched on.
About the server
In which region is Codex Heap Crash Current Recheck based?
There is no region published for Codex Heap Crash Current Recheck. The location shown on Rust Wipe Tracker is the one a server gives; where the machine stands is not looked up. You will find it at 96.55.62.126:59626.
What is the uptime of Codex Heap Crash Current Recheck, and is it online?
The current status for Codex Heap Crash Current Recheck is offline, last seen 44 days 20 hours ago. It was up 0 of 168 hours over the last 7 full days, 0% of the time. 13 September 2026 is when Rust Wipe Tracker first recorded it.
What Rust version is Codex Heap Crash Current Recheck using?
Rust network protocol 2633 and build 163696 on Windows is what Codex Heap Crash Current Recheck runs. Steam keeps your game updated; it has to be on the same protocol to join.
Map resets
When does Codex Heap Crash Current Recheck wipe? What schedule does it follow?
There are too few of Codex Heap Crash Current Recheck's wipes on record so far to show its rhythm. Next force wipe: Thursday 5 November at 19:00 UTC, when all Rust servers wipe together, once a month. You are playing a world created 44 days 20 hours.
Tags and listings
Where does Codex Heap Crash Current Recheck appear in Rust Wipe Tracker lists and filters?
You will find Codex Heap Crash Current Recheck on the following Rust Wipe Tracker lists: Rust community servers, unmodded. On the server list, apply Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more and it appears.
What is the meaning of the server tags on Codex Heap Crash Current Recheck?
Read off the game's server browser, the tags for Codex Heap Crash Current Recheck are: gmrust (Game mode): Survival in standard Rust; mp4 (Max players): It holds 4 slots; ts8 (Group limit): 8 per team, which is the default; v2633 (Protocol): Protocol 2633 is required; a different version can't join; cs163696 (Build): It runs game build 163696; ptrak (Networking): RakNet handles networking, as standard for the game; $r? (Region code): No region code is set. The top of this page also carries its current players and queue, plus when its world was made, all read from the tags.
Connecting
What is the process to join Codex Heap Crash Current Recheck?
Enter client.connect 96.55.62.126:59626 in the console, opened with F1 once Rust is running. Joining from this page with Launch Rust also works: it opens Rust through Steam and connects you.