Rust Server TrendsSeismic network · station log
Recording Stations11,846 Players84,816 Active3,802 Wipes · 3 h288 48 h

Station XX-15353 · no signal

BRUHUST 1.5x

Offline 75.220.26.13:28015 checked 7d ago

1.5x biweekly wipes moddedcarbon
Connect
Players now
0/ 40
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,353
top 69%
Last wipe
7d ago
biweekly schedule
Next wipe
7d 4h
Thu 5 Nov, 19:00 UTC FW
Seismic record · station XX-15353 · 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 40 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 16 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
15k10k15k20k15 Oct18 Oct21 Oct23 Oct26 Oct29 Oct

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

Expected events

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 7d 4h. The force wipe · high confidence

usual gap
0.9 daysbetween real wipes
on rhythm
50%of its recent wipes
wipe-day peak
3players, last three wipes
crowd held
0%else halves by day 1

Coming wipes

  1. 7d 4hThu 5 Nov, 19:00 UTCFW
  2. 20d 9hThu 19 Nov, 00:22 UTC
  3. 35d 4hThu 3 Dec, 19:00 UTCFW

The first 48 hours of its last wipes

Thu 22 OctWed 21 OctTue 20 Oct
01234+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
Thu 22 Oct, 00:22 UTC7d ago M0.0steady 2 – running 2
Wed 21 Oct, 17:38 UTC7d ago M0.3rising 3 – 0.3 days 1
Tue 20 Oct, 19:51 UTC8d ago M0.5rising 3 – 0.9 days 0
Mon 19 Oct, 23:17 UTC9d ago M0.0steady 4 – 0.9 days 4
Mon 19 Oct, 02:03 UTC10d ago M0.3rising 4 – 0.9 days 2
Fri 16 Oct, 13:34 UTC13d ago M0.5rising 3 halved by day 1 2.5 days 0
Fri 16 Oct, 01:11 UTC13d ago M0.3rising 3 – 0.5 days 1

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
RUST ROOM 1.5x | BIWEEKLY | Wipe 29.10 groups of 200+ · 1.5x · biweekly · 2 on average
474/ 500
Alkad #1 (x1.5|Kits) EU · groups of 16+ · 1.5x · biweekly · 2 on average
0/ 150
SURVIVORS.GG #2 [ 2x Vanilla ] WIPED 27.10 groups of 8+ · 2x · biweekly · 177 on average
108/ 200
Atlas - EU 2X Medium | Vanilla+ | No BP Wipes EU · groups of 16+ · 2x · biweekly · 145 on average
57/ 100
RUST ROOM 1.5x | MAIN | Wipe 23.10 groups of 200+ · 1.5x · weekly · 143 on average
4/ 500
HollowServers.co 3x Solo/Duo |LootX3|JUST FULLWIPED NA · groups of 8+ · 3x · biweekly · 129 on average
113/ 115
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on BRUHUST 1.5x?

BRUHUST 1.5x runs a procedural map of size 1,100 with seed 1401480073, produced by the game. You can view it on RustMaps from this page: the same size and seed produce the same map.

Which settings and rules apply on BRUHUST 1.5x?

Its name points to a gather rate of 1.5x on BRUHUST 1.5x. At the game's default, groups can have up to 8 players. In survival mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Carbon. VAC, Valve's anti-cheat, is switched on.

Population

How many players are recorded on BRUHUST 1.5x right now?

BRUHUST 1.5x is not responding at this moment and is offline, last seen 7 days 12 hours ago. Averaged across the last seven days, the population was 0 players.

How does BRUHUST 1.5x rank against other Rust servers?

On player hours for the past week, BRUHUST 1.5x sits at #15,353, which puts it inside the top 69% of every ranked server.

Server details

How reliably does BRUHUST 1.5x stay online?

As recorded now, BRUHUST 1.5x is not reachable, the last contact having been 7 days 12 hours ago. Of the 168 hours in the last 7 full days, it was up for 3, or 2% of the time. On 15 October 2026 it was recorded for the first time by Rust Server Trends.

Where in the world is BRUHUST 1.5x hosted?

No region is published by BRUHUST 1.5x. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 75.220.26.13:28015 is the address it uses.

Which Rust version is BRUHUST 1.5x running?

On Linux, BRUHUST 1.5x runs Rust network protocol 2634 and build 167781. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe pattern

What does wipe day look like on BRUHUST 1.5x?

The recent wipes averaged a busiest count of 3 players. The peak on the most recent wipe came 0 hours after the wipe. Half that peak was held until the next wipe in 0% of its recent wipes. In the wipes that didn't hold, the crowd was below half by day 1.

How often does BRUHUST 1.5x wipe, and on which days?

The prediction follows its tag, because too few of BRUHUST 1.5x's wipes are on record to confirm its schedule. On Thursday 5 November at 19:00 UTC the force wipe arrives: that is its next wipe, and every Rust server wipes then. 7 days 14 hours is how long the current world has been running. Its tags state that it wipes every two weeks.

Lists and tags

What do the server tags on BRUHUST 1.5x mean?

These are the tags BRUHUST 1.5x publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp40 (Max players): 40 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code; ^b (Biweekly): It wipes once a fortnight; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): Carbon is the plugin framework running here. 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 BRUHUST 1.5x appear?

You will find BRUHUST 1.5x on the following Rust Server Trends lists: 1.5x Rust servers and Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Biweekly ^b, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks; Gather rate: 1.5x.

Connecting

How do you connect to BRUHUST 1.5x?

Enter client.connect 75.220.26.13:28015 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 mp40,ptrak,$r?,v2634,^z,^y,^b,gmrust,cs167781,ts8

Game

gmrust
Game mode Survival in standard Rust.
mp40
Max players 40 slots are available.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2634
Protocol To connect, your game must be on the same protocol, 2634.
cs167781
Build The game build is 167781.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code The server has no region code.

Wipe schedule

^b
Biweekly It wipes once a fortnight.

Mods and access

^z
Modded Plugins or settings alter the game, so it's listed under Modded.
^y
Carbon Carbon is the plugin framework running here.

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.