Working its way up from the back of the class: #15,404 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
49/ 100
D
Slipped a little: down 174 places this week. Nothing a good wipe can't fix.
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. 218.91.93.107:28015 is the address to use.
Is [CN]FUXK 荒野生存 up, and how steady is its uptime?
The server is down: [CN]FUXK 荒野生存 is offline now, with the last sighting 8 days 12 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 19 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 schedule
On what schedule does [CN]FUXK 荒野生存 reset?
There are too few wipes on record for [CN]FUXK 荒野生存 to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 206 days 21 hours have passed since this world was made.
Player count
Where does [CN]FUXK 荒野生存 place in the wider field of Rust servers?
Over the last seven days, [CN]FUXK 荒野生存 has #15,404 for player hours, in the top 69% of all ranked servers.
Is [CN]FUXK 荒野生存 a busy server?
The last sighting of [CN]FUXK 荒野生存 was 8 days 12 hours ago, and it is offline right now.
Tags and filters
What do [CN]FUXK 荒野生存's tags stand for?
You'll see [CN]FUXK 荒野生存 tagged with gmvanilla (Game mode): This is vanilla survival; 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): Build number: 148916; ptrak (Networking): RakNet handles it, the game's default network layer; $rau1 (Region code): au1 is the region code this server uses; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does [CN]FUXK 荒野生存 appear in the Rust Server Score lists and filters?
These Rust Server Score lists count [CN]FUXK 荒野生存 among them: Modded Rust servers, graded. It shows under the following filters on the server list: Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Server rules
Which rules does [CN]FUXK 荒野生存 enforce, and what are its settings?
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. You get survival here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. You are covered by VAC, Valve's anti-cheat.
Which map is in play on [CN]FUXK 荒野生存?
The game generates a procedural map for [CN]FUXK 荒野生存.
Connecting
What is the way to join [CN]FUXK 荒野生存?
To connect, start Rust, press F1, and type client.connect 218.91.93.107: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 modeThis is vanilla survival.
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
BuildBuild number: 148916.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$rau1
Region codeau1 is the region code this server uses.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits 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).