Working its way up from the back of the class: #11,756 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
47/ 100
D
Slipped a little: down 620 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from D 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.
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 10 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 53% 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
You'll find no region listed by ShinobiRust2. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 45.140.128.117:12000.
How dependable is ShinobiRust2, and is it online at the moment?
At this moment, ShinobiRust2 is offline; the last time it was seen was 19 days 10 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 10 October 2026.
On what Rust version does ShinobiRust2 sit?
You will find ShinobiRust2 on Rust network protocol 2634 and build 167231, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does ShinobiRust2 wipe its map?
There are too few wipes on record for ShinobiRust2 to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 40 days 14 hours have passed since this world was made.
Player numbers
Where does ShinobiRust2 place in the wider field of Rust servers?
Over the last seven days, ShinobiRust2 has #11,756 for player hours, in the top 53% of all ranked servers.
Is ShinobiRust2 a busy server?
ShinobiRust2 is offline at the moment; the last time it was seen was 19 days 10 hours ago.
Tags
What is meant by the tags on ShinobiRust2?
You'll see ShinobiRust2 tagged with gmvanilla (Game mode): You play vanilla survival here; mp50 (Max players): 50 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): Join only if your game runs protocol 2634; cs167231 (Build): This runs on build 167231; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^o (Oxide): The plugin framework in use is 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. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Where does ShinobiRust2 appear in the Rust Server Score lists and filters?
These Rust Server Score lists count ShinobiRust2 among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules and settings
How is ShinobiRust2 set up, and what rules does it keep?
Nothing in the name of ShinobiRust2 states a gather rate. The default of 8 players applies as the group cap. You get survival here, gather and build and raid: the standard game. You can raid other players and fight them. 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.
ShinobiRust2 runs which map?
The game generates the procedural map on ShinobiRust2 at size 3,750 with seed 579120958. A matching size and seed produce the same map, viewable on RustMaps from this page.
Connecting
How should you connect to ShinobiRust2?
Enter client.connect 45.140.128.117:12000 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,$r?,v2634,gmvanilla,cs167231,ts8,^o^z
Game
gmvanilla
Game modeYou play vanilla survival here.
mp50
Max players50 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167231
BuildThis runs on build 167231.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideThe plugin framework in use is 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. Even marks across the subjects, from D to D.