Station XX-·· · no signal
Codex Heap Crash Current Recheck
Offline 96.55.62.126:59626 checked 44d ago
- Players now
- 0/ 4
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- –
- score 0
- Last wipe
- 44d ago
- no schedule published
- Next wipe
- –
- no wipe seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 4 slots
- Motion · 24 h
- M –not enough readings
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
daily · 1 is bestWipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| No wipe seen yet. | ||||||
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageRules and settings
Which map is running on Codex Heap Crash Current Recheck?
The map on Codex Heap Crash Current Recheck is procedural, produced by the game.
Which settings and rules apply on Codex Heap Crash Current Recheck?
No gather rate appears in the name of Codex Heap Crash Current Recheck. At the game's default, groups can have up to 8 players. In survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. It is a community server, and the browser lists it under Community. Anti-cheat is on: VAC, from Valve.
Population
What is the current population on Codex Heap Crash Current Recheck?
Codex Heap Crash Current Recheck is not responding at this moment and is offline, last seen 44 days 12 hours ago.
Server facts
How reliably does Codex Heap Crash Current Recheck stay online?
Codex Heap Crash Current Recheck is down at the moment; the last recorded contact was 44 days 12 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 13 September 2026 it was recorded for the first time by Rust Server Trends.
Where in the world is Codex Heap Crash Current Recheck hosted?
A region is not published by Codex Heap Crash Current Recheck. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 96.55.62.126:59626.
Which Rust version is Codex Heap Crash Current Recheck running?
Rust network protocol 2633 and build 163696 on Windows is what Codex Heap Crash Current Recheck runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe schedule
How often does Codex Heap Crash Current Recheck wipe, and on which days?
On record so far are too few of Codex Heap Crash Current Recheck's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 44 days 12 hours is how long the current world has been running.
Server tags
What do the server tags on Codex Heap Crash Current Recheck mean?
Tags published by Codex Heap Crash Current Recheck and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp4 (Max players): Slots: 4; ts8 (Group limit): This uses the game default of 8 per team; v2633 (Protocol): Your game needs to be on protocol 2633 to join; cs163696 (Build): It runs game build 163696; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does Codex Heap Crash Current Recheck appear?
The Rust Server Trends lists that take in Codex Heap Crash Current Recheck are: Rust community servers without the side modes. 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.
Connecting
What steps get you onto Codex Heap Crash Current Recheck?
To join, enter client.connect 96.55.62.126:59626 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.