Online 163.44.98.246:28015 checked 11m ago
JP_Solo/Duo
Connect
srv = rust.server("163.44.98.246: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 23 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 26% 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
4500 · seed 85804905
- map
- Procedural Map
- size
- 4500
- seed
- 85804905
Server
srv.info()- address
- 163.44.98.246:28015
- region
- –
- max players
- 15
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 23 Oct 2026, 01:50 UTC
- hostname
- –
- first seen
- 23 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 · 152 on average | 46/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 129/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 54/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 17/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 2/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 5/1000 |
Quick answers
From the figures on this page.
Population
How does JP_Solo/Duo compare in the rankings?
Over the last seven days JP_Solo/Duo sits at #5,791 on player hours, in the top 26% of ranked servers.
How full does JP_Solo/Duo run?
Current row: 0 players on JP_Solo/Duo, against 15 slots. Over the last seven days it averaged 0 players and peaked at 1.
Server facts
How well does JP_Solo/Duo perform?
Server fps over the last 48 hours averages 40; the floor is 23. Buildings, deployables and all else in the world took the count as high as 116,363 entities. A high of 4,693 MB of memory used. Low fps plus an entity count on the way up is the lag players report.
Which Rust version is JP_Solo/Duo on?
Version Rust network protocol 2635 and build 168909 on Linux is reported by JP_Solo/Duo. Steam updates your game for you, but the protocol must match to join.
Is JP_Solo/Duo up, and what does its uptime show?
JP_Solo/Duo reports itself online at the current refresh. A restart about 6 days 2 hours ago is what its reported uptime implies. Uptime of 99% across the last 5 full days: 119 hours of 120. Rust Data logged it first on 23 October 2026.
Which location does JP_Solo/Duo run from?
No region is published by JP_Solo/Duo. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 163.44.98.246:28015.
Settings and map
Which settings and rules does JP_Solo/Duo run?
No gather rate appears in the name: JP_Solo/Duo. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and gather, build, raid: the standard loop. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
Which map has JP_Solo/Duo selected?
Size 4,500, seed 85804905: the procedural map on JP_Solo/Duo, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipes and dates
On what schedule does JP_Solo/Duo wipe?
The record for JP_Solo/Duo holds too few wipes to show a 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 6 days 3 hours ago.
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. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
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): Rust survival in its standard form; mp15 (Max players): 15 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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 JP_Solo/Duo?
The manual route: launch Rust, F1, then client.connect 163.44.98.246:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.