Rust Server TrendsSeismic network · station log
Recording Stations11,647 Players39,332 Active2,956 Wipes · 3 h71 48 h

Station XX-15420 · no signal

ShibaLabs 100x - Outbreak | S/D/T | Weekly

Offline 159.2.92.90:28090 checked 1d ago

100x moddedoxide
Connect
Players now
0/ 500
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak –
Rank
#15,420
top 69%
Last wipe
8d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15420 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 500 slots
Motion · 24 h
M0.0steady+0 players
Channel 1 · calibrated

Players

AveragePeak
0123403:0006:0010:0013:0017:0020:00

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. 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
15k10k15k20k20 Sep24 Sep28 Sep20 Oct24 Oct28 Oct

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

Expected events

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak
0players, last three wipes

The first 48 hours of its last wipes

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

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Mon 19 Oct, 20:26 UTC8d ago M0.0steady 0 – 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
Rustafields.com [X100][RB][TP][Shop] EU · groups of 40+ · 100x · monthly · 6 on average
5/ 150
Alaskan Bull Worms 100x Noob Friendly groups of 10+ · 100x · 4 on average
3/ 125
No Rules | 100x | Clans | Free Mini | Cars | Noob Friendly NA · groups of 20+ · 100x · weekly · 2 on average
3/ 125
X-PUNCH[x100/kit/tp/]Wipe 01.10 EA · groups of 8+ · 100x · monthly · 1 on average
2/ 100
[EU] WOLFPACK.GG 100x [No BPs | Kits | Shop | TP | VIP] EU · groups of 100+ · 100x · monthly · 1 on average
1/ 200
Atlas - EU 10x | No BPs | Kits | Shop EU · groups of 20+ · 10x · weekly · 341 on average
92/ 150
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on ShibaLabs 100x - Outbreak | S/D/T | Weekly?

ShibaLabs 100x - Outbreak | S/D/T | Weekly uses a procedural map, which the game generates.

Which settings and rules apply on ShibaLabs 100x - Outbreak | S/D/T | Weekly?

Its name points to a gather rate of 100x on ShibaLabs 100x - Outbreak | S/D/T | Weekly. At the game's default, groups can have up to 8 players. In survival mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. Its plugins are run through Oxide. VAC, Valve's anti-cheat, is switched on.

Population

What is the current population on ShibaLabs 100x - Outbreak | S/D/T | Weekly?

ShibaLabs 100x - Outbreak | S/D/T | Weekly is not responding at this moment and is offline, last seen 30 hours ago. The seven-day average for this server is 0 players.

How does ShibaLabs 100x - Outbreak | S/D/T | Weekly rank against other Rust servers?

Over the last seven days, ShibaLabs 100x - Outbreak | S/D/T | Weekly recorded enough player hours to reach #15,420 worldwide, placing it in the top 69% of all ranked servers.

Server facts

How reliably does ShibaLabs 100x - Outbreak | S/D/T | Weekly stay online?

As recorded now, ShibaLabs 100x - Outbreak | S/D/T | Weekly is not reachable, the last contact having been 30 hours ago. Of the 168 hours in the last 7 full days, it was up for 141, or 84% of the time. Its earliest appearance in the records of Rust Server Trends dates to 16 September 2026.

Which region does ShibaLabs 100x - Outbreak | S/D/T | Weekly run from?

A region is not published by ShibaLabs 100x - Outbreak | S/D/T | Weekly. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 159.2.92.90:28090.

What build of Rust does ShibaLabs 100x - Outbreak | S/D/T | Weekly use?

ShibaLabs 100x - Outbreak | S/D/T | Weekly is running Rust network protocol 2627 and build 153858 on a machine with Linux. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe day

What does wipe day look like on ShibaLabs 100x - Outbreak | S/D/T | Weekly?

The recent wipes averaged a busiest count of 0 players. 0 hours after the latest wipe, the crowd peaked.

How often does ShibaLabs 100x - Outbreak | S/D/T | Weekly wipe, and on which days?

Too few wipes of ShibaLabs 100x - Outbreak | S/D/T | Weekly are on record yet to show its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 8 days 6 hours is how long the current world has been running.

Lists and tags

What do the server tags on ShibaLabs 100x - Outbreak | S/D/T | Weekly mean?

Tags published by ShibaLabs 100x - Outbreak | S/D/T | Weekly and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp500 (Max players): The server has 500 slots; ts8 (Group limit): Teams max out at 8, the default set by the game; v2627 (Protocol): Your game needs to be on protocol 2627 to join; cs153858 (Build): It runs game build 153858; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does ShibaLabs 100x - Outbreak | S/D/T | Weekly appear?

You will find ShibaLabs 100x - Outbreak | S/D/T | Weekly on the following Rust Server Trends lists: Rust servers above 10x gather rate and Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks; Gather rate: More than 10x.

Connecting

What steps get you onto ShibaLabs 100x - Outbreak | S/D/T | Weekly?

Enter client.connect 159.2.92.90:28090 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp500,ptrak,$r?,v2627,gmrust,cs153858,ts8,^o^z

Game

gmrust
Game mode Survival in standard Rust.
mp500
Max players The server has 500 slots.
ts8
Group limit Teams max out at 8, the default set by the game.
v2627
Protocol Your game needs to be on protocol 2627 to join.
cs153858
Build It runs game build 153858.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code The server has no region code.

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.