Offline 79.127.128.118:28015 checked 24d ago
FERRUM TEST
Connect
srv = rust.server("79.127.128.118: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 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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
- 79.127.128.118:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 4 Oct 2026, 21:12 UTC
- hostname
- –
- first seen
- 5 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 | 24/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 127/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 122 on average | 44/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 97 on average | 9/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 94 on average | 28/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 51/200 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does FERRUM TEST rank?
Over the last seven days FERRUM TEST sits at #15,966 on player hours, in the top 71% of ranked servers.
How many players does FERRUM TEST hold at once?
The current row shows FERRUM TEST offline; the last response was 24 days 19 hours ago.
About the server
Which Rust version is FERRUM TEST on?
Rust network protocol 2634 and build 166652 on Linux is what FERRUM TEST runs. Steam updates your game for you, but the protocol must match to join.
How reliable is FERRUM TEST, and is it up?
Offline now for FERRUM TEST, last seen 24 days 19 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 5 October 2026.
Where does FERRUM TEST sit?
No region is published by FERRUM TEST. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 79.127.128.118:28015 is its address.
Settings and map
Which settings and rules does FERRUM TEST run?
No gather rate appears in the name: FERRUM TEST. The group limit sits at the default of 8 players. survival is the game mode here, and the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Carbon. VAC, Valve's anti-cheat, is enabled.
What is the map on FERRUM TEST?
A procedural map runs on FERRUM TEST, generated by the game.
Wipe schedule
On what schedule does FERRUM TEST wipe?
A rhythm cannot be read from the wipes of FERRUM TEST on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 25 days 7 hours ago.
Tags, lists
Which lists on Rust Data hold FERRUM TEST, and which filters?
The Rust Data lists that FERRUM TEST fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the server tags on FERRUM TEST?
The game's server browser reads these tags from FERRUM TEST: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166652 (Build): Recorded game build: 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): Plugin framework: Carbon. 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.
Connecting
What is the way to join FERRUM TEST?
The manual route: launch Rust, F1, then client.connect 79.127.128.118:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.