Rust StatisticsWorking papers on every public Rust server · 46,883 players now

Codex Heap Crash Current Recheck

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 44d ago · 96.55.62.126:59626

Abstract

We describe the public Rust server Codex Heap Crash Current Recheck, reached at 96.55.62.126:59626. It is offline at the last check, against a seven-day mean of 01. It last wiped 44d ago.

Keywordsrust server

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now0/40% full
In the queue0no queue
Seven-day mean0peak –
Rank2–score 0
Last wipe44d agono schedule published
Next wipe3–no wipe seen yet

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

No hourly history yet.
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
This server has not answered a direct query in the last 48 hours.
Figure 2: 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.

4Rank

Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

No rank history yet.
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

5.2History

Table 2: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

No map picture published
Figure 4: The map: Procedural Map.
Table 3: The server's published settings.
Address96.55.62.126:59626
Region–
Max players4
Group limit8, the default
Wipe schedule–
Last wipe13 Sep 2026, 11:57 UTC
Hostname–
First seen13 Sep 2026
MapProcedural Map
Size–
Seed–

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are busiest community rust servers [2] and next Rust wipe times [3].

Table 4: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 536 on average454/475
Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average259/225
Rustoria.co - EU MainEU · groups of 16+ · weekly · 318 on average27/250
Rusty Moose |EU Main|EU · groups of 12+ · weekly · 317 on average33/250
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 276 on average140/200
Rustafied.com - EU FridayEU · groups of 16+ · weekly · 265 on average53/100

Appendix AQuick answers

From the figures on this page.

Server details

A.1In which location is Codex Heap Crash Current Recheck based?

A region is not published by Codex Heap Crash Current Recheck. Rust Statistics does not look up the machine's location; it shows where the server says it is. 96.55.62.126:59626 is its address.

A.2What is the reliability of Codex Heap Crash Current Recheck, and is it online?

Codex Heap Crash Current Recheck is currently offline, with the last sighting 44 days 20 hours ago. Its uptime over the last full days (7 days) was 0%, with 0 of 168 hours online. It was first observed on 13 September 2026 by Rust Statistics.

A.3What is the Rust version for Codex Heap Crash Current Recheck?

Rust network protocol 2633 and build 163696 is the version that Codex Heap Crash Current Recheck runs, on Windows. To join, your game must use the same protocol; Steam handles the update for you.

Wipe schedule

A.4On what cycle does Codex Heap Crash Current Recheck wipe?

There are not yet enough recorded wipes for Codex Heap Crash Current Recheck to reveal its rhythm. The monthly force wipe takes place on Thursday 5 November at 19:00 UTC and clears all Rust servers. 44 days 20 hours have passed since the current world was generated.

Player count

A.5What is the population level of Codex Heap Crash Current Recheck?

At this moment Codex Heap Crash Current Recheck is offline, having last been seen 44 days 20 hours ago.

Tags and filters

A.6What is the meaning of the tags on Codex Heap Crash Current Recheck?

gmrust (Game mode): Survival on standard Rust rules; mp4 (Max players): It offers 4 slots; ts8 (Group limit): 8 per team, the value the game sets by default; v2633 (Protocol): Your game must run protocol 2633 to connect; cs163696 (Build): This server runs game build 163696; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): The region code is unset: these are the tags Codex Heap Crash Current Recheck publishes, and the server browser reads them. Also in the tags: players now, the queue, and when the world was made; these appear at the top of this page.

A.7Where can Codex Heap Crash Current Recheck be found among the Rust Statistics lists and filters?

These Rust Statistics lists include Codex Heap Crash Current Recheck: Rust community servers, measured. It appears under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Rules, settings, map

A.8Which settings and rules are in force on Codex Heap Crash Current Recheck?

The name of Codex Heap Crash Current Recheck states no gather rate. No cap is given beyond the game's default of 8 players per group. The mode is survival, which means the standard mode, in which you gather, build and raid. Fighting and raiding between players are both permitted. Community is its category in the server browser. The server has VAC on, Valve's anti-cheat.

A.9What is the map for Codex Heap Crash Current Recheck?

A procedural map, generated by the game, is what Codex Heap Crash Current Recheck runs.

How to join

A.10What is the process for joining Codex Heap Crash Current Recheck?

Press F1 inside Rust to open the console and enter client.connect 96.55.62.126:59626. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp4,ptrak,$r?,v2633,gmrust,cs163696,ts8.

Table 5: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Survival on standard Rust rules.
mp4Max players. It offers 4 slots.
ts8Group limit. 8 per team, the value the game sets by default.
v2633Protocol. Your game must run protocol 2633 to connect.
cs163696Build. This server runs game build 163696.
ptrakNetworking. Networking runs on RakNet, the game's standard layer.
$r?Region code. The region code is unset.

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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Busiest community rust servers. ruststatistics.org/top-rust-community-servers.
  3. [3]Rust Statistics. Next Rust wipe times. ruststatistics.org/rust-servers-wiping-today-list.