Offline 45.140.128.113:10200 checked 26d ago
Sakura Rust Server [PVE]
Connect
srv = rust.server("45.140.128.113:10201")
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 2 Oct. 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 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())Map
3500 · seed 6738![Map of Sakura Rust Server [PVE]](https://files.facepunch.com/rust/map-images/44043788ee5eb0df0e217cc410be02292c554074fa2a71d8da79ff5f8a035801/proceduralmap.3500.1790925636323.289_44043788ee5eb0df0e217cc410be0229.jpg)
- map
- Procedural Map
- size
- 3500
- seed
- 6738
Server
srv.info()- address
- 45.140.128.113:10200
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 2 Oct 2026, 07:21 UTC
- hostname
- –
- first seen
- 2 Oct 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 · 155 on average | 32/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 132/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 30/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 92 on average | 24/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 5/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 4/1000 |
Quick answers
From the figures on this page.
Player counts
How does Sakura Rust Server [PVE] compare in the rankings?
Over the last seven days Sakura Rust Server [PVE] sits at #15,920 on player hours, in the top 70% of ranked servers.
How full does Sakura Rust Server [PVE] run?
Offline now for Sakura Rust Server [PVE], with the last sample 26 days 10 hours ago.
Server data
What Rust version does Sakura Rust Server [PVE] run?
The build is Rust network protocol 2634 and build 166586 on Windows, run by Sakura Rust Server [PVE]. Joining needs the same protocol on your game; Steam handles the update.
Is Sakura Rust Server [PVE] up, and what does its uptime show?
The latest sample has Sakura Rust Server [PVE] offline, with a last sighting 26 days 10 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 2 October 2026.
Where does Sakura Rust Server [PVE] sit?
No region is published by Sakura Rust Server [PVE]. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 45.140.128.113:10200 is its address.
Rules, settings, map
What rules and settings are recorded for Sakura Rust Server [PVE]?
The name Sakura Rust Server [PVE] carries no gather rate. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. Anti-cheat status: VAC on.
Which map has Sakura Rust Server [PVE] selected?
Size 3,500, seed 6738: the procedural map on Sakura Rust Server [PVE], generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipes and dates
On what schedule does Sakura Rust Server [PVE] wipe?
Too few wipes are on record for Sakura Rust Server [PVE] to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 26 days 18 hours ago.
Lists and tags
Which lists on Rust Data hold Sakura Rust Server [PVE], and which filters?
The Rust Data lists that Sakura Rust Server [PVE] fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on Sakura Rust Server [PVE] hold?
Read by the game's server browser, the tags Sakura Rust Server [PVE] publishes are: gmvanilla (Game mode): The mode is vanilla survival; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166586 (Build): Recorded game build: 166586; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way into Sakura Rust Server [PVE]?
In Rust, F1 opens the console: type client.connect 45.140.128.113:10200. Launch Rust on this page does the same by opening the game through Steam and connecting.