testgbl

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 45d ago · 94.98.39.42:29843

Abstract

We describe the public Rust server testgbl, reached at 94.98.39.42:29843. It is offline at the last check, against a seven-day mean of 0¹. It ranks #15,121 of all servers. It last wiped 55d ago.

Keywordsrust server

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.

Measure	Value	Note
Players now	0/67	0% full
In the queue	0	no queue
Seven-day mean	0	peak –
Rank²	#15,121	no region published
Last wipe	55d ago	no schedule published
Next wipe³	–	no wipe seen yet

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

No hourly history yet.

Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory⁴. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure

range

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

Figure 2: 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.

4Rank

Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region

Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule

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

5.2History

Table 2: Every wipe recorded, newest first.

Wiped (UTC)	Peak	Crowd	Lasted	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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

No map picture published

Figure 4: The map: Procedural Map.

Table 3: The server's published settings.

Address	`94.98.39.42:29843`
Region	–
Max players	67
Group limit	8, the default
Wipe schedule	–
Last wipe	4 Sep 2026, 07:34 UTC
Hostname	–
First seen	14 Sep 2026
Map	Procedural Map
Size	–
Seed	–

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are player-run rust server list [2] and next Rust wipe times [3].

Table 4: Similar servers: the same kind of game, then region, group limit, rate and wipes.

Server	Players
Rusty Moose \|EU Mondays\|EU · groups of 12+ · weekly · 508 on average	239/275
Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average	318/350
Rusty Moose \|EU Main\|EU · groups of 12+ · weekly · 282 on average	782/1000
Rustafied.com - EU FridayEU · groups of 16+ · weekly · 277 on average	48/100
Rustoria.co - EU MainEU · groups of 16+ · weekly · 266 on average	895/950
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 240 on average	748/800

Appendix AQuick answers

From the figures on this page.

About the server

A.1What is the location of testgbl?

No region is published by testgbl. The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. You will find it at 94.98.39.42:29843.

A.2How reliable is testgbl, and is it currently online?

testgbl is currently offline, with the last sighting 45 days 17 hours ago. Of the 168 hours in the last 7 full days, 0 were served, an availability of 0%. It was first observed on 14 September 2026 by Rust Statistics.

A.3What version of Rust is run on testgbl?

testgbl is running Rust network protocol 2633 and build 163794 on the Windows operating system. Steam updates your game for you, but you must be on the same protocol to join.

Wipe timing

A.4On what cycle does testgbl wipe?

The record of testgbl's wipes is not yet sufficient to establish its rhythm. Wiping is compulsory for every Rust server at the monthly force wipe, the next of which is Thursday 5 November at 19:00 UTC. The current world has been running for 55 days 13 hours.

Player count

A.5What position does testgbl occupy in the ranking of Rust servers?

Ranked by player hours across seven days, testgbl holds #15,121, in the top – of all ranked servers.

A.6How would you characterise the player activity on testgbl?

At this moment testgbl is offline, having last been seen 45 days 17 hours ago.

Tags, lists

A.7What is the meaning of the tags on testgbl?

Tags from testgbl, read by the game's server browser, are gmrust (Game mode): This is survival as standard Rust plays; mp67 (Max players): 67 slots are available; ts8 (Group limit): The team cap is 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to connect; cs163794 (Build): The game build is 163794; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region code is unset. Also in the tags: players now, the queue, and when the world was made; these appear at the top of this page.

A.8Where can testgbl be found among the Rust Statistics lists and filters?

The Rust Statistics lists that testgbl fits are: Rust community servers, measured. These filters on the server list return it: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Rules, settings, map

A.9Under what rules and settings does testgbl operate?

Its name carries no gather rate for testgbl. No cap is given beyond the game's default of 8 players per group. survival is the game mode here; gather, build and raid: the standard game. Combat and raiding against other players are allowed. The server browser lists it under Community. VAC is active: that is Valve's anti-cheat.

A.10What map is in use on testgbl?

On testgbl the terrain is procedural, built by the game itself.

Connection

A.11What is the process for joining testgbl?

Press F1 inside Rust to open the console and enter client.connect 94.98.39.42:29843. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp67,ptrak,$r?,v2633,gmrust,cs163794,ts8.

Table 5: The server's tags and their meanings.

Tag	Meaning
Game
`gmrust`	Game mode. This is survival as standard Rust plays.
`mp67`	Max players. 67 slots are available.
`ts8`	Group limit. The team cap is 8, which is the game default.
`v2633`	Protocol. Your game must run protocol 2633 to connect.
`cs163794`	Build. The game build is 163794.
`ptrak`	Networking. The network layer is RakNet, standard for the game.
`$r?`	Region code. The region code is unset.

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.

References

[1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
[2]Rust Statistics. Player-run rust server list. ruststatistics.org/top-rust-community-servers.
[3]Rust Statistics. Next Rust wipe times. ruststatistics.org/rust-servers-wiping-today-list.