Online EA 162.222.17.244:27777 checked 11m ago
Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com
Connect
srv = rust.server("162.222.17.244:27778")
print(srv.connect_command)Right now
srv.summary()display(Image(srv.banner))
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 22 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 2% of all ranked servers, top 2% in EA. Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()Next wipe Monday 2 November, 08:41 UTC, in 3d 13h. # Its biweekly schedule tag · low confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 3d 13h | Mon 2 Nov, 08:41 UTC | wipe |
| 1 | 6d 23h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 2 | 17d 13h | Mon 16 Nov, 08:41 UTC | wipe |
| 3 | 31d 13h | Mon 30 Nov, 08:41 UTC | wipe |
| 4 | 34d 23h | 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 214, 4 hours in, with 96 in the queue.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 19 Oct, 08:41 UTC10d ago | 214+96 queue | NaN | running | 15 |
| 1 | Mon 5 Oct, 05:58 UTC24d ago | 212+121 queue | halved by day 4 | 14.1 days | 1 |
| 2 | Sat 3 Oct, 08:52 UTC26d ago | 1+4 queue | NaN | 1.9 days | 0 |
| 3 | Thu 1 Oct, 17:42 UTC FW28d ago | 1 | NaN | 1.6 days | 6 |
| 4 | Mon 21 Sep, 08:34 UTC38d ago | 218+155 queue | halved by day 4 | 10.4 days | 33 |
# 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
4000 · seed 1337
- map
- ✿ JumpRust.com日本™ FPS+
- size
- 4000
- seed
- 1337
Server
srv.info()- address
- 162.222.17.244:27777
- region
- EA
- max players
- 215
- group limit
- 8, the default
- wipe schedule
- biweekly
- last wipe
- 19 Oct 2026, 08:41 UTC
- hostname
- jpmonday.jumprust.com
- first seen
- 13 Sep 2026
Operator · jumprust.com
rust.servers(operator="jumprust.com").sort_values("players")16 servers publish a jumprust.com hostname; the busiest are listed.
About this server · in its own words
print(srv.description)Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | Rustoria.co - SEA Medium | EA · groups of 16+ · biweekly · 75 on average | 227/250 |
| 1 | Rustafied.com - SEA Medium | EA · groups of 16+ · biweekly · 29 on average | 93/250 |
| 2 | [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla | EA · groups of 8+ · biweekly · 4 on average | 17/200 |
| 3 | [SEA] BRUNEI/MALAYSIA/INDONESIA | Rust Battleground | Biweekly | EA · groups of 8+ · biweekly · 2 on average | 5/100 |
| 4 | 新手村 | Rookie Village | 四人 | 1x PVP 10.26新开 | EA · groups of 8+ · 1x · biweekly · 1 on average | 0/500 |
| 5 | ［JP］初心者PVPサーバー｜RaidTime・ Events | EA · groups of 10+ · biweekly · 15 on average | 1/100 |
Quick answers
From the figures on this page.
Player counts
How does Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com compare in the rankings?
Player hours over the last seven days: #480 for Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com, #11 in Asia, within the top 2% of the ranked set.
How many players does Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com hold at once?
The sample now reads 13 players for Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com, out of 215 slots. Over the last seven days it averaged 36 players and peaked at 101. Peak hour in the last 48 hours: 14:00 UTC, mean 53 players.
Server data
How smoothly does Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com run?
The 48-hour average is 45 server fps, with a low of 44. The entity count peaked at 227,693, covering buildings, deployables and the rest of the world. A high of 5,671 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.
Which Rust version is Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com on?
Rust network protocol 2635 and build 168909 on Windows is what Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com, and is it online now?
The current sample puts Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com online. Count back 14 hours from its reported uptime to get the last restart. 167 of 168 hours up over the last 7 full days, or 99%. Rust Data logged it first on 13 September 2026.
Where does Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com sit?
The EA tag is what Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com uses to list itself in Asia. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 162.222.17.244:27777 is its address.
Rules, settings, map
What rules and settings are recorded for Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com?
No gather rate appears in the name: Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and gather, build, raid: the standard loop. Combat and raiding between players: both allowed. The server browser lists it under Community. Plugins installed: Oxide. Its own label is vanilla: no changed rates, kits or rules: the game as Facepunch ships it. VAC, Valve's anti-cheat, is enabled.
Which map has Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com loaded?
Size 4,000, seed 1337: the procedural map on Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page. Under map name you will find: ✿ JumpRust.com日本™ FPS+.
Wipe data
When does Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com wipe, and how often?
The prediction follows the tag, because Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com's wipes on record are too few to confirm the schedule. On Monday 2 November at 08:41 UTC the next wipe is due. A new world was started 10 days 10 hours ago, and that is the one in play. Its tags carry a wipe schedule of every two weeks.
On Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com, what happens on wipe day?
The average peak over recent wipes is 142 players. On the latest wipe the peak came 4 hours after the wipe, with a queue of 96. Half the peak or more was held to the next wipe in 0% of recent wipes. In the wipes where it did not hold, half was lost by day 4.
Tags and filters
Which Rust Data filters and lists contain Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com?
On Rust Data, Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com appears in these lists: Rust community servers, unfiltered and Vanilla Rust servers. These filters bring it up on the server list: Region: Asia; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Server tag: Biweekly ^b, Vanilla ^v and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks; Players now: At least 10; Average players: 25+ on average.
Who is behind Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com?
A jumprust.com hostname is published by Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com and by 15 other servers we track, which suggests the same operator runs them.
Which meanings do the tags on Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com hold?
Read by the game's server browser, the tags Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com publishes are: gmrust (Game mode): Survival play, standard Rust; mp215 (Max players): The server lists 215 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): The server runs build 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^b (Biweekly): Two weeks between wipes; ^v (Vanilla): No changed rates, kits or rules: the game as Facepunch ships it; ^o (Oxide): Plugin framework: Oxide (uMod); EA (East Asia): East Asia is its listing in the server browser. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way to join Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com?
In Rust, F1 opens the console: type client.connect 162.222.17.244:27777. Launch Rust on this page does the same by opening the game through Steam and connecting. You will find its website at https://jumprust.com/.