RUST METRICSFlight deck · live data
Data live Servers11,695 Players60,531 Populated3,473 Fresh wipes 3 h109 Scan5 min
‹ All servers141.94.64.178:48015
Offline Full Queue Fresh wipe Wipe due No query

Rust lifecycle test

Offline 141.94.64.178:48015 checked 2d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 4 6 8 PAX 0 /8

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#15,411top 69%
Last wipe2d agono schedule published
Next wipe4d 17hMon 2 Nov, 04:09 UTC
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
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.

PLAN

Wipe schedule

fixed weekdays

Next wipe Monday 2 November, 04:09 UTC, in 4d 17h. 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

  1. WPT 1Mon 2 Nov, 04:09 UTC4d 17h
  2. WPT 2Thu 5 Nov, 19:00 UTC8d 7hFW
  3. WPT 3Mon 9 Nov, 04:09 UTC11d 17h
  4. WPT 4Mon 16 Nov, 04:09 UTC18d 17h
  5. WPT 5Mon 23 Nov, 04:09 UTC25d 17h
  6. WPT 6Mon 30 Nov, 04:09 UTC32d 17h
  7. WPT 7Thu 3 Dec, 19:00 UTC36d 7hFW
  8. WPT 8Mon 7 Dec, 04:09 UTC39d 17h

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.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 26 Oct, 04:09 UTC2d ago 0 – running 0
Mon 19 Oct, 04:08 UTC9d ago 0 – 7 days 0
Mon 12 Oct, 04:13 UTC16d ago 0 – 7 days 0
Mon 5 Oct, 04:08 UTC23d ago 0 – 7 days 0
Mon 28 Sep, 04:10 UTC30d ago 0 – 7 days 0
Mon 21 Sep, 04:05 UTC37d ago 0 – 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.

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

What should you expect from wipe day on Rust lifecycle test?

An average of 0 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 0 hours in.

How often does Rust lifecycle test wipe, and when?

every Monday at 04:09 UTC is how Rust lifecycle test wipes. On Monday 2 November at 04:09 UTC its next wipe is due. 2 days 6 hours ago the current world was made.

Tags

Which tags does Rust lifecycle test carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp8 (Max players): Slots: 8; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set from Rust lifecycle test. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show Rust lifecycle test?

These Rust Metrics lists carry Rust lifecycle test: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 3 days.

Population

What position does Rust lifecycle test hold among Rust servers?

Player hours over seven days put Rust lifecycle test at #15,411, in the top 69% of all ranked servers.

What player count does Rust lifecycle test carry?

Reading for Rust lifecycle test: offline at this moment; last seen 2 days 6 hours ago. A seven-day average of 0 players is the reading.

Server

Where does Rust lifecycle test sit?

Reading: location. Rust lifecycle test gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 141.94.64.178:48015.

What Rust version is Rust lifecycle test on?

Rust network protocol 2635 and build 168909 on Linux is the build Rust lifecycle test runs. To get in, your game needs the same protocol; Steam applies the update.

Is Rust lifecycle test up, and how often does it stay up?

Check: connection. Rust lifecycle test is offline at this moment. Last contact was 2 days 6 hours ago. Uptime for the last 7 full days: 1 of 168 hours, or 1%. Check: first contact. Rust Metrics logged it on 14 September 2026.

Rules and settings

What rules does Rust lifecycle test enforce, and what are its settings?

Reading the name gives no gather rate for Rust lifecycle test. The group cap is 8 players, which is the default in the game. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

Which map is live on Rust lifecycle test?

Check: map. Procedural, generated by the game, on Rust lifecycle test.

Connection

How do you connect to Rust lifecycle test?

To join: start Rust, press F1 and type client.connect 141.94.64.178:48015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp8
Max players Slots: 8.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is 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.