JP_Solo/Duo
160.251.185.196:28015 checked 13m ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
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 8 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Top 21% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- wipe-day peak
- 2 players, last three wipes
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
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 9 Oct, 00:01 UTC 6d ago | 2 | – | 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.
Similar servers
Quick answers
Population
JP_Solo/Duo ranking: what position does it hold?
Rank #4,735 over the last seven days in player hours: JP_Solo/Duo, inside the top 21% of ranked servers.
Is JP_Solo/Duo busy?
The current player count for JP_Solo/Duo is 0, out of 15 slots. The seven-day average player count stands at 0, and the highest point was 2. The busiest time in the last 48 hours was 07:00 UTC, when the average player count was 1.
Tags and Filters
How should the tags on JP_Solo/Duo be interpreted?
The game's server browser reads these tags from JP_Solo/Duo: gmrust (Game mode): Survival as standard in Rust; mp15 (Max players): The server has 15 slots; ts8 (Group limit): The game default is 8 per team; v2634 (Protocol): Game protocol 2634; the same version is required to join; cs167058 (Build): Running build 167058; ptrak (Networking): RakNet is the network layer in use; $r? (Region code): Region code not set; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The Modded category applies; plugins or settings alter gameplay. At the top of this page you also see its players now, its queue and when its world was made, taken from the tags.
JP_Solo/Duo in BestRustServers.xyz lists and filters: which ones?
The BestRustServers.xyz lists that include JP_Solo/Duo are: Best modded Rust servers. These filters on the server list display it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Server Details
JP_Solo/Duo Rust version: which one?
On Linux, JP_Solo/Duo runs Rust network protocol 2634 and build 167058. Joining requires the same protocol; Steam updates your game for you.
JP_Solo/Duo performance: is it smooth?
Over 48 hours, it averaged 44 server fps; the lowest was 30. Buildings, deployables and the rest of the world accounted for up to 119,659 entities. The maximum memory used was 4,886 MB. Players feel lag when fps is low and entity count climbs.
What is the uptime and reliability of JP_Solo/Duo?
At the moment, JP_Solo/Duo is up. The uptime it reports shows a restart roughly 6 days 1 hours ago. It was up 100% of the time over the last 6 full days, 144 of 144 hours. On 8 October 2026, BestRustServers.xyz saw it for the first time.
What is the location of JP_Solo/Duo?
No region is published by JP_Solo/Duo. BestRustServers.xyz does not look up where the machine stands; it shows where a server says it is. You can reach it at 160.251.185.196:28015.
Rules and Settings
JP_Solo/Duo map: which one is it?
On JP_Solo/Duo, the map is procedural, size 4,500 with seed 225714968, generated by the game. On RustMaps, from this page, the same size and seed show the same map.
What are the settings and rules for JP_Solo/Duo?
No gather rate appears in the name of JP_Solo/Duo. The default cap of 8 players per group is in force. It runs survival, gather, build, raid: the standard game. Raids and PvP are on. Listed as Modded in the browser: the game is changed by plugins or settings. Oxide plugins are used. The server has VAC on.
Wipe Information
JP_Solo/Duo wipe schedule: what does it show?
The record holds too few wipes for JP_Solo/Duo to show a rhythm. The monthly force wipe applies to every Rust server, and the next is on Thursday 5 November at 19:00 UTC. The current world has been running since 6 days 6 hours.
On JP_Solo/Duo, what occurs on wipe day?
An average peak of 2 players was drawn by its recent wipes. 34 hours after the latest wipe, the crowd hit its peak.
Connect
JP_Solo/Duo joining: how is it done?
Enter client.connect 160.251.185.196:28015 in the console (F1 in Rust), or use Launch Rust on this page to open Steam and connect.
Server tags
Published as mp15,ptrak,$r?,v2634,gmrust,cs167058,ts8,^o^z
Game
gmrust- Game mode Survival as standard in Rust.
mp15- Max players The server has 15 slots.
ts8- Group limit The game default is 8 per team.
v2634- Protocol Game protocol 2634; the same version is required to join.
cs167058- Build Running build 167058.
ptrak- Networking RakNet is the network layer in use.
$r?- Region code Region code not set.
Mods and access
^o- Oxide Oxide (uMod) provides the plugin framework here.
^z- Modded The Modded category applies; plugins or settings alter gameplay.
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.