Online 69.41.181.103:25726 checked 10m ago
MoJo
Connect
srv = rust.server("69.41.181.103:25728")
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 best
Top 69% 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 2 Oct, 09:32 UTC26d ago | 0 | 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
3000 · seed 8326175
- map
- Procedural Map
- size
- 3000
- seed
- 8326175
Server
srv.info()- address
- 69.41.181.103:25726
- region
- –
- max players
- 16
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 2 Oct 2026, 09:32 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 · 157 on average | 109/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 · 116 on average | 132/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 91 on average | 102/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 32/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 29/1000 |
Quick answers
From the figures on this page.
Player counts
How does MoJo compare in the rankings?
Player hours over seven days put MoJo at #15,348, in the top 69% of the ranked set.
How full does MoJo run?
The sample now reads 0 players for MoJo, out of 16 slots. Over the last seven days it averaged 0 players.
Server facts
What does performance look like on MoJo?
The 48-hour average is 229 server fps, with a low of 196. Buildings, deployables and all else in the world took the count as high as 45,978 entities. The memory field tops out at 1,906 MB. Low fps plus an entity count on the way up is the lag players report.
What Rust version does MoJo run?
Version Rust network protocol 2635 and build 168909 on Linux is reported by MoJo. The protocol has to match before you can join, and Steam does the updating.
How reliable is MoJo, and is it up?
The current sample puts MoJo online. Count back 6 hours from its reported uptime to get the last restart. Uptime of 100% across the last 7 full days: 168 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.
Where does MoJo sit?
No region is published by MoJo. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 69.41.181.103:25726.
Settings and map
Which settings and rules does MoJo run?
You will not find a gather rate in the string MoJo. The group limit sits at the default of 8 players. survival is the game mode here, and the usual game, with gathering, building and raiding. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. Anti-cheat status: VAC on.
Which map has MoJo selected?
MoJo runs a procedural map of size 3,000 with seed 8326175, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipes and dates
When does MoJo wipe, and on what schedule?
Too few wipes are on record for MoJo 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. This world was created 26 days 11 hours ago.
What is wipe day on MoJo like?
Across recent wipes the busiest point averaged 0 players. 0 hours after the latest wipe, the crowd reached its peak.
Lists and tags
Where does MoJo appear among Rust Data lists and filters?
These Rust Data lists include MoJo: 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 MoJo?
Read by the game's server browser, the tags MoJo publishes are: gmrust (Game mode): Survival play, standard Rust; mp16 (Max players): The server lists 16 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; 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.
Connecting
What is the way into MoJo?
Enter client.connect 69.41.181.103:25726 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.