Rust Data

rustdata.spaceservers103.15.236.184:28016.ipynb

Run all rust-data · live

‹ All servers

Online OC 103.15.236.184:28015 checked 13m ago

BushRust | Bi-Weekly TEST | Low upkeep | Chill | Quad

biweekly wipes vanillaoxide

Connect

srv = rust.server("103.15.236.184:28016")
print(srv.connect_command)

Right now

srv.summary()
players now 0/125 # 0% full
7-day average 1 # peak 4
rank #3,546 # top 16% · #91 in OC
last wipe 10d ago # biweekly schedule
next wipe 3d 6h # Sun 1 Nov, 21:54 UTC

Players

srv.players.plot(range="48h")
AveragePeak
0123416:0001:0010:0020:0005:0014:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020016:0001:0010:0020:0005:0014: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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
12k4k6k8k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Wipe schedule · from its schedule tag

srv.wipe_schedule()

Next wipe Sunday 1 November, 21:54 UTC, in 3d 6h. # Its biweekly schedule tag · low confidence

usual gap17 daysbetween real wipes
wipe-day peak16players, last three wipes
crowd held0%else halves by day 4

Coming wipes

inatkind
03d 6hSun 1 Nov, 21:54 UTCwipe
17d 3hThu 5 Nov, 19:00 UTCFW force wipe
217d 6hSun 15 Nov, 21:54 UTCwipe
331d 6hSun 29 Nov, 21:54 UTCwipe
435d 3hThu 3 Dec, 19:00 UTCFW force wipe

The first 48 hours of its last wipes

Sun 18 OctThu 1 Oct
010203040+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Sun 18 Oct, 21:54 UTC10d ago 5 NaN running 1
1 Thu 1 Oct, 22:19 UTC FW27d ago 26 halved by day 4 17 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.

display(srv.map, srv.info())

Map

4740 · seed 3028
Map of BushRust | Bi-Weekly TEST | Low upkeep | Chill | Quad
map
Procedural Map
size
4740
seed
3028
Open on RustMaps

Server

srv.info()
address
103.15.236.184:28015
region
OC
max players
125
group limit
8, the default
wipe schedule
biweekly
last wipe
18 Oct 2026, 21:54 UTC
hostname
–
first seen
13 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0Rustafied.com - AU MediumOC · groups of 16+ · biweekly · 35 on average91/300
1Rustoria.co - AU PremiumOC · groups of 16+ · biweekly · 28 on average56/200
2[NZ/AU] Whangaparusta - Wiped 16/10OC · groups of 8+ · biweekly · 3 on average0/126
3Rusty Coights All Rusty AdventuresOC · groups of 8+ · biweekly · 3 on average1/100
4[AU] Perth Rust Spot | PVP | Vanilla + QoL | FortnightlyOC · groups of 8+ · biweekly · 2 on average0/50
5Rustafied.com - AU MainOC · groups of 16+ · weekly · 146 on average264/700

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does BushRust | Bi-Weekly TEST | Low upkeep | Chill | Quad rank?

Ranked #3,546 on seven-day player hours, BushRust | Bi-Weekly TEST | Low upkeep | Chill | Quad is #91 in Oceania and in the top 16% of all ranked servers.

What population does BushRust | Bi-Weekly TEST | Low upkeep | Chill | Quad carry?

The sample now reads 0 players for BushRust | Bi-Weekly TEST | Low upkeep | Chill | Quad, out of 125 slots. Over the last seven days it averaged 1 players and peaked at 4. The 48-hour sample puts the busiest hour at 10:00 UTC, averaging 2 players.

Server data

How smoothly does BushRust | Bi-Weekly TEST | Low upkeep | Chill | Quad run?

Averaged over 48 hours: 113 server fps, never under 92. Entity numbers reached 127,254, and that includes buildings, deployables and the rest. The memory field tops out at 5,763 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

Which Rust version is BushRust | Bi-Weekly TEST | Low upkeep | Chill | Quad on?

