『夜猫子』特色PVE/御剑飞行/死亡不掉/超级技能
Online EA 103.91.210.17:10001 checked 1m 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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 25% of all ranked servers, top 64% 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 2, 4 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sat 7 Nov, 03:41 UTC6d ago | 2 | – | running | 0 |
| Thu 5 Nov, 19:00 UTC FW7d ago | – | – | – | – |
| Fri 2 Oct, 06:35 UTC42d ago | 3 | halved by day 1 | 35.9 days | 1 |
| Thu 1 Oct, 18:00 UTC FW42d 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/御剑飞行/死亡不掉/超级技能?
Not enough of 『夜猫子』特色PVE/御剑飞行/死亡不掉/超级技能'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 6 days 2 hours ago.
What does wipe day look like on 『夜猫子』特色PVE/御剑飞行/死亡不掉/超级技能?
Its recent wipes drew 2 players at their busiest, on average. On the latest wipe the crowd peaked 4 hours after the wipe. In 0% of its recent wipes the crowd stayed above half that peak until the next wipe. When it didn't, it fell below half by day 1.
Players
How busy is 『夜猫子』特色PVE/御剑飞行/死亡不掉/超级技能?
Right now 『夜猫子』特色PVE/御剑飞行/死亡不掉/超级技能 has 2 players on 188 slots. Over the last seven days it averaged 0 players and peaked at 3. In the last 48 hours it was busiest at 11:00 UTC, with 2 players on average.
How does 『夜猫子』特色PVE/御剑飞行/死亡不掉/超级技能 rank against other Rust servers?
『夜猫子』特色PVE/御剑飞行/死亡不掉/超级技能 is #5,650 on player hours over the last seven days, in the top 25% of all ranked servers and #375 in Asia.
Rules and map
What are the rules and settings on 『夜猫子』特色PVE/御剑飞行/死亡不掉/超级技能?
『夜猫子』特色PVE/御剑飞行/死亡不掉/超级技能 gives no gather rate in its name. Groups can have up to 100 players. Its game mode is build & creative, sandbox building, no gathering. It is listed under Modded in the server browser: plugins or settings change the game. It runs Carbon plugins. Valve's anti-cheat, VAC, is on.
Which map does 『夜猫子』特色PVE/御剑飞行/死亡不掉/超级技能 run?
『夜猫子』特色PVE/御剑飞行/死亡不掉/超级技能 runs a procedural map, generated by the game, of size 4,000 with seed 1582241908. The same size and seed give the same map, so it can be looked at on RustMaps from this page.
Tags and lists
What do the server tags on 『夜猫子』特色PVE/御剑飞行/死亡不掉/超级技能 mean?
『夜猫子』特色PVE/御剑飞行/死亡不掉/超级技能 publishes these tags, which the game's server browser reads: gmrust (Game mode): Standard Rust survival; mp188 (Max players): 188 slots; ts100 (Group limit): At most 100 per team; v2636 (Protocol): Game protocol 2636: your game has to be on the same version to join; cs170545 (Build): Game build 170545; ptrak (Networking): RakNet, the game's standard network layer; $r? (Region code): No region code set; ^c (Creative): Sandbox building: no gathering, build what you like; ^z (Modded): Listed under Modded: plugins or settings change the game; ^y (Carbon): Runs Carbon, a plugin framework; 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/御剑飞行/死亡不掉/超级技能?
『夜猫子』特色PVE/御剑飞行/死亡不掉/超级技能 fits these Zongarust lists: Best modded Rust servers, Best Rust build servers and Best Rust creative servers. On the server list it comes up under these filters: Region: Asia; Type: Modded; Server tag: Creative ^c, Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.
The server
Where is 『夜猫子』特色PVE/御剑飞行/死亡不掉/超级技能 located?
『夜猫子』特色PVE/御剑飞行/死亡不掉/超级技能 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 103.91.210.17:10001.
Is 『夜猫子』特色PVE/御剑飞行/死亡不掉/超级技能 online, and how reliable is it?
『夜猫子』特色PVE/御剑飞行/死亡不掉/超级技能 is online right now. It last restarted about 6 hours ago, going by the uptime it reports. Over the last 7 full days it was up 87% of the time, 146 of 168 hours. Zongarust first saw it on 13 September 2026.
Does 『夜猫子』特色PVE/御剑飞行/死亡不掉/超级技能 run smoothly?
Over the last 48 hours it ran at 99 server fps on average, never below 58. It carried up to 102,000 entities: buildings, deployables and everything else in the world. It used up to 3,025 MB of memory. Low fps and a climbing entity count are what players feel as lag.
Which version of Rust does 『夜猫子』特色PVE/御剑飞行/死亡不掉/超级技能 run?
『夜猫子』特色PVE/御剑飞行/死亡不掉/超级技能 runs Rust network protocol 2636 and build 170545 on Windows. Your game has to be on the same protocol to join; Steam updates it for you.
Joining
How do I join 『夜猫子』特色PVE/御剑飞行/死亡不掉/超级技能?
Start Rust, press F1 to open the console and enter client.connect 103.91.210.17:10001. Or use Launch Rust and join on this page, which opens Rust through Steam and connects you. Its website is https://qun.qq.com/universal-share/share?ac=1&authKey=acH%2BGlrSxOs52K3mJVOt8u8C4x8a1Oj%2F5ZzL50nSIy1%2FN7HvqikokTAWvRcAaaWZ&busi_data=eyJncm91cENvZGUiOiIyMjIxMzMzNDgiLCJ0b2tlbiI6IkNXeVRqMXhLdERvQ0tEcWd5SkVjczdEZ2xocjc0V0pxVTZsM3hLSmthejVEczh4TGRGZ3FpY3FLNG5qT0lSL0UiLCJ1aW4iOiIxMTA1MDAwNjAwIn0%3D&data=lzDsRKjOMAfhSfiYz8ZXJbu7j2R26xcSooWWmZv_3tKl6PJVtrRH-L9u0rTY_BfejmO8WURhzU9Ck5k7bCEvGtH3eHZ7ooldVo32BILYJdM&svctype=5&tempid=h5_group_info.