Online 66.51.96.75:28010 checked 8m ago
GfG Test Server
Connect
srv = rust.server("66.51.96.75:28011")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is best
Top 30% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 7d 1h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 1h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 1h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Wed 28 Oct, 14:17 UTC1d ago | NaN | NaN | running | 0 |
| 1 | Wed 21 Oct, 20:47 UTC7d ago | 1 | halved by day 1 | 6.7 days | 0 |
| 2 | Mon 19 Oct, 21:40 UTC9d ago | 2 | NaN | 2 days | 0 |
| 3 | Fri 2 Oct, 21:33 UTC26d ago | 2 | halved by day 16 | 17 days | 0 |
| 4 | Thu 1 Oct, 23:34 UTC FW27d ago | 2 | NaN | 0.9 days | 1 |
| 5 | Mon 21 Sep, 22:40 UTC37d ago | 4 | halved by day 1 | 10 days | 2 |
| 6 | Sun 20 Sep, 22:15 UTC38d ago | 4 | NaN | 1 days | 2 |
| 7 | Thu 17 Sep, 13:34 UTC42d ago | 2 | halved by day 1 | 3.4 days | 0 |
| 8 | Thu 17 Sep, 01:26 UTC42d ago | 2 | NaN | 0.5 days | 1 |
| 9 | Mon 14 Sep, 22:54 UTC44d ago | 4 | halved by day 1 | 2.1 days | 1 |
| 10 | Mon 14 Sep, 00:56 UTC45d ago | 4 | NaN | 0.9 days | 0 |
# 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.
display(srv.map, srv.info())
About this server · in its own words
print(srv.description)
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 97/700 |
| 1 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 88 on average | 229/700 |
| 2 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 32/1000 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|МОСКОВСКИЙ 26.10 | EU · groups of 16+ · monthly · 74 on average | 144/1000 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЙСКИЙ 28.10 | EU · groups of 16+ · monthly · 70 on average | 327/1000 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 29.10 | EU · groups of 16+ · monthly · 66 on average | 512/1000 |
Quick answers
From the figures on this page.
Player counts
How does GfG Test Server compare in the rankings?
Rank #6,761 on seven-day player hours for GfG Test Server, within the top 30% of all ranked servers.
How many players does GfG Test Server hold at once?
The sample now reads 0 players for GfG Test Server, out of 50 slots. Over the last seven days it averaged 0 players and peaked at 3. Averaged by hour over 48 hours, 23:00 UTC is the busiest, at 3 players.
Server facts
How smoothly does GfG Test Server run?
Averaged over 48 hours: 14 server fps, never under 5. The entity count peaked at 123,427, covering buildings, deployables and the rest of the world. A high of 3,863 MB of memory used. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
What Rust version does GfG Test Server run?
Version Rust network protocol 2635 and build 168909 on Linux is reported by GfG Test Server. Steam updates your game for you, but the protocol must match to join.
Is GfG Test Server up, and what does its uptime show?
GfG Test Server reports itself online at the current refresh. Count back 19 hours from its reported uptime to get the last restart. Uptime of 99% across the last 7 full days: 167 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.
Where does GfG Test Server sit?
No region is published by GfG Test Server. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 66.51.96.75:28010.
Map and rules
Which rules apply on GfG Test Server, and what settings?
No gather rate appears in the name: GfG Test Server. The group limit sits at the default of 8 players. Game mode survival, with this note: the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. Anti-cheat status: VAC on.
What is the map on GfG Test Server?
GfG Test Server runs a procedural map of size 4,500 with seed 1337, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed. Custom Map is what the map name field says.
Wipe data
On what schedule does GfG Test Server wipe?
Once a month GfG Test Server wipes, with the force wipe. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. This world was created 26 hours ago. A monthly wipe schedule is published in its tags.
On GfG Test Server, what happens on wipe day?
The average peak over recent wipes is 2 players. The crowd on the latest wipe topped out 1 hours after it began. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. The drop under half arrived by day 1 in the other cases.
Tags and filters
Which Rust Data filters and lists contain GfG Test Server?
The Rust Data lists that GfG Test Server fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last 3 days.
How should you read the server tags on GfG Test Server?
The game's server browser reads these tags from GfG Test Server: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): Slot count: 50; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Connecting
How can I connect to GfG Test Server?
In Rust, F1 opens the console: type client.connect 66.51.96.75:28010. Launch Rust on this page does the same by opening the game through Steam and connecting. https://discord.com/invite/55c8SAFSbq is the website recorded for it.