Offline 31.201.123.139:28015 checked 27d ago
Jurgen Solo Rust
Connect
srv = rust.server("31.201.123.139: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 · force wipes only
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 7d 6h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 6h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 6h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 21:57 UTC FW27d ago | 1 | 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 31.201.123.139:28015
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 21:57 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 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 514 on average | 521/525 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 387/450 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 291 on average | 45/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 276 on average | 49/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 275 on average | 52/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 241 on average | 167/200 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does Jurgen Solo Rust rank?
Player hours over seven days put Jurgen Solo Rust at #13,894, in the top 60% of the ranked set.
How many players does Jurgen Solo Rust hold at once?
Jurgen Solo Rust returns no live count at this refresh, having last been seen 27 days 13 hours ago.
About the server
What Rust version does Jurgen Solo Rust run?
The build is Rust network protocol 2634 and build 166494 on Windows, run by Jurgen Solo Rust. Steam updates your game for you, but the protocol must match to join.
How reliable is Jurgen Solo Rust, and is it online now?
Offline now for Jurgen Solo Rust, last seen 27 days 13 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 Jurgen Solo Rust sit?
There is no region published for Jurgen Solo Rust. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 31.201.123.139:28015.
Settings and map
What rules and settings are recorded for Jurgen Solo Rust?
The name Jurgen Solo Rust carries no gather rate. The group limit sits at the default of 8 players. Recorded as survival, the base game, where you gather, build and raid. Raids and player combat are enabled. It is a community server, and the browser files it under Community. VAC is running: Valve's anti-cheat is on.
Which map has Jurgen Solo Rust selected?
A procedural map runs on Jurgen Solo Rust, generated by the game.
Wipes and dates
On what schedule does Jurgen Solo Rust wipe?
The only wipe Jurgen Solo Rust takes is the monthly force wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. A new world was started 27 days 14 hours ago, and that is the one in play.
What is wipe day on Jurgen Solo Rust like?
Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 1 hours in.
Tags and filters
Which Rust Data filters and lists contain Jurgen Solo Rust?
These Rust Data lists include Jurgen Solo Rust: Rust community servers, unfiltered. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the server tags on Jurgen Solo Rust?
The game's server browser reads these tags from Jurgen Solo Rust: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): The server lists 1 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166494 (Build): The server runs build 166494; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty. 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 to join Jurgen Solo Rust?
In Rust, F1 opens the console: type client.connect 31.201.123.139:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.