Online 103.137.14.69:28015 checked 9m ago
JoeLoneWolf
Connect
srv = rust.server("103.137.14.69: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, measured since 17 Sep. 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 bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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
3500 · seed 1767964926
- map
- Procedural Map
- size
- 3500
- seed
- 1767964926
Server
srv.info()- address
- 103.137.14.69:28015
- region
- –
- max players
- 20
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 4 Sep 2026, 04:56 UTC
- hostname
- –
- first seen
- 13 Sep 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 · 149 on average | 189/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 130/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 119 on average | 54/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 77/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 46/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 85 on average | 254/700 |
Quick answers
From the figures on this page.
Population
How does JoeLoneWolf compare in the rankings?
Rank #15,335 on seven-day player hours for JoeLoneWolf, within the top 69% of all ranked servers.
How full does JoeLoneWolf run?
Current row: 0 players on JoeLoneWolf, against 20 slots. Over the last seven days it averaged 0 players.
Server data
How smoothly does JoeLoneWolf run?
Server fps over the last 48 hours averages 30; the floor is 30. The entity count peaked at 74,159, covering buildings, deployables and the rest of the world. The memory field tops out at 4,988 MB. What players call lag is these two fields together: low fps and a rising entity count.
What is the Rust version on JoeLoneWolf?
The build is Rust network protocol 2633 and build 162929 on Windows, run by JoeLoneWolf. Joining needs the same protocol on your game; Steam handles the update.
How reliable is JoeLoneWolf, and is it up?
Online is the state at the latest refresh for JoeLoneWolf. A restart about 14 days 23 hours ago is what its reported uptime implies. 167 of 168 hours up over the last 7 full days, or 99%. Rust Data logged it first on 13 September 2026.
In which location is JoeLoneWolf hosted?
For JoeLoneWolf, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 103.137.14.69:28015 is its address.
Rules, settings, map
What rules and settings are recorded for JoeLoneWolf?
You will not find a gather rate in the string JoeLoneWolf. No custom cap; the default of 8 players per group stands. Recorded as survival, the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
Which map has JoeLoneWolf selected?
JoeLoneWolf runs a procedural map of size 3,500 with seed 1767964926, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipes and dates
On what schedule does JoeLoneWolf wipe?
Too few wipes are on record for JoeLoneWolf to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 55 days 9 hours ago, and that is the one in play.
Lists and tags
Which lists on Rust Data hold JoeLoneWolf, and which filters?
These Rust Data lists include JoeLoneWolf: 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.
How should you read the server tags on JoeLoneWolf?
The game's server browser reads these tags from JoeLoneWolf: gmvanilla (Game mode): The mode is vanilla survival; mp20 (Max players): The server lists 20 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs162929 (Build): Build number: 162929; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way into JoeLoneWolf?
In Rust, F1 opens the console: type client.connect 103.137.14.69:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.