Rust PopulationField survey · Rust servers
Observing 75,264 players 11,770 servers 3,495 with someone on 241 fresh wipes in 3 h counted every five minutes
‹ All serversspecimen record
Specimen recordcat. no. 5,825habitat unknownfirst seen 13 Sep 2026

Barregaanders

Online 176.57.171.141:29115 checked 10m ago

Measurements

Players now
1/ 50
= 1 player
2% full
7-day average
0
peak 4
Rank
#5,825
top 26%
Last wipe
18d ago
no schedule published
Next wipe
–
no rhythm it keeps
Obs. 1 · sightings

Players

AveragePeak
00.250.50.75123:0008:0017:0003:0012:0021:00

Hourly average and peak, UTC.

Obs. 2 · condition

Server performance

02040608023:0008:0017:0003:0012:0021: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.

Obs. 3 · standing

Rank

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

Obs. 4 · the wipe cycle

Wipe schedule

no rhythm it keeps

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

0.7 days
usual gap
between real wipes
33%
on rhythm
of its recent wipes
2
wipe-day peak
players, last three wipes
0%
crowd held
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.

Log · wipes seen

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 11 Oct, 15:08 UTC18d ago 2 – running 1
Sat 10 Oct, 22:58 UTC18d ago 2 – 0.7 days 2
Sat 10 Oct, 13:57 UTC19d ago 2 – 0.4 days 0
Thu 1 Oct, 18:03 UTC FW28d 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.

Field questions

Quick answers

from the figures on this page

Population

How does Barregaanders rank against other Rust servers?

Over the past week it ranks #5,825 for player hours, which puts Barregaanders in the top 26% of all ranked servers.

How busy is Barregaanders?

The count reads 1 players on Barregaanders, which has 50 slots. We counted an average of 0 players in the past week, with 4 at the busiest. The busiest hour in the last 48 was 16:00 UTC, when an average of 1 players were on.

Lists and tags

What do the server tags on Barregaanders mean?

These are the tags Barregaanders publishes, as read by the game's server browser: gmvanilla (Game mode): This is vanilla survival; mp50 (Max players): You can join up to 50 slots; ts8 (Group limit): Teams are capped at 8, the default setting; v2635 (Protocol): The protocol is 2635; a different version will not connect; cs168909 (Build): The game build is 168909; ptrak (Networking): The standard network layer, RakNet, is in use; $r? (Region code): This server has no region code. The tags also carry the current player count, the queue and when the world was made; you will find them at the top of this page.

Which Rust Population lists and filters include Barregaanders?

Barregaanders appears among the Rust Population lists that follow: Community servers, field-listed. Filter the server list by Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more and it will show up.

Wipe schedule

What does wipe day look like on Barregaanders?

Averaged over recent wipes, 2 players were counted at the busiest point. Peak came 0 hours into the latest wipe. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. In those that did not hold, the fall below half came by day 1.

What is the wipe schedule on Barregaanders?

No next wipe can be predicted for Barregaanders, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. Counted from 18 days 7 hours ago, that is how long the current world has stood.

Settings

Which map does Barregaanders run?

Barregaanders uses a map the game generates, procedural, at size 3,650 with seed 1988292877. You can look at it on RustMaps from this page: size and seed determine the map.

What are the rules and settings on Barregaanders?

Nothing in Barregaanders's name says how gather works. No limit is set beyond the standard 8 players per group. This server runs survival, raid, build and gather: the standard game. You can raid and fight other players here. The server browser lists it under Community, as a community server. You play with Valve's anti-cheat on: VAC.

About the server

Which version of Rust does Barregaanders run?

Rust network protocol 2635 and build 168909 on Windows is what Barregaanders uses. Your game needs the same protocol to join; Steam takes care of updating it.

Does Barregaanders run smoothly?

It ran at 57 server fps on average over the last 48 hours, and never went below 41. Up to 74,236 entities were present, counting buildings, deployables and everything else. The highest memory usage was 1,956 MB. What players experience as lag comes from low fps and a rising entity count.

Is Barregaanders online, and how reliable is it?

Barregaanders is up and running at the moment. The uptime it reports suggests a restart roughly 22 hours ago. Over the last 7 full days, 167 of 168 hours were online, or 99%. On 13 September 2026, Rust Population saw it for the first time.

Where is Barregaanders located?

No region is published by Barregaanders. Rust Population does not look up where the machine stands; it shows where the server says it is. You will find it at 176.57.171.141:29115.

How to join

How do I join Barregaanders?

To connect directly, open Rust's console with F1 and type client.connect 176.57.171.141:29115; or press Launch Rust on this page and Steam opens Rust and joins for you.

Key to its markings

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,gmvanilla,cs168909,ts8

Game

gmvanilla
Game mode This is vanilla survival.
mp50
Max players You can join up to 50 slots.
ts8
Group limit Teams are capped at 8, the default setting.
v2635
Protocol The protocol is 2635; a different version will not connect.
cs168909
Build The game build is 168909.
ptrak
Networking The standard network layer, RakNet, is in use.
$r?
Region code This server has no region code.

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.