A1270/ 250 players
Community
Codex Heap Crash Current Recheck
Offline 96.55.62.126:59626 checked 30d ago
players now0of 4 slots
7-day average0peak –
rank–score 0
last wipe · restocked30d agono schedule published
next wipe · restock–no wipe seen yet
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
No daily history yet.
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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 bestNo rank history yet.
Wipe 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 | 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.
Also on the shelf
Similar servers
The same kind of game, then region, group limit, rate and wipes.
A2156/ 200 players
A3218/ 250 players
B1149/ 200 players
B222/ 250 players
B3115/ 150 players
On the back of the pack
Quick answers
From the figures on this page.
Lists and tags
How should you read the tags on Codex Heap Crash Current Recheck?
The server browser reads these tags that Codex Heap Crash Current Recheck publishes: gmrust (Game mode): The standard survival game mode; mp4 (Max players): The cap is 4; ts8 (Group limit): 8 to a team, as the game ships it; v2633 (Protocol): To join, your game version must line up with protocol 2633; cs163696 (Build): Game build: 163696; ptrak (Networking): The game's usual network layer, RakNet, is used; $r? (Region code): Region code not set. Tags also carry its current players, its queue and when the world was made, all up top on this page.
Where does Codex Heap Crash Current Recheck appear in the lists and filters on Rust Vending Machine?
These Rust Vending Machine lists include Codex Heap Crash Current Recheck: Community Rust servers in stock. It shows under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Settings and rules
Which map is currently on Codex Heap Crash Current Recheck?
A procedural map, generated by the game, is what Codex Heap Crash Current Recheck runs.
What rules does Codex Heap Crash Current Recheck enforce, and what settings does it run?
There is no gather rate in the name Codex Heap Crash Current Recheck. Groups can reach 8 players, which is the default. You play survival, gather, build, raid: the standard game. Player versus player combat and raiding are on. In the server browser it is listed under Community, being a community server. VAC, Valve's anti-cheat, is enabled.
Server details
What is the location of Codex Heap Crash Current Recheck?
No region is published by Codex Heap Crash Current Recheck. Rust Vending Machine reports the location a server claims, not where the machine actually sits. The endpoint is 96.55.62.126:59626.
How reliable is Codex Heap Crash Current Recheck, and is it online now?
No stock on Codex Heap Crash Current Recheck at the moment, last seen 30 days 19 hours ago. 0 of 168 hours online over the last 7 full days, or 0% uptime. Its first record on Rust Vending Machine is dated 13 September 2026.
What version does Codex Heap Crash Current Recheck use?
On Windows, Codex Heap Crash Current Recheck is running Rust network protocol 2633 and build 163696. To get in, your game must match the protocol; Steam keeps that updated.
Population
Is Codex Heap Crash Current Recheck busy at the moment?
Current status for Codex Heap Crash Current Recheck: offline, last seen 30 days 19 hours ago.
Wipe schedule
On what schedule does Codex Heap Crash Current Recheck wipe?
Too few wipes of Codex Heap Crash Current Recheck are recorded to tell what its rhythm is. When the monthly force wipe arrives on Thursday 5 November at 19:00 UTC, every Rust server wipes. It has been running its current world since 30 days 19 hours ago.
Getting in
What steps do you take to join Codex Heap Crash Current Recheck?
Open Rust and press F1 for the console, then type client.connect 96.55.62.126:59626. Or use the Launch Rust button here to open the game through Steam and connect.
Server tags
what each one meansPublished as mp4,ptrak,$r?,v2633,gmrust,cs163696,ts8
Game
gmrust
Game mode The standard survival game mode.
mp4
Max players The cap is 4.
ts8
Group limit 8 to a team, as the game ships it.
v2633
Protocol To join, your game version must line up with protocol 2633.
cs163696
Build Game build: 163696.
ptrak
Networking The game's usual network layer, RakNet, is used.
$r?
Region code Region code not set.
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.