Working its way up from the back of the class: #15,101 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
52/ 100
D
Moving up: up 753 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 70% 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 us3, [CN]FUXK 荒野生存 has no region tag but a name that points to Asia. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 49.86.251.251:28015.
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 13 days 21 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 14 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. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
When does [CN]FUXK 荒野生存 wipe, and how often?
The record holds too few of [CN]FUXK 荒野生存's wipes to tell 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 207 days 5 hours.
Player count
Where does [CN]FUXK 荒野生存 sit among Rust servers?
Over the last seven days, [CN]FUXK 荒野生存 has #15,101 for player hours, in the top 70% of all ranked servers.
What does the population on [CN]FUXK 荒野生存 look like?
It has been 13 days 21 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 荒野生存?
gmvanilla (Game mode): You play vanilla survival here; mp50 (Max players): 50 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2623 (Protocol): The game protocol is 2623, so your game must match that version to join; cs148916 (Build): The game build is 148916; ptrak (Networking): The network layer is RakNet, standard for the game; $rus3 (Region code): us3 is the region code this server uses; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded are the tags [CN]FUXK 荒野生存 publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which Rust Server Score filters and lists feature [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.
Rules and settings
What settings and rules apply on [CN]FUXK 荒野生存?
You will find no gather rate in the name of [CN]FUXK 荒野生存. With no change from the game default, groups take up to 8 players. It runs survival, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
Can you tell me which map [CN]FUXK 荒野生存 uses?
A procedural map, generated by the game, is what [CN]FUXK 荒野生存 runs.
How to join
What is the way to join [CN]FUXK 荒野生存?
Enter client.connect 49.86.251.251:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp50,ptrak,$rus3,v2623,gmvanilla,cs148916,ts8,^o^z
Game
gmvanilla
Game modeYou play vanilla survival here.
mp50
Max players50 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2623
ProtocolThe game protocol is 2623, so your game must match that version to join.
cs148916
BuildThe game build is 148916.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$rus3
Region codeus3 is the region code this server uses.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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).