Fig. 1Players on GfG Test ServerRG-S6765-01 · Sheet 1 of 11
Fig. 2
Server performance
Server fpsWipe
EntitiesWipe
Memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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.
Fig. 2FPS, entities and memoryRG-S6765-02 · Sheet 2 of 11
Fig. 3
Rank
daily · 1 is best
RankRank in region
Top 30% of all ranked servers. Ranked on player hours over the last seven days.
Fig. 3Rank on player hours, dailyRG-S6765-03 · Sheet 3 of 11
Schedule
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 2h.
The force wipe · high confidence
usual gap2.7 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 1
Coming wipes
7d 2hThu 5 Nov, 19:00 UTCFW
35d 2hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Wed 21 OctMon 19 OctFri 2 Oct
Fig. 4Players each hour from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
ScheduleExpected wipesRG-S6765-04 · Sheet 4 of 11
Log
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Wed 28 Oct, 14:17 UTC1d ago
–
–
running
0
Wed 21 Oct, 20:47 UTC7d ago
1
halved by day 1
6.7 days
0
Mon 19 Oct, 21:40 UTC9d ago
2
–
2 days
0
Fri 2 Oct, 21:33 UTC26d ago
2
halved by day 16
17 days
0
Thu 1 Oct, 23:34 UTCFW27d ago
2
–
0.9 days
1
Mon 21 Sep, 22:40 UTC37d ago
4
halved by day 1
10 days
2
Sun 20 Sep, 22:15 UTC38d ago
4
–
1 days
2
Thu 17 Sep, 13:34 UTC42d ago
2
halved by day 1
3.4 days
0
Thu 17 Sep, 01:26 UTC42d ago
2
–
0.5 days
1
Mon 14 Sep, 22:54 UTC44d ago
4
halved by day 1
2.1 days
1
Mon 14 Sep, 00:56 UTC45d ago
4
–
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.
Table 1Wipe logRG-S6765-05 · Sheet 5 of 11
Similar assemblies
Similar servers
the same kind of game, then region, group limit, rate and wipes
Is GfG Test Server online, and what uptime has been recorded?
At this moment GfG Test Server is online. The uptime it reports puts the last restart at about 18 hours ago. 167 of 168 hours up over the last 7 full days, which is 99% of the time. On 13 September 2026 is when Rust Graphs first saw it.
2.
What does the recorded performance of GfG Test Server show?
The last 48 hours give an average of 14 server fps and a floor of 5. Counted at its highest: 123,427 entities, buildings, deployables and the rest of the world included. 3,863 MB is the memory peak. What players feel as lag is low fps together with a climbing entity count.
3.
In which location is GfG Test Server hosted?
There is no region published by GfG Test Server. No lookup of the machine's location is done: Rust Graphs shows where a server says it is. It is reached at 66.51.96.75:28010.
4.
On which Rust version is GfG Test Server running?
The platform is Linux and the version is Rust network protocol 2635 and build 168909 on GfG Test Server. To join, your game must be on the same protocol; Steam handles the update.
Population
5.
What player count is recorded on GfG Test Server?
Current player count on GfG Test Server: 0, of 50 slots. Averaged across seven days, the player count is 0, with a peak of 3. Over the last 48 hours the busiest hour was 23:00 UTC, at an average of 3 players.
6.
In the rankings, which position does GfG Test Server hold?
Within the top 30% of all ranked servers: GfG Test Server at #6,765 for player hours, seven days recorded.
Wipe times
7.
On GfG Test Server, what does the data show for wipe day?
An average of 2 players was recorded at the busiest point of its recent wipes. At 1 hours after the latest wipe the crowd was at its peak. The crowd stayed above half the peak until the next wipe in 0% of its recent wipes. In the other cases the crowd was below half by day 1.
8.
What wipe schedule has been recorded for GfG Test Server?
Once a month, with the force wipe, is when GfG Test Server wipes. On Thursday 5 November at 19:00 UTC the force wipe falls; that is the next wipe, and it wipes every Rust server. The current world has been in use since 26 hours ago. A wipe every month is the schedule its tags set out.
Settings
9.
Which rules and settings are recorded for GfG Test Server?
Gather rate for GfG Test Server: not stated in the name. The group limit is 8 players, the game's default. survival, the standard game: gather, build, raid, is the game mode. PvP and raiding are on. Plugins or settings change the game, and the browser lists it as Modded. Plugins run: Oxide. VAC is on: that is Valve's anti-cheat.
10.
What is the map for GfG Test Server?
Size 4,500 with seed 1337: that is the procedural map GfG Test Server runs, generated by the game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map. The name of the map reads: Custom Map.
Lists and filters
11.
On Rust Graphs, which lists and filters contain GfG Test Server?
The Rust Graphs lists that carry GfG Test Server are: Modded Rust servers. On the server list, these filters bring it up: 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.
12.
On GfG Test Server, what is meant by each tag?
The game's server browser reads these tags from GfG Test Server: gmrust (Game mode): Standard survival, as Rust plays; mp50 (Max players): Slots: 50; ts8 (Group limit): Teams are capped at 8, the default setting; v2635 (Protocol): Your game must match protocol 2635 to join; cs168909 (Build): 168909 is the game build; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): Region code not set; ^m (Monthly): Facepunch's force wipe brings a monthly wipe; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
Joining the server
13.
By what method do you join GfG Test Server?
Enter client.connect 66.51.96.75:28010 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you. You will find its website at https://discord.com/invite/55c8SAFSbq.
NotesAnswered from the figuresRG-S6765-10 · Sheet 10 of 11
Key
Server tags
what each one means
Published asmp50,ptrak,$r?,v2635,^m,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeStandard survival, as Rust plays.
mp50
Max playersSlots: 50.
ts8
Group limitTeams are capped at 8, the default setting.
v2635
ProtocolYour game must match protocol 2635 to join.
cs168909
Build168909 is the game build.
ptrak
NetworkingThe network layer is RakNet, the game's standard.
$r?
Region codeRegion code not set.
Wipe schedule
^m
MonthlyFacepunch's force wipe brings a monthly wipe.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; the listing is 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.