Offline 159.26.107.34:28015 checked 8d ago
Japiman Server
Connect
srv = rust.server("159.26.107.34: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 bestTop 59% 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 159.26.107.34:28015
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 19 Oct 2026, 11:33 UTC
- hostname
- –
- first seen
- 19 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 · 159 on average | 43/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 114 on average | 50/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 21/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 6/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 6/1000 |
Quick answers
From the figures on this page.
Player counts
What position does Japiman Server take in the server rankings?
Over the last seven days Japiman Server sits at #13,021 on player hours, in the top 59% of ranked servers.
What population does Japiman Server carry?
Japiman Server returns no live count at this refresh, having last been seen 8 days 7 hours ago.
Server facts
Which Rust version is Japiman Server on?
The build is Rust network protocol 2634 and build 167781 on Windows, run by Japiman Server. The protocol has to match before you can join, and Steam does the updating.
How reliable is Japiman Server, and is it up?
Offline now for Japiman Server, last seen 8 days 7 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 19 October 2026.
Which location does Japiman Server run from?
For Japiman Server, 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. You can reach it at 159.26.107.34:28015.
Rules, settings, map
What rules and settings are recorded for Japiman Server?
You will not find a gather rate in the string Japiman Server. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Carbon plugins run on it. Anti-cheat status: VAC on.
Which map has Japiman Server selected?
A procedural map runs on Japiman Server, generated by the game.
Wipes and dates
When does Japiman Server wipe, and on what schedule?
A rhythm cannot be read from the wipes of Japiman Server 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 8 days 16 hours ago, and that is the one in play.
Tags, lists
Which Rust Data filters and lists contain Japiman Server?
On Rust Data, Japiman Server appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Which meanings do the tags on Japiman Server hold?
The game's server browser reads these tags from Japiman Server: gmvanilla (Game mode): The mode is vanilla survival; mp5 (Max players): Slot count: 5; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): Runs on Carbon for plugins. 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 Japiman Server?
In Rust, F1 opens the console: type client.connect 159.26.107.34:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.