【英雄PVE】武器特效/BOSS/死亡不掉/无需加速器
Online EA 202.189.16.89:22222 checked 3m ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 22 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 2% of all ranked servers, top 2% in EA. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 76, 31 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 6 Nov, 01:08 UTC7d ago | 76 | – | running | 51 |
| Thu 5 Nov, 19:00 UTC FW7d ago | – | – | – | – |
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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageWipes
What is the wipe schedule on 【英雄PVE】武器特效/BOSS/死亡不掉/无需加速器?
Not enough of 【英雄PVE】武器特效/BOSS/死亡不掉/无需加速器's wipes are on record yet to tell its rhythm. Every Rust server wipes at the monthly force wipe, next on Thursday 3 December at 19:00 UTC. Its current world was made 7 days 5 hours ago.
What does wipe day look like on 【英雄PVE】武器特效/BOSS/死亡不掉/无需加速器?
Its recent wipes drew 76 players at their busiest, on average. On the latest wipe the crowd peaked 31 hours after the wipe.
Players
How busy is 【英雄PVE】武器特效/BOSS/死亡不掉/无需加速器?
Right now 【英雄PVE】武器特效/BOSS/死亡不掉/无需加速器 has 69 players on 123 slots. Over the last seven days it averaged 61 players and peaked at 81. In the last 48 hours it was busiest at 11:00 UTC, with 78 players on average.
How does 【英雄PVE】武器特效/BOSS/死亡不掉/无需加速器 rank against other Rust servers?
【英雄PVE】武器特效/BOSS/死亡不掉/无需加速器 is #358 on player hours over the last seven days, in the top 2% of all ranked servers and #10 in Asia.
Rules and map
What are the rules and settings on 【英雄PVE】武器特效/BOSS/死亡不掉/无需加速器?
【英雄PVE】武器特效/BOSS/死亡不掉/无需加速器 gives no gather rate in its name. Groups can have up to 8 players, the game's default. Its game mode is softcore, Facepunch's easier mode: you keep part of your loot. Players can fight and raid each other. It is listed under Modded in the server browser: plugins or settings change the game. It runs Oxide plugins. Valve's anti-cheat, VAC, is on.
Which map does 【英雄PVE】武器特效/BOSS/死亡不掉/无需加速器 run?
【英雄PVE】武器特效/BOSS/死亡不掉/无需加速器 runs a procedural map, generated by the game, of size 4,500 with seed 1337. The same size and seed give the same map, so it can be looked at on RustMaps from this page. Its map name reads: 萌新首选.
Tags and lists
What do the server tags on 【英雄PVE】武器特效/BOSS/死亡不掉/无需加速器 mean?
【英雄PVE】武器特效/BOSS/死亡不掉/无需加速器 publishes these tags, which the game's server browser reads: gmrust (Game mode): Standard Rust survival; mp123 (Max players): 123 slots; ts8 (Group limit): At most 8 per team, the game default; v2636 (Protocol): Game protocol 2636: your game has to be on the same version to join; cs170220 (Build): Game build 170220; ptrak (Networking): RakNet, the game's standard network layer; $r? (Region code): No region code set; ^s (Softcore): Facepunch's easier mode: you keep part of your inventory when you die; ^p (PvE): Players don't fight each other; the danger is the world; ^o (Oxide): Runs Oxide (uMod), a plugin framework; ^z (Modded): Listed under Modded: plugins or settings change the game; EA (East Asia): Listed under East Asia in the server browser. Its players now, its queue and the time its world was made are in the tags too, and are shown at the top of this page.
Which Zongarust lists and filters include 【英雄PVE】武器特效/BOSS/死亡不掉/无需加速器?
【英雄PVE】武器特效/BOSS/死亡不掉/无需加速器 fits these Zongarust lists: Best modded Rust servers and Best Rust PvE servers. On the server list it comes up under these filters: Region: Asia; Type: Modded; Game mode: PvE and Softcore; Server tag: Softcore ^s, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks; Players now: At least 50; Average players: 50+ on average.
Who runs 【英雄PVE】武器特效/BOSS/死亡不掉/无需加速器?
【英雄PVE】武器特效/BOSS/死亡不掉/无需加速器 publishes a rustyx.cn hostname, and so do 2 other servers we track, so they are most likely run by the same operator.
The server
Where is 【英雄PVE】武器特效/BOSS/死亡不掉/无需加速器 located?
【英雄PVE】武器特效/BOSS/死亡不掉/无需加速器 lists itself in Asia with its EA tag. Zongarust shows where a server says it is; it does not look up where the machine stands. Its address is 202.189.16.89:22222.
Is 【英雄PVE】武器特效/BOSS/死亡不掉/无需加速器 online, and how reliable is it?
【英雄PVE】武器特效/BOSS/死亡不掉/无需加速器 is online right now. It last restarted about 7 hours ago, going by the uptime it reports. Over the last 7 full days it was up 99% of the time, 167 of 168 hours. Zongarust first saw it on 22 October 2026.
Does 【英雄PVE】武器特效/BOSS/死亡不掉/无需加速器 run smoothly?
Over the last 48 hours it ran at 78 server fps on average, never below 28. It carried up to 538,000 entities: buildings, deployables and everything else in the world. It used up to 18,008 MB of memory. Low fps and a climbing entity count are what players feel as lag.
Which version of Rust does 【英雄PVE】武器特效/BOSS/死亡不掉/无需加速器 run?
【英雄PVE】武器特效/BOSS/死亡不掉/无需加速器 runs Rust network protocol 2636 and build 170220 on Windows. Your game has to be on the same protocol to join; Steam updates it for you.
Joining
How do I join 【英雄PVE】武器特效/BOSS/死亡不掉/无需加速器?
Start Rust, press F1 to open the console and enter client.connect 202.189.16.89:22222. Or use Launch Rust and join on this page, which opens Rust through Steam and connects you. Its website is https://qm.qq.com/cgi-bin/qm/qr?_wv=1027&k=oTr2KHoFHAzWhbernnfJrtAmEH2Q6fHu&authKey=Dv9GFwoxFRSaBpZcEuyempmN0R3QjUiiRhbxmlF02sPWI3eeuhBroDmjiMFdIeB6&noverify=0&group_code=154575000.
