Rust Data LabData lab · live
Live readings Servers11,681 Players64,778 Populated3,475 Fresh wipes · 3h118 Sampled every 5 min

Element card · group Community · atomic number 16,275, its rank

Iluhatuz

Offline 91.223.70.225:28015 checked 26d ago

Join the experiment
Atomic mass · players now 0/ 500 0% full Room to join
7-day average0peak –
Rank · atomic number#16,275top 69%
Last wipe27d agono schedule published
Next wipe–too few wipes seen yet
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
No hourly history yet.

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
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.

Result 03

Rank

Result

daily · 1 is best

RankRank in region
15k10k15k20k30 Sep2 Oct3 Oct5 Oct6 Oct8 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

Reaction kinetics

Wipe schedule

too few wipes seen yet

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

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 30 Sep, 17:14 UTC27d ago 1 – running 0

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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
  1. 1 Ru Rusty Moose |E… 651
    Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 540 on average 651/ 675
  2. 2 Ru Rustoria.co - … 393
    Rustoria.co - EU East Long EU · groups of 12+ · monthly · 318 on average 393/ 425
  3. 3 Ru Rustoria.co - … 42
    Rustoria.co - EU Main EU · groups of 16+ · weekly · 312 on average 42/ 250
  4. 4 Ru Rusty Moose |E… 50
    Rusty Moose |EU Main| EU · groups of 12+ · weekly · 311 on average 50/ 250
  5. 5 Ru Rustoria.co - … 169
    Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 272 on average 169/ 200
  6. 6 Ru Rustafied.com … 97
    Rustafied.com - EU Friday EU · groups of 16+ · weekly · 265 on average 97/ 125

Quick answers

from the figures on this page

Settings and map

What map is in play on Iluhatuz?

Generated by the game, the map on Iluhatuz is procedural.

What settings and rules apply on Iluhatuz?

The name of Iluhatuz carries no gather rate. Eight players per group is the limit, the game's default. Play runs as survival, gather, build and raid, as in the standard game. Raids and player fights are part of play here. The server browser lists it under Community. The VAC anti-cheat from Valve is enabled.

Server details

Which location is Iluhatuz based in?

There is no region on record for Iluhatuz. The location shown is the one a server states; Rust Data Lab does not check where the machine actually stands. You will find it at 91.223.70.225:28015.

What Rust version does Iluhatuz currently run?

Rust network protocol 2633 and build 165217 on Windows is what Iluhatuz uses. The protocol must match for you to join; Steam will update your game.

How reliably does Iluhatuz stay online?

Iluhatuz is not online at the moment; the last sighting was 26 days 17 hours ago. It was online for 0 of 168 hours in the last 7 full days, which is 0% uptime. On 30 September 2026, Rust Data Lab saw it for the first time.

Wipe days

How often does a wipe happen on Iluhatuz, and at what time?

The record holds too few of Iluhatuz's wipes to show its rhythm. The monthly force wipe resets every Rust server; it next occurs on Thursday 5 November at 19:00 UTC. Counting back, the current world began 27 days 18 hours ago.

What does a typical wipe day on Iluhatuz involve?

At their busiest, recent wipes averaged 1 players. 0 hours after the latest wipe, the crowd peaked.

Where it appears

How should you read the tags on Iluhatuz?

These are the tags Iluhatuz makes public for the server browser to read: gmrust (Game mode): Standard Rust survival is the game here; mp500 (Max players): 500 is the slot count; ts8 (Group limit): This uses the game's default: 8 per team; v2633 (Protocol): Protocol 2633 is required; join only if your game matches it; cs165217 (Build): The game build is 165217; ptrak (Networking): This runs on RakNet, the standard layer; $r? (Region code): The region field is left blank. The tags carry more as well: current players, the queue and when the world was made, all shown at the top of this page.

Where among the Rust Data Lab lists and filters does Iluhatuz come up?

You will find Iluhatuz on the following Rust Data Lab lists: Rust community servers, measured. You can find it on the server list by applying these filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player counts

Against other Rust servers, where does Iluhatuz place?

The seven-day player-hours table has Iluhatuz at #16,275, in the top 69% of ranked servers.

How full is Iluhatuz right now?

No live signal from Iluhatuz right now, which was last seen 26 days 17 hours ago.

Getting on

How can you connect to Iluhatuz?

Open the console with F1 in Rust and type client.connect 91.223.70.225:28015. The Launch Rust button on this page does the same job through Steam.

Server tags

what each one means

Published as mp500,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode Standard Rust survival is the game here.
mp500
Max players 500 is the slot count.
ts8
Group limit This uses the game's default: 8 per team.
v2633
Protocol Protocol 2633 is required; join only if your game matches it.
cs165217
Build The game build is 165217.
ptrak
Networking This runs on RakNet, the standard layer.
$r?
Region code The region field is left blank.

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.