RUST METRICSFlight deck · live data
Data live Servers11,696 Players36,352 Populated2,907 Fresh wipes 3 h94 Scan5 min
‹ All servers162.43.17.235:28015
Online Full Queue Fresh wipe Wipe due No query

JP ONLY 2WEEK SOLO/DUO/TORIO#84

Online EA 162.43.17.235:28015 checked 6m ago

biweekly wipes
COM 1 · connect

Server instruments

last reading Thu 01:00 UTC
0 15 30 45 60 PAX 1 /60

Players now

2% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 96 SERVER FPS

Server fps

48 h low 54 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 70,500 ×1000

Entities

48 h range 69,999–73,379 · memory 2,158 MB
1239 ET SINCE RESTART 1D 06H

Uptime

1 days 6 hours since its last restart, at the last reading
7-day average3peak 13
Rank#1,779top 8% · #174 in EA
Last wipe13d agobiweekly schedule
Next wipe7d 16hThu 5 Nov, 19:00 UTC FW
Memory2,158MB48 h peak 9 players
REC 1

Players

AveragePeak
02.557.51003:0012:0021:0006:0015:0001:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020003:0012:0021:0006:0015:0001: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.

REC 3

Rank

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

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

PLAN

Wipe schedule

fixed weekdays

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

usual gap28 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak27players, last three wipes
crowd held0%else halves by day 11

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC7d 16hFW
  2. WPT 2Fri 13 Nov, 01:06 UTC14d 22h
  3. WPT 3Thu 3 Dec, 19:00 UTC35d 16hFW
  4. WPT 4Fri 11 Dec, 01:06 UTC42d 22h

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.

LOG

Wipes

newest first
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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe timing

What should you expect from wipe day on JP ONLY 2WEEK SOLO/DUO/TORIO#84?

An average of 27 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 12 hours in. Above half that peak the crowd stayed until the next wipe in 0% of recent wipes. By day 11 it fell below half when it didn't.

When does JP ONLY 2WEEK SOLO/DUO/TORIO#84 wipe?

The wipe rhythm of JP ONLY 2WEEK SOLO/DUO/TORIO#84 is every 4 weeks on Friday at 01:06 UTC. Force wipe falls on Thursday 5 November at 19:00 UTC. Every Rust server wipes then; yours included. 13 days 1 hours ago the current world was made. A wipe schedule of every two weeks is published in its tags.

Tags

Which tags does JP ONLY 2WEEK SOLO/DUO/TORIO#84 carry, and what do they mean?

These are the tags JP ONLY 2WEEK SOLO/DUO/TORIO#84 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp60 (Max players): Slots: 60; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Game build reading: 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^b (Biweekly): Check: wipe cycle. Every two weeks; EA (East Asia): Its browser listing: East Asia. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does JP ONLY 2WEEK SOLO/DUO/TORIO#84 appear in Rust Metrics lists and filters?

On Rust Metrics, JP ONLY 2WEEK SOLO/DUO/TORIO#84 sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under 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.

Occupancy

What position does JP ONLY 2WEEK SOLO/DUO/TORIO#84 hold among Rust servers?

Player hours over the last seven days put JP ONLY 2WEEK SOLO/DUO/TORIO#84 at #1,779, #174 in Asia, in the top 8% of all ranked servers.

How full does JP ONLY 2WEEK SOLO/DUO/TORIO#84 get?

Current headcount on JP ONLY 2WEEK SOLO/DUO/TORIO#84: 1 players, 60 slots available. Seven-day check: 3 players on average. Peak reading: 13. The last 48 hours peaked at 14:00 UTC, averaging 8 players at that hour.

Server

What location is JP ONLY 2WEEK SOLO/DUO/TORIO#84 hosted in?

Its EA tag places JP ONLY 2WEEK SOLO/DUO/TORIO#84 in Asia. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 162.43.17.235:28015.

What Rust version is JP ONLY 2WEEK SOLO/DUO/TORIO#84 on?

Reading: JP ONLY 2WEEK SOLO/DUO/TORIO#84, Rust network protocol 2635 and build 168909, Linux. To get in, your game needs the same protocol; Steam applies the update.

How does JP ONLY 2WEEK SOLO/DUO/TORIO#84 perform?

Over the last 48 hours the average was 95 server fps; the floor was 54. Reading: 73,379 entities at the highest. That covers buildings, deployables and everything else. Memory peak: 2,666 MB. Lag, as players feel it, is low fps plus a climbing entity count.

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

Check: connection. JP ONLY 2WEEK SOLO/DUO/TORIO#84 is online at this moment. Check: restart. The uptime it reports puts the last restart about 30 hours ago. Uptime for the last 7 full days: 167 of 168 hours, or 99%. The first sighting on Rust Metrics was 13 September 2026.

Settings and map

How is JP ONLY 2WEEK SOLO/DUO/TORIO#84 configured, and what rules are in force?

No gather rate appears in the name: JP ONLY 2WEEK SOLO/DUO/TORIO#84. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.

What map is JP ONLY 2WEEK SOLO/DUO/TORIO#84 on?

Size 3,500 and seed 1976019099: the game generates the procedural map on JP ONLY 2WEEK SOLO/DUO/TORIO#84 from them. The map repeats when size and seed match. Open it on RustMaps from this page.

Connection

How do you connect to JP ONLY 2WEEK SOLO/DUO/TORIO#84?

Press F1 in Rust and enter client.connect 162.43.17.235:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. You can find its website at https://discord.com/invite/BA4t9FYKQa.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp60
Max players Slots: 60.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Game build reading: 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

Wipe schedule

^b
Biweekly Check: wipe cycle. Every two weeks.

Region

EA
East Asia Its browser listing: East Asia.

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.