Online 136.61.101.213:28015 checked 8m ago
fatche.at test server
Connect
srv = rust.server("136.61.101.213:27017")
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 best
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 12 Oct, 03:59 UTC17d ago | 1 | NaN | running | 0 |
| 1 | Tue 15 Sep, 23:07 UTC43d ago | 1 | halved by day 1 | 26.2 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.
display(srv.map, srv.info())
Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 136.61.101.213:28015
- region
- –
- max players
- 40
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 12 Oct 2026, 03:59 UTC
- hostname
- –
- first seen
- 13 Sep 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 | 113/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 135/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 188/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 95 on average | 72/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 90 on average | 208/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 349/350 |
Quick answers
From the figures on this page.
Population
What position does fatche.at test server take in the server rankings?
Rank #15,289 on seven-day player hours for fatche.at test server, within the top 69% of all ranked servers.
How full does fatche.at test server run?
fatche.at test server reports 0 players at this refresh, with 40 slots configured. Over the last seven days it averaged 0 players.
About the server
What Rust version does fatche.at test server run?
The build is Rust network protocol 2634 and build 167398 on Linux, run by fatche.at test server. The protocol has to match before you can join, and Steam does the updating.
How reliable is fatche.at test server, and is it up?
The current sample puts fatche.at test server online. Uptime of 99% across the last 7 full days: 167 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.
Which location does fatche.at test server run from?
No region is published by fatche.at test server. Rust Data does not look up where the machine stands; it shows where a server says it is. 136.61.101.213:28015 is its address.
Settings and map
Which settings and rules does fatche.at test server run?
You will not find a gather rate in the string fatche.at test server. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Carbon. VAC is not running; Valve's anti-cheat is off.
Which map has fatche.at test server selected?
The game generates its map: procedural, on fatche.at test server.
Wipes and dates
When does fatche.at test server wipe, and how often?
A rhythm cannot be read from the wipes of fatche.at test server on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 17 days 15 hours ago.
On fatche.at test server, what happens on wipe day?
Recent wipes averaged 1 players at their peak. The crowd on the latest wipe topped out 1 hours after it began. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. Otherwise the crowd fell below half by day 1.
Lists and tags
Which Rust Data filters and lists contain fatche.at test server?
The Rust Data lists that fatche.at test server 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.
Which meanings do the tags on fatche.at test server hold?
Read by the game's server browser, the tags fatche.at test server publishes are: gmrust (Game mode): Survival play, standard Rust; mp40 (Max players): 40 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167398 (Build): The server runs build 167398; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
How can I connect to fatche.at test server?
The manual route: launch Rust, F1, then client.connect 136.61.101.213:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.