Rust Server TrendsSeismic network · station log
Recording Stations11,611 Players36,787 Active2,913 Wipes · 3 h75 48 h

Station XX-15383 · no signal

[JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24

Offline 45.140.129.117:11200 checked 8d ago

Connect
Players now
0/ 105
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,383
top 70%
Last wipe
27d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-15383 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 105 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

Top 70% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap
7.2 daysbetween real wipes
on rhythm
100%of its recent wipes
wipe-day peak
8players, last three wipes
crowd held
0%else halves by day 3

The first 48 hours of its last wipes

Thu 1 OctThu 24 SepThu 17 Sep
05101520+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 6, 39 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Thu 1 Oct, 19:14 UTC FW27d ago M0.8rising 6 – running 0
Thu 24 Sep, 13:21 UTC34d ago M0.0rising 1 halved by day 2 7.2 days 0
Thu 17 Sep, 10:20 UTC41d ago M1.2rising 18 halved by day 4 7.1 days 1

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Rustoria.co - SEA Main EA · groups of 16+ · weekly · 183 on average
0/ 200
Japan Tokyo - Main|10/23|JP/KR/SEA|金曜日|JumpRust.com EA · groups of 16+ · weekly · 119 on average
12/ 550
Rustoria.co - SEA Long EA · groups of 12+ · monthly · 106 on average
74/ 200
Rustafied.com - SEA Main EA · groups of 16+ · weekly · 88 on average
0/ 100
Rustoria.co - SEA Medium | JUST WIPED 29.10 EA · no group limit · 65 on average
77/ 100
Japan Beginner Server - BPwipe 10/23 [JP/KR/SEA|初心者] EA · groups of 8+ · weekly · 53 on average
10/ 200
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24?

Generated by the game, the map on [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 is procedural, size 4,000 with seed 2026680033. Size and seed produce the same map, so RustMaps can show it from this page.

Which settings and rules apply on [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24?

The name of [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 gives no gather rate. At the game's default, groups can have up to 8 players. survival is the game mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Under Community in the server browser, it runs as a community server. VAC, Valve's anti-cheat, is switched on.

Population

What is the current population on [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24?

[JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 is not responding at this moment and is offline, last seen 8 days 12 hours ago.

How does [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 rank against other Rust servers?

The last seven days of player hours place [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 at #15,383, in the top 70% of all ranked servers.

Server details

How reliably does [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 stay online?

No contact with [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 right now, and the last recorded contact was 8 days 12 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 13 September 2026 it was recorded for the first time by Rust Server Trends.

Which region does [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 run from?

No region tag comes from [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24, though the name points to Asia. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 45.140.129.117:11200 is the address it uses.

Which Rust version is [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 running?

On Windows, [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 runs Rust network protocol 2634 and build 167781. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe schedule

What does wipe day look like on [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24?

The recent wipes averaged a busiest count of 8 players. 39 hours into the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. It fell under half by day 3 in the wipes where it didn't hold.

On what timetable does [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 run its wipes?

There is no next wipe to predict at [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24, since its wipes fall at irregular times. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 27 days 11 hours.

Server tags

What do the server tags on [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 mean?

The game's server browser reads the tags [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 publishes: gmvanilla (Game mode): Survival in vanilla mode; mp105 (Max players): The server has 105 slots; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 appear?

These Rust Server Trends lists include [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24: Beginner Rust servers: live trends and Rust community servers without the side modes. You will find it under these filters on the server list: Region: Asia; Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Join the server

How do you connect to [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24?

You can connect by pressing F1 in Rust and typing client.connect 45.140.129.117:11200 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you. https://discord.com/invite/CptKMHfmm is where its website lives.

Instrument codes

Server tags

what each one means

Published as mp105,ptrak,$r?,v2634,gmvanilla,cs167781,ts8

Game

gmvanilla
Game mode Survival in vanilla mode.
mp105
Max players The server has 105 slots.
ts8
Group limit Teams max out at 8, the default set by the game.
v2634
Protocol To connect, your game must be on the same protocol, 2634.
cs167781
Build The game build is 167781.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code A region code has not been set.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.