Local forecast
GridControlTest
Offline 176.224.105.75:29261 checked 16d ago
Current conditions
observed 16d agoplayers now
0% full
- 7-day average
- 0
- peak –
- Rank
- #15,519
- top 71%
- Last wipe
- 27d ago
- no schedule published
- Next wipe
- –
- no wipe seen yet
Next wipe
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
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
daily · 1 is bestTop 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.
Past weather: its wipes
newest first| 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. The weather: fair when the crowd held, showers when it halved within two days, a storm for the force wipe.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageAbout the server
How reliable is GridControlTest, and is it online now?
Right now GridControlTest is down; the last sighting was 16 days 21 hours ago. In the last 7 full days it stayed up 0 of 168 hours, 0% of the time. It came to Rust Wipe Stats's notice first on 10 October 2026.
Where does GridControlTest run from?
For GridControlTest, no region is published. Where a server says it is, that is what Rust Wipe Stats shows; it does not look up the machine's actual location. 176.224.105.75:29261 is its address.
What version of Rust is running on GridControlTest?
On GridControlTest you will find Rust network protocol 2634 and build 167584, hosted on Windows. Steam updates your game for you; the protocol must match to join.
Lists and tags
Which meaning sits behind each tag on GridControlTest?
These are the tags GridControlTest publishes for the game's server browser to read: gmrust (Game mode): Survival as standard Rust plays; mp1 (Max players): It holds 1 players; ts8 (Group limit): Teams are at the game default of 8; v2634 (Protocol): Game protocol 2634 applies; match it to join; cs167584 (Build): Build 167584 is installed here; ptrak (Networking): The standard RakNet layer carries the connection; $r? (Region code): The region field is left blank; ^o (Oxide): Oxide, known too as uMod, provides the plugin framework; ^z (Modded): Modded is its category, with plugins or settings changing the game. At the top of this page you can see the player count now, the queue and the world's creation time, all from the tags.
Which Rust Wipe Stats filters and lists carry GridControlTest?
These Rust Wipe Stats lists include GridControlTest: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules and settings
Which map is in use on GridControlTest?
The game generates the map on GridControlTest, a procedural one.
Which settings and rules are in force on GridControlTest?
No gather rate appears in the name GridControlTest. No group setting is published, so the game default of 8 players applies. It plays as survival, gathering, building and raiding, as the game normally plays. Both PvP and raiding are on. Plugins or settings change the game here, and the browser files it under Modded. Plugin frameworks in use: Oxide. Valve anti-cheat (VAC) runs on this server.
Wipe schedule
On what schedule does GridControlTest wipe?
Its rhythm cannot be read yet, as too few of GridControlTest's wipes are on record. The next monthly force wipe, which every Rust server takes, is on Thursday 5 November at 19:00 UTC. The world it is running now dates from 27 days 14 hours.
Population history
Is GridControlTest busy or quiet?
The last time GridControlTest was seen was 16 days 21 hours ago; it is offline right now.
What position does GridControlTest hold among Rust servers?
The last seven days of player hours rank GridControlTest at #15,519, in the top 71% of ranked servers.
Getting in
What steps let you join GridControlTest?
Open the console in Rust with F1, then type client.connect 176.224.105.75:29261 to join. On this page, Launch Rust does the same through Steam.