Offline 96.55.62.126:59626 checked 44d ago

Codex Heap Crash Current Recheck

Connect

srv = rust.server("96.55.62.126:59627")
print(srv.connect_command)

Launch Rust and join

Right now

srv.summary()

players now 0/4 # 0% full

7-day average 0 # peak –

rank None # score 0

last wipe 44d ago # no schedule published

next wipe – # no wipe seen yet

Players

srv.players.plot(range="48h")

No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")

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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best

No rank history yet.

Wipe schedule

srv.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

srv.wipes.head(20)

	wiped	peak	crowd	lasted	players_before
	datetime64[UTC]	int64	object	timedelta	int64
Empty DataFrame · 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.

display(srv.map, srv.info())

Map

No map picture published

map: Procedural Map
size: –
seed: –

Server

srv.info()

<class 'rust.Server'>
Index: 8 entries, address to first_seen

address: 96.55.62.126:59626
region: –
max players: 4
group limit: 8, the default
wipe schedule: –
last wipe: 13 Sep 2026, 11:57 UTC
hostname: –
first seen: 13 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)

	server	like_this	players
0	Rusty Moose \|EU Mondays\|	EU · groups of 12+ · weekly · 540 on average	517/250
1	Rustoria.co - EU East Long	EU · groups of 12+ · monthly · 318 on average	339/325
2	Rustoria.co - EU Main	EU · groups of 16+ · weekly · 314 on average	34/250
3	Rusty Moose \|EU Main\|	EU · groups of 12+ · weekly · 313 on average	40/250
4	Rustoria.co - EU East Medium	EU · groups of 12+ · biweekly · 273 on average	154/200
5	Rustafied.com - EU Friday	EU · groups of 16+ · weekly · 265 on average	78/100

Quick answers

From the figures on this page.

Population

How full does Codex Heap Crash Current Recheck run?

The current row shows Codex Heap Crash Current Recheck offline; the last response was 44 days 22 hours ago.

Server facts

What Rust version does Codex Heap Crash Current Recheck run?

Version Rust network protocol 2633 and build 163696 on Windows is reported by Codex Heap Crash Current Recheck. The protocol has to match before you can join, and Steam does the updating.

How reliable is Codex Heap Crash Current Recheck, and is it online now?

Offline now for Codex Heap Crash Current Recheck, last seen 44 days 22 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.

Where does Codex Heap Crash Current Recheck sit?

No region is published by Codex Heap Crash Current Recheck. Rust Data does not look up where the machine stands; it shows where a server says it is. 96.55.62.126:59626 is its address.

Settings and map

Which settings and rules does Codex Heap Crash Current Recheck run?

You will not find a gather rate in the string Codex Heap Crash Current Recheck. The group limit sits at the default of 8 players. Game mode survival, with this note: the base game, where you gather, build and raid. Raids and player combat are enabled. It is a community server, and the browser files it under Community. VAC, Valve's anti-cheat, is enabled.

Which map has Codex Heap Crash Current Recheck selected?

Codex Heap Crash Current Recheck runs a procedural map, which the game generates.

Wipe data

When does Codex Heap Crash Current Recheck wipe, and on what schedule?

Too few wipes are on record for Codex Heap Crash Current Recheck to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 44 days 22 hours ago.

Tags, lists

Which lists on Rust Data hold Codex Heap Crash Current Recheck, and which filters?

The Rust Data lists that Codex Heap Crash Current Recheck fits are: Rust community servers, unfiltered. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

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

The game's server browser reads these tags from Codex Heap Crash Current Recheck: gmrust (Game mode): Survival play, standard Rust; mp4 (Max players): Slot count: 4; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): To join, your game must run protocol 2633; cs163696 (Build): The server runs build 163696; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

How to join

What is the way into Codex Heap Crash Current Recheck?

Enter client.connect 96.55.62.126:59626 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

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

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.