Fig. 1Players on GOM TEST SERVER.RG-S6115-01 · Sheet 1 of 10
Fig. 2
Server performance
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-S6115-02 · Sheet 2 of 10
Fig. 3
Rank
daily · 1 is best
RankRank in region
Top 27% of all ranked servers, top 64% in EU. Ranked on player hours over the last seven days.
Fig. 3Rank on player hours, dailyRG-S6115-03 · Sheet 3 of 10
Schedule
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap1 daysbetween real wipes
on rhythm25%of its recent wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 2
The first 48 hours of its last wipes
Fri 23 OctThu 22 OctWed 21 Oct
Fig. 4Players each hour from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 2, 9 hours in.
ScheduleExpected wipesRG-S6115-04 · Sheet 4 of 10
Log
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 23 Oct, 15:38 UTC5d ago
2
–
running
0
Thu 22 Oct, 12:54 UTC6d ago
2
–
1.1 days
0
Wed 21 Oct, 23:35 UTC7d ago
2
–
0.6 days
0
Wed 14 Oct, 23:49 UTC14d ago
3
halved by day 2
7 days
0
Wed 14 Oct, 02:19 UTC15d ago
3
–
0.9 days
0
Mon 12 Oct, 20:38 UTC16d ago
1
–
1.2 days
0
Mon 12 Oct, 01:25 UTC17d ago
1
–
0.8 days
0
Sun 11 Oct, 18:57 UTC17d ago
1
–
0.3 days
0
Fri 2 Oct, 02:02 UTC27d ago
2
halved by day 2
9.7 days
0
Sun 27 Sep, 12:22 UTC31d ago
1
halved by day 2
4.6 days
0
Sat 26 Sep, 17:09 UTC32d ago
1
–
0.8 days
0
Fri 25 Sep, 19:52 UTC33d ago
1
–
0.9 days
0
Mon 14 Sep, 20:51 UTC44d ago
5
halved by day 8
11 days
0
Mon 14 Sep, 02:27 UTC45d ago
5
–
0.8 days
0
Sun 13 Sep, 14:16 UTC45d ago
1
–
0.5 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-S6115-05 · Sheet 5 of 10
Similar assemblies
Similar servers
the same kind of game, then region, group limit, rate and wipes
How reliable is GOM TEST SERVER., and is it online now?
Right now, GOM TEST SERVER. is recorded as online. About 7 hours ago is when it last restarted, measured from the uptime it reports. 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 GOM TEST SERVER. show?
30 server fps on average over the last 48 hours, and never under 30. Counted at its highest: 96,522 entities, buildings, deployables and the rest of the world included. Memory use peaked at 4,716 MB. Players feel low fps and a climbing entity count as lag.
3.
What location is recorded for GOM TEST SERVER.?
The EU tag is how GOM TEST SERVER. lists itself in Europe. No lookup of the machine's location is done: Rust Graphs shows where a server says it is. 168.100.161.195:33015 is its address.
4.
On which Rust version is GOM TEST SERVER. running?
On Linux, GOM TEST SERVER. runs Rust network protocol 2635 and build 168909. To join, your game must be on the same protocol; Steam handles the update.
Counts
5.
How many players are plotted on GOM TEST SERVER.?
0 of 100 slots on GOM TEST SERVER. are taken at the latest refresh. Averaged across seven days, the player count is 0, with a peak of 2.
6.
What rank has been recorded for GOM TEST SERVER.?
GOM TEST SERVER. also measures #1,873 in Europe on the same seven-day player-hour count, at #6,115 globally and in the top 27% of ranked servers.
Wipe data
7.
What happens on GOM TEST SERVER. on the day of a wipe?
At their busiest, its recent wipes drew 2 players on average. At 9 hours after the latest wipe the crowd was at its peak. Half that peak was held until the next wipe in 0% of its recent wipes. On the wipes where it did not hold, the crowd dropped below half by day 2.
8.
On GOM TEST SERVER., when do wipes occur?
GOM TEST SERVER. wipes at times that follow no pattern, so no next wipe can be predicted. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, and it wipes every Rust server. The world it runs now was made 5 days 17 hours ago.
Settings
9.
Which rules and settings are recorded for GOM TEST SERVER.?
Gather rate for GOM TEST SERVER.: not stated in the name. Eight players per group: the default for the game. survival, the standard game: gather, build, raid, is the game mode. Fighting and raiding between players are enabled. The server browser lists it under Modded: plugins or settings change the game. The plugin count is Oxide. Anti-cheat: VAC, from Valve, is on.
10.
On which map is GOM TEST SERVER. played?
Seed 240001 and size 4,950 define the procedural map GOM TEST SERVER. generates in game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map. Recorded map name: Custom Map.
Lists and filters
11.
Where does GOM TEST SERVER. appear among the Rust Graphs lists and filters?
The Rust Graphs lists that carry GOM TEST SERVER. are: Europe servers, plotted and Modded Rust servers. On the server list, these filters bring it up: Region: Europe; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
12.
Which meaning is attached to each tag on GOM TEST SERVER.?
gmrust (Game mode): Standard survival, as Rust plays; mp100 (Max players): The slot count is 100; ts8 (Group limit): The team limit is 8, which is the game default; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): 168909 is the game build; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is recorded; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it is listed under Modded; EU (Europe): The server browser lists it under Europe are the tags GOM TEST SERVER. publishes; the game's server browser reads them. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.
Connect
13.
What is the way to connect to GOM TEST SERVER.?
Enter client.connect 168.100.161.195:33015 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. https://discord.com/invite/grumpyoldman is its website.
NotesAnswered from the figuresRG-S6115-09 · Sheet 9 of 10
Key
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,EU,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeStandard survival, as Rust plays.
mp100
Max playersThe slot count is 100.
ts8
Group limitThe team limit is 8, which is the game default.
v2635
ProtocolJoin only if your game is on protocol 2635.
cs168909
Build168909 is the game build.
ptrak
NetworkingThe network layer is RakNet, the game's standard.
$r?
Region codeNo region code is recorded.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings change the game, so it is listed under Modded.
Region
EU
EuropeThe server browser lists it under Europe.
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.