Rust Data

rustdata.spaceservers160.16.115.86:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 160.16.115.86:28015 checked 1d ago

菠萝测试

biweekly wipes moddedoxidepve

Connect

srv = rust.server("160.16.115.86:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 0/100 # 0% full
7-day average 0 # peak 1
rank #11,409 # top 51%
last wipe 2d ago # biweekly schedule
next wipe 7d 20h # Thu 5 Nov, 19:00 UTC FW

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75115:0016:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
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. 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
15k10k15k20k4 Oct9 Oct14 Oct18 Oct23 Oct28 Oct

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

Wipe schedule · from its schedule tag

srv.wipe_schedule()

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

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

Coming wipes

inatkind
07d 20hThu 5 Nov, 19:00 UTCFW force wipe
111d 17hMon 9 Nov, 15:50 UTCwipe
225d 17hMon 23 Nov, 15:50 UTCwipe
335d 20hThu 3 Dec, 19:00 UTCFW force wipe
439d 17hMon 7 Dec, 15:50 UTCwipe

The first 48 hours of its last wipes

Mon 26 OctSun 18 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Mon 26 Oct, 15:50 UTC2d ago 1 NaN running 0
1 Sun 18 Oct, 15:19 UTC10d ago 1 halved by day 4 8 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

Custom map, no picture published
map
Custom Map
size
–
seed
–

Server

srv.info()
address
160.16.115.86:28015
region
–
max players
100
group limit
8, the default
wipe schedule
biweekly
last wipe
26 Oct 2026, 15:50 UTC
hostname
–
first seen
4 Oct 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0【炮炮PVE启蒙】纯净|特色|突袭|技能EA · groups of 16+ · biweekly · 60 on average15/200
1[JP][PvE]mameserver初心者おいで!EA · groups of 8+ · biweekly · 8 on average1/65
2JP 1x-10x PVE++|XPレベル1000|火山|ペット|NPCレイドEA · groups of 1000+ · 1x · biweekly · 7 on average2/69
3[喜相逢] PVE丨仿官原倍丨萌新养老EA · groups of 12+ · biweekly · 5 on average0/100
4[PVE][JP] そば鯖 Raidable Bases 初心者大歓迎EA · groups of 16+ · biweekly · 4 on average0/50
5『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老EA · groups of 8+ · biweekly · 3 on average1/100

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does 菠萝测试 rank?

Player hours over seven days put 菠萝测试 at #11,409, in the top 51% of the ranked set.

What population does 菠萝测试 carry?

The current row shows 菠萝测试 offline; the last response was 30 hours ago. Over the last seven days it averaged 0 players and peaked at 1. Peak hour in the last 48 hours: 15:00 UTC, mean 0 players.

Server facts

Which Rust version is 菠萝测试 on?

Version Rust network protocol 2635 and build 168909 on Windows is reported by 菠萝测试. The protocol has to match before you can join, and Steam does the updating.

How reliable is 菠萝测试, and is it up?

菠萝测试 is offline at this refresh; the last response came 30 hours ago. 6 of 168 hours up over the last 7 full days, or 4%. Rust Data logged it first on 4 October 2026.

Where does 菠萝测试 sit?

No region tag is published by 菠萝测试, though its name points to Asia. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 160.16.115.86:28015.

Rules, settings, map

Which settings and rules does 菠萝测试 run?

No gather rate appears in the name: 菠萝测试. The group limit sits at the default of 8 players. Game mode pve, with this note: no combat between players. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.

Wipe data

On what schedule does 菠萝测试 wipe?

The prediction follows the tag, because 菠萝测试's wipes on record are too few to confirm the schedule. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. This world was created 2 days 6 hours ago. Its tags carry a wipe schedule of every two weeks.

On 菠萝测试, what happens on wipe day?

Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 1 hours after it began. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. In the wipes where it did not hold, half was lost by day 4.

Tags, lists

Which Rust Data filters and lists contain 菠萝测试?

These Rust Data lists include 菠萝测试: Modded Rust servers and Rust PvE servers. It appears under these filters on the server list: Region: Asia; Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 3 days.

Which meanings do the tags on 菠萝测试 hold?

Read by the game's server browser, the tags 菠萝测试 publishes are: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): The server lists 100 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): The server runs 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; ^p (PvE): No player-versus-player combat; the danger comes from the world; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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.

How to join

How can I connect to 菠萝测试?

Enter client.connect 160.16.115.86:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Rust survival in its standard form.
mp100
Max players The server lists 100 slots.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build The server runs 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.

Gameplay

^p
PvE No player-versus-player combat; the danger comes from the world.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it sits under Modded.

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 61,343 players 11,769 servers online