Online EA 162.43.17.235:28015 checked 13m ago
JP ONLY 2WEEK SOLO/DUO/TORIO#84
Connect
srv = rust.server("162.43.17.235:29015")
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 8% of all ranked servers, top 31% in EA. Ranked on player hours over the last seven days.
Wipe schedule · fixed weekdays
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 9h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 9h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 14d 15h | Fri 13 Nov, 01:06 UTC | wipe |
| 2 | 35d 9h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 3 | 42d 15h | Fri 11 Dec, 01:06 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 25, 12 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 16 Oct, 01:06 UTC13d ago | 25 | NaN | running | 1 |
| 1 | Thu 1 Oct, 22:34 UTC FW27d ago | 25 | halved by day 12 | 14.1 days | 8 |
| 2 | Fri 18 Sep, 02:26 UTC41d ago | 31 | halved by day 10 | 13.8 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
3500 · seed 1976019099
- map
- Procedural Map
- size
- 3500
- seed
- 1976019099
Server
srv.info()- address
- 162.43.17.235:28015
- region
- EA
- max players
- 60
- group limit
- 8, the default
- wipe schedule
- biweekly
- last wipe
- 16 Oct 2026, 01:06 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 | Rustoria.co - SEA Medium | EA · groups of 16+ · biweekly · 64 on average | 301/325 |
| 1 | Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com | EA · groups of 8+ · biweekly · 40 on average | 16/215 |
| 2 | Rustafied.com - SEA Medium | EA · groups of 16+ · biweekly · 26 on average | 52/250 |
| 3 | [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla | EA · groups of 8+ · biweekly · 4 on average | 10/200 |
| 4 | [SEA] BRUNEI/MALAYSIA/INDONESIA | Rust Battleground | Biweekly | EA · groups of 8+ · biweekly · 2 on average | 1/100 |
| 5 | 新手村 | Rookie Village | 四人 | 1x PVP 10.26新开 | EA · groups of 8+ · 1x · biweekly · 1 on average | 0/500 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does JP ONLY 2WEEK SOLO/DUO/TORIO#84 rank?
On seven-day player hours JP ONLY 2WEEK SOLO/DUO/TORIO#84 is #1,792 overall and #175 in Asia, inside the top 8% of all ranked servers.
How many players does JP ONLY 2WEEK SOLO/DUO/TORIO#84 hold at once?
The sample now reads 0 players for JP ONLY 2WEEK SOLO/DUO/TORIO#84, out of 60 slots. Over the last seven days it averaged 3 players and peaked at 13. The 48-hour sample puts the busiest hour at 14:00 UTC, averaging 8 players.
Server facts
How smoothly does JP ONLY 2WEEK SOLO/DUO/TORIO#84 run?
Averaged over 48 hours: 95 server fps, never under 54. The entity count peaked at 73,379, covering buildings, deployables and the rest of the world. A high of 2,666 MB of memory used. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
What Rust version does JP ONLY 2WEEK SOLO/DUO/TORIO#84 run?
The build is Rust network protocol 2635 and build 168909 on Linux, run by JP ONLY 2WEEK SOLO/DUO/TORIO#84. The protocol has to match before you can join, and Steam does the updating.
How reliable is JP ONLY 2WEEK SOLO/DUO/TORIO#84, and is it online now?
Online is the state at the latest refresh for JP ONLY 2WEEK SOLO/DUO/TORIO#84. A restart about 37 hours ago is what its reported uptime implies. Uptime of 99% across the last 7 full days: 167 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.
Which location does JP ONLY 2WEEK SOLO/DUO/TORIO#84 run from?
The EA tag is what JP ONLY 2WEEK SOLO/DUO/TORIO#84 uses to list itself in Asia. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 162.43.17.235:28015.
Settings and map
What rules and settings are recorded for JP ONLY 2WEEK SOLO/DUO/TORIO#84?
You will not find a gather rate in the string JP ONLY 2WEEK SOLO/DUO/TORIO#84. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the base game, where you gather, build and raid. Fighting and raiding between players are allowed. It is a community server, and the browser files it under Community. Anti-cheat status: VAC on.
What is the map on JP ONLY 2WEEK SOLO/DUO/TORIO#84?
Size 3,500, seed 1976019099: the procedural map on JP ONLY 2WEEK SOLO/DUO/TORIO#84, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe schedule
When does JP ONLY 2WEEK SOLO/DUO/TORIO#84 wipe, and on what schedule?
Wipes on JP ONLY 2WEEK SOLO/DUO/TORIO#84 run every 4 weeks on Friday at 01:06 UTC. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. This world was created 13 days 8 hours ago. Its tags carry a wipe schedule of every two weeks.
On JP ONLY 2WEEK SOLO/DUO/TORIO#84, what happens on wipe day?
The average peak over recent wipes is 27 players. Peak population on the latest wipe came 12 hours in. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. In the wipes where it did not hold, half was lost by day 11.
Tags, lists
Which Rust Data filters and lists contain JP ONLY 2WEEK SOLO/DUO/TORIO#84?
On Rust Data, JP ONLY 2WEEK SOLO/DUO/TORIO#84 appears in these lists: Rust community servers, unfiltered. These filters bring it up on the server list: Region: Asia; Type: Community (not modded, not official) and No plugins at all; Server tag: Biweekly ^b; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.
How should you read the server tags on JP ONLY 2WEEK SOLO/DUO/TORIO#84?
The game's server browser reads these tags from JP ONLY 2WEEK SOLO/DUO/TORIO#84: gmrust (Game mode): Rust survival in its standard form; mp60 (Max players): 60 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): The server runs build 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^b (Biweekly): Wipes run on a two-week cycle; EA (East Asia): East Asia is its listing in the server browser. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
How can I connect to JP ONLY 2WEEK SOLO/DUO/TORIO#84?
Enter client.connect 162.43.17.235:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. https://discord.com/invite/BA4t9FYKQa is the website recorded for it.