RUST METRICSFlight deck · live data
Data live Servers11,637 Players32,155 Populated2,791 Fresh wipes 3 h71 Scan5 min
‹ All servers96.55.62.126:59626
Offline Full Queue Fresh wipe Wipe due No query

Codex Heap Crash Current Recheck

Offline 96.55.62.126:59626 checked 45d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 1 2 3 4 PAX 0 /4

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank–score 0
Last wipe45d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

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.

REC 3

Rank

daily · 1 is best
No rank history yet.
PLAN

Wipe schedule

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

LOG

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

When does Codex Heap Crash Current Recheck wipe?

To tell the rhythm of Codex Heap Crash Current Recheck, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 45 days 16 hours ago.

Lists and filters

How should you read the tags on Codex Heap Crash Current Recheck?

These are the tags Codex Heap Crash Current Recheck publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp4 (Max players): The server holds 4 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163696 (Build): Build 163696; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does Codex Heap Crash Current Recheck appear in Rust Metrics lists and filters?

On Rust Metrics, Codex Heap Crash Current Recheck sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Occupancy

What is the population on Codex Heap Crash Current Recheck?

Status for Codex Heap Crash Current Recheck: offline. Last seen 45 days 16 hours ago.

Server

What location is Codex Heap Crash Current Recheck hosted in?

Reading: location. Codex Heap Crash Current Recheck gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 96.55.62.126:59626.

What Rust version is Codex Heap Crash Current Recheck on?

Rust network protocol 2633 and build 163696 on Windows is the build Codex Heap Crash Current Recheck runs. Matching protocol is required to join. Let Steam update your game.

Is Codex Heap Crash Current Recheck up, and how often does it stay up?

Codex Heap Crash Current Recheck reports offline. The last reading came 45 days 16 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Rules and settings

What settings and rules apply on Codex Heap Crash Current Recheck?

Reading the name gives no gather rate for Codex Heap Crash Current Recheck. 8 players per group, the default value. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.

What map is Codex Heap Crash Current Recheck on?

Check: map. Procedural, generated by the game, on Codex Heap Crash Current Recheck.

Join

How do you connect to Codex Heap Crash Current Recheck?

Press F1 in Rust and enter client.connect 96.55.62.126:59626. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp4
Max players The server holds 4 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Protocol 2633: join only on the same game version.
cs163696
Build Build 163696.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none 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.