Fig. 1Players on BRUHUST 1.5xRG-S15353-01 · Sheet 1 of 11
Fig. 2
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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.
Fig. 2FPS, entities and memoryRG-S15353-02 · Sheet 2 of 11
Fig. 3
Rank
daily · 1 is best
RankRank in region
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Fig. 3Rank on player hours, dailyRG-S15353-03 · Sheet 3 of 11
Schedule
Wipe schedule
from its schedule tag
Next wipe Thursday 5 November, 19:00 UTC, in 7d 6h.
The force wipe · high confidence
usual gap0.9 daysbetween real wipes
on rhythm50%of its recent wipes
wipe-day peak3players, last three wipes
crowd held0%else halves by day 1
Coming wipes
7d 6hThu 5 Nov, 19:00 UTCFW
20d 12hThu 19 Nov, 00:22 UTC
35d 6hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Thu 22 OctWed 21 OctTue 20 Oct
Fig. 4Players each hour from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 2, 0 hours in.
ScheduleExpected wipesRG-S15353-04 · Sheet 4 of 11
Log
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 22 Oct, 00:22 UTC7d ago
2
–
running
2
Wed 21 Oct, 17:38 UTC7d ago
3
–
0.3 days
1
Tue 20 Oct, 19:51 UTC8d ago
3
–
0.9 days
0
Mon 19 Oct, 23:17 UTC9d ago
4
–
0.9 days
4
Mon 19 Oct, 02:03 UTC10d ago
4
–
0.9 days
2
Fri 16 Oct, 13:34 UTC12d ago
3
halved by day 1
2.5 days
0
Fri 16 Oct, 01:11 UTC13d ago
3
–
0.5 days
1
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.
Table 1Wipe logRG-S15353-05 · Sheet 5 of 11
Similar assemblies
Similar servers
the same kind of game, then region, group limit, rate and wipes
How reliable is BRUHUST 1.5x, and is it online now?
The current state of BRUHUST 1.5x is offline, with the last sighting 7 days 9 hours ago. 3 of 168 hours up over the last 7 full days, which is 2% of the time. The first sighting of it by Rust Graphs was on 15 October 2026.
2.
What location is recorded for BRUHUST 1.5x?
No region is published by BRUHUST 1.5x. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. 75.220.26.13:28015 is its address.
3.
On which Rust version is BRUHUST 1.5x running?
On Linux, BRUHUST 1.5x runs Rust network protocol 2634 and build 167781. Steam updates your game, which must be on the same protocol for you to join.
Player data
4.
What does the population history show for BRUHUST 1.5x?
The latest refresh records BRUHUST 1.5x as offline, last seen 7 days 9 hours ago. Averaged across seven days, the player count is 0.
5.
Against other Rust servers, where is BRUHUST 1.5x placed?
Within the top 69% of all ranked servers: BRUHUST 1.5x at #15,353 for player hours, seven days recorded.
Schedules
6.
What is recorded on BRUHUST 1.5x on wipe day?
An average of 3 players was recorded at the busiest point of its recent wipes. 0 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 0% of its recent wipes. In the other cases the crowd was below half by day 1.
7.
Which times and days are wipes plotted at on BRUHUST 1.5x?
The prediction follows its tag, because too few wipes of BRUHUST 1.5x are on record to confirm the schedule. On Thursday 5 November at 19:00 UTC the force wipe falls; that is the next wipe, and it wipes every Rust server. The world it runs now was made 7 days 11 hours ago. The tags state a wipe schedule at two-week intervals.
Map and rules
8.
Which settings does BRUHUST 1.5x run, and what rules?
The name records 1.5x gather for BRUHUST 1.5x. No limit is published beyond the default: 8 players per group. It runs the survival game mode, the standard game: gather, build, raid. Raiding and player combat are permitted. The server browser lists it under Modded: plugins or settings change the game. Carbon plugins are run on it. Anti-cheat: VAC, from Valve, is on.
9.
What is the map for BRUHUST 1.5x?
Size 1,100 with seed 1401480073: that is the procedural map BRUHUST 1.5x runs, generated by the game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map.
Tags
10.
Where does BRUHUST 1.5x appear among the Rust Graphs lists and filters?
The Rust Graphs lists that carry BRUHUST 1.5x are: 1.5x Rust servers and Modded Rust servers. It is returned by 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.
11.
Which meaning is attached to each tag on BRUHUST 1.5x?
gmrust (Game mode): Standard survival, as Rust plays; mp40 (Max players): The slot count is 40; ts8 (Group limit): The default team size of 8 applies; v2634 (Protocol): Your game must match protocol 2634 to join; cs167781 (Build): Build: 167781; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): Region code not set; ^b (Biweekly): Every two weeks it wipes; ^z (Modded): Plugins or settings change the game, so it is listed under Modded; ^y (Carbon): Plugin framework: Carbon are the tags BRUHUST 1.5x publishes; the game's server browser reads them. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.
Joining the server
12.
What is the way to connect to BRUHUST 1.5x?
Connect with client.connect 75.220.26.13:28015: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you.
NotesAnswered from the figuresRG-S15353-10 · Sheet 10 of 11
Key
Server tags
what each one means
Published asmp40,ptrak,$r?,v2634,^z,^y,^b,gmrust,cs167781,ts8
Game
gmrust
Game modeStandard survival, as Rust plays.
mp40
Max playersThe slot count is 40.
ts8
Group limitThe default team size of 8 applies.
v2634
ProtocolYour game must match protocol 2634 to join.
cs167781
BuildBuild: 167781.
ptrak
NetworkingStandard network layer: RakNet.
$r?
Region codeRegion code not set.
Wipe schedule
^b
BiweeklyEvery two weeks it wipes.
Mods and access
^z
ModdedPlugins or settings change the game, so it is listed under Modded.
^y
CarbonPlugin framework: Carbon.
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.
KeyTag string decodedRG-S15353-11 · Sheet 11 of 11