Online 46.110.130.11:28015 checked 7m ago
Barley Ate Oilrig
Connect
srv = rust.server("46.110.130.11:28017")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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. 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 bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 12h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 12h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 12h | Thu 3 Dec, 19:00 UTC | FW force wipe |
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.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 23:30 UTC FW27d ago | 1 | NaN | 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. 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 46.110.130.11:28015
- region
- –
- max players
- 4
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 23:30 UTC
- hostname
- –
- first seen
- 1 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 151 on average | 52/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 134/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 70/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 20/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 3/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 6/1000 |
Quick answers
From the figures on this page.
Population
How does Barley Ate Oilrig compare in the rankings?
Player hours over seven days put Barley Ate Oilrig at #15,341, in the top 69% of the ranked set.
How many players does Barley Ate Oilrig hold at once?
Barley Ate Oilrig reports 0 players at this refresh, with 4 slots configured. Over the last seven days it averaged 0 players.
About the server
What Rust version does Barley Ate Oilrig run?
The build is Rust network protocol 2634 and build 166494 on Linux, run by Barley Ate Oilrig. The protocol has to match before you can join, and Steam does the updating.
How reliable is Barley Ate Oilrig, and is it online now?
Online is the state at the latest refresh for Barley Ate Oilrig. Uptime of 99% across the last 7 full days: 167 hours of 168. Rust Data logged it first on 1 October 2026.
Which location does Barley Ate Oilrig run from?
For Barley Ate Oilrig, no region is published. 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 46.110.130.11:28015.
Map and rules
Which rules apply on Barley Ate Oilrig, and what settings?
You will not find a gather rate in the string Barley Ate Oilrig. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and gather, build, raid: the standard loop. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. Anti-cheat status: VAC on.
Which map has Barley Ate Oilrig selected?
Barley Ate Oilrig runs a procedural map, which the game generates.
Wipe data
When does Barley Ate Oilrig wipe, and on what schedule?
Once a month Barley Ate Oilrig wipes, with the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. A new world was started 27 days 6 hours ago, and that is the one in play.
On Barley Ate Oilrig, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 0 hours after it began.
Tags and filters
Which lists on Rust Data hold Barley Ate Oilrig, and which filters?
The Rust Data lists that Barley Ate Oilrig fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on Barley Ate Oilrig hold?
Read by the game's server browser, the tags Barley Ate Oilrig publishes are: gmrust (Game mode): Survival play, standard Rust; mp4 (Max players): The server lists 4 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs166494 (Build): Recorded game build: 166494; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
What is the way into Barley Ate Oilrig?
Enter client.connect 46.110.130.11:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.