Rust Data

rustdata.spaceservers64.40.9.223:28166.ipynb

Run all rust-data · live

‹ All servers

Online 64.40.9.223:28169 checked 12m ago

expired - reason: unpaid

moddedoxide

Connect

srv = rust.server("64.40.9.223:28166")
print(srv.connect_command)

Right now

srv.summary()
players now 2/60 # 3% full
7-day average 0 # peak 2
rank #6,338 # top 29%
last wipe 23d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
00.511.5222:0007:0016:0002:0011:0020:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
01020304022:0007:0016:0002:0011:0020:00

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, measured since 17 Sep. 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
RankRank in region
12.5k5k7.5k10k20 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

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

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

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

wipe-day peak2players, last three wipes

The first 48 hours of its last wipes

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

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Sun 4 Oct, 14:45 UTC23d ago 2 NaN 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.

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

Map

3750 · seed 1004191596
Map of expired - reason: unpaid
map
Procedural Map
size
3750
seed
1004191596
Open on RustMaps

Server

srv.info()
address
64.40.9.223:28169
region
–
max players
60
group limit
8, the default
wipe schedule
–
last wipe
4 Oct 2026, 14:45 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)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 164 on average137/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average124/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 112 on average127/225
3RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average29/200
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 86 on average124/700
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 83 on average38/1000

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does expired - reason: unpaid rank?

Over the last seven days expired - reason: unpaid sits at #6,338 on player hours, in the top 29% of ranked servers.

How many players does expired - reason: unpaid hold at once?

expired - reason: unpaid reports 2 players at this refresh, with 60 slots configured. Over the last seven days it averaged 0 players and peaked at 2. Peak hour in the last 48 hours: 00:00 UTC, mean 2 players.

Server data

How smoothly does expired - reason: unpaid run?

Averaged over 48 hours: 10 server fps, never under 5. The entity count peaked at 98,937, covering buildings, deployables and the rest of the world. A high of 3,785 MB of memory used. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

What is the Rust version on expired - reason: unpaid?

The build is Rust network protocol 2635 and build 168909 on Linux, run by expired - reason: unpaid. The protocol has to match before you can join, and Steam does the updating.

Is expired - reason: unpaid up, and what does its uptime show?

The current sample puts expired - reason: unpaid online. The uptime it reports puts the last restart about 4 days 22 hours ago. Uptime of 100% across the last 7 full days: 168 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.

Which location does expired - reason: unpaid run from?

No region is published by expired - reason: unpaid. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 64.40.9.223:28169 is its address.

Rules, settings, map

Which settings and rules does expired - reason: unpaid run?

The name expired - reason: unpaid carries no gather rate. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. Anti-cheat status: VAC off.

Which map has expired - reason: unpaid selected?

The game generates the map on expired - reason: unpaid: procedural, size 3,750, seed 1004191596. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipe data

When does expired - reason: unpaid wipe, and how often?

Too few wipes are on record for expired - reason: unpaid to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 23 days 6 hours ago.

What is wipe day on expired - reason: unpaid like?

Across recent wipes the busiest point averaged 2 players. 1 hours after the latest wipe, the crowd reached its peak.

Tags, lists

Which Rust Data filters and lists contain expired - reason: unpaid?

On Rust Data, expired - reason: unpaid appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

How should you read the server tags on expired - reason: unpaid?

Read by the game's server browser, the tags expired - reason: unpaid publishes are: gmrust (Game mode): Survival play, standard Rust; mp60 (Max players): Slot count: 60; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Connecting

What is the way to join expired - reason: unpaid?

Enter client.connect 64.40.9.223:28169 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 mp60,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp60
Max players Slot count: 60.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build Build number: 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded Modded listing: the game is changed by plugins or settings.

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.

Rust Data 74,934 players 11,814 servers online