GridControlTest
Key statistics
the figures behind the quote- Players now
- 0/ 1 0% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 0 peak –
- Rank
- #15,912 top 72%
- Rank · 7d ago
- – not ranked a week ago
- Last wipe
- 13d ago no schedule published
- Next wipe
- – no wipe seen yet
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 0 player hours, last seven days
- Map
- – Procedural Map
- First seen
- 10 Oct 2026 no hostname published
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 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | ShockRust | Blue | NoLimitno group limit · 128 on average | 47/300 | ▲+33+241.1% | |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 13.10EU · groups of 16+ · weekly · 108 on average | 46/225 | ▲+5+12.9% | |
| 3 | МИНИ-КАРТА 2Х | STORM | FPS+ 14.10EU · groups of 8+ · weekly · 90 on average | 88/100 | ▼−2−2.5% | |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 10.10EU · groups of 16+ · monthly · 88 on average | 8/1000 | ▼−8−49.5% | |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 08.10EU · groups of 16+ · monthly · 76 on average | 4/1000 | ▼−1−23.8% | |
| 6 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 11.10EU · groups of 16+ · monthly · 72 on average | 23/700 | ▪+0+0.4% |
Quick answers
from the figures on this pageMap and Rules
What settings and rules are in place on GridControlTest?
The name of GridControlTest carries no gather rate. Groups can contain a maximum of 8 players, the default for the game. It runs survival, gather, build and raid in the standard game. You can fight and raid other players. In the server browser it appears under Modded, with plugins or settings that change the game. Plugin count: Oxide. VAC, Valve's anti-cheat, is enabled.
Which map is played on GridControlTest?
GridControlTest uses a procedural map, which the game generates.
Population
Where does GridControlTest sit in the rankings?
In the top 72% of all ranked servers, GridControlTest is #15,912 on player hours over the last seven days.
How many players does GridControlTest have?
Right now, GridControlTest is offline; the last sighting was 2 days 7 hours ago. Average players over the last seven days: 0.
Wipe Cycle
When does GridControlTest schedule its wipes?
The record holds too few of GridControlTest's wipes to establish its rhythm. The monthly force wipe takes every Rust server. Next: Thursday 5 November at 19:00 UTC. This world has been running for 13 days 1 hours.
Server Details
What is the server location for GridControlTest?
For GridControlTest, no region is published. The location shown by Rust Analytics is the one a server states; it does not verify the machine's position. 176.224.105.75:29261 is its address.
GridControlTest runs which version of Rust?
Rust network protocol 2634 and build 167584 on Windows is what GridControlTest runs. Joining requires the same protocol on your game, which Steam updates.
What is the uptime and reliability of GridControlTest?
GridControlTest is down. The last time we saw it was 2 days 7 hours ago. The last 3 full days give 1% uptime, 1 hours on out of 72. The earliest Rust Analytics saw it was 10 October 2026.
Tags & Filters
How should you interpret the tags on GridControlTest?
Published by GridControlTest for the game's server browser to read: gmrust (Game mode): Survival in the standard Rust format; mp1 (Max players): Slot count: 1; ts8 (Group limit): 8 per team: the default setting, unchanged; v2634 (Protocol): To join, your game needs protocol 2634; cs167584 (Build): It runs build 167584; ptrak (Networking): RakNet, the network layer the game ships with; $r? (Region code): Region code: none set; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. The top of this page and the tags both show its players now, its queue and when its world was made.
On Rust Analytics, which lists and filters feature GridControlTest?
These Rust Analytics 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; Last wipe: In the last 2 weeks.
Connection
What is the process to join GridControlTest?
Type client.connect 176.224.105.75:29261 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you.
Server tags
what each one meansPublished as mp1,ptrak,$r?,v2634,gmrust,cs167584,ts8,^o^z
Game
gmrust
mp1
ts8
v2634
cs167584
ptrak
$r?
Mods and access
^o
^z
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.