Working its way up from the back of the class: #16,450 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
48/ 100
D
Slipped a little: down 666 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); standing is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
No daily history yet.
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
Average fpsLowest fpsWipe
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
Average fpsLowest fpsWipe
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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 25 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe 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
classmates: the same kind of game, then region, group limit, rate and wipes
GSM Settings Test 334 leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 155.138.209.228:28015.
Is GSM Settings Test 334 up, and how steady is its uptime?
At this moment, GSM Settings Test 334 is offline; the last time it was seen was 33 days 12 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 25 September 2026.
On what Rust version does GSM Settings Test 334 sit?
The server GSM Settings Test 334 is on Rust network protocol 2633 and build 165217 under Windows. To join, your game must use the same protocol; Steam handles the update.
Resets
On what schedule does GSM Settings Test 334 reset?
GSM Settings Test 334 has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 33 days 14 hours.
Population
What position does GSM Settings Test 334 hold in the rankings?
Over the last seven days, GSM Settings Test 334 has #16,450 for player hours, in the top 71% of all ranked servers.
Is GSM Settings Test 334 a busy server?
GSM Settings Test 334 is offline at the moment; the last time it was seen was 33 days 12 hours ago.
Lists and filters
What is meant by the tags on GSM Settings Test 334?
You'll see GSM Settings Test 334 tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): Its slot count is 50; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs165217 (Build): The game build is 165217; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which Rust Server Score filters and lists feature GSM Settings Test 334?
Rust Server Score lists that include GSM Settings Test 334: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
Which rules does GSM Settings Test 334 enforce, and what are its settings?
Nothing in the name of GSM Settings Test 334 states a gather rate. The default of 8 players applies as the group cap. It runs survival, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
Which map is in play on GSM Settings Test 334?
A procedural map of size 2,000 and seed 1494663522, generated by the game, is what GSM Settings Test 334 runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
What is the way to join GSM Settings Test 334?
Enter client.connect 155.138.209.228:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2633,gmrust,cs165217,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max playersIts slot count is 50.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs165217
BuildThe game build is 165217.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it under 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.
A term to build on. Strongest in momentum (D); standing is the one to work on (F).