Offline 176.224.105.75:29261 checked 17d ago
GridControlTest
Connect
srv = rust.server("176.224.105.75:29262")
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
- 176.224.105.75:29261
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 21:31 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 · 151 on average | 162/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 128/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 191/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 96/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 88 on average | 234/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 349/350 |
Quick answers
From the figures on this page.
Player counts
How does GridControlTest compare in the rankings?
Player hours over seven days put GridControlTest at #15,519, in the top 71% of the ranked set.
What population does GridControlTest carry?
Offline now for GridControlTest, with the last sample 17 days 2 hours ago.
About the server
What is the Rust version on GridControlTest?
Version Rust network protocol 2634 and build 167584 on Windows is reported by GridControlTest. The protocol has to match before you can join, and Steam does the updating.
How reliable is GridControlTest, and is it online now?
GridControlTest is offline at this refresh; the last response came 17 days 2 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 10 October 2026.
Which location does GridControlTest run from?
For GridControlTest, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 176.224.105.75:29261 is its address.
Map and rules
Which rules apply on GridControlTest, and what settings?
The name GridControlTest carries no gather rate. The group limit sits at the default of 8 players. Recorded as survival, the base game, where you gather, build and raid. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has GridControlTest selected?
The game generates its map: procedural, on GridControlTest.
Wipe schedule
When does GridControlTest wipe, and on what schedule?
A rhythm cannot be read from the wipes of GridControlTest 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 27 days 19 hours ago.
Lists and tags
Which lists on Rust Data hold GridControlTest, and which filters?
The Rust Data lists that GridControlTest fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on GridControlTest?
The game's server browser reads these tags from GridControlTest: gmrust (Game mode): Survival play, standard Rust; mp1 (Max players): The server lists 1 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167584 (Build): The server runs build 167584; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
What is the way into GridControlTest?
The manual route: launch Rust, F1, then client.connect 176.224.105.75:29261. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.