Rust Data

rustdata.spaceservers157.85.88.137:29440.ipynb

Run all rust-data · live

‹ All servers

Online EA 157.85.88.137:29439 checked 12m ago

JP ともすけサーバー  5x Raidable Bases | Bosses

5x monthly wipes moddedoxidepve

Connect

srv = rust.server("157.85.88.137:29440")
print(srv.connect_command)

Right now

srv.summary()
players now 1/20 # 5% full
7-day average 3 # peak 10
rank #1,825 # top 8% · #175 in EA
last wipe 23d ago # monthly schedule
next wipe 6d 20h # Thu 5 Nov, 19:00 UTC FW
display(Image(srv.banner))

Players

srv.players.plot(range="48h")
AveragePeak
02.557.51023:0008:0017:0003:0012:0021:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
010020030040023:0008:0017:0003:0012:0021: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 23 Sep. 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.5k10k23 Sep30 Sep7 Oct15 Oct22 Oct29 Oct

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

Wipe schedule · force wipes only

srv.wipe_schedule()

Next wipe Thursday 5 November, 19:00 UTC, in 6d 20h. # The force wipe · high confidence

usual gap1.6 daysbetween real wipes
on rhythm20%of its recent wipes
wipe-day peak3players, last three wipes
crowd held100%of its cycles kept half the crowd

Coming wipes

inatkind
06d 20hThu 5 Nov, 19:00 UTCFW force wipe
134d 20hThu 3 Dec, 19:00 UTCFW force wipe

The first 48 hours of its last wipes

Tue 6 OctFri 2 OctSun 27 Sep
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 3, 9 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Tue 6 Oct, 01:40 UTC23d ago 3 NaN running 0
1 Fri 2 Oct, 09:12 UTC27d ago 3 held half 3.7 days 0
2 Sun 27 Sep, 11:14 UTC32d ago 2 held half 4.9 days 1
3 Sat 26 Sep, 03:01 UTC33d ago 1 NaN 1.3 days 1
4 Thu 24 Sep, 11:55 UTC35d ago 1 NaN 1.6 days 1
5 Wed 23 Sep, 04:48 UTC36d ago 1 NaN 1.3 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.

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

Map

3500 · seed 814726395
Map of JP ともすけサーバー  5x Raidable Bases | Bosses
map
Procedural Map
size
3500
seed
814726395
Open on RustMaps

Server

srv.info()
address
157.85.88.137:29439
region
EA
max players
20
group limit
8, the default
wipe schedule
monthly
last wipe
6 Oct 2026, 01:40 UTC
hostname
–
first seen
23 Sep 2026

About this server · in its own words

print(srv.description)
【JP ともすけサーバー|運営情報】 ワイプ:毎月第1金曜早朝(日本時間) 次回予定:2026年11月6日 PvE専用|初心者・ソロ歓迎 質問・不具合報告・最新情報はDiscordへ Discord:下の外部ウェブサイトから参加できます。 日本時間午前5時にサーバー再起動します。

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

rust.similar(srv).head(6)
serverlike_thisplayers
0SEA | Eclipse | PVE 5x | Newbie Friendly | Events | Perfectly MEA · groups of 8+ · 5x · monthly · 5 on average1/100
1[KR] 쿠키서버 PVE/X3/NPC레이드/낚시/초보EA · groups of 8+ · 3x · monthly · 15 on average2/100
2[SEA] MALAYSIAN LEGION X5 PVE WIPE (25/10)EA · groups of 8+ · 5x · weekly · 5 on average3/50
3[KR] HAPPY PIG | PVE 5X | 2-3 Week Wipe | Final Day PVPEA · groups of 8+ · 5x · biweekly · 2 on average0/30
4모코코서버 [PVE|X3|이벤트|초보]EA · groups of 8+ · 3x · monthly · 2 on average0/100
5[坚果PVE]原倍养老/打怪升级/合成强化/召唤副本EA · groups of 8+ · monthly · 34 on average25/100

Quick answers

From the figures on this page.

Population data

What position does JP ともすけサーバー 5x Raidable Bases | Bosses take in the server rankings?

Player hours over the last seven days: #1,825 for JP ともすけサーバー 5x Raidable Bases | Bosses, #175 in Asia, within the top 8% of the ranked set.

How many players does JP ともすけサーバー 5x Raidable Bases | Bosses hold at once?

