#01 [中国PVE] 1000倍/死亡不掉/新手服
Online 153.35.147.23:1949 checked 14m ago
Players now
Live- Full
- 0%
- In queue
- 0
- Peak, 48 hours
- 7
- Peak, 7 days
- 8
0% full
Rank
top 14%
7-day average
peak 8
Last wipe
monthly schedule
Next wipe
Thu 5 Nov, 19:00 UTC FW
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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 14% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 8d 15h. The force wipe · high confidence
Coming wipes
- 8d 15hThu 5 Nov, 19:00 UTCFW
- 36d 15hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 4, 9 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 1 Oct, 18:57 UTC FW26d ago | 4 | – | running | 2 |
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 wipes- 1 22/ 200
- 2 8/ 200
- 3 7/ 200
- 4 2/ 30
- 5 5/ 50
- 6 2/ 100
Quick answers
from the figures on this pageServer details
Is #01 [中国PVE] 1000倍/死亡不掉/新手服 online, and how reliable is it?
#01 [中国PVE] 1000倍/死亡不掉/新手服 is up and taking players now. Its reported uptime points to a restart roughly 1 hours ago. It was online 100% of the last 7 full days, which is 168 of 168 hours. Our records for it start on 13 September 2026, when Rust Dashboard first saw it.
Which version of Rust does #01 [中国PVE] 1000倍/死亡不掉/新手服 run?
Rust network protocol 2635 and build 168909 is running on #01 [中国PVE] 1000倍/死亡不掉/新手服, which sits on Windows. Steam keeps your game updated, so it will be on the same protocol and able to join.
Where is #01 [中国PVE] 1000倍/死亡不掉/新手服 located?
No region tag comes from #01 [中国PVE] 1000倍/死亡不掉/新手服, though the name points to Asia. A server's stated location is what Rust Dashboard displays; it does not check where the machine stands. You'll connect at 153.35.147.23:1949.
Does #01 [中国PVE] 1000倍/死亡不掉/新手服 run smoothly?
Across the last 48 hours the average was 77 fps, with a floor of 26. The world held as many as 117,049 entities, counting buildings, deployables and all the rest. It drew as much as 5,834 MB of memory at peak. A low fps figure and an entity count that keeps rising are what lag feels like to players.
Lists
Which Rust Dashboard lists and filters include #01 [中国PVE] 1000倍/死亡不掉/新手服?
You'll find #01 [中国PVE] 1000倍/死亡不掉/新手服 on these themed lists at Rust Dashboard: Best Rust community servers, Rust PvE servers and Vanilla Rust servers. These filters bring it up on the server list: Region: Asia; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Game mode: PvE; Server tag: Monthly ^m, Vanilla ^v, PvE ^p and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
What do the server tags on #01 [中国PVE] 1000倍/死亡不掉/新手服 mean?
The browser in the game reads gmrust (Game mode): Standard Rust survival is the game mode; mp100 (Max players): 100 is the slot count; ts9 (Group limit): 9 is the most you can have per team; v2635 (Protocol): The game protocol is 2635; your build has to match it to join; cs168909 (Build): This one runs game build 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it is what runs here; $r? (Region code): No region code is set; ^m (Monthly): Once a month it wipes, together with the force wipe from Facepunch; ^v (Vanilla): Facepunch's game, unaltered in rates, kits and rules; ^p (PvE): There is no player fighting: the world provides the danger; ^o (Oxide): The plugin framework is Oxide (uMod) from #01 [中国PVE] 1000倍/死亡不掉/新手服 as its tags. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
Population
How busy is #01 [中国PVE] 1000倍/死亡不掉/新手服?
As things stand, 0 players are on #01 [中国PVE] 1000倍/死亡不掉/新手服, which holds 100 slots. Over seven days the mean is 1 players and the peak is 8. It was busiest at 17:00 UTC over the last 48 hours, when it averaged 6 players.
How does #01 [中国PVE] 1000倍/死亡不掉/新手服 rank against other Rust servers?
Player hours over seven days put #01 [中国PVE] 1000倍/死亡不掉/新手服 at #3,077, in the top 14% of all ranked servers.
Wipe days
What does wipe day look like on #01 [中国PVE] 1000倍/死亡不掉/新手服?
The average busiest point of its recent wipes was 4 players. 9 hours into the latest wipe the crowd peaked.
What is the wipe schedule on #01 [中国PVE] 1000倍/死亡不掉/新手服?
Wipes come once a month on #01 [中国PVE] 1000倍/死亡不掉/新手服, in step with the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. 26 days 8 hours ago the current world was made. The tags carry a wipe schedule of once a month.
Map and rules
What are the rules and settings on #01 [中国PVE] 1000倍/死亡不掉/新手服?
The name of #01 [中国PVE] 1000倍/死亡不掉/新手服 gives no gather rate. 9 players is the most a group can take. pve is the mode here, no PvP between players. You will find it under Community in the server browser. Oxide plugins run on it. The server describes itself as vanilla: facepunch's game, unaltered in rates, kits and rules. VAC is off: that is Valve's anti-cheat.
Which map does #01 [中国PVE] 1000倍/死亡不掉/新手服 run?
#01 [中国PVE] 1000倍/死亡不掉/新手服 runs a procedural map of size 3,600 with seed 1337, made by the game. This page links to RustMaps, where the map looks the same for its size and seed.
How to join
How do I join #01 [中国PVE] 1000倍/死亡不掉/新手服?
Type client.connect 153.35.147.23:1949 in the Rust console, which F1 opens. Launch Rust on this page also works: Steam opens Rust and connects you. You can find it online at https://qm.qq.com/cgi-bin/qm/qr?authKey=Cfo470jB58Yv1efdwnphDPUj4MbYBbsTDnPrJwZxCNDCujXlTEVNElxYlGt5MxZ2&k=wVRM9Vohb1fS7DYZ8fP8tKwVqnscM7nj&noverify=0.