Offline 185.61.48.15:28015 checked 12d ago
JAD SOLO PVE NEW
Connect
srv = rust.server("185.61.48.15:28016")
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. 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 best
Top 60% 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 1, 27 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 15 Oct, 08:52 UTC13d ago | 1 | NaN | running | 0 |
| 1 | Fri 2 Oct, 20:07 UTC26d ago | 1 | held half | 12.5 days | 1 |
# 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 185.61.48.15:28015
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 15 Oct 2026, 08:52 UTC
- hostname
- –
- first seen
- 1 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 | ABYSS | PvE | US | Vanilla | Noob Friendly | NA · groups of 8+ · monthly · 54 on average | 65/200 |
| 1 | [EU] RustEZ Pure PvE | Low Decay | No Killing | No Raiding | EU · groups of 8+ · monthly · 33 on average | 24/200 |
| 2 | [US] RustEZ Pure PvE | Low Decay | No Killing | No Raiding | NA · groups of 8+ · monthly · 32 on average | 35/200 |
| 3 | 【云梦泽PVE】萌新学习|土味养老|死亡不掉|原倍 | EA · groups of 30+ · monthly · 22 on average | 2/200 |
| 4 | [PvE] Skyline PvE - No Raiding/Killing, No Decay, Noob Friendly | groups of 8+ · monthly · 21 on average | 16/150 |
| 5 | [EU/GER] Rust Norddeutschland PVE | EU · groups of 8+ · biweekly · 16 on average | 6/100 |
Quick answers
From the figures on this page.
Population data
How does JAD SOLO PVE NEW compare in the rankings?
Rank #12,917 on seven-day player hours for JAD SOLO PVE NEW, within the top 60% of all ranked servers.
How many players does JAD SOLO PVE NEW hold at once?
JAD SOLO PVE NEW returns no live count at this refresh, having last been seen 12 days 10 hours ago.
Server data
What Rust version does JAD SOLO PVE NEW run?
Rust network protocol 2634 and build 166652 on Windows is what JAD SOLO PVE NEW runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is JAD SOLO PVE NEW, and is it up?
JAD SOLO PVE NEW is offline at this refresh; the last response came 12 days 10 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 1 October 2026.
Where does JAD SOLO PVE NEW sit?
For JAD SOLO PVE NEW, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 185.61.48.15:28015 is its address.
Map and rules
What rules and settings are recorded for JAD SOLO PVE NEW?
No gather rate appears in the name: JAD SOLO PVE NEW. No custom cap; the default of 8 players per group stands. Recorded as pve, no combat between players. The server browser lists it under Community. VAC is running: Valve's anti-cheat is on.
Which map has JAD SOLO PVE NEW loaded?
A procedural map runs on JAD SOLO PVE NEW, generated by the game.
Wipe data
On what schedule does JAD SOLO PVE NEW wipe?
A rhythm cannot be read from the wipes of JAD SOLO PVE NEW on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 13 days 13 hours ago.
On JAD SOLO PVE NEW, what happens on wipe day?
The average peak over recent wipes is 1 players. 27 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.
Tags, lists
Where does JAD SOLO PVE NEW appear among Rust Data lists and filters?
On Rust Data, JAD SOLO PVE NEW appears in these lists: Rust community servers, unfiltered and Rust PvE servers. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: PvE ^p; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the server tags on JAD SOLO PVE NEW?
The game's server browser reads these tags from JAD SOLO PVE NEW: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): The server lists 1 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166652 (Build): The server runs build 166652; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^p (PvE): Players do not fight each other here; the world supplies the danger. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
What is the way into JAD SOLO PVE NEW?
The manual route: launch Rust, F1, then client.connect 185.61.48.15:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.