Working its way up from the back of the class: #15,920 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 429 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.
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.
Average fpsLowest fpsWipe
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.
Average fpsLowest fpsWipe
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.
Average fpsLowest fpsWipe
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, measured since 2 Oct. 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
No region is published for Sakura Rust Server [PVE]. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 45.140.128.113:10200.
How reliable is Sakura Rust Server [PVE], and is it up?
The server is down: Sakura Rust Server [PVE] is offline now, with the last sighting 26 days 7 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 2 October 2026, Rust Server Score saw it for the first time.
On what Rust version does Sakura Rust Server [PVE] sit?
The server Sakura Rust Server [PVE] is on Rust network protocol 2634 and build 166586 under Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
How frequently does Sakura Rust Server [PVE] wipe its map?
Sakura Rust Server [PVE] has not had enough wipes recorded to reveal its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 26 days 15 hours.
Player count
Where does Sakura Rust Server [PVE] place in the wider field of Rust servers?
Over the last seven days, Sakura Rust Server [PVE] has #15,920 for player hours, in the top 70% of all ranked servers.
Is Sakura Rust Server [PVE] a busy server?
Sakura Rust Server [PVE] is offline at the moment; the last time it was seen was 26 days 7 hours ago.
Lists and filters
What is meant by the tags on Sakura Rust Server [PVE]?
The game's browser takes its cue from the tags Sakura Rust Server [PVE] has set: gmvanilla (Game mode): You play vanilla survival here; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166586 (Build): The game build is 166586; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded. 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 Sakura Rust Server [PVE] appear in the Rust Server Score lists and filters?
Rust Server Score lists that include Sakura Rust Server [PVE]: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
How is Sakura Rust Server [PVE] set up, and what rules does it keep?
The name of Sakura Rust Server [PVE] gives no gather rate. The default of 8 players applies as the group cap. It runs survival, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. Oxide plugins are running on it. The server runs Valve's anti-cheat, VAC.
Which map is in play on Sakura Rust Server [PVE]?
The game generates the procedural map on Sakura Rust Server [PVE] at size 3,500 with seed 6738. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Connecting
How do you get onto Sakura Rust Server [PVE]?
To connect, start Rust, press F1, and type client.connect 45.140.128.113:10200. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2634,gmvanilla,cs166586,ts8,^o^z
Game
gmvanilla
Game modeYou play vanilla survival here.
mp50
Max playersThe server holds 50 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166586
BuildThe game build is 166586.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxidePlugin framework: 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).