Rust Data

rustdata.spaceservers157.85.88.162:27189.ipynb

Run all rust-data · live

‹ All servers

Offline 157.85.88.162:27188 checked 24d ago

[KR/JP] Shock - Solo/Duo/Trio 10/06

weekly wipes moddedoxide

Connect

srv = rust.server("157.85.88.162:27189")
print(srv.connect_command)

Right now

srv.summary()
players now 0/130 # 0% full
7-day average 0 # peak –
rank #14,619 # top 65%
last wipe 24d ago # weekly schedule
next wipe 3d 15h # Mon 2 Nov, 15:01 UTC

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 5 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
15k10k15k20k5 Oct6 Oct8 Oct9 Oct11 Oct12 Oct

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

Wipe schedule · from its schedule tag

srv.wipe_schedule()

Next wipe Monday 2 November, 15:01 UTC, in 3d 15h. # Its weekly schedule tag · low confidence

wipe-day peak2players, last three wipes

Coming wipes

inatkind
03d 15hMon 2 Nov, 15:01 UTCwipe
16d 19hThu 5 Nov, 19:00 UTCFW force wipe
210d 15hMon 9 Nov, 15:01 UTCwipe
317d 15hMon 16 Nov, 15:01 UTCwipe
424d 15hMon 23 Nov, 15:01 UTCwipe
531d 15hMon 30 Nov, 15:01 UTCwipe
634d 19hThu 3 Dec, 19:00 UTCFW force wipe
738d 15hMon 7 Dec, 15:01 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, 0 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Mon 5 Oct, 15:01 UTC24d 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 50000
Map of [KR/JP] Shock - Solo/Duo/Trio 10/06
map
Procedural Map
size
3500
seed
50000
Open on RustMaps

Server

srv.info()
address
157.85.88.162:27188
region
–
max players
130
group limit
8, the default
wipe schedule
weekly
last wipe
5 Oct 2026, 15:01 UTC
hostname
–
first seen
5 Oct 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0QS『芬达』100000倍/10.30/枪战/蓝图全解/萌新/建造EA · groups of 20+ · weekly · 25 on average28/100
1【蛋壳】10倍|10.23档|爆枪|礼包|新手推荐EA · groups of 8+ · weekly · 22 on average0/200
2〈红牛〉 五倍6人服/10.28号18:00新开 |新手入门|EA · groups of 30+ · weekly · 3 on average2/200
3[Uz/Ru/Kz] #1 UzRust - ModdedEA · groups of 8+ · weekly · 2 on average0/100
4【独来独往】10.27新档|3倍|独狼Solo|秒造|拾取EA · groups of 8+ · weekly · 2 on average2/200
5Rustoria.co - SEA MainEA · groups of 16+ · weekly · 181 on average140/200

Quick answers

From the figures on this page.

Population data

How does [KR/JP] Shock - Solo/Duo/Trio 10/06 compare in the rankings?

Rank #14,619 on seven-day player hours for [KR/JP] Shock - Solo/Duo/Trio 10/06, within the top 65% of all ranked servers.

What population does [KR/JP] Shock - Solo/Duo/Trio 10/06 carry?

Offline now for [KR/JP] Shock - Solo/Duo/Trio 10/06, with the last sample 24 days 4 hours ago.

Server data

What Rust version does [KR/JP] Shock - Solo/Duo/Trio 10/06 run?

Rust network protocol 2634 and build 166652 on Linux is what [KR/JP] Shock - Solo/Duo/Trio 10/06 runs. The protocol has to match before you can join, and Steam does the updating.

Is [KR/JP] Shock - Solo/Duo/Trio 10/06 up, and what does its uptime show?

The latest sample has [KR/JP] Shock - Solo/Duo/Trio 10/06 offline, with a last sighting 24 days 4 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 5 October 2026.

Where does [KR/JP] Shock - Solo/Duo/Trio 10/06 sit?

The name of [KR/JP] Shock - Solo/Duo/Trio 10/06 points to Asia, even though no region tag is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 157.85.88.162:27188 is its address.

Settings and map

What rules and settings are recorded for [KR/JP] Shock - Solo/Duo/Trio 10/06?

You will not find a gather rate in the string [KR/JP] Shock - Solo/Duo/Trio 10/06. The group limit sits at the default of 8 players. Recorded as survival, the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. Anti-cheat status: VAC on.

Which map has [KR/JP] Shock - Solo/Duo/Trio 10/06 loaded?

[KR/JP] Shock - Solo/Duo/Trio 10/06 runs a procedural map of size 3,500 with seed 50000, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipe schedule

When does [KR/JP] Shock - Solo/Duo/Trio 10/06 wipe, and on what schedule?

The tag sets the prediction: [KR/JP] Shock - Solo/Duo/Trio 10/06 has too few wipes on record to confirm its schedule. On Monday 2 November at 15:01 UTC the next wipe is due. A new world was started 24 days 8 hours ago, and that is the one in play. The tags list wipes as weekly.

On [KR/JP] Shock - Solo/Duo/Trio 10/06, what happens on wipe day?

Across recent wipes the busiest point averaged 2 players. The crowd on the latest wipe topped out 0 hours after it began.

Lists and tags

Where does [KR/JP] Shock - Solo/Duo/Trio 10/06 appear among Rust Data lists and filters?

These Rust Data lists include [KR/JP] Shock - Solo/Duo/Trio 10/06: Modded Rust servers. Under these filters on the server list, it is listed: Region: Asia; Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly.

Which meanings do the tags on [KR/JP] Shock - Solo/Duo/Trio 10/06 hold?

Read by the game's server browser, the tags [KR/JP] Shock - Solo/Duo/Trio 10/06 publishes are: gmrust (Game mode): Survival play, standard Rust; mp130 (Max players): The server lists 130 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs166652 (Build): The server runs build 166652; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^w (Weekly): Wipes run weekly; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Join steps

What is the way into [KR/JP] Shock - Solo/Duo/Trio 10/06?

In Rust, F1 opens the console: type client.connect 157.85.88.162:27188. 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 mp130,ptrak,$r?,v2634,^w,gmrust,cs166652,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp130
Max players The server lists 130 slots.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol To join, your game must run protocol 2634.
cs166652
Build The server runs build 166652.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code The region field is empty.

Wipe schedule

^w
Weekly Wipes run weekly.

Mods and access

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

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 69,537 players 11,768 servers online