RS-···Community server
Codex Heap Crash Current Recheck
Offline 96.55.62.126:59626 checked 30d ago
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.
Population
What is the typical player count on Codex Heap Crash Current Recheck?
Currently, Codex Heap Crash Current Recheck is offline; the last sighting was 30 days 12 hours ago.
Tags and filters
Where does Codex Heap Crash Current Recheck show up in Top Rust Servers lists and filters?
These Top Rust Servers lists count Codex Heap Crash Current Recheck among their servers: Best Rust community servers. 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.
How should you read the tags on Codex Heap Crash Current Recheck?
Published by Codex Heap Crash Current Recheck for the game's server browser to read: gmrust (Game mode): Survival follows the standard Rust ruleset; mp4 (Max players): Player slots: 4; ts8 (Group limit): 8 per team is the default limit; v2633 (Protocol): This server runs protocol 2633; match it to connect; cs163696 (Build): Running game build 163696; ptrak (Networking): The network layer is RakNet, which is standard for Rust; $r? (Region code): Region code not set. At the top of this page you also see its players now, its queue, and the time its world was made, taken from the tags.
Rules, settings, and map
Which map is running on Codex Heap Crash Current Recheck?
Codex Heap Crash Current Recheck uses a procedural map, which the game generates.
What does Codex Heap Crash Current Recheck run for rules and settings?
The name Codex Heap Crash Current Recheck does not state a gather rate. Up to 8 players per group, as the game defaults. It runs survival, the normal mode where you gather, build and raid. You can fight and raid other players. The server browser shows it under Community. The server runs with VAC on.
About the server
What version is Codex Heap Crash Current Recheck running?
On Windows, Codex Heap Crash Current Recheck operates Rust network protocol 2633 and build 163696. Joining requires matching protocols, and Steam updates your game automatically.
Where can Codex Heap Crash Current Recheck be found?
A region is not published by Codex Heap Crash Current Recheck. Top Rust Servers does not look up where the machine stands; it shows where a server says it is. It answers at 96.55.62.126:59626.
Is Codex Heap Crash Current Recheck currently online?
Codex Heap Crash Current Recheck is offline now; the last time it was seen was 30 days 12 hours ago. It spent 0 of the last 168 hours online across 7 days, giving 0% uptime. It was first observed by Top Rust Servers on 13 September 2026.
Wipe cycle
How often does Codex Heap Crash Current Recheck wipe?
Not enough wipe data exists yet to identify the rhythm of Codex Heap Crash Current Recheck. A force wipe happens monthly across all Rust servers; the next is scheduled for Thursday 5 November at 19:00 UTC. Its world was last replaced 30 days 12 hours ago.
Connection
How can I connect to Codex Heap Crash Current Recheck?
Use the console: open Rust, press F1, and type client.connect 96.55.62.126:59626. Or simply click Launch Rust here; it opens the game through Steam and connects you.