Rust Data

rustdata.spaceservers176.57.171.141:29116.ipynb

Run all rust-data · live

‹ All servers

Online 176.57.171.141:29115 checked 8m ago

Barregaanders

Connect

srv = rust.server("176.57.171.141:29116")
print(srv.connect_command)

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 0 # peak 4
rank #5,684 # top 26%
last wipe 17d ago # no schedule published
next wipe – # no rhythm it keeps
display(Image(srv.banner))

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75112:0021:0006:0014:0000:0009:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
02040608012:0021:0006:0014:0000:0009:00

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 17 Sep. 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
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap0.7 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Sun 11 OctSat 10 OctSat 10 Oct
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 Sun 11 Oct, 15:08 UTC17d ago 2 NaN running 1
1 Sat 10 Oct, 22:58 UTC18d ago 2 NaN 0.7 days 2
2 Sat 10 Oct, 13:57 UTC18d ago 2 NaN 0.4 days 0
3 Thu 1 Oct, 18:03 UTC FW27d ago 1 halved by day 1 8.8 days 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

3650 · seed 1988292877
Map of Barregaanders
map
Procedural Map
size
3650
seed
1988292877
Open on RustMaps

Server

srv.info()
address
176.57.171.141:29115
region
–
max players
50
group limit
8, the default
wipe schedule
–
last wipe
11 Oct 2026, 15:08 UTC
hostname
–
first seen
13 Sep 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 516 on average441/475
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average355/375
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average42/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 276 on average33/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 275 on average49/100
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 243 on average152/200

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does Barregaanders rank?

Rank #5,684 on seven-day player hours for Barregaanders, within the top 26% of all ranked servers.

How full does Barregaanders run?

The sample now reads 0 players for Barregaanders, out of 50 slots. Over the last seven days it averaged 0 players and peaked at 4. Averaged by hour over 48 hours, 16:00 UTC is the busiest, at 1 players.

Server facts

What does performance look like on Barregaanders?

The 48-hour average is 56 server fps, with a low of 41. Entity numbers reached 74,236, and that includes buildings, deployables and the rest. A high of 1,941 MB of memory used. Low fps plus an entity count on the way up is the lag players report.

Which Rust version is Barregaanders on?

The build is Rust network protocol 2635 and build 168909 on Windows, run by Barregaanders. The protocol has to match before you can join, and Steam does the updating.

Is Barregaanders up, and what does its uptime show?

The current sample puts Barregaanders online. The uptime it reports puts the last restart about 10 hours ago. Uptime of 99% across the last 7 full days: 167 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.

Which location does Barregaanders run from?

There is no region published for Barregaanders. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 176.57.171.141:29115.

Rules, settings, map

Which rules apply on Barregaanders, and what settings?

You will not find a gather rate in the string Barregaanders. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the base game, where you gather, build and raid. Raids and player combat are enabled. The server browser lists it under Community. Anti-cheat status: VAC on.

What is the map on Barregaanders?

Size 3,650, seed 1988292877: the procedural map on Barregaanders, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipe data

When does Barregaanders wipe, and on what schedule?

Irregular wipe times on Barregaanders leave no next wipe to forecast. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 17 days 19 hours ago.

On Barregaanders, 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. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. In the wipes where it did not hold, half was lost by day 1.

Tags, lists

Which lists on Rust Data hold Barregaanders, and which filters?

On Rust Data, Barregaanders appears in these lists: Rust community servers, unfiltered. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

How should you read the server tags on Barregaanders?

Read by the game's server browser, the tags Barregaanders publishes are: gmvanilla (Game mode): Survival in vanilla form; mp50 (Max players): Slot count: 50; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

How to join

How can I connect to Barregaanders?

In Rust, F1 opens the console: type client.connect 176.57.171.141:29115. 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 mp50,ptrak,$r?,v2635,gmvanilla,cs168909,ts8

Game

gmvanilla
Game mode Survival in vanilla form.
mp50
Max players Slot count: 50.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build The server runs build 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code The region field is empty.

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 60,383 players 11,716 servers online