The sample now reads 1 players for JP ともすけサーバー 5x Raidable Bases | Bosses, out of 20 slots. Over the last seven days it averaged 3 players and peaked at 10. Averaged by hour over 48 hours, 13:00 UTC is the busiest, at 7 players.

About the server

How smoothly does JP ともすけサーバー 5x Raidable Bases | Bosses run?

Averaged over 48 hours: 222 server fps, never under 125. The entity count peaked at 87,075, covering buildings, deployables and the rest of the world. A high of 4,465 MB of memory used. Low fps plus an entity count on the way up is the lag players report.

Which Rust version is JP ともすけサーバー 5x Raidable Bases | Bosses on?

Rust network protocol 2635 and build 168909 on Linux is what JP ともすけサーバー 5x Raidable Bases | Bosses runs. Steam updates your game for you, but the protocol must match to join.

Is JP ともすけサーバー 5x Raidable Bases | Bosses up, and what does its uptime show?

The current sample puts JP ともすけサーバー 5x Raidable Bases | Bosses online. The uptime it reports puts the last restart about 1 hours ago. 167 of 168 hours up over the last 7 full days, or 99%. Its earliest recorded date in Rust Data is 23 September 2026.

Which location does JP ともすけサーバー 5x Raidable Bases | Bosses run from?

In Asia, JP ともすけサーバー 5x Raidable Bases | Bosses lists itself, using the EA tag. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 157.85.88.137:29439 is its address.

Settings and map

Which settings and rules does JP ともすけサーバー 5x Raidable Bases | Bosses run?

Gather sits at 5x, read from the server's own name: JP ともすけサーバー 5x Raidable Bases | Bosses. No custom cap; the default of 8 players per group stands. pve is the game mode here, and no combat between players. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. Anti-cheat status: VAC on.

Which map has JP ともすけサーバー 5x Raidable Bases | Bosses loaded?

JP ともすけサーバー 5x Raidable Bases | Bosses runs a procedural map of size 3,500 with seed 814726395, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipe schedule

When does JP ともすけサーバー 5x Raidable Bases | Bosses wipe, and how often?

A single wipe each month, the force wipe, is all JP ともすけサーバー 5x Raidable Bases | Bosses does. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world it runs now was generated 23 days 20 hours ago. A monthly wipe schedule is published in its tags.

What is wipe day on JP ともすけサーバー 5x Raidable Bases | Bosses like?

Recent wipes averaged 3 players at their peak. 9 hours after the latest wipe, the crowd reached its peak. Half the peak or more was held to the next wipe in 100% of recent wipes.

Tags, lists

Which lists on Rust Data hold JP ともすけサーバー 5x Raidable Bases | Bosses, and which filters?

On Rust Data, JP ともすけサーバー 5x Raidable Bases | Bosses appears in these lists: Modded Rust servers, Rust servers filtered by gather rate: 5x and Rust PvE servers. Under these filters on the server list, it is listed: Region: Asia; Type: Modded; Game mode: PvE; Server tag: Monthly ^m, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Gather rate: 5x.

How should you read the server tags on JP ともすけサーバー 5x Raidable Bases | Bosses?

The game's server browser reads these tags from JP ともすけサーバー 5x Raidable Bases | Bosses: gmrust (Game mode): Rust survival in its standard form; mp20 (Max players): Slot count: 20; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^m (Monthly): Monthly: the wipe lands with Facepunch's force wipe; ^p (PvE): PvE: the world is the threat, not other players; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings; EA (East Asia): East Asia is its listing in the server browser. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Connecting

How can I connect to JP ともすけサーバー 5x Raidable Bases | Bosses?

The manual route: launch Rust, F1, then client.connect 157.85.88.137:29439. 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/hdC8JWtRj.

Server tags · what each one means

srv.tags.decode()

Published as mp20,ptrak,$r?,v2635,^m,EA,^p,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp20
Max players Slot count: 20.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build Build number: 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code The region field is empty.

Wipe schedule

^m
Monthly Monthly: the wipe lands with Facepunch's force wipe.

Gameplay

^p
PvE PvE: the world is the threat, not other players.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Modded listing: the game is changed by plugins or settings.

Region

EA
East Asia East Asia is its listing in the server browser.

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 78,653 players 11,789 servers online