Rust network protocol 2635 and build 168909 on Linux is what BushRust | Bi-Weekly TEST | Low upkeep | Chill | Quad runs. The protocol has to match before you can join, and Steam does the updating.

Is BushRust | Bi-Weekly TEST | Low upkeep | Chill | Quad up, and what does its uptime show?

The current sample puts BushRust | Bi-Weekly TEST | Low upkeep | Chill | Quad online. The uptime it reports puts the last restart about 19 hours ago. Over the last 7 full days the hours up number 167 of 168, 99%. The first row Rust Data holds for it is dated 13 September 2026.

In which location is BushRust | Bi-Weekly TEST | Low upkeep | Chill | Quad hosted?

In Oceania, BushRust | Bi-Weekly TEST | Low upkeep | Chill | Quad lists itself, using the OC tag. Rust Data does not look up where the machine stands; it shows where a server says it is. 103.15.236.184:28015 is its address.

Rules, settings, map

Which rules apply on BushRust | Bi-Weekly TEST | Low upkeep | Chill | Quad, and what settings?

You will not find a gather rate in the string BushRust | Bi-Weekly TEST | Low upkeep | Chill | Quad. The group limit sits at the default of 8 players. Recorded as survival, the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Community is its browser category. Plugins installed: Oxide. The description says vanilla, which here means no changed rates, kits or rules: the game as Facepunch ships it. Anti-cheat status: VAC on.

Which map has BushRust | Bi-Weekly TEST | Low upkeep | Chill | Quad selected?

Size 4,740, seed 3028: the procedural map on BushRust | Bi-Weekly TEST | Low upkeep | Chill | Quad, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipe data

When does BushRust | Bi-Weekly TEST | Low upkeep | Chill | Quad wipe, and how often?

The tag sets the prediction: BushRust | Bi-Weekly TEST | Low upkeep | Chill | Quad has too few wipes on record to confirm its schedule. Sunday 1 November at 21:54 UTC is when the next wipe is due. This world was created 10 days 17 hours ago. A fortnightly wipe schedule is published in its tags.

What is wipe day on BushRust | Bi-Weekly TEST | Low upkeep | Chill | Quad like?

The average peak over recent wipes is 16 players. Peak population on the latest wipe came 2 hours in. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. Otherwise the crowd fell below half by day 4.

Tags and filters

Where does BushRust | Bi-Weekly TEST | Low upkeep | Chill | Quad appear among Rust Data lists and filters?

These Rust Data lists include BushRust | Bi-Weekly TEST | Low upkeep | Chill | Quad: Oceania Rust servers, Rust community servers, unfiltered and Vanilla Rust servers. It appears under these filters on the server list: Region: Oceania; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Server tag: Biweekly ^b, Vanilla ^v and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.

Which meanings do the tags on BushRust | Bi-Weekly TEST | Low upkeep | Chill | Quad hold?

Read by the game's server browser, the tags BushRust | Bi-Weekly TEST | Low upkeep | Chill | Quad publishes are: gmrust (Game mode): Survival play, standard Rust; mp125 (Max players): 125 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^b (Biweekly): The cycle is fourteen days; ^v (Vanilla): No changed rates, kits or rules: the game as Facepunch ships it; ^o (Oxide): The plugin framework in use is Oxide (uMod); OC (Oceania): The server browser files it under Oceania. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Join steps

What is the way into BushRust | Bi-Weekly TEST | Low upkeep | Chill | Quad?

In Rust, F1 opens the console: type client.connect 103.15.236.184:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp125,ptrak,$r?,v2635,^b,^v,OC,gmrust,cs168909,ts8,^o

Game

gmrust
Game mode Survival play, standard Rust.
mp125
Max players 125 slots in total.
ts8
Group limit Team limit of 8, as shipped by default.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Recorded game build: 168909.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code The region field is empty.

Wipe schedule

^b
Biweekly The cycle is fourteen days.

Difficulty

^v
Vanilla No changed rates, kits or rules: the game as Facepunch ships it.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).

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.

Rust Data 94,541 players 11,866 servers online