RUST METRICSFlight deck · live data
Data live Servers11,882 Players96,098 Populated4,089 Fresh wipes 3 h162 Scan5 min
‹ All servers159.196.30.227:20030
Online Full Queue Fresh wipe Wipe due No query

[AU/NZ] TearBearGaming PvE | 1000x|BP Unlocked

Online 159.196.30.227:20030 checked 12m ago

1000x biweekly wipes vanillamoddedoxidepve
COM 1 · connect

Server instruments

last reading Tue 17:00 UTC
0 25 50 75 100 PAX 1 /100

Players now

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

Server fps

48 h low 8 · below 20 is lag, below 10 is bad
0 25 50 75 100 ENT 76,829 ×1000

Entities

48 h range 74,514–78,604 · memory 2,492 MB
1239 ET SINCE RESTART 09:59

Uptime

9 h 59 min since its last restart, at the last reading
7-day average1peak 6
Rank#3,993top 18%
Last wipe10d agobiweekly schedule
Next wipe3d 18hSat 31 Oct, 13:10 UTC
Memory2,492MB48 h peak 6 players
REC 1

Players

AveragePeak
0246819:0004:0013:0023:0008:0017:00

Hourly average and peak, UTC.

REC 2

Server performance

01020304019:0004:0013: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
12k4k6k8k20 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

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

PLAN

Wipe schedule

from its schedule tag

Next wipe Saturday 31 October, 13:10 UTC, in 3d 18h. Its biweekly schedule tag · low confidence

usual gap14.6 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak3players, last three wipes
crowd held50%else halves by day 4

Coming wipes

  1. WPT 1Sat 31 Oct, 13:10 UTC3d 18h
  2. WPT 2Thu 5 Nov, 19:00 UTC9d 0hFW
  3. WPT 3Sat 14 Nov, 13:10 UTC17d 18h
  4. WPT 4Sat 28 Nov, 13:10 UTC31d 18h
  5. WPT 5Thu 3 Dec, 19:00 UTC37d 0hFW

The first 48 hours of its last wipes

Sat 17 OctThu 1 OctFri 18 Sep
00.511.52+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 17 Oct, 13:10 UTC10d ago 2 – running 0
Thu 1 Oct, 20:51 UTC FW25d ago 2 held half 15.7 days 0
Fri 18 Sep, 08:37 UTC39d ago 4 halved by day 4 13.5 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 [AU/NZ] TearBearGaming PvE | 1000x|BP Unlocked?

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

What wipe timing does [AU/NZ] TearBearGaming PvE | 1000x|BP Unlocked follow?

The prediction follows its tag, because too few of [AU/NZ] TearBearGaming PvE | 1000x|BP Unlocked's wipes are on record to confirm its schedule. Saturday 31 October at 13:10 UTC is when its next wipe is due. 10 days 4 hours ago the current world was made. Its tags publish a wipe schedule of one wipe every two weeks.

Tag meanings

Which tags does [AU/NZ] TearBearGaming PvE | 1000x|BP Unlocked carry, and what do they mean?

Tags published by [AU/NZ] TearBearGaming PvE | 1000x|BP Unlocked, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): Slots: 100; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): The server runs game build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^b (Biweekly): Two-week wipe schedule; ^v (Vanilla): The stock game: Facepunch's rates, kits and rules, unchanged; ^p (PvE): Check: mode. PvE, so the world supplies the danger, not other players; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game. 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 [AU/NZ] TearBearGaming PvE | 1000x|BP Unlocked?

Rust Metrics lists featuring [AU/NZ] TearBearGaming PvE | 1000x|BP Unlocked: Gather rate above 10x: server list, Rust servers in Oceania, Modded Rust servers, checked live and Rust PvE servers. These filters bring it up on the server list: Region: Oceania; Type: Vanilla and Modded; Game mode: PvE; Server tag: Biweekly ^b, Vanilla ^v, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks; Gather rate: More than 10x.

Player count

Where does [AU/NZ] TearBearGaming PvE | 1000x|BP Unlocked sit in the rankings?

Player hours over seven days put [AU/NZ] TearBearGaming PvE | 1000x|BP Unlocked at #3,993, in the top 18% of all ranked servers.

What player count does [AU/NZ] TearBearGaming PvE | 1000x|BP Unlocked carry?

1 of 100 slots are filled on [AU/NZ] TearBearGaming PvE | 1000x|BP Unlocked right now. Seven-day check: 1 players on average. Peak reading: 6. Check: 48-hour peak. 12:00 UTC, 4 players on average.

Server

What location is [AU/NZ] TearBearGaming PvE | 1000x|BP Unlocked hosted in?

Reading: location. Nothing in the tags, but the name of [AU/NZ] TearBearGaming PvE | 1000x|BP Unlocked points to Oceania. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 159.196.30.227:20030.

What Rust version is [AU/NZ] TearBearGaming PvE | 1000x|BP Unlocked on?

Rust network protocol 2635 and build 168909 on Windows is the build [AU/NZ] TearBearGaming PvE | 1000x|BP Unlocked runs. Matching protocol is required to join. Let Steam update your game.

Is performance on [AU/NZ] TearBearGaming PvE | 1000x|BP Unlocked within range?

Over the last 48 hours the average was 21 server fps; the floor was 8. Check: entities. The peak was 78,604, counting buildings, deployables and the rest of the world. Reading: 2,868 MB of memory at the highest. Lag, as players feel it, is low fps plus a climbing entity count.

Is [AU/NZ] TearBearGaming PvE | 1000x|BP Unlocked up, and how often does it stay up?

Reading: online. [AU/NZ] TearBearGaming PvE | 1000x|BP Unlocked answers right now. Reading: uptime. About 9 hours ago it restarted, on its own count. Uptime for the last 7 full days: 145 of 168 hours, or 86%. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Rules and settings

What rules does [AU/NZ] TearBearGaming PvE | 1000x|BP Unlocked enforce, and what are its settings?

The name carries the rate: 1000x gather on [AU/NZ] TearBearGaming PvE | 1000x|BP Unlocked. 8 players per group, the default value. Mode check gives pve; fighting between players is off. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Oxide. The server calls itself vanilla, with this meaning: the stock game: Facepunch's rates, kits and rules, unchanged. Check: anti-cheat. VAC, Valve's system, is off.

What map is [AU/NZ] TearBearGaming PvE | 1000x|BP Unlocked on?

Check: map. Procedural, size 3,500, seed 901796074, generated by the game on [AU/NZ] TearBearGaming PvE | 1000x|BP Unlocked. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

Join

What do you do to join [AU/NZ] TearBearGaming PvE | 1000x|BP Unlocked?

Check: join. Open Rust, press F1, then enter client.connect 159.196.30.227:20030. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. You can find its website at https://www.tearbeargaming.com.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2635,^b,^v,^p,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players Slots: 100.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build The server runs game build 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly Two-week wipe schedule.

Difficulty

^v
Vanilla The stock game: Facepunch's rates, kits and rules, unchanged.

Gameplay

^p
PvE Check: mode. PvE, so the world supplies the danger, not other players.

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.