Rust Server TrendsSeismic network · station log
Recording Stations11,716 Players55,754 Active3,252 Wipes · 3 h168 48 h

Station XX-15330 · no signal

JP_Solo/Duo

Offline 160.251.185.196:28015 checked 11d ago

moddedoxide
Connect
Players now
0/ 15
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,330
top 70%
Last wipe
20d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15330 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 15 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k8 Oct11 Oct14 Oct18 Oct21 Oct24 Oct

Top 70% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak
2players, last three wipes

The first 48 hours of its last wipes

00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 2, 34 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Fri 9 Oct, 00:01 UTC20d ago M0.3rising 2 – running 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit no group limit · 149 on average
143/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
122/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 118 on average
184/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 93 on average
78/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average
7/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
18/ 1000
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on JP_Solo/Duo?

Generated by the game, the map on JP_Solo/Duo is procedural, size 4,500 with seed 225714968. From this page you can look at it on RustMaps, since the same size and seed give the same map.

Which settings and rules apply on JP_Solo/Duo?

You will find no gather rate in the name of JP_Solo/Duo. At the game's default, groups can have up to 8 players. In survival mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Oxide. The server has VAC on, Valve's anti-cheat.

Live population

How many players are recorded on JP_Solo/Duo right now?

JP_Solo/Duo is not responding at this moment and is offline, last seen 11 days 9 hours ago.

How does JP_Solo/Duo rank against other Rust servers?

The last seven days of player hours place JP_Solo/Duo at #15,330, in the top 70% of all ranked servers.

Server details

How reliably does JP_Solo/Duo stay online?

No contact with JP_Solo/Duo right now, and the last recorded contact was 11 days 9 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. 8 October 2026 is when Rust Server Trends first recorded it.

Which region does JP_Solo/Duo run from?

A region is not published by JP_Solo/Duo. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 160.251.185.196:28015.

Which Rust version is JP_Solo/Duo running?

Rust network protocol 2634 and build 167058 on Linux is what JP_Solo/Duo runs. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe day

What does wipe day look like on JP_Solo/Duo?

2 players, on average, was the busiest crowd at its recent wipes. 34 hours into the latest wipe, the crowd reached its peak.

How often does JP_Solo/Duo wipe, and on which days?

Too few wipes of JP_Solo/Duo are on record yet to show its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The present world dates from 20 days 10 hours.

Lists and tags

What do the server tags on JP_Solo/Duo mean?

Tags published by JP_Solo/Duo and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp15 (Max players): 15 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs167058 (Build): The game build is 167058; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does JP_Solo/Duo appear?

The Rust Server Trends lists that take in JP_Solo/Duo are: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Connecting

What steps get you onto JP_Solo/Duo?

Enter client.connect 160.251.185.196:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp15,ptrak,$r?,v2634,gmrust,cs167058,ts8,^o^z

Game

gmrust
Game mode Survival in standard Rust.
mp15
Max players 15 slots are available.
ts8
Group limit This uses the game default of 8 per team.
v2634
Protocol Game protocol 2634: to join, your game must match this version.
cs167058
Build The game build is 167058.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code No region code is set for this server.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded Plugins or settings alter the game, so it's listed under Modded.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.