Offline 39.182.16.163:28015 checked 26d ago
菠萝测试
Connect
srv = rust.server("39.182.16.163:28017")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 bestTop 61% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()Next wipe Saturday 31 October, 14:46 UTC, in 1d 6h. # Its biweekly schedule tag · low confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 1d 6h | Sat 31 Oct, 14:46 UTC | wipe |
| 1 | 6d 10h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 2 | 15d 6h | Sat 14 Nov, 14:46 UTC | wipe |
| 3 | 29d 6h | Sat 28 Nov, 14:46 UTC | wipe |
| 4 | 34d 10h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 5 | 43d 6h | Sat 12 Dec, 14:46 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 3 Oct, 14:46 UTC26d ago | 1 | NaN | running | 0 |
| 1 | Sat 3 Oct, 01:34 UTC27d ago | 1 | NaN | 0.6 days | 0 |
| 2 | Thu 1 Oct, 16:06 UTC28d ago | 1 | NaN | 1.4 days | 0 |
| 3 | Mon 28 Sep, 15:43 UTC31d ago | 1 | NaN | 3 days | 0 |
| 4 | Sun 27 Sep, 09:05 UTC32d ago | 1 | NaN | 1.3 days | 1 |
# 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 39.182.16.163:28015
- region
- –
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- biweekly
- last wipe
- 3 Oct 2026, 14:46 UTC
- hostname
- –
- first seen
- 27 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | 【炮炮PVE启蒙】纯净｜特色｜突袭｜技能 | EA · groups of 16+ · biweekly · 59 on average | 65/200 |
| 1 | JP 1x-10x PVE++|XPレベル1000|火山|ペット|NPCレイド | EA · groups of 1000+ · 1x · biweekly · 7 on average | 8/69 |
| 2 | [JP][PvE]mameserver初心者おいで！ | EA · groups of 8+ · biweekly · 7 on average | 8/? |
| 3 | [喜相逢] PVE丨仿官原倍丨萌新养老 | EA · groups of 12+ · biweekly · 5 on average | 2/100 |
| 4 | [PVE][JP] そば鯖 Raidable Bases 初心者大歓迎 | EA · groups of 16+ · biweekly · 4 on average | 2/50 |
| 5 | 『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老 | EA · groups of 8+ · biweekly · 3 on average | 9/100 |
Quick answers
From the figures on this page.
Population
What position does 菠萝测试 take in the server rankings?
Player hours over seven days put 菠萝测试 at #13,917, in the top 61% of the ranked set.
How many players does 菠萝测试 hold at once?
Offline now for 菠萝测试, with the last sample 26 days 17 hours ago.
Server facts
What is the Rust version on 菠萝测试?
Rust network protocol 2634 and build 166652 on Windows is what 菠萝测试 runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is 菠萝测试, and is it up?
Offline now for 菠萝测试, last seen 26 days 17 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 27 September 2026.
Where does 菠萝测试 sit?
The name of 菠萝测试 points to Asia, even though no region tag is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 39.182.16.163:28015.
Settings and map
Which rules apply on 菠萝测试, and what settings?
No gather rate appears in the name: 菠萝测试. The group limit sits at the default of 8 players. Recorded as pve, player combat is not allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. The VAC field reads off.
Which map has 菠萝测试 selected?
The game generates its map: procedural, on 菠萝测试.
Wipe schedule
On what schedule does 菠萝测试 wipe?
The tag sets the prediction: 菠萝测试 has too few wipes on record to confirm its schedule. Saturday 31 October at 14:46 UTC is when the next wipe is due. This world was created 26 days 17 hours ago. A fortnightly wipe schedule is published in its tags.
What is wipe day on 菠萝测试 like?
Across recent wipes the busiest point averaged 1 players. 1 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Which lists on Rust Data hold 菠萝测试, and which filters?
These Rust Data lists include 菠萝测试: 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.
How should you read the server tags on 菠萝测试?
Read by the game's server browser, the tags 菠萝测试 publishes are: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): Slot count: 100; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs166652 (Build): The server runs build 166652; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^b (Biweekly): Wipes run on a two-week cycle; ^p (PvE): Players do not fight each other here; the world supplies the danger; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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.
Connecting
What is the way to join 菠萝测试?
Enter client.connect 39.182.16.163:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.