Server profile · EA
『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老
Online, with 3 of 100 players on; ranked #2,022 of every public Rust server, the top 9%. It last wiped 13d ago.
Online EA 144.255.147.233:10086 checked 8m ago
The crowd
Players
Who is on it, hour by hour and day by day.
Source: every five minutes, from the Steam server list.
Note: hourly average and peak, UTC.
Note: daily average and peak, UTC.
Under the hood
Server performance
Frames per second, entities and memory, asked of the server itself.
Note: 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, measured since 23 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
The standings
Rank
Its place among every ranked server, day by day; 1 is best.
Note: Top 9% of all ranked servers, top 34% in EA. Ranked on player hours over the last seven days.
The wipe cycle
Wipe schedule
Next wipe Friday 30 October, 02:06 UTC, in 22h. Biweekly: 14 days after its last wipe
The record
Wipes
Every wipe we saw, newest first.
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
Note: 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.
If you like this one
Similar servers
The same kind of game, then region, group limit, rate and wipes.
The short version
Quick answers
From the figures on this page.
Wipe cycle
When does 『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老 wipe, and how often?
The date for 『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老's next wipe is an estimate, and biweekly: 14 days after its last wipe provides the basis. Friday 30 October at 02:06 UTC is when the next wipe is due. This world dates from 13 days 1 hours ago. Its tags carry an every-two-weeks wipe schedule.
Server details
Does 『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老 hold a steady frame rate?
Server fps averaged 115 over 48 hours; the lowest reading was 85. The world held a peak of 168,587 entities, counting buildings, deployables and all the rest. Memory use peaked at 5,842 MB. What players feel as lag comes from low fps and an entity count on the rise.
On what version does 『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老 currently run?
Rust network protocol 2635 and build 168909 on Windows is what 『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老 runs. You can only join if your game is on the same protocol; Steam handles that update.
How reliable is 『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老, and is it up at the moment?
Right now 『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老 is up and running. Going by the uptime figure it gives, its last restart was around 4 hours ago. The last 5 full days gave 119 of 120 hours up, or 99% of the time. Rust Insights first logged this server on 23 October 2026.
Where does 『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老 run from?
Its EA tag is what 『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老 uses to list itself in Asia. Rust Insights reports the location a server declares, not the physical place of the machine. 144.255.147.233:10086 is where it answers.
Lists and tags
How should you read the tags listed for 『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老?
When the game's server browser reads 『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老, it finds these tags: gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): It holds 100 slots; ts8 (Group limit): The game default applies: teams cap at 8; v2635 (Protocol): To join you need the same version; protocol 2635; cs168909 (Build): Build 168909 is what it runs; ptrak (Networking): Rust's standard network layer, RakNet, carries it; $r? (Region code): No region code is set; ^b (Biweekly): Two weeks is the gap between wipes; ^p (PvE): Danger comes from the world, not from other players; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; EA (East Asia): Its browser listing sits under East Asia. You will find the present player count, the queue and the world's creation time among the tags, and they are displayed at the top of this page.
Where does 『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老 turn up among the Rust Insights lists and filters?
『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老 appears among the following Rust Insights lists: Modded Rust servers, explained and Rust PvE servers, live. You will find it on the server list by applying these filters: 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 2 weeks.
Population
How many players are on 『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老 right now, and how does that number move?
Of its 100 slots, 『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老 currently has 3 filled. A weekly average of 3 players goes with a peak of 11. The busiest point of the last 48 hours fell at 11:00 UTC, averaging 7 players.
In the ranking of Rust servers, where does 『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老 place?
『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老 holds #2,022 for player hours over the last seven days, #192 in Asia and in the top 9% of all ranked servers.
Settings and rules
What settings and rules apply on 『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老?
Nothing about gather rate is given in the name of 『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老. No group limit is set, so the game's default of 8 players applies. pve is the game mode, no fighting other players. Plugins or settings change the game, so it sits under Modded in the browser. It runs plugins, Oxide of them. Anti-cheat: VAC, from Valve, is on.
What is the map on 『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老?
Size 4,750 and seed 678254 define the procedural map on 『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老, generated by the game. The same size and seed produce the same map, so from this page you can look at it on RustMaps.
Connecting
How can you get onto 『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老?
To connect, start Rust and enter client.connect 144.255.147.233:10086 in the console (F1). Or join through Launch Rust on this page, which opens Rust via Steam and connects you. You will find its website at https://actech28.github.io/Actech/.