Rust Server IndexCard catalogue of Rust servers

Holdings11,620 servers40,450 players92 fresh wipes

Call no.n.r. Off the shelf · offline

Codex Heap Crash Current Recheck

Offline 96.55.62.126:59626 checked 44d ago

Subjects
Players now
0/ 4
0% full
7-day average
0
peak –
Rank
–
score 0
Last wipeWiped13 SEP2026 · 44d 19h ago
44d ago · no schedule published
Next wipe
–
no wipe seen yet
Call slipPaste it into the F1 console
Record sheet A · appended

Players

No hourly history yet.

Hourly average and peak, UTC.

Record sheet B · appended

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Record sheet C · appended

Rank

daily · 1 is best
No rank history yet.
Record sheet D · loan terms

Wipe schedule

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

Record sheet E · date due

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

Shelf list · shelved beside it

Similar servers

The same kind of game, then region, group limit, rate and wipes.

EU
Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 535 on average
336/ 350
EU
Rustoria.co - EU MainEU · groups of 16+ · weekly · 320 on average
11/ 250
EU
Rusty Moose |EU Main|EU · groups of 12+ · weekly · 319 on average
22/ 250
EU
Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average
148/ 225
EU
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 277 on average
85/ 225
EU
Rustafied.com - EU FridayEU · groups of 16+ · weekly · 265 on average
33/ 100
Reference desk

Quick answers

From the figures on this page.

Map and rules

Where can you read the rules and settings that apply on Codex Heap Crash Current Recheck?

You will find no gather rate in the name of Codex Heap Crash Current Recheck. The default group limit of 8 players applies. The server runs survival, building, gathering and raiding in the standard game. Fighting and raiding other players is permitted. It is listed under Community in the server browser and is a community server. VAC is on: Valve's anti-cheat is enabled.

Which map is in use on Codex Heap Crash Current Recheck?

Generated by the game, the map is procedural on Codex Heap Crash Current Recheck.

Tags and filters

Where does Codex Heap Crash Current Recheck appear among the Rust Server Index lists and filters?

These lists on Rust Server Index take Codex Heap Crash Current Recheck: Community Rust servers, indexed. Filed 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 listed for Codex Heap Crash Current Recheck?

These are the tags Codex Heap Crash Current Recheck publishes; the game's server browser reads this list: gmrust (Game mode): Survival on standard Rust rules; mp4 (Max players): Player cap: 4; ts8 (Group limit): Teams cap at 8, the default setting; v2633 (Protocol): Your client must run protocol 2633 to connect; cs163696 (Build): Build on file: 163696; ptrak (Networking): Networking runs on RakNet, the game's default layer; $r? (Region code): No region code has been set. See also the top of this page, where the tags carry the current players, the queue and the time the world was made.

Wipe schedule

Which wipe timetable does Codex Heap Crash Current Recheck follow?

The record holds too few of Codex Heap Crash Current Recheck's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. Its present world dates from 44 days 19 hours.

Players and ranking

What does the player count on Codex Heap Crash Current Recheck look like?

Filed under offline: Codex Heap Crash Current Recheck, last seen 44 days 19 hours ago.

Server details

Which Rust build is Codex Heap Crash Current Recheck running?

Rust network protocol 2633 and build 163696, on Windows, is what Codex Heap Crash Current Recheck runs. The protocol must match before you can join, and Steam takes care of updating it.

What is the uptime and current status of Codex Heap Crash Current Recheck?

Last seen 44 days 19 hours ago, Codex Heap Crash Current Recheck is offline right now. It was up 0 of 168 hours across the last 7 full days, or 0% of the time. On 13 September 2026 it was first seen by Rust Server Index.

Where in the world is Codex Heap Crash Current Recheck hosted?

Codex Heap Crash Current Recheck gives no region at all. What Rust Server Index shows is the stated location, not the machine's actual position, which it does not look up. Connection details: 96.55.62.126:59626.

How to join

How can you connect to Codex Heap Crash Current Recheck?

If you would rather use the console, press F1 in Rust and enter client.connect 96.55.62.126:59626. You can also choose Launch Rust and join here; that opens Rust through Steam and connects you.

Subject headings explained

Server tags

What each one means.

Published as mp4,ptrak,$r?,v2633,gmrust,cs163696,ts8

Game

gmrust
Game mode Survival on standard Rust rules.
mp4
Max players Player cap: 4.
ts8
Group limit Teams cap at 8, the default setting.
v2633
Protocol Your client must run protocol 2633 to connect.
cs163696
Build Build on file: 163696.
ptrak
Networking Networking runs on RakNet, the game's default layer.
$r?
Region code No region code has been 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.