Statistical profileOffline
Codex Heap Crash Current Recheck
96.55.62.126:59626 checked 45d ago
Connect to this server
1. Main points
Players now
0/ 4
0% full
7-day average
0
peak –
Rank
–
score 0
Last wipe
45d ago
no schedule published
Next wipe
–
no wipe seen yet
Main points
- The server is offline; at its last check there were 0 players on it, 0% of its 4 slots.
- Its current map went up 45d ago.
2. Players
Figure 1: Players on Codex Heap Crash Current Recheck
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
Note
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.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Source: Live server queries, Rust Census
5. Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
6. Wipes
Table 1: Wipes, newest first
Every wipe seen on this server
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
Notes
- 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.
Source: Live server queries, Rust Census
7. Map
Figure 4: Map of Codex Heap Crash Current Recheck
Table 2: The world
As the server publishes it
| Map | Procedural Map |
|---|---|
| Size | – |
| Seed | – |
8. Server characteristics
Table 3: Characteristics of Codex Heap Crash Current Recheck
What the server publishes and what was recorded
| Address | 96.55.62.126:59626 |
|---|---|
| Region | – |
| Max players | 4 |
| Group limit | 8, the default |
| Wipe schedule | – |
| Last wipe | 13 Sep 2026, 11:57 UTC |
| Hostname | – |
| First seen | 13 Sep 2026 |
9. Similar servers
Table 4: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 553 on average | 548 / 675 |
| Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 318 on average | 357 / 525 |
| Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 297 on average | 44 / 250 |
| Rustoria.co - EU Main | EU · groups of 16+ · weekly · 296 on average | 37 / 250 |
| Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 272 on average | 118 / 200 |
| Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 253 on average | 128 / 300 |
10. Quick answers
From the figures on this page.
Wipe details
When does Codex Heap Crash Current Recheck wipe, and how often?
With too few wipes of Codex Heap Crash Current Recheck on record, its rhythm remains unclear. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. The present world dates from 45 days 9 hours.
About the server
What does the record show for the uptime and current status of Codex Heap Crash Current Recheck?
Codex Heap Crash Current Recheck is offline at the time of this release; it was last seen 45 days 9 hours ago. 0 of 168 hours on across the last 7 full days gives an uptime of 0%. It was first seen by Rust Census on 13 September 2026.
What location has been recorded for Codex Heap Crash Current Recheck?
A region is not published by Codex Heap Crash Current Recheck. Where a server says it is is what Rust Census shows; where the machine stands is not looked up. At 96.55.62.126:59626 it is addressed.
Which Rust version is Codex Heap Crash Current Recheck running?
This release lists Codex Heap Crash Current Recheck on Rust network protocol 2633 and build 163696, running on Windows. Steam updates your game for you, but it has to be on the same protocol to join.
Player figures
How many players does Codex Heap Crash Current Recheck carry?
At this release Codex Heap Crash Current Recheck is offline, having last been seen 45 days 9 hours ago.
Tags, lists
On Rust Census, which lists and filters carry Codex Heap Crash Current Recheck?
Included in these Rust Census lists is Codex Heap Crash Current Recheck: Community servers. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
What is meant by each tag shown on Codex Heap Crash Current Recheck?
gmrust (Game mode): The game mode is standard survival as Rust runs it; mp4 (Max players): Slots: 4; ts8 (Group limit): 8 per team, which is the game's default limit; v2633 (Protocol): Your game must run protocol 2633 to join; cs163696 (Build): Build 163696 is installed; ptrak (Networking): Networking is handled by RakNet, which the game uses by default; $r? (Region code): This server carries no region code are the tags Codex Heap Crash Current Recheck publishes, and the game's server browser reads them. Current players, queue length and world creation time are in the tags as well, and are shown at the top of this page.
Settings and map
What map is listed for Codex Heap Crash Current Recheck?
A procedural map runs on Codex Heap Crash Current Recheck, generated by the game.
What settings and rules have been listed for Codex Heap Crash Current Recheck?
No gather rate is given in the name of Codex Heap Crash Current Recheck. The default applies: groups are capped at 8 players. It runs survival, the standard game: gather, build, raid. Fighting other players and raiding are allowed. It appears under Community in the server browser. VAC, Valve's anti-cheat, is enabled.
Connecting
How can you connect to Codex Heap Crash Current Recheck?
Enter client.connect 96.55.62.126:59626 in Rust's console, opened with F1. Alternatively, use Launch Rust and join here: Steam opens the game and connects you.
11. Server tags
What each tag this server publishes means: a glossary.
Published asmp4,ptrak,$r?,v2633,gmrust,cs163696,ts8
Game
gmrust | Game mode The game mode is standard survival as Rust runs it. |
|---|---|
mp4 | Max players Slots: 4. |
ts8 | Group limit 8 per team, which is the game's default limit. |
v2633 | Protocol Your game must run protocol 2633 to join. |
cs163696 | Build Build 163696 is installed. |
ptrak | Networking Networking is handled by RakNet, which the game uses by default. |
$r? | Region code This server carries no region code. |
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.