Codex Heap Crash Current Recheck
Offline 96.55.62.126:59626 checked 45d ago
Measurements
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.
Quick answers
Population
How busy is Codex Heap Crash Current Recheck?
Codex Heap Crash Current Recheck is offline at this count; we last saw it 45 days 8 hours ago.
Lists and tags
What do the server tags on Codex Heap Crash Current Recheck mean?
The game's server browser reads the tags Codex Heap Crash Current Recheck publishes: gmrust (Game mode): Survival in the standard Rust style; mp4 (Max players): You can join up to 4 slots; ts8 (Group limit): This is the game default: at most 8 per team; v2633 (Protocol): To join, your game must match protocol 2633; cs163696 (Build): This server runs game build 163696; ptrak (Networking): RakNet is the network layer here, as standard for the game; $r? (Region code): The region code is left blank. Player count now, queue length and the making of the world all sit in the tags as well, and the top of this page shows them.
Which Rust Population lists and filters include Codex Heap Crash Current Recheck?
On Rust Population, Codex Heap Crash Current Recheck is filed under these lists: Community servers, field-listed. These are the filters it appears under when you browse the list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Wipe schedule
What is the wipe schedule on Codex Heap Crash Current Recheck?
The record holds too few of Codex Heap Crash Current Recheck's wipes to show a rhythm. The next monthly force wipe is on Thursday 5 November at 19:00 UTC; all Rust servers wipe then, this one too. The world it runs now dates from 45 days 9 hours ago.
Settings
Which map does Codex Heap Crash Current Recheck run?
A procedural map, generated by the game, is in use on Codex Heap Crash Current Recheck.
What are the rules and settings on Codex Heap Crash Current Recheck?
The name tells you nothing about gather rates: Codex Heap Crash Current Recheck states none. Eight players per group is the default, and it applies here. survival is what it runs, gather, build and raid, as in the standard game. Fighting and raiding between players is allowed. The server browser lists it under Community, as a community server. VAC, Valve's anti-cheat, runs here.
Server details
Which version of Rust does Codex Heap Crash Current Recheck run?
On Windows, Codex Heap Crash Current Recheck runs Rust network protocol 2633 and build 163696. Your game needs the same protocol to join; Steam takes care of updating it.
Is Codex Heap Crash Current Recheck online, and how reliable is it?
Offline at the moment, Codex Heap Crash Current Recheck was last seen 45 days 8 hours ago. It was up 0% of the time over the last 7 full days, 0 out of 168 hours. On 13 September 2026, Rust Population saw it for the first time.
Where is Codex Heap Crash Current Recheck located?
Nothing published by Codex Heap Crash Current Recheck states a region. The location a server claims is what Rust Population shows, not the place where the machine stands. You will find it at 96.55.62.126:59626.
Getting in
How do I join Codex Heap Crash Current Recheck?
Either enter client.connect 96.55.62.126:59626 in Rust's console after pressing F1, or use Launch Rust here to open Rust through Steam and be connected.