Offline 45.140.128.93:11000 checked 27d ago
ShinobiRust2
Connect
srv = rust.server("45.140.128.93:11001")
print(srv.connect_command)Right now
srv.summary()display(Image(srv.banner))
Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 19 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 6d 23h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 6d 23h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 34d 23h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 19:10 UTC FW28d ago | 2 | NaN | running | 2 |
# 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.
display(srv.map, srv.info())Map
3750 · seed 579120958
- map
- Procedural Map
- size
- 3750
- seed
- 579120958
Server
srv.info()- address
- 45.140.128.93:11000
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 19:10 UTC
- hostname
- –
- first seen
- 19 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 151 on average | 106/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 135/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 163/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 95 on average | 67/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 90 on average | 206/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 345/350 |
Quick answers
From the figures on this page.
Population data
How does ShinobiRust2 compare in the rankings?
Player hours over seven days put ShinobiRust2 at #16,006, in the top 69% of the ranked set.
How full does ShinobiRust2 run?
ShinobiRust2 returns no live count at this refresh, having last been seen 27 days 20 hours ago.
About the server
What Rust version does ShinobiRust2 run?
Version Rust network protocol 2634 and build 166494 on Windows is reported by ShinobiRust2. The protocol has to match before you can join, and Steam does the updating.
How reliable is ShinobiRust2, and is it online now?
The latest sample has ShinobiRust2 offline, with a last sighting 27 days 20 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 19 September 2026.
Which location does ShinobiRust2 run from?
There is no region published for ShinobiRust2. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 45.140.128.93:11000.
Settings and map
Which settings and rules does ShinobiRust2 run?
No gather rate appears in the name: ShinobiRust2. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the base game, where you gather, build and raid. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. Anti-cheat status: VAC on.
Which map has ShinobiRust2 selected?
ShinobiRust2 runs a procedural map of size 3,750 with seed 579120958, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe schedule
On what schedule does ShinobiRust2 wipe?
The only wipe ShinobiRust2 takes is the monthly force wipe. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. This world was created 28 days ago.
What is wipe day on ShinobiRust2 like?
The average peak over recent wipes is 2 players. 1 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Where does ShinobiRust2 appear among Rust Data lists and filters?
The Rust Data lists that ShinobiRust2 fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on ShinobiRust2 hold?
Read by the game's server browser, the tags ShinobiRust2 publishes are: gmvanilla (Game mode): Survival in vanilla form; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): To join, your game must run protocol 2634; cs166494 (Build): Build number: 166494; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
How to join
What is the way to join ShinobiRust2?
In Rust, F1 opens the console: type client.connect 45.140.128.93:11000. Launch Rust on this page does the same by opening the game through Steam and connecting.