Rust Data

rustdata.spaceservers210.131.218.193:29015.ipynb

Run all rust-data · live

‹ All servers

Offline 210.131.218.193:28015 checked 5d ago

JP 社会人 SOLO Chill 2x NoTeams

2x biweekly wipes moddedoxide

Connect

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

Right now

srv.summary()
players now 0/20 # 0% full
7-day average 0 # peak 1
rank #11,050 # top 50%
last wipe 26d ago # biweekly schedule
next wipe 1d 2h # Fri 30 Oct, 09:29 UTC
display(Image(srv.banner))

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
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

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Wipe schedule · from its schedule tag

srv.wipe_schedule()

Next wipe Friday 30 October, 09:29 UTC, in 1d 2h. # Its biweekly schedule tag · low confidence

usual gap13.9 daysbetween real wipes
wipe-day peak5players, last three wipes
crowd held0%else halves by day 12

Coming wipes

inatkind
01d 2hFri 30 Oct, 09:29 UTCwipe
17d 11hThu 5 Nov, 19:00 UTCFW force wipe
215d 2hFri 13 Nov, 09:29 UTCwipe
329d 2hFri 27 Nov, 09:29 UTCwipe
435d 11hThu 3 Dec, 19:00 UTCFW force wipe
543d 2hFri 11 Dec, 09:29 UTCwipe

The first 48 hours of its last wipes

Fri 2 OctFri 18 Sep
02468+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 2 Oct, 09:29 UTC26d ago 4 NaN running 0
1 Fri 18 Sep, 11:10 UTC40d ago 6 halved by day 12 13.9 days 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 50005
Map of JP 社会人 SOLO Chill 2x NoTeams
map
Procedural Map
size
3500
seed
50005
Open on RustMaps

Server

srv.info()
address
210.131.218.193:28015
region
–
max players
20
group limit
8, the default
wipe schedule
biweekly
last wipe
2 Oct 2026, 11:08 UTC
hostname
–
first seen
13 Sep 2026

About this server · in its own words

print(srv.description)
JP 社会人 SOLO | PvP | Map 3500 | Wood Stone Metal 2x | Sulfur 1x | NoTeams | Chill | Raid Enabled: 21:00-24:00 JST | Protected: 00:00-21:00 JST | Wipe: 1st & 3rd Friday 20:00 JST | BP Wipe: 1st Friday

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

rust.similar(srv).head(6)
serverlike_thisplayers
0[SEA] AseanPanda.net | 2x Vanilla | MAP WIPE 3 | 27/10EA · groups of 8+ · 2x · biweekly · 82 on average55/115
1[SEA] Rust Manila 2x | BiweeklyEA · groups of 8+ · 2x · biweekly · 24 on average41/150
2[SEA] MayhemPH | 2x PvPvE | Raid 3PM-12AM | FULL WIPE 23/10EA · groups of 8+ · 2x · biweekly · 4 on average4/140
3[JP]初心者PVPサーバー|RaidTime・ EventsEA · groups of 10+ · biweekly · 16 on average8/100
4[JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29EA · no group limit · biweekly · 4 on average0/20
5瞌睡熊『5倍10废|10.29|萌新首选|无权限』EA · groups of 8+ · biweekly · 4 on average3/100

Quick answers

From the figures on this page.

Population data

What position does JP 社会人 SOLO Chill 2x NoTeams take in the server rankings?

Rank #11,050 on seven-day player hours for JP 社会人 SOLO Chill 2x NoTeams, within the top 50% of all ranked servers.

How full does JP 社会人 SOLO Chill 2x NoTeams run?

JP 社会人 SOLO Chill 2x NoTeams returns no live count at this refresh, having last been seen 5 days 11 hours ago. Over the last seven days it averaged 0 players and peaked at 1.

Server facts

Which Rust version is JP 社会人 SOLO Chill 2x NoTeams on?

The build is Rust network protocol 2634 and build 166586 on Linux, run by JP 社会人 SOLO Chill 2x NoTeams. Joining needs the same protocol on your game; Steam handles the update.

Is JP 社会人 SOLO Chill 2x NoTeams up, and what does its uptime show?

Offline now for JP 社会人 SOLO Chill 2x NoTeams, last seen 5 days 11 hours ago. Uptime of 27% across the last 7 full days: 45 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.

Where does JP 社会人 SOLO Chill 2x NoTeams sit?

Its name points to Asia, but JP 社会人 SOLO Chill 2x NoTeams publishes no region tag. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 210.131.218.193:28015 is its address.

Map and rules

Which rules apply on JP 社会人 SOLO Chill 2x NoTeams, and what settings?

2x gather is what the name states, and the name is JP 社会人 SOLO Chill 2x NoTeams. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the usual game, with gathering, building and raiding. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.

Which map has JP 社会人 SOLO Chill 2x NoTeams loaded?

Size 3,500, seed 50005: the procedural map on JP 社会人 SOLO Chill 2x NoTeams, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipe schedule

When does JP 社会人 SOLO Chill 2x NoTeams wipe, and how often?

The tag sets the prediction: JP 社会人 SOLO Chill 2x NoTeams has too few wipes on record to confirm its schedule. The schedule puts the next wipe on Friday 30 October at 09:29 UTC. A new world was started 26 days 20 hours ago, and that is the one in play. Its tags carry a wipe schedule of every two weeks.

What is wipe day on JP 社会人 SOLO Chill 2x NoTeams like?

The average peak over recent wipes is 5 players. Peak population on the latest wipe came 4 hours in. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. The drop under half arrived by day 12 in the other cases.

Lists and tags

Where does JP 社会人 SOLO Chill 2x NoTeams appear among Rust Data lists and filters?

The Rust Data lists that JP 社会人 SOLO Chill 2x NoTeams fits are: Modded Rust servers and 2x Rust servers. It appears under these filters on the server list: Region: Asia; Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Gather rate: 2x.

Which meanings do the tags on JP 社会人 SOLO Chill 2x NoTeams hold?

These tags are published by JP 社会人 SOLO Chill 2x NoTeams and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp20 (Max players): The server lists 20 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs166586 (Build): Recorded game build: 166586; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^b (Biweekly): Two weeks between wipes; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Join steps

What is the way to join JP 社会人 SOLO Chill 2x NoTeams?

In Rust, F1 opens the console: type client.connect 210.131.218.193:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp20,ptrak,$r?,v2634,^b,gmrust,cs166586,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp20
Max players The server lists 20 slots.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol To join, your game must run protocol 2634.
cs166586
Build Recorded game build: 166586.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code Region code: not set.

Wipe schedule

^b
Biweekly Two weeks between wipes.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded The Modded section lists it, because plugins or settings change the game.

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 37,258 players 11,622 servers online