testgbl
Offline 149.109.254.118:29843 checked 45d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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 bestWipe 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 | 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- 456/575
- 434/475
- 983/250
- 61/100
- 982/250
- 21/250
Quick answers
from the figures on this pageWipe timing
What wipe timing does testgbl follow?
The rhythm of testgbl's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 55 days 8 hours ago the current world was made.
Lists and filters
How should you read the tags on testgbl?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp67 (Max players): Slots: 67; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163794 (Build): The server runs game build 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set from testgbl. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show testgbl?
On Rust Metrics, testgbl sits in these lists: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Population
What position does testgbl hold among Rust servers?
Player hours over seven days put testgbl at #15,098, in the top – of all ranked servers.
What player count does testgbl carry?
Reading for testgbl: offline at this moment; last seen 45 days 9 hours ago.
Server details
Where does testgbl sit?
No region comes from testgbl. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 149.109.254.118:29843.
What Rust version is testgbl on?
Rust network protocol 2633 and build 163794 on Windows is the build testgbl runs. Matching protocol is required to join. Let Steam update your game.
How reliable is testgbl, and is it online now?
testgbl reports offline. The last reading came 45 days 9 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 14 September 2026, recorded by Rust Metrics.
Rules and settings
What settings and rules apply on testgbl?
No gather rate appears in the name: testgbl. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.
What map is testgbl on?
Procedural map on testgbl, made by the game's generator.
Connection
How do you connect to testgbl?
To join: start Rust, press F1 and type client.connect 149.109.254.118:29843. Or press Launch Rust here and Steam opens the game and connects you.