Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO G SRV11,814online PAX72,000playing OCC3,646with players WIPED 3H206
COMCommunity traffic
Callsign

TKO15383

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

Offline 45.140.129.117:11200 checked 8d ago

Clearance · join
Launch Rust and join Website
Players now 0/ 105 0% full
7-day average0peak –
Rank#15,383top 70%
Last wipe27d agono schedule published
Next wipe–no rhythm it keeps
Track history

Players

No hourly history yet.

Hourly average and peak, UTC.

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.

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.

Flight plan

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 gap7.2 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak8players, last three wipes
crowd held0%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.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 19:14 UTC FW27d ago 6 – running 0
Thu 24 Sep, 13:21 UTC35d ago 1 halved by day 2 7.2 days 0
Thu 17 Sep, 10:20 UTC42d ago 18 halved by day 4 7.1 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.

Nearby traffic

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. 01COM
    Callsign RST015EA · groups of 16+ · weekly · 181 on average Rustoria.co - SEA Main
    Players 442/450
  2. 02COM
    Callsign JPN002EA · groups of 16+ · weekly · 119 on average Japan Tokyo - Main|10/23|JP/KR/SEA|金曜日|JumpRust.com
    Players 26/550
  3. 03COM
    Callsign RST015EA · groups of 12+ · monthly · 104 on average Rustoria.co - SEA Long
    Players 77/200
  4. 04COM
    Callsign RST018EA · groups of 16+ · weekly · 83 on average Rustafied.com - SEA Main
    Players 236/450
  5. 05COM
    Callsign RST018EA · no group limit · 65 on average Rustoria.co - SEA Medium | JUST WIPED 29.10
    Players 64/100
  6. 06COM
    Callsign JPN016EA · groups of 8+ · weekly · 53 on average Japan Beginner Server - BPwipe 10/23 [JP/KR/SEA|初心者]
    Players 28/200
ATIS · this server

Quick answers

From the figures on this page.

Filters

Where does [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 appear in Rust Tracker lists and filters?

Beginner Rust servers, tracked live and Community servers, no tags — the Rust Tracker lists that include [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24. It comes up 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.

What do the tags mean that [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 is listed under?

The game's server browser reads these tags from [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24: gmvanilla (Game mode): Game mode: vanilla survival; mp105 (Max players): Capacity: 105 slots; ts8 (Group limit): Team limit is 8, the game default; v2634 (Protocol): Join only if your game is on protocol 2634; cs167781 (Build): This server runs game build 167781; ptrak (Networking): Network layer: RakNet, the game's standard; $r? (Region code): Region code: not set. The tags also hold the current player count, the queue and when the world was made; all appear at the top of this page.

Wipe Times

What should you expect on [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 when wipe day lands?

At their busiest, recent wipes averaged 8 players. The peak on the latest wipe came 39 hours after it. The crowd stayed above half the peak until the next wipe in 0% of recent wipes. By day 3 the crowd dropped below half where it did not hold.

Which wipe times are confirmed for [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24?

Irregular wipe times at [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24: there is no next wipe to predict. Thursday 5 November at 19:00 UTC is the next monthly force wipe. No server is exempt. 27 days 18 hours since this world was made.

Server Details

What is the uptime on [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24, and is it online?

Offline: [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 confirmed offline, last seen 8 days 18 hours ago. Uptime stood at 0% for the last 7 full days, 0 of 168 hours online. The first sighting by Rust Tracker was 13 September 2026.

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

Rust network protocol 2634 and build 167781 on Windows is what [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 runs. To join, your game must be on the same protocol; Steam handles the update.

What location is [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 hosted in?

The name of [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 points to Asia, though no region tag is published. The location shown by Rust Tracker is the server's own claim; no lookup of the machine's position is made. Connect on 45.140.129.117:11200.

Player Count

How many players are on [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 right now?

Last seen 8 days 18 hours ago; [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 is offline at present.

How does [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 compare in the rankings?

Top 70% of all ranked servers, and #15,383 on seven-day player hours: [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24.

Map and Rules

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

No gather rate appears in [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24's name. Up to 8 players per group, the game's default. survival is the game mode, gather, build and raid: the standard game. Raiding and PvP are permitted between players. A community server: the server browser lists it under Community. On: VAC, Valve's anti-cheat.

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

The map on [JP/Tokyo]Beginner Biweekly | Solo/Duo/Trio/Quad | Wipe 9/24 is procedural, size 4,000, seed 2026680033, generated by the game. Size and seed match, so the map is the same: view it on RustMaps from this page.

How to Join

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

To connect: start Rust, press F1, enter client.connect 45.140.129.117:11200 in the console. Or use Launch Rust on this page to open Rust through Steam and join. For the website, go to https://discord.com/invite/CptKMHfmm.

Transponder codes

Server tags

What each one means.

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

Game

gmvanilla
Game mode Game mode: vanilla survival.
mp105
Max players Capacity: 105 slots.
ts8
Group limit Team limit is 8, the game default.
v2634
Protocol Join only if your game is on protocol 2634.
cs167781
Build This server runs game build 167781.
ptrak
Networking Network layer: RakNet, the game's standard.
$r?
Region code Region code: not 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.