RUST METRICSFlight deck · live data
Data live Servers11,886 Players104,326 Populated3,964 Fresh wipes 3 h514 Scan5 min
‹ All servers103.193.81.15:28080
Offline Full Queue Fresh wipe Wipe due No query

[AU/NZ] RUINFRONT WARFARE | 3X PvPvE WEEKLY

Offline OC 103.193.81.15:28080 checked 10d ago

3x weekly wipes moddedoxide
COM 1 · connect

Server instruments

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

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,300top 69% · #183 in OC
Last wipe25d agoweekly schedule
Next wipe2d 3hSat 31 Oct, 23:13 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 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
15k10k15k20k20 Sep27 Sep4 Oct12 Oct19 Oct26 Oct

Top 69% of all ranked servers, top 86% in OC. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

from its schedule tag

Next wipe Saturday 31 October, 23:13 UTC, in 2d 3h. Its weekly schedule tag · low confidence

usual gap7.9 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1.5

Coming wipes

  1. WPT 1Sat 31 Oct, 23:13 UTC2d 3h
  2. WPT 2Thu 5 Nov, 19:00 UTC6d 23hFW
  3. WPT 3Sat 7 Nov, 23:13 UTC9d 3h
  4. WPT 4Sat 14 Nov, 23:13 UTC16d 3h
  5. WPT 5Sat 21 Nov, 23:13 UTC23d 3h
  6. WPT 6Sat 28 Nov, 23:13 UTC30d 3h
  7. WPT 7Thu 3 Dec, 19:00 UTC34d 23hFW
  8. WPT 8Sat 5 Dec, 23:13 UTC37d 3h

The first 48 hours of its last wipes

Sat 3 OctFri 25 SepFri 18 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 3 Oct, 23:13 UTC25d ago 1 – running 0
Fri 25 Sep, 05:19 UTC34d ago 2 halved by day 2 8.7 days 0
Fri 18 Sep, 05:16 UTC41d ago 1 halved by day 1 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

Reset cycle

What happens on [AU/NZ] RUINFRONT WARFARE | 3X PvPvE WEEKLY when wipe day comes?

The busiest point of its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 0 hours. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. By day 1.5 it fell below half when it didn't.

What wipe timing does [AU/NZ] RUINFRONT WARFARE | 3X PvPvE WEEKLY follow?

The prediction follows its tag, because too few of [AU/NZ] RUINFRONT WARFARE | 3X PvPvE WEEKLY's wipes are on record to confirm its schedule. On Saturday 31 October at 23:13 UTC its next wipe is due. The world in play was created 25 days 20 hours ago. The tags state a wipe schedule of one wipe a week.

Tag meanings

How should you read the tags on [AU/NZ] RUINFRONT WARFARE | 3X PvPvE WEEKLY?

These are the tags [AU/NZ] RUINFRONT WARFARE | 3X PvPvE WEEKLY 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): Match the game version: protocol 2634 is required; cs166652 (Build): Build 166652; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^w (Weekly): Check: wipe cycle. Every week; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; OC (Oceania): The server browser files it under Oceania. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does [AU/NZ] RUINFRONT WARFARE | 3X PvPvE WEEKLY appear in Rust Metrics lists and filters?

These Rust Metrics lists carry [AU/NZ] RUINFRONT WARFARE | 3X PvPvE WEEKLY: 3x Rust servers, checked live, Rust servers in Oceania and Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Region: Oceania; Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Gather rate: 3x.

Player count

What position does [AU/NZ] RUINFRONT WARFARE | 3X PvPvE WEEKLY hold among Rust servers?

Ranked by seven-day player hours, [AU/NZ] RUINFRONT WARFARE | 3X PvPvE WEEKLY sits at #15,300 and #183 in Oceania, inside the top 69%.

How full does [AU/NZ] RUINFRONT WARFARE | 3X PvPvE WEEKLY get?

Status for [AU/NZ] RUINFRONT WARFARE | 3X PvPvE WEEKLY: offline. Last seen 10 days 12 hours ago.

Server

What location is [AU/NZ] RUINFRONT WARFARE | 3X PvPvE WEEKLY hosted in?

Reading: location. The OC tag puts [AU/NZ] RUINFRONT WARFARE | 3X PvPvE WEEKLY in Oceania. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 103.193.81.15:28080.

What Rust version is [AU/NZ] RUINFRONT WARFARE | 3X PvPvE WEEKLY on?

Version check: Rust network protocol 2634 and build 166652 on Windows, run by [AU/NZ] RUINFRONT WARFARE | 3X PvPvE WEEKLY. Matching protocol is required to join. Let Steam update your game.

Is [AU/NZ] RUINFRONT WARFARE | 3X PvPvE WEEKLY up, and how often does it stay up?

[AU/NZ] RUINFRONT WARFARE | 3X PvPvE WEEKLY reports offline. The last reading came 10 days 12 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Map and rules

What rules does [AU/NZ] RUINFRONT WARFARE | 3X PvPvE WEEKLY enforce, and what are its settings?

The name carries the rate: 3x gather on [AU/NZ] RUINFRONT WARFARE | 3X PvPvE WEEKLY. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; 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. Oxide plugins are running. VAC is on. That is Valve's anti-cheat.

What map is [AU/NZ] RUINFRONT WARFARE | 3X PvPvE WEEKLY on?

Check: map. Procedural, size 3,500, seed 20260925, generated by the game on [AU/NZ] RUINFRONT WARFARE | 3X PvPvE WEEKLY. View it on RustMaps from this page: matching size and seed give an identical map.

Connection

How do you connect to [AU/NZ] RUINFRONT WARFARE | 3X PvPvE WEEKLY?

To join: start Rust, press F1 and type client.connect 103.193.81.15:28080. Or press Launch Rust here and Steam opens the game and connects you. https://ruinfront-warfare.tebex.store is where its website sits.

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2634,^w,OC,gmrust,cs166652,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 Match the game version: protocol 2634 is required.
cs166652
Build Build 166652.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

Wipe schedule

^w
Weekly Check: wipe cycle. Every week.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Check: category. Modded, because plugins or settings alter the game.

Region

OC
Oceania The server browser files it under Oceania.

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.