Working its way up from the back of the class: #13,177 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
21/ 100
F
Lost ground: down 7,606 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.
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 61% 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. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 36.234.89.167:7777.
How reliable is YukikaedeServer, and is it up?
At this moment, YukikaedeServer is offline; the last time it was seen was 35 days 16 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 21 September 2026.
What Rust version is YukikaedeServer on?
The server YukikaedeServer is on Rust network protocol 2633 and build 165217 under Windows. To join, your game must use the same protocol; Steam handles the update.
Resets
When does YukikaedeServer wipe, and how often?
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. 37 days 18 hours have passed since this world was made.
Player numbers
Where does YukikaedeServer place in the wider field of Rust servers?
Over the last seven days, YukikaedeServer has #13,177 for player hours, in the top 61% of all ranked servers.
Is YukikaedeServer a busy server?
It has been 35 days 16 hours since YukikaedeServer was last seen, and it is offline right now.
Tags and filters
How should you read 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): Its slot count is 4; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs165217 (Build): This runs on build 165217; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^p (PvE): This is player against world: players do not fight each other. 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 lists and filters on Rust Server Score show 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
Which rules does YukikaedeServer enforce, and what are its settings?
You will find no gather rate in the name of YukikaedeServer. The default of 8 players applies as the group cap. It runs pve, no PvP between players. Under Community in the server browser you will find this community server. VAC, Valve's anti-cheat, is enabled.
Which map is in play on YukikaedeServer?
The game generates a procedural map for YukikaedeServer.
How to join
What is the way to join YukikaedeServer?
To connect, start Rust, press F1, and type client.connect 36.234.89.167:7777. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp4,ptrak,$r?,v2633,^p,gmrust,cs165217,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp4
Max playersIts slot count is 4.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs165217
BuildThis runs on build 165217.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Gameplay
^p
PvEThis is player against world: players do not fight each other.
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).