Rust Data

rustdata.spaceservers113.26.38.27:29016.ipynb

Run all rust-data · live

‹ All servers

Offline EA 113.26.38.27:28015 checked 12d ago

【炮炮PVE启蒙】测试

biweekly wipes vanillamoddedoxidepve

Connect

srv = rust.server("113.26.38.27:29016")
print(srv.connect_command)

Right now

srv.summary()
players now 1/1 # 100% full
7-day average 0 # peak –
rank #13,938 # top 64% · #511 in EA
last wipe 18d ago # biweekly schedule
next wipe 7d 16h # Thu 5 Nov, 19:00 UTC FW

Players

srv.players.plot(range="48h")
No hourly history yet.

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
15k10k15k20k27 Sep2 Oct7 Oct13 Oct18 Oct23 Oct

Top 64% of all ranked servers, top 91% in EA. 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 16h. # The force wipe · high confidence

usual gap2.9 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd

Coming wipes

inatkind
07d 16hThu 5 Nov, 19:00 UTCFW force wipe
19d 13hSat 7 Nov, 16:09 UTCwipe
223d 13hSat 21 Nov, 16:09 UTCwipe
335d 16hThu 3 Dec, 19:00 UTCFW force wipe
437d 13hSat 5 Dec, 16:09 UTCwipe

The first 48 hours of its last wipes

Sat 10 OctThu 8 OctSun 4 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, 0 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Sat 10 Oct, 16:09 UTC18d ago 1 NaN running 1
1 Thu 8 Oct, 00:23 UTC21d ago 1 held half 2.7 days 1
2 Sun 4 Oct, 19:45 UTC24d ago 1 held half 3.2 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

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
113.26.38.27:28015
region
EA
max players
1
group limit
8, the default
wipe schedule
biweekly
last wipe
10 Oct 2026, 16:16 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)
serverlike_thisplayers
0【炮炮PVE启蒙】纯净|特色|突袭|技能EA · groups of 16+ · biweekly · 60 on average36/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 average5/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 average1/100

Quick answers

From the figures on this page.

Population data

Against other Rust servers, how does 【炮炮PVE启蒙】测试 rank?

On seven-day player hours 【炮炮PVE启蒙】测试 is #13,938 overall and #511 in Asia, inside the top 64% of all ranked servers.

How many players does 【炮炮PVE启蒙】测试 hold at once?

【炮炮PVE启蒙】测试 returns no live count at this refresh, having last been seen 12 days 17 hours ago.

About the server

What Rust version does 【炮炮PVE启蒙】测试 run?

Rust network protocol 2634 and build 167058 on Windows is what 【炮炮PVE启蒙】测试 runs. The protocol has to match before you can join, and Steam does the updating.

How reliable is 【炮炮PVE启蒙】测试, and is it online now?

Offline now for 【炮炮PVE启蒙】测试, last seen 12 days 17 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 27 September 2026.

Where does 【炮炮PVE启蒙】测试 sit?

In Asia, 【炮炮PVE启蒙】测试 lists itself, using the EA tag. Rust Data does not look up where the machine stands; it shows where a server says it is. 113.26.38.27:28015 is its address.

Map and rules

Which rules apply on 【炮炮PVE启蒙】测试, and what settings?

The name 【炮炮PVE启蒙】测试 carries no gather rate. No custom cap; the default of 8 players per group stands. pve is the game mode here, and player combat is not allowed. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. Its own label is vanilla: no changed rates, kits or rules: the game as Facepunch ships it. VAC, Valve's anti-cheat, is enabled.

Which map has 【炮炮PVE启蒙】测试 loaded?

【炮炮PVE启蒙】测试 runs a procedural map, which the game generates.

Wipe schedule

On what schedule does 【炮炮PVE启蒙】测试 wipe?

The prediction follows the tag, because 【炮炮PVE启蒙】测试's wipes on record are too few to confirm the schedule. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. A new world was started 18 days 10 hours ago, and that is the one in play. The tags list a two-weekly wipe cycle.

What is wipe day on 【炮炮PVE启蒙】测试 like?

Recent wipes averaged 1 players at their peak. The crowd on the latest wipe topped out 0 hours after it began. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.

Tags, lists

Which lists on Rust Data hold 【炮炮PVE启蒙】测试, and which filters?

On Rust Data, 【炮炮PVE启蒙】测试 appears in these lists: Modded Rust servers and Rust PvE servers. These filters bring it up on the server list: Region: Asia; Type: Vanilla and Modded; Game mode: PvE; Server tag: Biweekly ^b, Vanilla ^v, 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 【炮炮PVE启蒙】测试?

These tags are published by 【炮炮PVE启蒙】测试 and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp1 (Max players): Slot count: 1; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs167058 (Build): Recorded game build: 167058; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^b (Biweekly): Wipes run on a two-week cycle; ^v (Vanilla): No changed rates, kits or rules: the game as Facepunch ships it; ^p (PvE): Players do not fight each other here; the world supplies the danger; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; EA (East Asia): The server browser files it under East Asia. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

How to join

What is the way into 【炮炮PVE启蒙】测试?

In Rust, F1 opens the console: type client.connect 113.26.38.27: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 mp1,ptrak,$r?,v2634,^b,^v,EA,^p,gmrust,cs167058,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp1
Max players Slot count: 1.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol To join, your game must run protocol 2634.
cs167058
Build Recorded game build: 167058.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code Region code: not set.

Wipe schedule

^b
Biweekly Wipes run on a two-week cycle.

Difficulty

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

Gameplay

^p
PvE Players do not fight each other here; the world supplies the danger.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it sits under Modded.

Region

EA
East Asia The server browser files it under East Asia.

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 36,352 players 11,696 servers online