Rust Data

rustdata.spaceservers162.43.16.74:29015.ipynb

Run all rust-data · live

‹ All servers

Online EA 162.43.16.74:28015 checked 9m ago

[JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け

quad biweekly wipes vanilla

Connect

srv = rust.server("162.43.16.74:29015")
print(srv.connect_command)

Right now

srv.summary()
players now 3/100 # 3% full
7-day average 2 # peak 6
rank #2,483 # top 11% · #251 in EA
last wipe 12d ago # biweekly schedule
next wipe 1d 21h # Fri 30 Oct, 08:51 UTC

Players

srv.players.plot(range="48h")
AveragePeak
0123412:0021:0006:0015:0000:0009:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
010020030040012:0021:0006: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 2 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
12.5k5k7.5k10k2 Oct7 Oct12 Oct18 Oct23 Oct28 Oct

Top 11% of all ranked servers, top 45% in EA, and #143 of the quad servers (top 17%). Ranked on player hours over the last seven days.

Wipe schedule · from its schedule tag

srv.wipe_schedule()

Next wipe Friday 30 October, 08:51 UTC, in 1d 21h. # Its biweekly schedule tag · low confidence

wipe-day peak2players, last three wipes

Coming wipes

inatkind
01d 21hFri 30 Oct, 08:51 UTCwipe
18d 7hThu 5 Nov, 19:00 UTCFW force wipe
215d 21hFri 13 Nov, 08:51 UTCwipe
329d 21hFri 27 Nov, 08:51 UTCwipe
436d 7hThu 3 Dec, 19:00 UTCFW force wipe
543d 21hFri 11 Dec, 08:51 UTCwipe

The first 48 hours of its last wipes

00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 2, 5 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 16 Oct, 08:51 UTC12d ago 2 NaN running 0

# 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.

display(srv.map, srv.info())

Map

3500 · seed 1029781210
Map of [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け
map
Procedural Map
size
3500
seed
1029781210
Open on RustMaps

Server

srv.info()
address
162.43.16.74:28015
region
EA
max players
100
group limit
quad
wipe schedule
biweekly
last wipe
16 Oct 2026, 08:51 UTC
hostname
–
first seen
2 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0[RU] SAHAMUREA · quad · biweekly · 3 on average6/100
1『小宇宙』10.27号/新开/四人服/萌新服EA · quad · weekly · 21 on average4/200
2『次空间』10.28号/14:00新开/四人服/萌新服EA · quad · weekly · 20 on average98/200
3小虎鲸10.25号|14点新档|四人游玩EA · quad · weekly · 13 on average0/200
4TheCove.GG|无权|新手村|四人|10.28号16:00清档EA · quad · weekly · 4 on average4/100
5【拾破烂】10.16新开丨4人队丨萌新养老原生态EA · quad · monthly · 4 on average6/100

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け rank?

Player hours over the last seven days: #2,483 for [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け, #251 in Asia, within the top 11% of the ranked set. The quad group places it at #143.

What population does [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け carry?

Current row: 3 players on [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け, against 100 slots. Over the last seven days it averaged 2 players and peaked at 6. The 48-hour sample puts the busiest hour at 17:00 UTC, averaging 3 players.

About the server

How smoothly does [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け run?

Server fps over the last 48 hours averages 147; the floor is 96. Entity numbers reached 58,066, and that includes buildings, deployables and the rest. The memory field tops out at 3,264 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

What Rust version does [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け run?

The build is Rust network protocol 2635 and build 168909 on Linux, run by [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け. The protocol has to match before you can join, and Steam does the updating.

How reliable is [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け, and is it up?

[JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け reports itself online at the current refresh. The uptime it reports puts the last restart about 18 hours ago. Over the last 7 full days the hours up number 168 of 168, 100%. The first row Rust Data holds for it is dated 2 October 2026.

Which location does [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け run from?

The EA tag is what [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け uses to list itself in Asia. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 162.43.16.74:28015.

Rules, settings, map

Which settings and rules does [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け run?

You will not find a gather rate in the string [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け. Up to 4 players may share a group (quad). survival is the game mode here, and the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Community is its browser category. Its own label is vanilla: no changed rates, kits or rules: the game as Facepunch ships it. VAC, Valve's anti-cheat, is enabled.

Which map has [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け loaded?

The game generates the map on [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け: procedural, size 3,500, seed 1029781210. Size and seed fix the map, so RustMaps can show it, linked from this page.

Wipe schedule

When does [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け wipe, and how often?

The prediction follows the tag, because [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け's wipes on record are too few to confirm the schedule. Friday 30 October at 08:51 UTC is when the next wipe is due. This world was created 12 days 2 hours ago. Its tags carry a wipe schedule of every two weeks.

What is wipe day on [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け like?

The average peak over recent wipes is 2 players. The crowd on the latest wipe topped out 5 hours after it began.

Lists and tags

Where does [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け appear among Rust Data lists and filters?

On Rust Data, [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け appears in these lists: Rust community servers, unfiltered and Vanilla Rust servers. Under these filters on the server list, it is listed: Region: Asia; Type: Vanilla, Community (not modded, not official) and No plugins at all; Server tag: Biweekly ^b and Vanilla ^v; Group limit: Quad; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.

Which meanings do the tags on [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け hold?

Read by the game's server browser, the tags [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け publishes are: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): 100 slots in total; ts4 (Group limit): No team may exceed 4; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^b (Biweekly): Wipes run on a two-week cycle; ^v (Vanilla): No changed rates, kits or rules: the game as Facepunch ships it; EA (East Asia): The server browser files it under East Asia. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

How to join

How can I connect to [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け?

The manual route: launch Rust, F1, then client.connect 162.43.16.74:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you. You will find its website at https://discord.com/invite/n4cemh8hm5.

Server tags · what each one means

srv.tags.decode()

Published as mp100,ptrak,$r?,v2635,^b,^v,EA,gmrust,cs168909,ts4

Game

gmrust
Game mode Survival play, standard Rust.
mp100
Max players 100 slots in total.
ts4
Group limit No team may exceed 4.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Recorded game build: 168909.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly Wipes run on a two-week cycle.

Difficulty

^v
Vanilla No changed rates, kits or rules: the game as Facepunch ships it.

Region

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

Rust Data 60,760 players 11,689 servers online