Working its way up from the back of the class: #15,478 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
13/ 100
F
Lost ground: down 11,440 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.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 17 Sep. 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
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···WW··
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap0.3 daysbetween real wipes
on rhythm67%of its recent wipes
wipe-day peak8players, last three wipes
The first 48 hours of its last wipes
Fri 18 SepThu 17 SepThu 17 Sep
Players each hour, from the hour of the wipe. The latest peaked at 8, 3 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 18 Sep, 06:13 UTC41d ago
8
–
running
0
Thu 17 Sep, 23:08 UTC41d ago
8
–
0.3 days
1
Thu 17 Sep, 14:26 UTC41d ago
8
–
0.4 days
2
Thu 17 Sep, 08:09 UTC42d ago
8
–
0.3 days
1
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 SAMURAI Server V2. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 139.99.22.28:27291.
Is SAMURAI Server V2 up, and how steady is its uptime?
The server is down: SAMURAI Server V2 is offline now, with the last sighting 38 days 3 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 17 September 2026.
What Rust version is SAMURAI Server V2 on?
Rust network protocol 2633 and build 164530 on Linux is what SAMURAI Server V2 runs. Steam updates your game for you, but you need the same protocol to join.
Resets
On what schedule does SAMURAI Server V2 reset?
SAMURAI Server V2 wipes at times that vary, so no next wipe can be predicted. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 41 days 7 hours.
What happens on SAMURAI Server V2 when wipe day arrives?
The average peak on its recent wipes was 8 players. The crowd on the latest wipe was largest 3 hours after it began.
Player count
Where does SAMURAI Server V2 sit among Rust servers?
In the top 70% of all ranked servers, SAMURAI Server V2 sits at #15,478 for player hours over the last seven days.
What does the population on SAMURAI Server V2 look like?
The last sighting of SAMURAI Server V2 was 38 days 3 hours ago, and it is offline right now.
Tags and filters
What is meant by the tags on SAMURAI Server V2?
The game's browser takes its cue from the tags SAMURAI Server V2 has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp25 (Max players): 25 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs164530 (Build): The game build is 164530; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does SAMURAI Server V2 appear in the Rust Server Score lists and filters?
These Rust Server Score lists count SAMURAI Server V2 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.
Map and rules
What settings and rules apply on SAMURAI Server V2?
Nothing in the name of SAMURAI Server V2 states a gather rate. The group limit stays at the game's default of 8 players. You get survival here, gather, build and raid, as in 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 not covered by VAC, Valve's anti-cheat.
SAMURAI Server V2 runs which map?
A procedural map of size 2,100 and seed 5001200, generated by the game, is what SAMURAI Server V2 runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
How do you get onto SAMURAI Server V2?
Enter client.connect 139.99.22.28:27291 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 asmp25,ptrak,$r?,v2633,gmrust,cs164530,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp25
Max players25 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs164530
BuildThe game build is 164530.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
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. Strongest in standing (F); momentum is the one to work on (F).