Offline 143.255.105.111:28015 checked 1d ago
gatovaca
Connect
srv = rust.server("143.255.105.111: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 55% 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 3h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 3h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 3h | Thu 3 Dec, 19:00 UTC | FW force wipe |
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 27 Oct, 22:14 UTC1d ago | NaN | NaN | running | 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 143.255.105.111:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 27 Oct 2026, 22:14 UTC
- hostname
- –
- first seen
- 13 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 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 88/700 |
| 1 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 86 on average | 229/700 |
| 2 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 25/1000 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|МОСКОВСКИЙ 26.10 | EU · groups of 16+ · monthly · 74 on average | 113/1000 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЙСКИЙ 28.10 | EU · groups of 16+ · monthly · 68 on average | 379/1000 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 29.10 | EU · groups of 16+ · monthly · 66 on average | 359/1000 |
Quick answers
From the figures on this page.
Population
How does gatovaca compare in the rankings?
Rank #12,266 on seven-day player hours for gatovaca, within the top 55% of all ranked servers.
What population does gatovaca carry?
gatovaca returns no live count at this refresh, having last been seen 39 hours ago. Over the last seven days it averaged 1 players and peaked at 1. The 48-hour sample puts the busiest hour at 23:00 UTC, averaging 1 players.
Server data
Which Rust version is gatovaca on?
Rust network protocol 2635 and build 168909 on Windows is what gatovaca runs. Steam updates your game for you, but the protocol must match to join.
How reliable is gatovaca, and is it up?
The latest sample has gatovaca offline, with a last sighting 39 hours ago. Uptime of 1% across the last 7 full days: 2 hours of 168. Rust Data logged it first on 13 October 2026.
Where does gatovaca sit?
There is no region published for gatovaca. Rust Data does not look up where the machine stands; it shows where a server says it is. 143.255.105.111:28015 is its address.
Map and rules
What rules and settings are recorded for gatovaca?
No gather rate appears in the name: gatovaca. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: gather, build, raid: the standard loop. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Carbon. Anti-cheat status: VAC on.
Which map has gatovaca loaded?
The game generates its map: procedural, on gatovaca.
Wipe data
When does gatovaca wipe, and how often?
Once a month gatovaca wipes, with the force wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. The world it runs now was generated 41 hours ago. The tags list wipes as monthly.
Lists and tags
Which lists on Rust Data hold gatovaca, and which filters?
The Rust Data lists that gatovaca fits are: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Monthly ^m, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last 3 days.
How should you read the server tags on gatovaca?
Read by the game's server browser, the tags gatovaca publishes are: gmvanilla (Game mode): The mode is vanilla survival; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): The plugin framework in use is 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 into gatovaca?
The manual route: launch Rust, F1, then client.connect 143.255.105.111:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.