Station XX-15519 · no signal
GridControlTest
Offline 176.224.105.75:29261 checked 16d ago
- Players now
- 0/ 1
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,519
- top 71%
- Last wipe
- 27d ago
- no schedule published
- Next wipe
- –
- no wipe seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 1 slots
- Motion · 24 h
- M –not enough readings
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.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| No wipe seen yet. | ||||||
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageServer rules
Which map is running on GridControlTest?
A procedural map runs on GridControlTest, generated by the game.
Which settings and rules apply on GridControlTest?
No gather rate appears in the name of GridControlTest. The group limit is 8 players, the game's default. survival is the game mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. Its plugins are run through Oxide. Anti-cheat is on: VAC, from Valve.
Population
What is the current population on GridControlTest?
No players are recorded on GridControlTest at this moment; it is offline, and the last sighting was 16 days 23 hours ago.
How does GridControlTest rank against other Rust servers?
On player hours for the past week, GridControlTest sits at #15,519, which puts it inside the top 71% of every ranked server.
Server facts
How reliably does GridControlTest stay online?
No contact with GridControlTest right now, and the last recorded contact was 16 days 23 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. Its earliest appearance in the records of Rust Server Trends dates to 10 October 2026.
Which region does GridControlTest run from?
No region is published by GridControlTest. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 176.224.105.75:29261 is the address it uses.
Which Rust version is GridControlTest running?
GridControlTest is running Rust network protocol 2634 and build 167584 on a machine with Windows. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe day
On what timetable does GridControlTest run its wipes?
Too few wipes of GridControlTest are on record yet to show its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The present world dates from 27 days 16 hours.
Lists and tags
What do the server tags on GridControlTest mean?
The game's server browser reads the tags GridControlTest publishes: gmrust (Game mode): The game mode is standard Rust survival; mp1 (Max players): Slots: 1; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs167584 (Build): The game build is 167584; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does GridControlTest appear?
The Rust Server Trends lists that take in GridControlTest are: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How to join
How do you connect to GridControlTest?
Enter client.connect 176.224.105.75:29261 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.