Working its way up from the back of the class: #13,597 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
45/ 100
D
Slipped a little: down 1,281 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to D.
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.
No daily history yet.
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 62% 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
YukikaedeServer leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 36.234.88.42:7777.
How reliable is YukikaedeServer, and is it up?
You cannot join now: YukikaedeServer is offline, last seen 19 days 3 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 10 October 2026.
On what Rust version does YukikaedeServer sit?
Rust network protocol 2634 and build 166652 on Windows is what YukikaedeServer runs. To join, your game must use the same protocol; Steam handles the update.
Resets
On what schedule does YukikaedeServer reset?
The record holds too few of YukikaedeServer'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 26 days 4 hours.
Population
What position does YukikaedeServer hold in the rankings?
In the top 62% of all ranked servers, YukikaedeServer sits at #13,597 for player hours over the last seven days.
What does the population on YukikaedeServer look like?
YukikaedeServer is offline at the moment; the last time it was seen was 19 days 3 hours ago.
Tags and filters
What is meant by the tags on YukikaedeServer?
The game's browser takes its cue from the tags YukikaedeServer has set: gmrust (Game mode): Rust survival, played by the standard rules; mp4 (Max players): The server holds 4 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166652 (Build): Build number: 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^p (PvE): Players do not fight one another here; the world is the danger. 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 YukikaedeServer?
Rust Server Score lists that include YukikaedeServer: Best community servers, graded and Rust PvE servers, graded. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: PvE ^p; Group limit: 5 or more.
Map and rules
How is YukikaedeServer set up, and what rules does it keep?
The name of YukikaedeServer gives no gather rate. The group limit stays at the game's default of 8 players. pve is the mode here, no PvP between players. Under Community in the server browser you will find this community server. You are not covered by VAC, Valve's anti-cheat.
Which map is in play on YukikaedeServer?
The game generates a procedural map for YukikaedeServer.
Getting in
How do you get onto YukikaedeServer?
Enter client.connect 36.234.88.42:7777 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 asmp4,ptrak,$r?,v2634,^p,gmrust,cs166652,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp4
Max playersThe server holds 4 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166652
BuildBuild number: 166652.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Gameplay
^p
PvEPlayers do not fight one another here; the world is the danger.
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. Even marks across the subjects, from F to D.