Working its way up from the back of the class: #15,218 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 704 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.
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.
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 70% of all ranked servers, top 87% in EU, and #521 of the trio servers (top 83%). 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 Wednesday 28 October, 10:00 UTC, in 1h.
Weekly: 7 days after its last 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 see testserver listed in Europe, tagged EU. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 89.222.124.49:28015 is the address to use.
Is testserver up, and how steady is its uptime?
You cannot join now: testserver is offline, last seen 13 days 21 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 14 October 2026, Rust Server Score saw it for the first time.
What Rust version is testserver on?
The server testserver is on Rust network protocol 2634 and build 167781 under Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
On what schedule does testserver reset?
The estimate for testserver's next wipe comes from weekly: 7 days after its last wipe. It is due to wipe next on Wednesday 28 October at 10:00 UTC. The world it runs now was created 13 days 22 hours. Its tags state that it wipes weekly.
Population
What position does testserver hold in the rankings?
Over the last seven days, testserver has #15,218 for player hours, in the top 70% of all ranked servers and #2,560 in Europe. It comes #521 among servers in the trio group.
How many players does testserver usually have?
testserver is offline at the moment; the last time it was seen was 13 days 21 hours ago.
Lists and filters
How should you read the tags on testserver?
The game's browser takes its cue from the tags testserver has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp200 (Max players): The server holds 200 slots; ts3 (Group limit): Teams cap out at 3; v2634 (Protocol): Join only if your game runs protocol 2634; cs167781 (Build): This runs on build 167781; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^w (Weekly): A wipe happens every week; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; EU (Europe): You will find it under Europe in the browser. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show testserver?
These Rust Server Score lists count testserver among them: European Rust servers, graded, Modded Rust servers, graded and Rust servers with a trio group limit. You can find it under these server-list filters: Region: Europe; Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: Trio; Wipe schedule: Weekly; Last wipe: In the last 2 weeks.
Rules and settings
How is testserver set up, and what rules does it keep?
Nothing in the name of testserver states a gather rate. The cap on group size is 3 players (trio). It runs survival, gather, build and raid, as in the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
Connecting
How should you connect to testserver?
To connect, start Rust, press F1, and type client.connect 89.222.124.49:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp200,ptrak,$r?,v2634,^w,EU,gmrust,cs167781,ts3,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp200
Max playersThe server holds 200 slots.
ts3
Group limitTeams cap out at 3.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167781
BuildThis runs on build 167781.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Wipe schedule
^w
WeeklyA wipe happens every week.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
Region
EU
EuropeYou will find it under Europe in the browser.
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).