RUST METRICSFlight deck · live data
Data live Servers11,855 Players81,723 Populated3,800 Fresh wipes 3 h365 Scan5 min
‹ All servers176.224.105.75:29271
Offline Full Queue Fresh wipe Wipe due No query

GridControlCircuitTest

Offline 176.224.105.75:29271 checked 16d ago

COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 8 16 24 32 PAX 0 /32

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,398top 71%
Last wipe–no schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players
No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server 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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k13 Oct14 Oct16 Oct17 Oct19 Oct20 Oct

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

PLAN

Wipe schedule

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

LOG

Wipes

newest first
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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

When does GridControlCircuitTest wipe?

To tell the rhythm of GridControlCircuitTest, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one.

Lists and filters

Which lists and filters on Rust Metrics show GridControlCircuitTest?

Rust Metrics lists featuring GridControlCircuitTest: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all.

Population

What position does GridControlCircuitTest hold among Rust servers?

Ranking for GridControlCircuitTest: #15,398 on seven-day player hours, top 71% of all ranked servers.

What is the population on GridControlCircuitTest?

Status for GridControlCircuitTest: offline. Last seen 16 days 7 hours ago.

Operator and location

What location is GridControlCircuitTest hosted in?

No region tag on GridControlCircuitTest. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 176.224.105.75:29271.

What is the uptime on GridControlCircuitTest, and is it online?

Reading: offline. GridControlCircuitTest last answered 16 days 7 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 13 October 2026.

Map and rules

What settings and rules apply on GridControlCircuitTest?

Reading the name gives no gather rate for GridControlCircuitTest. The group limit is not published. The mode is survival. Note the following: standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on GridControlCircuitTest?

Procedural map on GridControlCircuitTest, made by the game's generator.

Join

What do you do to join GridControlCircuitTest?

To join: start Rust, press F1 and type client.connect 176.224.105.75:29271. Or press Launch Rust here and Steam opens the game and connects you.