GridControlTest
Offline 176.224.105.75:29261 checked 17d ago
Measurements
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| 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.
Quick answers
Player counts
How does GridControlTest rank against other Rust servers?
Over the past week it ranks #15,519 for player hours, which puts GridControlTest in the top 71% of all ranked servers.
How busy is GridControlTest?
GridControlTest is offline at this count; we last saw it 17 days 12 hours ago.
Tags
What do the server tags on GridControlTest mean?
What the game's server browser reads from GridControlTest is this set of tags: gmrust (Game mode): The game mode is standard Rust survival; mp1 (Max players): 1 slots are available; ts8 (Group limit): 8 per team is the default limit; v2634 (Protocol): Your game needs the same version, protocol 2634, to join; cs167584 (Build): Game build: 167584; ptrak (Networking): The standard network layer, RakNet, is in use; $r? (Region code): No region code is set; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by plugins or settings, so it is listed under Modded. Player count now, queue length and the making of the world all sit in the tags as well, and the top of this page shows them.
Which Rust Population lists and filters include GridControlTest?
GridControlTest appears among the Rust Population lists that follow: Modded Rust servers, counted. Filter the server list by Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more and it will show up.
Wipe notes
What is the wipe schedule on GridControlTest?
The record holds too few of GridControlTest's wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 28 days 6 hours ago the current world was made.
Map and rules
Which map does GridControlTest run?
A procedural map, generated by the game, is in use on GridControlTest.
What are the rules and settings on GridControlTest?
Nothing in GridControlTest's name says how gather works. No limit is set beyond the standard 8 players per group. This server runs survival, raid, build and gather: the standard game. Fighting and raiding between players is allowed. The server browser files it under Modded, where plugins or settings alter the game. The plugins it runs are Oxide. The anti-cheat VAC from Valve is enabled.
Server details
Which version of Rust does GridControlTest run?
Rust network protocol 2634 and build 167584 on Windows is what GridControlTest uses. Steam updates your game automatically, but you need the same protocol to join.
Is GridControlTest online, and how reliable is it?
We last saw GridControlTest 17 days 12 hours ago, and it is offline now. Over the last 7 full days, 0 of 168 hours were online, or 0%. On 10 October 2026, Rust Population saw it for the first time.
Where is GridControlTest located?
A region is not published by GridControlTest. The location a server claims is what Rust Population shows, not the place where the machine stands. You will find it at 176.224.105.75:29261.
Getting in
How do I join GridControlTest?
Either enter client.connect 176.224.105.75:29261 in Rust's console after pressing F1, or use Launch Rust here to open Rust through Steam and be connected.