Rust HeatmapInfrared · players
IR live Players95,534 Servers11,865 Warm3,881 Fresh wipes · 3h381 Frameevery 5 min
‹ All serversThermal scan
REC Thermal scan · 48 h Sp1 1° now Linear · 0–60° · slots

JP ONLY 2WEEK SOLO/DUO/TORIO#84

Offline EA 162.43.17.235:28015 checked 57m ago

biweekly wipes
Sp1 · players now 1/ 60
2% full
Li1 · players, the last 48 hours · hourly average, UTCpeak 5°
Tue 17:00flare: a wipe in that hourThu 14:00
3
7-day average
peak 13
#1,868
rank
top 8% · #178 in EA
13d ago
last wipe
biweekly schedule
7d 2h
next wipe
Thu 5 Nov, 19:00 UTC FW
UTC checked 57m ago

Li2Players

AveragePeak
0246817:0002:0011:0020:0005:0014:00

Hourly average and peak, UTC.

Li3Server performance

05010015020017:0002:0011:0020:0005:0014:00

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.

Li4Rank

daily · 1 is best
RankRank in region
15001k1.5k2k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 8% of all ranked servers, top 33% in EA. Ranked on player hours over the last seven days.

Bx1Wipe schedule

fixed weekdays

Next wipe Thursday 5 November, 19:00 UTC, in 7d 2h. The force wipe · high confidence

28 days
usual gap
between real wipes
100%
on rhythm
of its recent wipes
27
wipe-day peak
players, last three wipes
0%
crowd held
else halves by day 11

Coming wipes

7d 2h
Thu 5 Nov, 19:00 UTC
FW
14d 8h
Fri 13 Nov, 01:06 UTC
35d 2h
Thu 3 Dec, 19:00 UTC
FW
42d 8h
Fri 11 Dec, 01:06 UTC

The first 48 hours of its last wipes

Fri 16 OctThu 1 OctFri 18 Sep
010203040+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 25, 12 hours in.

Bx2Wipes

newest first · each peak a flare-up, on one √ span to its biggest
WipedPeakCrowdLastedPlayers before
Fri 16 Oct, 01:06 UTC13d ago 25 – running 1
Thu 1 Oct, 22:34 UTC FW27d ago 25 halved by day 12 14.1 days 8
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.

Bx6Similar servers

