Rust Data

rustdata.spaceservers173.171.5.27:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 173.171.5.27:28015 checked 20d ago

OL'Farts Gaming | Rust Plugin Testing

moddedoxide

Connect

srv = rust.server("173.171.5.27:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 0/100 # 0% full
7-day average 0 # peak –
rank #15,863 # top 72%
last wipe 20d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
This server has not answered a direct query in the last 48 hours.

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 best
RankRank in region
15k10k15k20k20 Sep25 Sep30 Sep5 Oct11 Oct16 Oct

Top 72% 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 gap9 daysbetween real wipes
on rhythm67%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Fri 9 OctWed 30 SepFri 25 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 9 Oct, 19:43 UTC20d ago 0 NaN running 1
1 Wed 30 Sep, 10:41 UTC29d ago 1 NaN 9.4 days 1
2 Fri 25 Sep, 19:14 UTC34d ago 1 held half 4.6 days 1
3 Wed 16 Sep, 18:10 UTC43d ago 1 held half 9 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.

display(srv.map, srv.info())

Map

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
173.171.5.27:28015
region
–
max players
100
group limit
8, the default
wipe schedule
–
last wipe
9 Oct 2026, 19:43 UTC
hostname
–
first seen
16 Sep 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 151 on average87/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average130/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average148/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 96 on average60/700
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 91 on average160/700
5RustSpain.com | EU MainEU · groups of 12+ · weekly · 85 on average348/350

Quick answers

From the figures on this page.

Player counts

Against other Rust servers, how does OL'Farts Gaming | Rust Plugin Testing rank?

Rank #15,863 on seven-day player hours for OL'Farts Gaming | Rust Plugin Testing, within the top 72% of all ranked servers.

How full does OL'Farts Gaming | Rust Plugin Testing run?

Offline now for OL'Farts Gaming | Rust Plugin Testing, with the last sample 20 days ago.

Server data

What Rust version does OL'Farts Gaming | Rust Plugin Testing run?

Version Rust network protocol 2634 and build 167398 on Windows is reported by OL'Farts Gaming | Rust Plugin Testing. Steam updates your game for you, but the protocol must match to join.

How reliable is OL'Farts Gaming | Rust Plugin Testing, and is it up?

OL'Farts Gaming | Rust Plugin Testing is offline at this refresh; the last response came 20 days ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 16 September 2026.

In which location is OL'Farts Gaming | Rust Plugin Testing hosted?

For OL'Farts Gaming | Rust Plugin Testing, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 173.171.5.27:28015 is its address.

Rules, settings, map

Which rules apply on OL'Farts Gaming | Rust Plugin Testing, and what settings?

You will not find a gather rate in the string OL'Farts Gaming | Rust Plugin Testing. The group limit sits at the default of 8 players. 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. VAC is running: Valve's anti-cheat is on.

Which map has OL'Farts Gaming | Rust Plugin Testing selected?

A procedural map runs on OL'Farts Gaming | Rust Plugin Testing, generated by the game.

Wipe data

On what schedule does OL'Farts Gaming | Rust Plugin Testing wipe?

OL'Farts Gaming | Rust Plugin Testing wipes on no fixed rhythm, so there is nothing to predict. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 20 days ago, and that is the one in play.

On OL'Farts Gaming | Rust Plugin Testing, what happens on wipe day?

Recent wipes averaged 1 players at their peak. Peak population on the latest wipe came 0 hours in. Half the peak or more was held to the next wipe in 100% of recent wipes.

Lists and tags

Which Rust Data filters and lists contain OL'Farts Gaming | Rust Plugin Testing?

On Rust Data, OL'Farts Gaming | Rust Plugin Testing appears in these lists: 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.

How should you read the server tags on OL'Farts Gaming | Rust Plugin Testing?

The game's server browser reads these tags from OL'Farts Gaming | Rust Plugin Testing: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): Slot count: 100; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs167398 (Build): Build number: 167398; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Join steps

How can I connect to OL'Farts Gaming | Rust Plugin Testing?

In Rust, F1 opens the console: type client.connect 173.171.5.27:28015. 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 mp100,ptrak,$r?,v2634,gmrust,cs167398,ts8,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp100
Max players Slot count: 100.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol To join, your game must run protocol 2634.
cs167398
Build Build number: 167398.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it sits under Modded.

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 101,030 players 11,856 servers online