Players now
Live- Full
- 0%
- In queue
- 0
- Peak, 48 hours
- 3
- Peak, 7 days
- 6
0% full
Rank
top 15%
7-day average
peak 6
Last wipe
biweekly schedule
Next wipe
Fri 30 Oct, 01:21 UTC
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 15% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
fixed weekdaysNext wipe Friday 30 October, 01:21 UTC, in 2d 8h. Every other Friday at 01:21 UTC · medium confidence
Coming wipes
- 2d 8hFri 30 Oct, 01:21 UTC
- 9d 1hThu 5 Nov, 19:00 UTCFW
- 16d 8hFri 13 Nov, 01:21 UTC
- 30d 8hFri 27 Nov, 01:21 UTC
- 37d 1hThu 3 Dec, 19:00 UTCFW
- 44d 8hFri 11 Dec, 01:21 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 10, 10 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 16 Oct, 01:21 UTC11d ago | 10 | – | running | 0 |
| Fri 2 Oct, 01:34 UTC25d ago | 9 | halved by day 3 | 14 days | 0 |
| Fri 18 Sep, 01:26 UTC39d ago | 6 | halved by day 8 | 14 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 1 4/ 100
- 2 44/ 200
- 3 4/ 65
- 4 4/ 69
- 5 2/ 100
- 6 3/ 99
Quick answers
from the figures on this pageServer
Is Hakuna PVE丨萌新丨仿官丨原倍 online, and how reliable is it?
Hakuna PVE丨萌新丨仿官丨原倍 is up and taking players now. The uptime it reports puts its last restart about 16 hours ago. The last 7 full days show 100% uptime, with 168 hours up out of 168. Our records for it start on 13 September 2026, when Rust Dashboard first saw it.
Which version of Rust does Hakuna PVE丨萌新丨仿官丨原倍 run?
Hakuna PVE丨萌新丨仿官丨原倍 runs Rust network protocol 2635 and build 168909, and Windows is the system under it. Joining needs the same protocol on your side, and Steam handles that update.
Where is Hakuna PVE丨萌新丨仿官丨原倍 located?
No region tag comes from Hakuna PVE丨萌新丨仿官丨原倍, though the name points to Asia. The location shown at Rust Dashboard is the one the server states; no lookup of the machine's position happens. Connect to it at 116.231.241.49:20003.
Does Hakuna PVE丨萌新丨仿官丨原倍 run smoothly?
The last 48 hours gave an average of 132 server fps, and it never went under 90. At its highest the count reached 136,339 entities: buildings, deployables and the rest. It drew as much as 4,751 MB of memory at peak. Players feel lag when fps drops and the entity count climbs.
Lists
Which Rust Dashboard lists and filters include Hakuna PVE丨萌新丨仿官丨原倍?
You'll find Hakuna PVE丨萌新丨仿官丨原倍 on these themed lists at Rust Dashboard: Best Rust community servers and Rust PvE servers. These filters bring it up on the server list: Region: Asia; Type: Community (not modded, not official) and Plugins, not modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.
What do the server tags on Hakuna PVE丨萌新丨仿官丨原倍 mean?
These are the tags Hakuna PVE丨萌新丨仿官丨原倍 publishes, read by the game's server browser: gmrust (Game mode): Standard Rust survival is the game mode; mp100 (Max players): 100 is the slot count; ts18 (Group limit): Teams top out at 18; v2635 (Protocol): Your game needs to be on the same version, protocol 2635, to get in; cs168909 (Build): This one runs game build 168909; ptrak (Networking): The game's standard network layer, RakNet, carries this server; $r? (Region code): The region code is blank; ^b (Biweekly): Every two weeks brings a wipe; ^p (PvE): There is no player fighting: the world provides the danger; ^o (Oxide): The plugin framework is Oxide (uMod). At the top of this page you'll find the current players, the queue and the world's creation time, which the tags carry too.
Player counts
How busy is Hakuna PVE丨萌新丨仿官丨原倍?
As things stand, 0 players are on Hakuna PVE丨萌新丨仿官丨原倍, which holds 100 slots. Over seven days the mean is 1 players and the peak is 6. The busiest point in the last 48 hours was 12:00 UTC, averaging 3 players.
How does Hakuna PVE丨萌新丨仿官丨原倍 rank against other Rust servers?
Player hours over seven days put Hakuna PVE丨萌新丨仿官丨原倍 at #3,294, in the top 15% of all ranked servers.
Wipe days
What does wipe day look like on Hakuna PVE丨萌新丨仿官丨原倍?
Its recent wipes averaged a peak of 8 players. 10 hours into the latest wipe the crowd peaked. Above half that peak until the next wipe: that held in 0% of recent wipes. By day 5.5 it had fallen below half, where the crowd did not hold.
What is the wipe schedule on Hakuna PVE丨萌新丨仿官丨原倍?
The wipe rhythm on Hakuna PVE丨萌新丨仿官丨原倍 is every other Friday at 01:21 UTC. Friday 30 October at 01:21 UTC is when its next wipe falls due. 11 days 15 hours ago the current world was made. Wipes every two weeks, according to the schedule in its tags.
Settings
What are the rules and settings on Hakuna PVE丨萌新丨仿官丨原倍?
The name of Hakuna PVE丨萌新丨仿官丨原倍 gives no gather rate. 18 players is the most a group can take. pve is what it plays, no PvP between players. The server browser lists it under Community. Oxide plugins run on it. VAC is on: that is Valve's anti-cheat.
Which map does Hakuna PVE丨萌新丨仿官丨原倍 run?
Hakuna PVE丨萌新丨仿官丨原倍 runs a procedural map of size 4,250 with seed 477406466, made by the game. Size and seed fix the map, so this page can show it on RustMaps.
Connect
How do I join Hakuna PVE丨萌新丨仿官丨原倍?
Type client.connect 116.231.241.49:20003 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=Uy32ysaYZcFzWzw3LSHR%2BLGvOWQI0h8iGZfTatCFdSqSEQYE1uEsHZr9Zri4poDO&k=n7N1iwcts8uHPfj8CZB7889-MQyDexsK&noverify=0.
