Working its way up from the back of the class: #15,917 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
15/ 100
F
Lost ground: down 11,272 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); momentum is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 best
RankRank in region
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak2players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 8 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 17 Sep, 05:49 UTC42d ago
2
–
running
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
classmates: the same kind of game, then region, group limit, rate and wipes
No region tag appears for 繁花似锦:一个PVP以PVE玩法养老的服务器, but the name suggests Asia. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 43.249.194.92:11101.
Is 繁花似锦:一个PVP以PVE玩法养老的服务器 up, and how steady is its uptime?
The server is down: 繁花似锦:一个PVP以PVE玩法养老的服务器 is offline now, with the last sighting 27 days 7 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. The first sighting by Rust Server Score was on 16 September 2026.
Which Rust version is 繁花似锦:一个PVP以PVE玩法养老的服务器 running?
You will find 繁花似锦:一个PVP以PVE玩法养老的服务器 on Rust network protocol 2633 and build 163794, hosted on Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
On what schedule does 繁花似锦:一个PVP以PVE玩法养老的服务器 reset?
There are too few wipes on record for 繁花似锦:一个PVP以PVE玩法养老的服务器 to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 42 days 10 hours have passed since this world was made.
What happens on 繁花似锦:一个PVP以PVE玩法养老的服务器 when wipe day arrives?
Recent wipes have peaked at 2 players on average. The crowd on the latest wipe was largest 8 hours after it began.
Population
What position does 繁花似锦:一个PVP以PVE玩法养老的服务器 hold in the rankings?
In the top 69% of all ranked servers, 繁花似锦:一个PVP以PVE玩法养老的服务器 sits at #15,917 for player hours over the last seven days.
Is 繁花似锦:一个PVP以PVE玩法养老的服务器 a busy server?
The last sighting of 繁花似锦:一个PVP以PVE玩法养老的服务器 was 27 days 7 hours ago, and it is offline right now.
Tags
What is meant by the tags on 繁花似锦:一个PVP以PVE玩法养老的服务器?
The game's browser takes its cue from the tags 繁花似锦:一个PVP以PVE玩法养老的服务器 has set: gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): Its slot count is 50; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs163794 (Build): Build number: 163794; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^o (Oxide): The plugin framework in use is Oxide (uMod). Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which lists and filters on Rust Server Score show 繁花似锦:一个PVP以PVE玩法养老的服务器?
Rust Server Score lists that include 繁花似锦:一个PVP以PVE玩法养老的服务器: Best community servers, graded. You can find it under these server-list filters: Region: Asia; Type: Community (not modded, not official) and Plugins, not modded; Server tag: Oxide ^o; Group limit: 5 or more.
Rules and settings
What settings and rules apply on 繁花似锦:一个PVP以PVE玩法养老的服务器?
Nothing in the name of 繁花似锦:一个PVP以PVE玩法养老的服务器 states a gather rate. The default of 8 players applies as the group cap. survival is the mode here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map 繁花似锦:一个PVP以PVE玩法养老的服务器 uses?
The game generates the procedural map on 繁花似锦:一个PVP以PVE玩法养老的服务器 at size 5,000 with seed 498251216. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
How should you connect to 繁花似锦:一个PVP以PVE玩法养老的服务器?
To connect, start Rust, press F1, and type client.connect 43.249.194.92:11101. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2633,gmrust,cs163794,ts8,^o
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max playersIts slot count is 50.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs163794
BuildBuild number: 163794.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.
A term to build on. Strongest in standing (F); momentum is the one to work on (F).