RUST ZERG LIFEClan war room · live
No limit8 · game default
Deployment dossierOnline

JP ONLY 2WEEK SOLO/DUO/TORIO#83

EA 162.43.17.235:28015 checked 8m ago

biweekly wipes
Deploy
Zerg meter3%light
2/60 troops
7-day average9
peak 32
Rank#1,140
top 5% · #119 in EA
Last wipe12d ago
biweekly schedule
Next wipe · H-hour1d 12h
Thu 15 Oct, 22:34 UTC

Players

AveragePeak
0510152011:0020:0005:0015:0000:0009:00

Hourly average and peak, UTC.

Server performance

05010015020011:0020:0005:0015:0000:0009: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.

Rank

daily · 1 is best
RankRank in region
15001k1.5k2k20 Sep25 Sep30 Sep4 Oct9 Oct14 Oct

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

Wipe schedule

from its schedule tag

Next wipe Thursday 15 October, 22:34 UTC, in 1d 12h. Its biweekly schedule tag · low confidence

usual gap13.8 days
between real wipes
wipe-day peak28
players, last three wipes
crowd held0%
else halves by day 10

Coming wipes

1d 12hThu 15 Oct, 22:34 UTC
15d 12hThu 29 Oct, 22:34 UTC
22d 8hThu 5 Nov, 19:00 UTCFW
29d 12hThu 12 Nov, 22:34 UTC
43d 12hThu 26 Nov, 22:34 UTC

The first 48 hours of its last wipes

Thu 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, 39 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 22:34 UTC FW12d ago 25 – running 8
Fri 18 Sep, 02:26 UTC26d 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
Zergmax 16
Rustoria.co - SEA Medium EA · groups of 16+ · biweekly · 51 on average
38/200
No limit8 · game default
Japan Tokyo - Mondays|10/05|JP/KR/SEA|2週間|JumpRust.com EA · groups of 8+ · biweekly · 35 on average
16/215
Zergmax 16
Rustafied.com - SEA Medium EA · groups of 16+ · biweekly · 27 on average
14/100
No limit8 · game default
[SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla EA · groups of 8+ · biweekly · 9 on average
10/200
No limit8 · game default
[SEA] BRUNEI/MALAYSIA/INDONESIA | Rust Battleground | Biweekly EA · groups of 8+ · biweekly · 3 on average
1/100
Teams offteams disabled
[JP/ASIA] TOTO | SOLO ONLY | 2 WEEK WIPE EA · no group limit · biweekly · 3 on average
0/100

Quick answers

from the figures on this page

Map and rules

What settings does JP ONLY 2WEEK SOLO/DUO/TORIO#83 run?

There is no gather rate in the name JP ONLY 2WEEK SOLO/DUO/TORIO#83. Up to 8 players can group, which is the game's default. survival is its mode, gather, build, raid: the regular game. You can fight and raid other players here. You will find it under Community in the server browser. Anti-cheat is on: VAC, from Valve.

Which map is active on JP ONLY 2WEEK SOLO/DUO/TORIO#83?

The game generates the procedural map of size 3,500 on JP ONLY 2WEEK SOLO/DUO/TORIO#83 with seed 1370883674. From this page, RustMaps can show it: size and seed produce the same map each time.

Server population

How many players are on JP ONLY 2WEEK SOLO/DUO/TORIO#83?

JP ONLY 2WEEK SOLO/DUO/TORIO#83 has 2 of its 60 slots filled right now. Averaging 9 players over seven days, it peaked at 32. The highest average over the last 48 hours came at 13:00 UTC, with 13 players.

What is JP ONLY 2WEEK SOLO/DUO/TORIO#83's ranking?

With a global rank of #1,140 for player hours over the last week, JP ONLY 2WEEK SOLO/DUO/TORIO#83 is #119 in Asia and in the top 5% of ranked servers.

Lists and tags

How should you read the tags on JP ONLY 2WEEK SOLO/DUO/TORIO#83?

For the game's server browser, JP ONLY 2WEEK SOLO/DUO/TORIO#83 publishes these tags: gmrust (Game mode): Survival in the standard Rust mode; mp60 (Max players): It holds 60 players; ts8 (Group limit): The team cap is 8, which is the game's default; v2634 (Protocol): Protocol 2634—only players on that version can get in; cs167781 (Build): It runs build 167781; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): There's no region code here; ^b (Biweekly): The server wipes on a two-week cycle; EA (East Asia): The server browser puts it in East Asia. Also in the tags: its players now, its queue and the time its world was made, and the top of this page shows them.

Where does JP ONLY 2WEEK SOLO/DUO/TORIO#83 appear in Rust Zerg Life lists?

Rust community servers for clans: that is where you will find JP ONLY 2WEEK SOLO/DUO/TORIO#83 among the Rust Zerg Life rankings. 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.

Server details

Is JP ONLY 2WEEK SOLO/DUO/TORIO#83 currently online and stable?

JP ONLY 2WEEK SOLO/DUO/TORIO#83 is up and running as you read this. Based on the uptime it reports, the last restart was about 15 hours ago. It was up 100% of the time across the last 7 full days: 168 of 168 hours. The first time Rust Zerg Life saw it was on 13 September 2026.

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

Over the past 48 hours, server fps averaged 104 and never dropped below 70. The world held as many as 98,470 entities, including buildings, deployables and everything else. Memory use peaked at 2,677 MB. Lag, as players feel it, is caused by low fps and an increasing number of entities.

Which Rust build does JP ONLY 2WEEK SOLO/DUO/TORIO#83 use?

On Linux, JP ONLY 2WEEK SOLO/DUO/TORIO#83 runs Rust network protocol 2634 and build 167781. Joining requires your game to be on the same protocol, which Steam updates automatically.

What location does JP ONLY 2WEEK SOLO/DUO/TORIO#83 use?

The EA tag is what JP ONLY 2WEEK SOLO/DUO/TORIO#83 uses to list itself in Asia. Rust Zerg Life displays the location a server claims, not where the machine actually stands. Connect to it at 162.43.17.235:28015.

Wipe cycle

What can you expect on wipe day on JP ONLY 2WEEK SOLO/DUO/TORIO#83?

At their busiest, its recent wipes drew an average of 28 players. On the latest wipe, 39 hours after the wipe, the crowd hit its peak. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. Otherwise, it slipped below half by day 10.

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

The prediction follows its tag because not enough of JP ONLY 2WEEK SOLO/DUO/TORIO#83's wipes are on record to confirm the schedule. On Thursday 15 October at 22:34 UTC its next wipe is expected. The world it is running now dates from 12 days 11 hours ago. Its tags show a wipe schedule of every two weeks.

Join the server

How can I connect to JP ONLY 2WEEK SOLO/DUO/TORIO#83?

You can join by opening the console with F1 and typing client.connect 162.43.17.235:28015. Or hit Launch Rust on this page to open Rust through Steam and connect. For more, visit its website: https://discord.com/invite/BA4t9FYKQa.

Server tags

what each one means

Published as mp60,ptrak,$r?,v2634,^b,EA,gmrust,cs167781,ts8

Game

gmrust
Game mode Survival in the standard Rust mode.
mp60
Max players It holds 60 players.
ts8
Group limit The team cap is 8, which is the game's default.
v2634
Protocol Protocol 2634—only players on that version can get in.
cs167781
Build It runs build 167781.
ptrak
Networking It uses RakNet, the standard network layer for the game.
$r?
Region code There's no region code here.

Wipe schedule

^b
Biweekly The server wipes on a two-week cycle.

Region

EA
East Asia The server browser puts it in 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.