Working its way up from the back of the class: #15,126 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
52/ 100
D
Moving up: up 728 places this week.
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.
AveragePeakWipe
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.
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.
Rank
daily · 1 is best
RankRank in region
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·W·F···
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 20h.
The force wipe · high confidence
usual gap2.4 daysbetween real wipes
wipe-day peak0players, last three wipes
Coming wipes
7d 20hThu 5 Nov, 19:00 UTCFW
35d 20hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Thu 1 OctTue 29 Sep
Players each hour, from the hour of the wipe. The latest peaked at 1, 23 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 1 Oct, 17:36 UTCFW27d ago
1
–
running
0
Tue 29 Sep, 08:46 UTC29d ago
0
–
2.4 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
Geo TEST SERVER leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. 195.60.166.112:28015 is the address to use.
How reliable is Geo TEST SERVER, and is it up?
The server is down: Geo TEST SERVER is offline now, with the last sighting 12 days 22 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. The first sighting by Rust Server Score was on 13 September 2026.
On what Rust version does Geo TEST SERVER sit?
Rust network protocol 2634 and build 166640 on Linux is what Geo TEST SERVER runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does Geo TEST SERVER reset?
Geo TEST SERVER wipes with the force wipe and at no other time. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. It has been running its current world for 27 days 4 hours. Its tags record that it wipes monthly.
What should you expect from wipe day on Geo TEST SERVER?
Recent wipes have peaked at 0 players on average. Peak numbers came 23 hours into the latest wipe.
Population
Where does Geo TEST SERVER sit among Rust servers?
Over the last seven days, Geo TEST SERVER has #15,126 for player hours, in the top 70% of all ranked servers.
What does the population on Geo TEST SERVER look like?
The last sighting of Geo TEST SERVER was 12 days 22 hours ago, and it is offline right now.
Lists and filters
How should you read the tags on Geo TEST SERVER?
You'll see Geo TEST SERVER tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp150 (Max players): 150 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166640 (Build): The game build is 166640; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^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.
Where does Geo TEST SERVER appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Geo TEST SERVER among them: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Server rules
Which rules does Geo TEST SERVER enforce, and what are its settings?
You will find no gather rate in the name of Geo TEST SERVER. The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. VAC, Valve's anti-cheat, is enabled.
Which map is in play on Geo TEST SERVER?
Geo TEST SERVER runs a game-generated procedural map at size 4,500, seed 1337. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map. The name of the map reads: discord.gg/RenegadeRust.
Getting in
How do you get onto Geo TEST SERVER?
Enter client.connect 195.60.166.112: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 asmp150,ptrak,$r?,v2634,^m,gmrust,cs166640,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp150
Max players150 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166640
BuildThe game build is 166640.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
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).