RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h18 Scan5 min
‹ All servers46.181.239.168:30315
Online Full Queue Fresh wipe Wipe due No query

RustHunter Main [Ryzen9950x]

Online 46.181.239.168:30315 checked 2h ago

biweekly wipes moddedoxide
COM 1 · connect

Server instruments

last reading Wed 17:00 UTC
0 12 25 38 50 PAX 2 /50

Players now

4% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 60 SERVER FPS

Server fps

48 h low 30 · below 20 is lag, below 10 is bad
0 100 200 300 400 ENT 221,368 ×1000

Entities

48 h range 206,416–225,907 · memory 4,901 MB
1239 ET SINCE RESTART 17:59

Uptime

17 h 59 min since its last restart, at the last reading
7-day average2peak 6
Rank#2,389top 11%
Last wipe12d agobiweekly schedule
Next wipe7d 23hThu 5 Nov, 19:00 UTC FW
Memory4,901MB48 h peak 5 players
REC 1

Players

AveragePeak
0246820:0005:0014:0023:0008:0017:00

Hourly average and peak, UTC.

REC 2

Server performance

02040608020:0005:0014:0023:0008:0017: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.

REC 3

Rank

daily · 1 is best
RankRank in region
11k2k3k4k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

PLAN

Wipe schedule

fixed weekdays

Next wipe Thursday 5 November, 19:00 UTC, in 7d 23h. The force wipe · high confidence

usual gap28 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak6players, last three wipes
crowd held50%else halves by day 5

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC7d 23hFW
  2. WPT 2Thu 12 Nov, 22:09 UTC15d 2h
  3. WPT 3Thu 3 Dec, 19:00 UTC35d 23hFW
  4. WPT 4Thu 10 Dec, 22:09 UTC43d 2h

The first 48 hours of its last wipes

Thu 15 OctThu 1 OctThu 17 Sep
02468+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 15 Oct, 22:09 UTC12d ago 6 – running 0
Thu 1 Oct, 17:59 UTC FW27d ago 4 held half 14.2 days 1
Thu 17 Sep, 22:10 UTC40d ago 8 halved by day 5 13.8 days 2

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 happens on RustHunter Main [Ryzen9950x] when wipe day comes?

The busiest point of its recent wipes drew 6 players on average. After the latest wipe, numbers topped out at 14 hours. Above half that peak the crowd stayed until the next wipe in 50% of recent wipes. When it didn't hold, by day 5 it fell below half.

What wipe timing does RustHunter Main [Ryzen9950x] follow?

every 4 weeks on Thursday at 22:09 UTC is how RustHunter Main [Ryzen9950x] wipes. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. 12 days 21 hours ago the current world was made. A wipe schedule of every two weeks is published in its tags.

Lists and filters

How should you read the tags on RustHunter Main [Ryzen9950x]?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): 50 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): The server runs game build 168909; ptsw (Networking): It runs on the 'sw' network layer; $r? (Region code): No region code is set; ^b (Biweekly): It wipes once a fortnight; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game; jp0 (Custom tag): A plugin or the owner set this tag; Rust does not ship it from RustHunter Main [Ryzen9950x]. 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 RustHunter Main [Ryzen9950x]?

These Rust Metrics lists carry RustHunter Main [Ryzen9950x]: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.

Occupancy

Where does RustHunter Main [Ryzen9950x] sit in the rankings?

Player hours over seven days put RustHunter Main [Ryzen9950x] at #2,389, in the top 11% of all ranked servers.

How full does RustHunter Main [Ryzen9950x] get?

Current headcount on RustHunter Main [Ryzen9950x]: 2 players, 50 slots available. Check: players over seven days. Average 2, peak 6. Average at the busiest hour was 4 players, at 10:00 UTC over the last 48 hours.

Operator and location

Which location does RustHunter Main [Ryzen9950x] run from?

Reading: location. RustHunter Main [Ryzen9950x] gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 46.181.239.168:30315.

What Rust version is RustHunter Main [Ryzen9950x] on?

Reading: RustHunter Main [Ryzen9950x], Rust network protocol 2635 and build 168909, Windows. To get in, your game needs the same protocol; Steam applies the update.

How does RustHunter Main [Ryzen9950x] perform?

Over the last 48 hours the average was 55 server fps; the floor was 30. Peak entity count: 225,907. Buildings, deployables and all else included. Reading: 5,981 MB of memory at the highest. Expect lag when fps falls and entities climb.

Is RustHunter Main [Ryzen9950x] up, and how often does it stay up?

Reading: online. RustHunter Main [Ryzen9950x] answers right now. Reading: uptime. About 17 hours ago it restarted, on its own count. Reading: 100% uptime over the last 7 full days. It was up 168 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Settings and map

How is RustHunter Main [Ryzen9950x] configured, and what rules are in force?

Reading the name gives no gather rate for RustHunter Main [Ryzen9950x]. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Oxide of them. VAC is on. That is Valve's anti-cheat.

Which map is live on RustHunter Main [Ryzen9950x]?

Size 4,750 and seed 1413942102: the game generates the procedural map on RustHunter Main [Ryzen9950x] from them. The map repeats when size and seed match. Open it on RustMaps from this page.

Join

What do you do to join RustHunter Main [Ryzen9950x]?

Press F1 in Rust and enter client.connect 46.181.239.168:30315. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. https://m.vk.com/club222606635?from=groups is where its website sits.

PLACARDS

Server tags

what each one means

Published as mp50,ptsw,jp0,$r?,v2635,^b,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players 50 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build The server runs game build 168909.
ptsw
Networking It runs on the 'sw' network layer.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly It wipes once a fortnight.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Modded: plugins or settings depart from the stock game.

Other

jp0
Custom tag A plugin or the owner set this tag; Rust does not ship it.

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.