Offline 160.251.185.196:28015 checked 11d ago
JP_Solo/Duo
Connect
srv = rust.server("160.251.185.196:28017")
print(srv.connect_command)Right now
srv.summary()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 8 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 · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 34 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 9 Oct, 00:01 UTC20d ago | 2 | NaN | running | 0 |
# 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
4500 · seed 225714968
- map
- Procedural Map
- size
- 4500
- seed
- 225714968
Server
srv.info()- address
- 160.251.185.196:28015
- region
- –
- max players
- 15
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 9 Oct 2026, 00:01 UTC
- hostname
- –
- first seen
- 8 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 · 149 on average | 31/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 120 on average | 49/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 18/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 93 on average | 50/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 243/260 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does JP_Solo/Duo rank?
Player hours over seven days put JP_Solo/Duo at #15,330, in the top 70% of the ranked set.
How full does JP_Solo/Duo run?
Offline now for JP_Solo/Duo, with the last sample 11 days 23 hours ago.
Server data
What Rust version does JP_Solo/Duo run?
Rust network protocol 2634 and build 167058 on Linux is what JP_Solo/Duo runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is JP_Solo/Duo, and is it online now?
The latest sample has JP_Solo/Duo offline, with a last sighting 11 days 23 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 8 October 2026.
Where does JP_Solo/Duo sit?
For JP_Solo/Duo, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 160.251.185.196:28015.
Settings and map
Which settings and rules does JP_Solo/Duo run?
No gather rate appears in the name: JP_Solo/Duo. The group limit sits at the default of 8 players. Recorded as survival, the usual game, with gathering, building and raiding. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has JP_Solo/Duo loaded?
JP_Solo/Duo runs a procedural map of size 4,500 with seed 225714968, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipes and dates
When does JP_Solo/Duo wipe, and on what schedule?
Too few wipes are on record for JP_Solo/Duo to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 20 days 23 hours ago.
On JP_Solo/Duo, what happens on wipe day?
Recent wipes averaged 2 players at their peak. The crowd on the latest wipe topped out 34 hours after it began.
Tags, lists
Where does JP_Solo/Duo appear among Rust Data lists and filters?
On Rust Data, JP_Solo/Duo appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on JP_Solo/Duo hold?
Read by the game's server browser, the tags JP_Solo/Duo publishes are: gmrust (Game mode): Survival play, standard Rust; mp15 (Max players): 15 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167058 (Build): The server runs build 167058; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
How can I connect to JP_Solo/Duo?
In Rust, F1 opens the console: type client.connect 160.251.185.196:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.