Rust StatisticsWorking papers on every public Rust server · 39,834 players now

Barley Ate Oilrig

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 10m ago · 46.110.130.11:28015

Abstract

We describe the public Rust server Barley Ate Oilrig, reached at 46.110.130.11:28015. At the last check it held 0 of 4 places, against a seven-day mean of 01. It ranks #15,353 of all servers, the top 69%. It last wiped 27d ago; the next wipe is expected Thursday 5 November, 19:00 UTC, the force wipe.

Keywordsmodded oxide

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now0/40% full
In the queue0no queue
Seven-day mean0peak –
Rank2#15,353top 69%
Last wipe27d agono schedule published
Next wipe37d 16hThu 5 Nov, 19:00 UTCfw

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

AveragePeak
0123403:0012:0021:0005:0014:0000:00
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
This server has not answered a direct query in the last 48 hours.
Figure 2: Server performance. 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.

4Rank

The server stands in the top 69% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k1 Oct7 Oct12 Oct18 Oct23 Oct29 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: force wipes only

The next wipe is expected Thursday 5 November, 19:00 UTC, in 7d 16h. The force wipe (high confidence).

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Wipe-day peak1players, last three wipes
Table 3: Coming wipes, as expected.
When (UTC)InKind
Thu 5 Nov, 19:007d 16hforce wipefw
Thu 3 Dec, 19:0035d 16hforce wipefw
00.250.50.751+0h+9h+19h+28h+38h+47h
Figure 4: The first 48 hours of its last wipes: players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

5.2History

Table 4: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Thu 1 Oct, 23:30fw27d ago 1 – running 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

No map picture published
Figure 5: The map: Procedural Map.
Table 5: The server's published settings.
Address46.110.130.11:28015
Region–
Max players4
Group limit8, the default
Wipe schedule–
Last wipe1 Oct 2026, 23:30 UTC
Hostname–
First seen1 Oct 2026
MapProcedural Map
Size–
Seed–

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are browse modded Rust servers [2] and next Rust wipe times [3].

Table 6: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
ShockRust | Blue | NoLimitno group limit · 155 on average28/500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average121/100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 117 on average32/225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average17/700
RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average4/200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average2/1000

Appendix AQuick answers

From the figures on this page.

About the server

A.1What location does Barley Ate Oilrig have?

A region is not published by Barley Ate Oilrig. The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. You will find it at 46.110.130.11:28015.

A.2How reliable is Barley Ate Oilrig, and is it currently online?

Barley Ate Oilrig is online at this time. Its uptime over the last full days (7 days) was 99%, with 167 of 168 hours online. The first record of it by Rust Statistics dates to 1 October 2026.

A.3What is the Rust version for Barley Ate Oilrig?

The version of Rust on Barley Ate Oilrig is network protocol 2634 and build 166494, and the operating system is Linux. Steam updates your game for you, but you must be on the same protocol to join.

Wipe schedule

A.4What schedule does Barley Ate Oilrig follow for wipes?

The only wipe for Barley Ate Oilrig is the monthly force wipe. On Thursday 5 November at 19:00 UTC the force wipe occurs, and that is when every Rust server, including this one, next wipes. 27 days 2 hours have passed since the current world was generated.

A.5How would you describe wipe day on Barley Ate Oilrig?

Recent wipes saw an average peak of 1 players. The crowd reached its maximum 0 hours after the latest wipe.

Population

A.6What is the rank of Barley Ate Oilrig among Rust servers?

The seven-day player-hours ranking puts Barley Ate Oilrig at #15,353, within the top 69% of ranked servers.

A.7How would you characterise the player activity on Barley Ate Oilrig?

The current population of Barley Ate Oilrig is 0, drawn from 4 slots. Averaged across the last seven days, the population is 0 players.

Tags, lists

A.8What do the tags associated with Barley Ate Oilrig signify?

gmrust (Game mode): Survival on standard Rust rules; mp4 (Max players): 4 slots are available; ts8 (Group limit): Teams are limited to 8, as the game defaults; v2634 (Protocol): Joining requires the same game version: protocol 2634; cs166494 (Build): Build 166494 is the one running; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): The region code is unset; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: plugins or settings modify the game: these are the tags Barley Ate Oilrig publishes, and the server browser reads them. Also in the tags: players now, the queue, and when the world was made; these appear at the top of this page.

A.9Where can Barley Ate Oilrig be found among the Rust Statistics lists and filters?

The Rust Statistics lists that Barley Ate Oilrig fits are: Modded Rust servers. It appears under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Rules, settings, map

A.10Which settings and rules are in force on Barley Ate Oilrig?

The name of Barley Ate Oilrig states no gather rate. At 8 players, the group limit equals the game's default. The mode is survival, which means gather, build and raid: the standard game. Players may raid and fight one another. The server browser lists it as Modded, where plugins or settings alter the game. Oxide plugins are running. VAC, Valve's anti-cheat, is enabled.

A.11What map is in use on Barley Ate Oilrig?

The game generates the map on Barley Ate Oilrig; that format is procedural.

How to join

A.12What steps are required to join Barley Ate Oilrig?

Enter client.connect 46.110.130.11:28015 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you.

Appendix BServer tags

What each of the server's tags means. Published as mp4,ptrak,$r?,v2634,gmrust,cs166494,ts8,^o^z.

Table 7: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Survival on standard Rust rules.
mp4Max players. 4 slots are available.
ts8Group limit. Teams are limited to 8, as the game defaults.
v2634Protocol. Joining requires the same game version: protocol 2634.
cs166494Build. Build 166494 is the one running.
ptrakNetworking. Networking runs on RakNet, the game's standard layer.
$r?Region code. The region code is unset.
Mods and access
^oOxide. The plugin framework in use is Oxide (uMod).
^zModded. Modded listing: plugins or settings modify the game.

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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Browse modded Rust servers. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Next Rust wipe times. ruststatistics.org/rust-servers-wiping-today-list.