Offline 98.97.26.127:28015 checked 10d ago
Jim Solo
Connect
srv = rust.server("98.97.26.127: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. 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 70% 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, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 16 Oct, 20:43 UTC11d ago | 1 | NaN | running | 0 |
| 1 | Fri 16 Oct, 04:46 UTC11d ago | 1 | NaN | 0.7 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
- 98.97.26.127:28015
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 16 Oct 2026, 20:43 UTC
- hostname
- –
- first seen
- 16 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 · 163 on average | 51/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 131/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 113 on average | 64/225 |
| 3 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 15/200 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 87 on average | 62/700 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 14/1000 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does Jim Solo rank?
Player hours over seven days put Jim Solo at #15,193, in the top 70% of the ranked set.
How full does Jim Solo run?
Offline now for Jim Solo, with the last sample 10 days 12 hours ago.
Server data
Which Rust version is Jim Solo on?
The build is Rust network protocol 2634 and build 167781 on Linux, run by Jim Solo. The protocol has to match before you can join, and Steam does the updating.
How reliable is Jim Solo, and is it up?
Offline now for Jim Solo, last seen 10 days 12 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 16 October 2026.
In which location is Jim Solo hosted?
There is no region published for Jim Solo. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 98.97.26.127:28015.
Rules, settings, map
Which settings and rules does Jim Solo run?
No gather rate appears in the name: Jim Solo. The group limit sits at the default of 8 players. Recorded as survival, the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. Anti-cheat status: VAC off.
What is the map on Jim Solo?
The game generates its map: procedural, on Jim Solo.
Wipes and dates
When does Jim Solo wipe, and on what schedule?
A rhythm cannot be read from the wipes of Jim Solo on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 11 days 2 hours ago, and that is the one in play.
On Jim Solo, what happens on wipe day?
Recent wipes averaged 1 players at their peak. 0 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Which lists on Rust Data hold Jim Solo, and which filters?
These Rust Data lists include Jim Solo: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Which meanings do the tags on Jim Solo hold?
Read by the game's server browser, the tags Jim Solo publishes are: gmrust (Game mode): Survival play, standard Rust; mp5 (Max players): Slot count: 5; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): To join, your game must run protocol 2634; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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 Jim Solo?
In Rust, F1 opens the console: type client.connect 98.97.26.127:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.