Rust Server TrendsSeismic network · station log
Recording Stations11,851 Players94,129 Active3,887 Wipes · 3 h394 48 h

Station XX-14619 · no signal

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

Offline 157.85.88.162:27188 checked 23d ago

weekly wipes moddedoxide
Connect
Players now
0/ 130
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#14,619
top 65%
Last wipe
24d ago
weekly schedule
Next wipe
3d 23h
Mon 2 Nov, 15:01 UTC
Seismic record · station XX-14619 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 130 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

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 5 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

Channel 3 · rank movement

Rank

daily · 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.

Expected events

Wipe schedule

from its schedule tag

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

wipe-day peak
2players, last three wipes

Coming wipes

  1. 3d 23hMon 2 Nov, 15:01 UTC
  2. 7d 3hThu 5 Nov, 19:00 UTCFW
  3. 10d 23hMon 9 Nov, 15:01 UTC
  4. 17d 23hMon 16 Nov, 15:01 UTC
  5. 24d 23hMon 23 Nov, 15:01 UTC
  6. 31d 23hMon 30 Nov, 15:01 UTC
  7. 35d 3hThu 3 Dec, 19:00 UTCFW
  8. 38d 23hMon 7 Dec, 15:01 UTC

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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Mon 5 Oct, 15:01 UTC24d ago M0.3rising 2 – running 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
QS『芬达』100000倍/10.28/枪战/蓝图全解/萌新/建造 EA · groups of 20+ · weekly · 25 on average
32/ 100
【蛋壳】10倍|10.23档|爆枪|礼包|新手推荐 EA · groups of 8+ · weekly · 20 on average
38/ 200
〈红牛〉 五倍6人服/10.28号18:00新开 |新手入门| EA · groups of 30+ · weekly · 3 on average
4/ 200
【独来独往】10.27新档|3倍|独狼Solo|秒造|拾取 EA · groups of 8+ · weekly · 1 on average
2/ 200
Rustoria.co - SEA Main EA · groups of 16+ · weekly · 181 on average
441/ 450
Japan Tokyo - Main|10/23|JP/KR/SEA|金曜日|JumpRust.com EA · groups of 16+ · weekly · 119 on average
28/ 550
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on [KR/JP] Shock - Solo/Duo/Trio 10/06?

[KR/JP] Shock - Solo/Duo/Trio 10/06 runs a procedural map of size 3,500 with seed 50000, produced by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map.

Which settings and rules apply on [KR/JP] Shock - Solo/Duo/Trio 10/06?

The name of [KR/JP] Shock - Solo/Duo/Trio 10/06 gives no gather rate. At the game's default, groups can have up to 8 players. In survival mode, standard play, with gathering, building and raiding. You can raid and fight other players here. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Oxide. The server has VAC on, Valve's anti-cheat.

Population

What is the current population on [KR/JP] Shock - Solo/Duo/Trio 10/06?

A reading taken now finds [KR/JP] Shock - Solo/Duo/Trio 10/06 offline; the most recent activity was 23 days 21 hours ago.

How does [KR/JP] Shock - Solo/Duo/Trio 10/06 rank against other Rust servers?

On player hours for the past week, [KR/JP] Shock - Solo/Duo/Trio 10/06 sits at #14,619, which puts it inside the top 65% of every ranked server.

Operator and location

How reliably does [KR/JP] Shock - Solo/Duo/Trio 10/06 stay online?

No contact with [KR/JP] Shock - Solo/Duo/Trio 10/06 right now, and the last recorded contact was 23 days 21 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. On 5 October 2026 it was recorded for the first time by Rust Server Trends.

Which region does [KR/JP] Shock - Solo/Duo/Trio 10/06 run from?

No region tag comes from [KR/JP] Shock - Solo/Duo/Trio 10/06, though the name points to Asia. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 157.85.88.162:27188.

What build of Rust does [KR/JP] Shock - Solo/Duo/Trio 10/06 use?

On Linux, [KR/JP] Shock - Solo/Duo/Trio 10/06 runs Rust network protocol 2634 and build 166652. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe day

What does wipe day look like on [KR/JP] Shock - Solo/Duo/Trio 10/06?

2 players, on average, was the busiest crowd at its recent wipes. 0 hours into the latest wipe, the crowd reached its peak.

On what timetable does [KR/JP] Shock - Solo/Duo/Trio 10/06 run its wipes?

The prediction is taken from its tag, since [KR/JP] Shock - Solo/Duo/Trio 10/06 has too few wipes on record to confirm the schedule. Monday 2 November at 15:01 UTC is when its next wipe is due. The present world dates from 24 days. Its tags state a weekly wipe schedule.

Server tags

What do the server tags on [KR/JP] Shock - Solo/Duo/Trio 10/06 mean?

Tags published by [KR/JP] Shock - Solo/Duo/Trio 10/06 and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp130 (Max players): 130 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs166652 (Build): Game build: 166652; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^w (Weekly): Wipes happen weekly; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does [KR/JP] Shock - Solo/Duo/Trio 10/06 appear?

You will find [KR/JP] Shock - Solo/Duo/Trio 10/06 on the following Rust Server Trends lists: Modded Rust servers, tracked live. On the server list, the filters it matches are: Region: Asia; Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly.

Join the server

How do you connect to [KR/JP] Shock - Solo/Duo/Trio 10/06?

You can connect by pressing F1 in Rust and typing client.connect 157.85.88.162:27188 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp130,ptrak,$r?,v2634,^w,gmrust,cs166652,ts8,^o^z

Game

gmrust
Game mode You'll find standard Rust survival here.
mp130
Max players 130 slots are available.
ts8
Group limit This uses the game default of 8 per team.
v2634
Protocol To connect, your game must be on the same protocol, 2634.
cs166652
Build Game build: 166652.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code The server has no region code.

Wipe schedule

^w
Weekly Wipes happen weekly.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded The game is changed by plugins or settings, placing it under Modded.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.