Offline 40.76.191.131:28015 checked 6d ago
Takaro Dev
Connect
srv = rust.server("40.76.191.131: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 best
Top 69% 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
- 40.76.191.131:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 22 Oct 2026, 17:20 UTC
- hostname
- –
- first seen
- 22 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 · 157 on average | 53/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 125/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 44/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 92 on average | 54/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 8/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 8/1000 |
Quick answers
From the figures on this page.
Population data
What position does Takaro Dev take in the server rankings?
Rank #15,344 on seven-day player hours for Takaro Dev, within the top 69% of all ranked servers.
How full does Takaro Dev run?
Takaro Dev returns no live count at this refresh, having last been seen 6 days 6 hours ago. Over the last seven days it averaged 0 players.
About the server
Which Rust version is Takaro Dev on?
Rust network protocol 2634 and build 167781 on Linux is what Takaro Dev runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is Takaro Dev, and is it online now?
Offline now for Takaro Dev, last seen 6 days 6 hours ago. Over the last 5 full days the hours up number 0 of 120, 0%. Its earliest recorded date in Rust Data is 22 October 2026.
In which location is Takaro Dev hosted?
No region is published by Takaro Dev. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 40.76.191.131:28015 is its address.
Settings and map
Which settings and rules does Takaro Dev run?
No gather rate appears in the name: Takaro Dev. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Carbon. Anti-cheat status: VAC off.
Which map has Takaro Dev selected?
A procedural map runs on Takaro Dev, generated by the game.
Wipe data
When does Takaro Dev wipe, and on what schedule?
A rhythm cannot be read from the wipes of Takaro Dev on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 6 days 6 hours ago, and that is the one in play.
Tags, lists
Where does Takaro Dev appear among Rust Data lists and filters?
The Rust Data lists that Takaro Dev fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.
How should you read the server tags on Takaro Dev?
Read by the game's server browser, the tags Takaro Dev publishes are: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): Slot count: 10; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): Runs on Carbon for plugins. 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
What is the way into Takaro Dev?
The manual route: launch Rust, F1, then client.connect 40.76.191.131:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.