the same kind of game, then region, group limit, rate and wipes
Rustoria.co - SEA Medium
EA · groups of 16+ · biweekly · 72 on average
340 / 400
Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com
EA · groups of 8+ · biweekly · 37 on average
22 / 215
Rustafied.com - SEA Medium
EA · groups of 16+ · biweekly · 28 on average
113 / 250
[SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla
EA · groups of 8+ · biweekly · 4 on average
15 / 200
[SEA] BRUNEI/MALAYSIA/INDONESIA | Rust Battleground | Biweekly
EA · groups of 8+ · biweekly · 2 on average
9 / 100
新手村 | Rookie Village | 四人 | 1x PVP 10.26新开
EA · groups of 8+ · 1x · biweekly · 1 on average
1 / 500

LogQuick answers

from the figures on this page

Wipe schedule

What does wipe day look like on JP ONLY 2WEEK SOLO/DUO/TORIO#84?

At their busiest, its recent wipes averaged 27 players. 12 hours into the latest wipe, player numbers topped out. Half the peak was held until the next wipe in 0% of its recent wipes. It fell below half by day 11 when it did not hold.

What is the wipe schedule on JP ONLY 2WEEK SOLO/DUO/TORIO#84?

Wipes on JP ONLY 2WEEK SOLO/DUO/TORIO#84 follow this rhythm: 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, when all Rust servers wipe. 13 days 15 hours ago the server made the world it is on now. The tags declare one wipe every two weeks.

Population

How busy is JP ONLY 2WEEK SOLO/DUO/TORIO#84?

Last seen 57 minutes ago, JP ONLY 2WEEK SOLO/DUO/TORIO#84 is offline at the moment. Averaged over the past week: 3 players, peaking at 13. Look at 06:00 UTC for the last 48 hours: that hour averaged 5 players.

How does JP ONLY 2WEEK SOLO/DUO/TORIO#84 rank against other Rust servers?

Seven-day player hours place JP ONLY 2WEEK SOLO/DUO/TORIO#84 at #1,868, in the top 8% of ranked servers; within Asia it is #178.

Rules and settings

Which map does JP ONLY 2WEEK SOLO/DUO/TORIO#84 run?

The map on JP ONLY 2WEEK SOLO/DUO/TORIO#84 is procedural, size 3,500 with seed 1976019099, generated by the game. The map is the same for a given size and seed, so RustMaps can show it from this page.

What are the rules and settings on JP ONLY 2WEEK SOLO/DUO/TORIO#84?

No gather rate appears in the name JP ONLY 2WEEK SOLO/DUO/TORIO#84. 8 players is the default group size, and that is the limit here. The server runs survival, standard play: gathering, building and raiding. Players can fight each other, and raids are allowed. You will find it under Community in the server browser; it is a community server. The server has VAC, Valve's anti-cheat, turned on.

Location and uptime

Which version of Rust does JP ONLY 2WEEK SOLO/DUO/TORIO#84 run?

The build on JP ONLY 2WEEK SOLO/DUO/TORIO#84 is Rust network protocol 2635 and build 168909, running on Linux. Steam updates your game for you, and the protocol has to match for you to join.

Is JP ONLY 2WEEK SOLO/DUO/TORIO#84 online, and how reliable is it?

Last seen 57 minutes ago, JP ONLY 2WEEK SOLO/DUO/TORIO#84 is offline right now. Its reported uptime dates the last restart to about 42 hours ago. It was up 167 of 168 hours across the last 7 full days, or 99% of the time. It first appears in Rust Heatmap records on 13 September 2026.

Where is JP ONLY 2WEEK SOLO/DUO/TORIO#84 located?

With its EA tag, JP ONLY 2WEEK SOLO/DUO/TORIO#84 lists itself in Asia. What Rust Heatmap shows is where a server says it is. Where the machine stands is not looked up. 162.43.17.235:28015 is its address.

Does JP ONLY 2WEEK SOLO/DUO/TORIO#84 run smoothly?

Average server fps over the last 48 hours was 97; it never dropped below 54. Entities peaked at 73,227, counting buildings, deployables and all the rest of the world. At its peak it held 2,769 MB of memory. Lag, as players experience it, comes from low fps and a rising entity count.

Lists and filters

Which Rust Heatmap lists and filters include JP ONLY 2WEEK SOLO/DUO/TORIO#84?

Best Rust community servers are the Rust Heatmap lists that JP ONLY 2WEEK SOLO/DUO/TORIO#84 fits. Filtering the list by 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 brings it up.

What do the server tags on JP ONLY 2WEEK SOLO/DUO/TORIO#84 mean?

gmrust (Game mode): Rust survival, standard rules; mp60 (Max players): Slot count: 60; ts8 (Group limit): Teams cap at 8, which is the game default; v2635 (Protocol): The server runs game protocol 2635, so your game has to match it; cs168909 (Build): Build 168909; ptrak (Networking): The network layer is RakNet, the game's standard one; $r? (Region code): No region code is set; ^b (Biweekly): It wipes on a two-week cycle; EA (East Asia): East Asia is where the server browser puts it are the tags JP ONLY 2WEEK SOLO/DUO/TORIO#84 publishes, and the server browser reads them. The top of this page also shows the tags for players now, the queue and when the world was made.

How to join

How do I join JP ONLY 2WEEK SOLO/DUO/TORIO#84?

Press F1 in Rust to open the console, then enter client.connect 162.43.17.235:28015. Alternatively, join from this page with Launch Rust: it opens Rust through Steam and connects you. The server's site sits at https://discord.com/invite/BA4t9FYKQa.

KeyServer tags

what each one means

Published as mp60,ptrak,$r?,v2635,^b,EA,gmrust,cs168909,ts8

Game

gmrust
Game mode Rust survival, standard rules.
mp60
Max players Slot count: 60.
ts8
Group limit Teams cap at 8, which is the game default.
v2635
Protocol The server runs game protocol 2635, so your game has to match it.
cs168909
Build Build 168909.
ptrak
Networking The network layer is RakNet, the game's standard one.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly It wipes on a two-week cycle.

Region

EA
East Asia East Asia is where the server browser puts it.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.