Offline 95.182.82.154:28615 checked 3d ago
COOKING-ISOLATED-TEST
Connect
srv = rust.server("95.182.82.154:28616")
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 69% 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.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 25 Oct, 06:20 UTC3d ago | 0 | NaN | running | 0 |
| 1 | Thu 22 Oct, 13:49 UTC5d ago | 0 | NaN | 2.7 days | 0 |
| 2 | Mon 19 Oct, 10:27 UTC9d ago | 0 | NaN | 3.1 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
- 95.182.82.154:28615
- region
- –
- max players
- –
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 25 Oct 2026, 06:20 UTC
- hostname
- –
- first seen
- 10 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 · 155 on average | 176/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 120/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 115 on average | 189/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 131/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 15/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 51/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does COOKING-ISOLATED-TEST rank?
Rank #15,399 on seven-day player hours for COOKING-ISOLATED-TEST, within the top 69% of all ranked servers.
What population does COOKING-ISOLATED-TEST carry?
The current row shows COOKING-ISOLATED-TEST offline; the last response was 3 days 4 hours ago. Over the last seven days it averaged 0 players.
Server facts
What is the Rust version on COOKING-ISOLATED-TEST?
Rust network protocol 2634 and build 167781 on Windows is what COOKING-ISOLATED-TEST runs. Steam updates your game for you, but the protocol must match to join.
Is COOKING-ISOLATED-TEST up, and what does its uptime show?
Offline now for COOKING-ISOLATED-TEST, last seen 3 days 4 hours ago. Uptime of 1% across the last 7 full days: 2 hours of 168. The first row Rust Data holds for it is dated 10 October 2026.
In which location is COOKING-ISOLATED-TEST hosted?
There is no region published for COOKING-ISOLATED-TEST. Rust Data does not look up where the machine stands; it shows where a server says it is. 95.182.82.154:28615 is its address.
Map and rules
What rules and settings are recorded for COOKING-ISOLATED-TEST?
The name COOKING-ISOLATED-TEST carries no gather rate. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and 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. The VAC field reads off.
What is the map on COOKING-ISOLATED-TEST?
A procedural map runs on COOKING-ISOLATED-TEST, generated by the game.
Wipe schedule
When does COOKING-ISOLATED-TEST wipe, and on what schedule?
No next wipe can be predicted for COOKING-ISOLATED-TEST, which wipes at irregular times. 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 3 days 4 hours ago, and that is the one in play.
On COOKING-ISOLATED-TEST, what happens on wipe day?
Recent wipes averaged 0 players at their peak. The crowd on the latest wipe topped out 0 hours after it began.
Lists and tags
Which Rust Data filters and lists contain COOKING-ISOLATED-TEST?
The Rust Data lists that COOKING-ISOLATED-TEST fits are: Modded Rust servers. It appears under these filters on the server list: 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 COOKING-ISOLATED-TEST?
These tags are published by COOKING-ISOLATED-TEST and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp0 (Max players): The server lists 0 slots; 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): No region code is set; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^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.
Connecting
What is the way into COOKING-ISOLATED-TEST?
The manual route: launch Rust, F1, then client.connect 95.182.82.154:28615. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.