Working its way up from the back of the class: #15,332 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
50/ 100
D
Holding steady: up 109 places this week.
A term to build on.
Strongest in momentum (D); standing 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.
AveragePeak
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.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. 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
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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
With region code au1, [CN]FUXK 荒野生存 has no region tag but a name that points to Asia. Rust Server Score takes the server's word for its location and does not trace the hardware. 117.60.122.90:28015 is the address to use.
How dependable is [CN]FUXK 荒野生存, and is it online at the moment?
At this moment, [CN]FUXK 荒野生存 is offline; the last time it was seen was 9 days 10 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 18 October 2026.
Which Rust version is [CN]FUXK 荒野生存 running?
You will find [CN]FUXK 荒野生存 on Rust network protocol 2623 and build 148916, hosted on Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
On what schedule does [CN]FUXK 荒野生存 reset?
[CN]FUXK 荒野生存 has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 206 days 18 hours.
Player numbers
What position does [CN]FUXK 荒野生存 hold in the rankings?
In the top 69% of all ranked servers, [CN]FUXK 荒野生存 sits at #15,332 for player hours over the last seven days.
What does the population on [CN]FUXK 荒野生存 look like?
It has been 9 days 10 hours since [CN]FUXK 荒野生存 was last seen, and it is offline right now.
Lists and filters
How should you read the tags on [CN]FUXK 荒野生存?
The game's browser takes its cue from the tags [CN]FUXK 荒野生存 has set: gmvanilla (Game mode): Survival, vanilla style; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2623 (Protocol): To get in, your game needs to be on the same version: the protocol is 2623; cs148916 (Build): Build number: 148916; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $rau1 (Region code): It is filed under the region code au1; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show [CN]FUXK 荒野生存?
These Rust Server Score lists count [CN]FUXK 荒野生存 among them: Modded Rust servers, graded. These filters bring it up on the server list: Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
What settings and rules apply on [CN]FUXK 荒野生存?
Nothing in the name of [CN]FUXK 荒野生存 states a gather rate. With no change from the game default, groups take up to 8 players. survival is the mode here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. VAC, Valve's anti-cheat, is enabled.
[CN]FUXK 荒野生存 runs which map?
A procedural map, generated by the game, is what [CN]FUXK 荒野生存 runs.
Connecting
How do you get onto [CN]FUXK 荒野生存?
To connect, start Rust, press F1, and type client.connect 117.60.122.90:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$rau1,v2623,gmvanilla,cs148916,ts8,^o^z
Game
gmvanilla
Game modeSurvival, vanilla style.
mp50
Max playersThe server holds 50 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2623
ProtocolTo get in, your game needs to be on the same version: the protocol is 2623.
cs148916
BuildBuild number: 148916.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$rau1
Region codeIt is filed under the region code au1.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
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 momentum (D); standing is the one to work on (F).