Codex Heap Crash Current Recheck
Offline 96.55.62.126:59626 checked 46d ago
Vital stats
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
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
The same kind of game, then region, group limit, rate and wipes.
Quick answers
From the figures on this page.
Lists and tags
Which Rust Pop Watch lists and filters include Codex Heap Crash Current Recheck?
These Rust Pop Watch lists include Codex Heap Crash Current Recheck: Community servers, by the numbers. 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?
For the server browser, Codex Heap Crash Current Recheck lists these tags: gmrust (Game mode): This one runs standard Rust survival, as it comes; mp4 (Max players): There are 4 slots; ts8 (Group limit): Teams cap at 8, which is the game default; v2633 (Protocol): The game protocol is 2633, so your client has to match it to join; cs163696 (Build): Game build: 163696; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): Region code left blank. You'll find players now, queue length and world creation time in the tags, printed at the top of this page.
Population
How many players are on Codex Heap Crash Current Recheck right now?
Offline now, Codex Heap Crash Current Recheck was last spotted 46 days 9 hours ago.
About the server
Is Codex Heap Crash Current Recheck online, and how reliable is it?
Down at the moment: Codex Heap Crash Current Recheck was last seen 46 days 9 hours ago. The last 7 full days saw uptime of 0%, with 0 out of 168 hours online. Rust Pop Watch's first record of it is 13 September 2026.
Where is Codex Heap Crash Current Recheck located?
There is no region from Codex Heap Crash Current Recheck. It is where a server says it is that Rust Pop Watch shows; the machine's actual location is not looked up. Connect at 96.55.62.126:59626.
Which Rust version is Codex Heap Crash Current Recheck on?
On Windows, Codex Heap Crash Current Recheck runs Rust network protocol 2633 and build 163696. To join, your game must be on the same protocol; Steam handles the update.
Wipe days
What is the wipe schedule on Codex Heap Crash Current Recheck?
Too few wipes are on record for Codex Heap Crash Current Recheck to reveal its rhythm. A force wipe comes round every month for all Rust servers, with the next on Thursday 5 November at 19:00 UTC. Its current world has been live for 46 days 9 hours.
Map and rules
Which map does Codex Heap Crash Current Recheck run?
Codex Heap Crash Current Recheck uses a procedural map, which the game generates.
What are the rules and settings on Codex Heap Crash Current Recheck?
The name of Codex Heap Crash Current Recheck says nothing about gather rate. Groups go up to 8 players, which is the default. It runs survival, gather, build and raid, as standard. Fighting and raiding between players is allowed. The server browser lists it under Community. The VAC anti-cheat from Valve is on.
Getting in
How do I join Codex Heap Crash Current Recheck?
The console method: start Rust, press F1, and type client.connect 96.55.62.126:59626. Launch Rust on this page is another way, opening Rust via Steam and connecting.