Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO S SRV11,836online PAX72,948playing OCC3,667with players WIPED 3H218
MODModded traffic
Callsign

SRV13917

菠萝测试

Offline 39.182.16.163:28015 checked 25d ago

biweekly wipes moddedoxidepve
Clearance · join
Players now 1/ 100 1% full
7-day average0peak –
Rank#13,917top 61%
Last wipe25d agobiweekly schedule
Next wipe2d 1hSat 31 Oct, 14:46 UTC
Track history

Players

No hourly history yet.

Hourly average and peak, UTC.

Server performance

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
RankRank in region
15k10k15k20k27 Sep30 Sep2 Oct5 Oct7 Oct10 Oct

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

Flight plan

Wipe schedule

from its schedule tag
ETD · next wipe

Next wipe Saturday 31 October, 14:46 UTC, in 2d 1h.

Its biweekly schedule tag · low confidence

usual gap1.3 daysbetween real wipes
on rhythm50%of its recent wipes
wipe-day peak1players, last three wipes

Coming wipes

  1. 2d 1hSat 31 Oct, 14:46 UTC
  2. 7d 5hThu 5 Nov, 19:00 UTCFW
  3. 16d 1hSat 14 Nov, 14:46 UTC
  4. 30d 1hSat 28 Nov, 14:46 UTC
  5. 35d 5hThu 3 Dec, 19:00 UTCFW
  6. 44d 1hSat 12 Dec, 14:46 UTC

The first 48 hours of its last wipes

Sat 3 OctSat 3 OctThu 1 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
WipedPeakCrowdLastedPlayers before
Sat 3 Oct, 14:46 UTC25d ago 1 – running 0
Sat 3 Oct, 01:34 UTC26d ago 1 – 0.6 days 0
Thu 1 Oct, 16:06 UTC27d ago 1 – 1.4 days 0
Mon 28 Sep, 15:43 UTC30d ago 1 – 3 days 0
Sun 27 Sep, 09:05 UTC32d ago 1 – 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.

Nearby traffic

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. 01MOD
    Callsign PVE016EA · groups of 16+ · biweekly · 58 on average 【炮炮PVE启蒙】纯净|特色|突袭|技能
    Players 97/200
  2. 02MOD
    Callsign JPP159EA · groups of 8+ · biweekly · 8 on average [JP][PvE]mameserver初心者おいで!
    Players 10/65
  3. 03MOD
    Callsign JPX377EA · groups of 1000+ · 1x · biweekly · 7 on average JP 1x-10x PVE++|XPレベル1000|火山|ペット|NPCレイド
    Players 2/123
  4. 04MOD
    Callsign PVE957EA · groups of 12+ · biweekly · 5 on average [喜相逢] PVE丨仿官原倍丨萌新养老
    Players 4/100
  5. 05MOD
    Callsign RDB017EA · groups of 16+ · biweekly · 4 on average [PVE][JP] そば鯖 Raidable Bases 初心者大歓迎
    Players 4/50
  6. 06MOD
    Callsign PVE085EA · groups of 8+ · biweekly · 3 on average 『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老
    Players 3/100
ATIS · this server

Quick answers

From the figures on this page.

Filters

Where does 菠萝测试 appear in Rust Tracker lists and filters?

These Rust Tracker lists carry 菠萝测试: PvE servers, tracked live and Modded servers, tracked live. These filters surface it 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.

What do the tags mean that 菠萝测试 is listed under?

The game's server browser reads these tags from 菠萝测试: gmrust (Game mode): Survival as standard Rust plays; mp100 (Max players): Capacity: 100 slots; ts8 (Group limit): Teams cap at 8; this is the game default; v2634 (Protocol): Join only if your game is on protocol 2634; cs166652 (Build): The game build is 166652; ptrak (Networking): Network layer: RakNet, the game's standard; $r? (Region code): Region code: not set; ^b (Biweekly): Every two weeks it wipes; ^p (PvE): No player fights — the world is the danger; ^o (Oxide): A plugin framework runs here: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it is listed under Modded. The tags also hold the current player count, the queue and when the world was made; all appear at the top of this page.

Wipe Schedule

What should you expect on 菠萝测试 when wipe day lands?

The average peak across recent wipes: 1 players. The peak on the latest wipe came 1 hours after it.

Which wipe times are confirmed for 菠萝测试?

The prediction for 菠萝测试 follows its tag, as too few wipes are on record to confirm the schedule. Due on Saturday 31 October at 14:46 UTC: its next wipe. This world has been running 25 days 22 hours. Its tags carry an every-two-weeks wipe schedule.

Location and Status

Is 菠萝测试 up, and how does its uptime hold?

Offline: 菠萝测试 confirmed offline, last seen 25 days 22 hours ago. 0% uptime over the last 7 full days, with 0 of 168 hours up. The first sighting by Rust Tracker was 27 September 2026.

Which Rust version is confirmed on 菠萝测试?

Rust network protocol 2634 and build 166652 on Windows is what 菠萝测试 runs. Steam updates it for you; your game must share the protocol to join.

Where does 菠萝测试 sit?

The name of 菠萝测试 points to Asia, though no region tag is published. Where a server says it is, Rust Tracker shows; where the machine stands, it does not look up. Connect on 39.182.16.163:28015.

Player Count

How many players are on 菠萝测试 right now?

Last seen 25 days 22 hours ago; 菠萝测试 is offline at present.

What rank does 菠萝测试 carry among Rust servers?

Seven-day player hours put 菠萝测试 at #13,917, within the top 61% of all ranked servers.

Map and Rules

Which settings and rules are confirmed on 菠萝测试?

The name of 菠萝测试 carries no gather rate. Up to 8 players per group, the game's default. pve is the game mode, fighting between players is off. Plugins or settings change the game, and the server browser lists it under Modded. The plugin count stands at Oxide. VAC is off, Valve's anti-cheat.

What map is 菠萝测试 on?

A procedural map runs on 菠萝测试, generated by the game.

How to Join

Which steps join 菠萝测试?

Open the console in Rust with F1 after starting the game, then type client.connect 39.182.16.163:28015. Alternatively, Launch Rust here opens Rust via Steam and connects you.

Transponder codes

Server tags

What each one means.

Published as mp100,ptrak,$r?,v2634,^b,^p,gmrust,cs166652,ts8,^o^z

Game

gmrust
Game mode Survival as standard Rust plays.
mp100
Max players Capacity: 100 slots.
ts8
Group limit Teams cap at 8; this is the game default.
v2634
Protocol Join only if your game is on protocol 2634.
cs166652
Build The game build is 166652.
ptrak
Networking Network layer: RakNet, the game's standard.
$r?
Region code Region code: not set.

Wipe schedule

^b
Biweekly Every two weeks it wipes.

Gameplay

^p
PvE No player fights — the world is the danger.

Mods and access

^o
Oxide A plugin framework runs here: Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it is listed 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.