RUST METRICSFlight deck · live data
Data live Servers11,718 Players61,678 Populated3,282 Fresh wipes 3 h174 Scan5 min
‹ All servers159.69.137.116:40324
Offline Full Queue Fresh wipe Wipe due No query

RUST_PRIME Solo|Duo|Trio X3| TP | HOME | KIT

Offline 159.69.137.116:40324 checked 26d ago

3x weekly wipes moddedoxide
COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 1 /50

Players now

2% 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#13,901top 61%
Last wipe27d agoweekly schedule
Next wipe12hFri 30 Oct, 13:12 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, measured since 23 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k23 Sep26 Sep30 Sep3 Oct7 Oct10 Oct

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

PLAN

Wipe schedule

from its schedule tag

Next wipe Friday 30 October, 13:12 UTC, in 12h. Its weekly schedule tag · low confidence

usual gap4.1 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak3players, last three wipes
crowd held50%else halves by day 2

Coming wipes

  1. WPT 1Fri 30 Oct, 13:12 UTC12h
  2. WPT 2Thu 5 Nov, 19:00 UTC6d 18hFW
  3. WPT 3Fri 6 Nov, 13:12 UTC7d 12h
  4. WPT 4Fri 13 Nov, 13:12 UTC14d 12h
  5. WPT 5Fri 20 Nov, 13:12 UTC21d 12h
  6. WPT 6Fri 27 Nov, 13:12 UTC28d 12h
  7. WPT 7Thu 3 Dec, 19:00 UTC34d 18hFW
  8. WPT 8Fri 4 Dec, 13:12 UTC35d 12h

The first 48 hours of its last wipes

Fri 2 OctSat 26 SepThu 24 Sep
01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 13:12 UTC27d ago 2 – running 0
Sat 26 Sep, 10:20 UTC33d ago 3 halved by day 2 6.1 days 0
Thu 24 Sep, 10:39 UTC35d ago 4 held half 2 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

Reset cycle

What happens on RUST_PRIME Solo|Duo|Trio X3| TP | HOME | KIT when wipe day comes?

At their busiest, its recent wipes drew 3 players on average. After the latest wipe, numbers topped out at 6 hours. The crowd stayed above half that peak until the next wipe in 50% of its recent wipes. By day 2 it fell below half when it didn't.

What wipe timing does RUST_PRIME Solo|Duo|Trio X3| TP | HOME | KIT follow?

Its tag guides the prediction: too few of RUST_PRIME Solo|Duo|Trio X3| TP | HOME | KIT's wipes are on record to confirm its schedule. On Friday 30 October at 13:12 UTC its next wipe is due. 27 days 11 hours ago the current world was made. The tags state a wipe schedule of one wipe a week.

Lists and filters

How should you read the tags on RUST_PRIME Solo|Duo|Trio X3| TP | HOME | KIT?

These are the tags RUST_PRIME Solo|Duo|Trio X3| TP | HOME | KIT publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): Slots: 50; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166586 (Build): The server runs game build 166586; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^w (Weekly): It wipes each week; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show RUST_PRIME Solo|Duo|Trio X3| TP | HOME | KIT?

Rust Metrics lists featuring RUST_PRIME Solo|Duo|Trio X3| TP | HOME | KIT: 3x Rust servers, checked live and Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Gather rate: 3x.

Population

Where does RUST_PRIME Solo|Duo|Trio X3| TP | HOME | KIT sit in the rankings?

Ranking for RUST_PRIME Solo|Duo|Trio X3| TP | HOME | KIT: #13,901 on seven-day player hours, top 61% of all ranked servers.

What player count does RUST_PRIME Solo|Duo|Trio X3| TP | HOME | KIT carry?

RUST_PRIME Solo|Duo|Trio X3| TP | HOME | KIT is not responding; status offline, last seen 26 days 2 hours ago.

Operator and location

Which location does RUST_PRIME Solo|Duo|Trio X3| TP | HOME | KIT run from?

No region tag on RUST_PRIME Solo|Duo|Trio X3| TP | HOME | KIT. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 159.69.137.116:40324.

What Rust version is RUST_PRIME Solo|Duo|Trio X3| TP | HOME | KIT on?

Reading: RUST_PRIME Solo|Duo|Trio X3| TP | HOME | KIT, Rust network protocol 2634 and build 166586, Linux. To get in, your game needs the same protocol; Steam applies the update.

How reliable is RUST_PRIME Solo|Duo|Trio X3| TP | HOME | KIT, and is it online now?

Check: connection. RUST_PRIME Solo|Duo|Trio X3| TP | HOME | KIT is offline at this moment. Last contact was 26 days 2 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 23 September 2026.

Map and rules

What settings and rules apply on RUST_PRIME Solo|Duo|Trio X3| TP | HOME | KIT?

Gather rate check: 3x. That comes from the name RUST_PRIME Solo|Duo|Trio X3| TP | HOME | KIT. 8 players per group, the default value. Mode check gives survival; gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.

Which map is live on RUST_PRIME Solo|Duo|Trio X3| TP | HOME | KIT?

From seed 1337, the game generates the procedural map on RUST_PRIME Solo|Duo|Trio X3| TP | HOME | KIT. Its size is 3,500. The map repeats when size and seed match. Open it on RustMaps from this page. Its map carries the name Custom Map.

How to join

How can you get onto RUST_PRIME Solo|Duo|Trio X3| TP | HOME | KIT?

Press F1 in Rust and enter client.connect 159.69.137.116:40324. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2634,^w,gmrust,cs166586,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players Slots: 50.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166586
Build The server runs game build 166586.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Wipe schedule

^w
Weekly It wipes each week.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Check: category. Modded, because plugins or settings alter the game.

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.