Rust HeatmapInfrared · players
IR live Players101,018 Servers11,889 Warm3,946 Fresh wipes · 3h400 Frameevery 5 min
‹ All serversThermal scan
REC Thermal scan · 48 h Sp1 0° now Linear · 0–1° · slots

GridControlTest

Offline 176.224.105.75:29261 checked 17d ago

moddedoxide
Sp1 · players now 0/ 1
0% full
Li1 · players, the last 48 hours · hourly average, UTC
No hourly readings in the last 48 hours
0
7-day average
peak –
#15,519
rank
top 71%
27d ago
last wipe
no schedule published
–
next wipe
no wipe seen yet
UTC checked 17d ago

Li2Players

No hourly history yet.

Hourly average and peak, UTC.

Li3Server performance

This server has not answered a direct query in the last 48 hours.

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.

Li4Rank

daily · 1 is best
RankRank in region
15k10k15k20k10 Oct12 Oct14 Oct15 Oct17 Oct19 Oct

Top 71% of all ranked servers. Ranked on player hours over the last seven days.

Bx1Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Bx2Wipes

newest first · each peak a flare-up, on one √ span to its biggest
WipedPeakCrowdLastedPlayers 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.

Bx6Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit
no group limit · 151 on average
157 / 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10
EU · groups of 8+ · weekly · 128 on average
122 / 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10
EU · groups of 16+ · weekly · 118 on average
191 / 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10
EU · groups of 16+ · monthly · 94 on average
97 / 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10
EU · groups of 16+ · monthly · 88 on average
229 / 700
RustSpain.com | EU Main
EU · groups of 12+ · weekly · 84 on average
346 / 350

LogQuick answers

from the figures on this page

Wipe day

What is the wipe schedule on GridControlTest?

Its rhythm cannot yet be told: too few of GridControlTest's wipes are on record. Thursday 5 November at 19:00 UTC is the next monthly force wipe, when every Rust server wipes. The world in play now was made 27 days 19 hours ago.

Player counts

How busy is GridControlTest?

The last time GridControlTest was seen was 17 days 2 hours ago, and it is offline now.

How does GridControlTest rank against other Rust servers?

The top 71% of ranked servers includes GridControlTest, at #15,519 for player hours over the last seven days.

Rules and settings

Which map does GridControlTest run?

The game generates the procedural map on GridControlTest.

What are the rules and settings on GridControlTest?

No gather rate appears in the name GridControlTest. Groups can contain up to 8 players, the default in the game. The server runs survival, gather, build and raid in the standard game. Players can fight each other, and raids are allowed. The server browser lists it as Modded: plugins or settings change the game. Oxide plugins run on this server. Anti-cheat: Valve's VAC is on.

Location and uptime

Which version of Rust does GridControlTest run?

Rust network protocol 2634 and build 167584 on Windows is what GridControlTest runs. Steam updates your game for you, and the protocol has to match for you to join.

Is GridControlTest online, and how reliable is it?

GridControlTest is down just now; the last sighting was 17 days 2 hours ago. 0 of 168 hours up over the last 7 full days, which is 0%. It first appears in Rust Heatmap records on 10 October 2026.

Where is GridControlTest located?

Nothing about a region comes from GridControlTest. What Rust Heatmap shows is where a server says it is. Where the machine stands is not looked up. You can reach it at 176.224.105.75:29261.

Lists and filters

Which Rust Heatmap lists and filters include GridControlTest?

The Rust Heatmap lists that GridControlTest fits are: Modded Rust servers, by live population. These are the filters that return it on the list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

What do the server tags on GridControlTest mean?

These are the tags GridControlTest publishes for the game's server browser to read: gmrust (Game mode): Rust survival, standard rules; mp1 (Max players): This server has 1 slots; ts8 (Group limit): At most 8 per team: the default the game ships with; v2634 (Protocol): To join, run the same version: game protocol 2634; cs167584 (Build): Build 167584; ptrak (Networking): The network layer is RakNet, the game's standard one; $r? (Region code): A region code is not set; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Settings or plugins alter the game, which puts it under Modded. Also in the tags, shown at the top of this page: players now, the queue and the time the world was made.

Connect

How do I join GridControlTest?

To join by console, open it with F1 in Rust and enter client.connect 176.224.105.75:29261. Or press Launch Rust on this page, which connects you through Steam.

KeyServer tags

what each one means

Published as mp1,ptrak,$r?,v2634,gmrust,cs167584,ts8,^o^z

Game

gmrust
Game mode Rust survival, standard rules.
mp1
Max players This server has 1 slots.
ts8
Group limit At most 8 per team: the default the game ships with.
v2634
Protocol To join, run the same version: game protocol 2634.
cs167584
Build Build 167584.
ptrak
Networking The network layer is RakNet, the game's standard one.
$r?
Region code A region code is not set.

Mods and access

^o
Oxide Plugins run through Oxide (uMod).
^z
Modded Settings or plugins alter the game, which puts it under Modded.

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.