Working its way up from the back of the class: #13,798 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
18/ 100
F
Lost ground: down 8,820 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); momentum 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.
AveragePeak
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.
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.
This server has not answered a direct query in the last 60 days.
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.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 61% 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
Next wipe Thursday 5 November, 19:00 UTC, in 8d 7h.
The 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
You'll find no region listed by Testserver 123. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 98.167.32.80:28015 is the address to use.
Is Testserver 123 up, and how steady is its uptime?
You cannot join now: Testserver 123 is offline, last seen 23 days 18 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 2 October 2026.
What Rust version is Testserver 123 on?
The server Testserver 123 is on Rust network protocol 2634 and build 166652 under Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
On what schedule does Testserver 123 reset?
The next wipe on Testserver 123 is a projection from the force wipe. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. The world it runs now was created 30 days 21 hours. The tags show a monthly wipe schedule.
Player count
What position does Testserver 123 hold in the rankings?
Over the last seven days, Testserver 123 has #13,798 for player hours, in the top 61% of all ranked servers.
How many players does Testserver 123 usually have?
Testserver 123 is offline at the moment; the last time it was seen was 23 days 18 hours ago.
Lists and filters
How should you read the tags on Testserver 123?
The game's browser takes its cue from the tags Testserver 123 has set: gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): 100 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): Join only if your game runs protocol 2634; cs166652 (Build): Build number: 166652; 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): Plugins or settings alter the game, so it sits under Modded; rustmaps (Custom tag): A plugin or the owner set this tag; it is not a standard Rust one. 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 Testserver 123 appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Testserver 123 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.
Map and rules
Which rules does Testserver 123 enforce, and what are its settings?
The name of Testserver 123 gives no gather rate. The group limit stays at the game's default of 8 players. survival is the mode here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. You are not covered by VAC, Valve's anti-cheat.
Testserver 123 runs which map?
Testserver 123 runs a procedural map, which the game generates.
Getting in
How do you get onto Testserver 123?
To connect, start Rust, press F1, and type client.connect 98.167.32.80:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,^m,gmrust,cs166652,ts8,^o^z,rustmaps
Game
gmrust
Game modeSurvival in the standard Rust style.
mp100
Max players100 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs166652
BuildBuild number: 166652.
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
ModdedPlugins or settings alter the game, so it sits under Modded.
Other
rustmaps
Custom tagA plugin or the owner set this tag; it is not a standard Rust one.
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 standing (F); momentum is the one to work on (F).