Rust StatisticsWorking papers on every public Rust server · 81,308 players now

SAMURAI Server V2

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 38d ago · 139.99.22.28:27291

Abstract

We describe the public Rust server SAMURAI Server V2, reached at 139.99.22.28:27291. It is offline at the last check, against a seven-day mean of 01. It ranks #15,478 of all servers, the top 70%. It last wiped 41d ago.

Keywordsmodded oxide

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now0/250% full
In the queue0no queue
Seven-day mean0peak –
Rank2#15,478top 70%
Last wipe41d agono schedule published
Next wipe3–no rhythm it keeps

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

No hourly history yet.
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
This server has not answered a direct query in the last 48 hours.
Figure 2: Server performance. 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.

4Rank

The server stands in the top 70% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k20 Sep22 Sep24 Sep26 Sep28 Sep30 Sep
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: 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.

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Usual gap0.3 daysbetween real wipes
On rhythm67%of its recent wipes
Wipe-day peak8players, last three wipes
Fri 18 SepThu 17 SepThu 17 Sep
02468+0h+9h+19h+28h+38h+47h
Figure 4: The first 48 hours of its last wipes: players each hour, from the hour of the wipe. The latest peaked at 8, 3 hours in.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Fri 18 Sep, 06:1341d ago 8 – running 0
Thu 17 Sep, 23:0841d ago 8 – 0.3 d 1
Thu 17 Sep, 14:2642d ago 8 – 0.4 d 2
Thu 17 Sep, 08:0942d ago 8 – 0.3 d 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

Map of SAMURAI Server V2
Figure 5: The map: Procedural Map, size 2100, seed 5001200. Open on RustMaps.
Table 4: The server's published settings.
Address139.99.22.28:27291
Region–
Max players25
Group limit8, the default
Wipe schedule–
Last wipe18 Sep 2026, 06:13 UTC
Hostname–
First seen17 Sep 2026
MapProcedural Map
Size2100
Seed5001200

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded Rust servers listed live [2] and Rust wipe forecast [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
ShockRust | Blue | NoLimitno group limit · 149 on average183/500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average133/100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 119 on average94/225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 94 on average77/700
RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average42/200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 85 on average250/700

Appendix AQuick answers

From the figures on this page.

Server details

A.1In which location is SAMURAI Server V2 based?

A region is not published by SAMURAI Server V2. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. You will find it at 139.99.22.28:27291.

A.2What is the reliability of SAMURAI Server V2, and is it online?

Right now, SAMURAI Server V2 is offline, and the last time it was seen was 38 days 4 hours ago. Of the 168 hours in the last 7 full days, 0 were served, an availability of 0%. The first record of it by Rust Statistics dates to 17 September 2026.

A.3What is the Rust version for SAMURAI Server V2?

SAMURAI Server V2 is running Rust network protocol 2633 and build 164530 on the Linux operating system. Steam updates your game for you, but you must be on the same protocol to join.

Wipe schedule

A.4What schedule does SAMURAI Server V2 follow for wipes?

With irregular wipe times, SAMURAI Server V2 offers no next wipe to predict. Wiping is compulsory for every Rust server at the monthly force wipe, the next of which is Thursday 5 November at 19:00 UTC. The world currently in use was created 41 days 8 hours ago.

A.5What happens on SAMURAI Server V2 when wipe day arrives?

Across its recent wipes, the average peak population was 8 players. The crowd reached its maximum 3 hours after the latest wipe.

Population

A.6What is the rank of SAMURAI Server V2 among Rust servers?

The seven-day player-hours ranking puts SAMURAI Server V2 at #15,478, within the top 70% of ranked servers.

A.7How would you characterise the player activity on SAMURAI Server V2?

The last recorded sighting of SAMURAI Server V2 was 38 days 4 hours ago; it is offline now.

Tags and filters

A.8How should the tags on SAMURAI Server V2 be interpreted?

gmrust (Game mode): This is survival as standard Rust plays; mp25 (Max players): The slot count is 25; ts8 (Group limit): The team cap is 8, which is the game default; v2633 (Protocol): The game protocol is 2633; your client must match it to join; cs164530 (Build): The game build is 164530; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): The region code is unset; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded: these are the tags SAMURAI Server V2 publishes, and the server browser reads them. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.9Where can SAMURAI Server V2 be found among the Rust Statistics lists and filters?

The Rust Statistics lists that SAMURAI Server V2 fits are: Modded Rust servers. These filters on the server list return it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Rules, settings, map

A.10Under what rules and settings does SAMURAI Server V2 operate?

The name of SAMURAI Server V2 states no gather rate. At 8 players, the group limit equals the game's default. Listed as survival, the game mode is gather, build and raid: the standard game. Players may raid and fight one another. It appears under Modded in the browser: the game is changed by plugins or settings. Plugins number Oxide on this server. VAC is not in use; Valve's anti-cheat is off.

A.11What is the map for SAMURAI Server V2?

The game generates SAMURAI Server V2's procedural map at size 2,100, from seed 5001200. Equal size and seed yield an identical map, which this page offers to view on RustMaps.

How to join

A.12What steps are required to join SAMURAI Server V2?

Press F1 inside Rust to open the console and enter client.connect 139.99.22.28:27291. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp25,ptrak,$r?,v2633,gmrust,cs164530,ts8,^o^z.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. This is survival as standard Rust plays.
mp25Max players. The slot count is 25.
ts8Group limit. The team cap is 8, which is the game default.
v2633Protocol. The game protocol is 2633; your client must match it to join.
cs164530Build. The game build is 164530.
ptrakNetworking. Networking runs on RakNet, the game's standard layer.
$r?Region code. The region code is unset.
Mods and access
^oOxide. The plugin framework in use is Oxide (uMod).
^zModded. The game is altered by plugins or settings, so it is listed as 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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Modded Rust servers listed live. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Rust wipe forecast. ruststatistics.org/rust-servers-wiping-today-list.