Rust Data

rustdata.spaceservers141.94.64.178:48017.ipynb

Run all rust-data · live

‹ All servers

Offline 141.94.64.178:48015 checked 2d ago

Rust lifecycle test

Connect

srv = rust.server("141.94.64.178:48017")
print(srv.connect_command)

Right now

srv.summary()
players now 0/8 # 0% full
7-day average 0 # peak –
rank #15,400 # top 69%
last wipe 2d ago # no schedule published
next wipe 4d 19h # Mon 2 Nov, 04:09 UTC

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
RankRank in region
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

Wipe schedule · fixed weekdays

srv.wipe_schedule()

Next wipe Monday 2 November, 04:09 UTC, in 4d 19h. # Every Monday at 04:09 UTC · high confidence

usual gap7 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak0players, last three wipes

Coming wipes

inatkind
04d 19hMon 2 Nov, 04:09 UTCwipe
18d 10hThu 5 Nov, 19:00 UTCFW force wipe
211d 19hMon 9 Nov, 04:09 UTCwipe
318d 19hMon 16 Nov, 04:09 UTCwipe
425d 19hMon 23 Nov, 04:09 UTCwipe
532d 19hMon 30 Nov, 04:09 UTCwipe
636d 10hThu 3 Dec, 19:00 UTCFW force wipe
739d 19hMon 7 Dec, 04:09 UTCwipe

The first 48 hours of its last wipes

Mon 26 OctMon 19 OctMon 12 Oct
01234+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Mon 26 Oct, 04:09 UTC2d ago 0 NaN running 0
1 Mon 19 Oct, 04:08 UTC9d ago 0 NaN 7 days 0
2 Mon 12 Oct, 04:13 UTC16d ago 0 NaN 7 days 0
3 Mon 5 Oct, 04:08 UTC23d ago 0 NaN 7 days 0
4 Mon 28 Sep, 04:10 UTC30d ago 0 NaN 7 days 0
5 Mon 21 Sep, 04:05 UTC37d ago 0 NaN 7 days 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

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
141.94.64.178:48015
region
–
max players
8
group limit
8, the default
wipe schedule
–
last wipe
26 Oct 2026, 04:09 UTC
hostname
–
first seen
14 Sep 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 536 on average454/475
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average259/225
2Rustoria.co - EU MainEU · groups of 16+ · weekly · 318 on average27/250
3Rusty Moose |EU Main|EU · groups of 12+ · weekly · 317 on average33/250
4Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 276 on average140/200
5Rustafied.com - EU FridayEU · groups of 16+ · weekly · 265 on average53/100

Quick answers

From the figures on this page.

Player counts

How does Rust lifecycle test compare in the rankings?

Rank #15,400 on seven-day player hours for Rust lifecycle test, within the top 69% of all ranked servers.

How many players does Rust lifecycle test hold at once?

Rust lifecycle test returns no live count at this refresh, having last been seen 2 days 4 hours ago. Over the last seven days it averaged 0 players.

Server data

What Rust version does Rust lifecycle test run?

Rust network protocol 2635 and build 168909 on Linux is what Rust lifecycle test runs. Joining needs the same protocol on your game; Steam handles the update.

How reliable is Rust lifecycle test, and is it online now?

Rust lifecycle test is offline at this refresh; the last response came 2 days 4 hours ago. Uptime of 1% across the last 7 full days: 1 hours of 168. Its earliest recorded date in Rust Data is 14 September 2026.

In which location is Rust lifecycle test hosted?

No region is published by Rust lifecycle test. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 141.94.64.178:48015.

Map and rules

What rules and settings are recorded for Rust lifecycle test?

The name Rust lifecycle test carries no gather rate. The group limit sits at the default of 8 players. Game mode survival, with this note: the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. It is a community server, and the browser files it under Community. Anti-cheat status: VAC on.

What is the map on Rust lifecycle test?

The game generates its map: procedural, on Rust lifecycle test.

Wipe data

When does Rust lifecycle test wipe, and how often?

Wipes on Rust lifecycle test run every Monday at 04:09 UTC. Monday 2 November at 04:09 UTC is when the next wipe is due. This world was created 2 days 4 hours ago.

On Rust lifecycle test, what happens on wipe day?

The average peak over recent wipes is 0 players. Peak population on the latest wipe came 0 hours in.

Tags and filters

Which Rust Data filters and lists contain Rust lifecycle test?

On Rust Data, Rust lifecycle test appears in these lists: Rust community servers, unfiltered. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 3 days.

Which meanings do the tags on Rust lifecycle test hold?

Read by the game's server browser, the tags Rust lifecycle test publishes are: gmrust (Game mode): Survival play, standard Rust; mp8 (Max players): Slot count: 8; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Join steps

How can I connect to Rust lifecycle test?

The manual route: launch Rust, F1, then client.connect 141.94.64.178:48015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

Published as mp8,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp8
Max players Slot count: 8.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build Build number: 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code The region field is empty.

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 46,883 players 11,635 servers online