Rust Data

rustdata.spaceservers160.16.61.172:28017.ipynb

Run all rust-data · live

‹ All servers

Online 160.16.61.172:28015 checked 10m ago

菠萝测试

biweekly wipes moddedoxidepve

Connect

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

Right now

srv.summary()
players now 1/100 # 1% full
7-day average 0 # peak 1
rank #6,351 # top 29%
last wipe 2d ago # biweekly schedule
next wipe 3d 4h # Sun 1 Nov, 15:19 UTC

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75112:0014:0015:0017:0007:0009: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
15k10k15k20k3 Oct8 Oct13 Oct19 Oct24 Oct29 Oct

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

Wipe schedule · fixed weekdays

srv.wipe_schedule()

Next wipe Sunday 1 November, 15:19 UTC, in 3d 4h. # Every 3 weeks on Saturday at 16:16 and every other Sunday at 15:19 UTC · medium confidence

usual gap8.4 daysbetween real wipes
on rhythm80%of its recent wipes
wipe-day peak1players, last three wipes

Coming wipes

inatkind
03d 4hSun 1 Nov, 15:19 UTCwipe
17d 7hThu 5 Nov, 19:00 UTCFW force wipe
216d 5hSat 14 Nov, 16:16 UTCwipe
317d 4hSun 15 Nov, 15:19 UTCwipe
431d 4hSun 29 Nov, 15:19 UTCwipe
535d 7hThu 3 Dec, 19:00 UTCFW force wipe
637d 5hSat 5 Dec, 16:16 UTCwipe

The first 48 hours of its last wipes

Mon 26 OctSat 24 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, 11 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Mon 26 Oct, 15:50 UTC2d ago 1 NaN running 0
1 Sat 24 Oct, 16:16 UTC4d ago 1 NaN 2 days 0
2 Sun 18 Oct, 15:19 UTC10d ago NaN NaN 6 days 0
3 Sun 4 Oct, 16:34 UTC24d ago NaN NaN 13.9 days 0
4 Sat 3 Oct, 14:46 UTC25d ago 1 NaN 1.1 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.61.172:28015
region
–
max players
100
group limit
8, the default
wipe schedule
biweekly
last wipe
26 Oct 2026, 15:50 UTC
hostname
–
first seen
3 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 · 58 on average78/200
1[JP][PvE]mameserver初心者おいで!EA · groups of 8+ · biweekly · 8 on average5/65
2JP 1x-10x PVE++|XPレベル1000|火山|ペット|NPCレイドEA · groups of 1000+ · 1x · biweekly · 7 on average9/69
3[喜相逢] PVE丨仿官原倍丨萌新养老EA · groups of 12+ · biweekly · 5 on average3/100
4[PVE][JP] そば鯖 Raidable Bases 初心者大歓迎EA · groups of 16+ · biweekly · 4 on average2/50
5『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老EA · groups of 8+ · biweekly · 3 on average7/100

Quick answers

From the figures on this page.

Population data

What position does 菠萝测试 take in the server rankings?

Rank #6,351 on seven-day player hours for 菠萝测试, within the top 29% of all ranked servers.

What population does 菠萝测试 carry?

Current row: 1 players on 菠萝测试, against 100 slots. Over the last seven days it averaged 0 players and peaked at 1. Peak hour in the last 48 hours: 15:00 UTC, mean 1 players.

Server data

What is the Rust version on 菠萝测试?

Version Rust network protocol 2635 and build 168909 on Windows is reported by 菠萝测试. Joining needs the same protocol on your game; Steam handles the update.

How reliable is 菠萝测试, and is it online now?

Online is the state at the latest refresh for 菠萝测试. Uptime of 24% across the last 7 full days: 41 hours of 168. Rust Data logged it first on 3 October 2026.

Where does 菠萝测试 sit?

Its name points to Asia, but 菠萝测试 publishes no region tag. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 160.16.61.172:28015.

Rules, settings, map

Which rules apply on 菠萝测试, and what settings?

You will not find a gather rate in the string 菠萝测试. The group limit sits at the default of 8 players. Recorded as pve, player combat is not allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.

Wipe schedule

On what schedule does 菠萝测试 wipe?

Wipes on 菠萝测试 run every 3 weeks on Saturday at 16:16 and every other Sunday at 15:19 UTC. On Sunday 1 November at 15:19 UTC the next wipe is due. A new world was started 2 days 19 hours ago, and that is the one in play. A fortnightly wipe schedule is published in its tags.

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

Across recent wipes the busiest point averaged 1 players. 11 hours after the latest wipe, the crowd reached its peak.

Lists and tags

Which lists on Rust Data hold 菠萝测试, and which filters?

On Rust Data, 菠萝测试 appears in these lists: Modded Rust servers and Rust PvE servers. Under these filters on the server list, it is listed: 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.

How should you read the server tags on 菠萝测试?

The game's server browser reads these tags from 菠萝测试: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): 100 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): The server runs build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^b (Biweekly): The cycle is fourteen days; ^p (PvE): No player-versus-player combat; the danger comes from the world; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. 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

What is the way to join 菠萝测试?

Enter client.connect 160.16.61.172: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 Survival play, standard Rust.
mp100
Max players 100 slots in total.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build The server runs build 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code No region code is set.

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 The plugin framework in use is Oxide (uMod).
^z
Modded Modded listing: the game is changed by plugins or settings.

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 59,874 players 11,727 servers online