A quiet classroom so far: 0 of 50 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,414 on player hours.
Uptimehours on the list, last 48
8/ 100
F
Attendance needs work: on the list only 4 of the last 48 hours.
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
unmarked
–
No rank a week ago to compare with.
A term to build on.
Strongest in standing (F); population 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.
AveragePeakWipe
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 69% of all ranked servers, top 89% in EU. 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 17h.
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
In Europe, according to its own listing, sits #3, with the EU tag. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 91.122.158.45:26015.
Is #3 up, and how steady is its uptime?
You cannot join now: #3 is offline, last seen 13 hours ago. The first sighting by Rust Server Score was on 27 October 2026.
On what Rust version does #3 sit?
You will find #3 on Rust network protocol 2635 and build 168909, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
When does #3 wipe, and how often?
the force wipe gives the basis for estimating #3's next 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. 17 hours have passed since this world was made. A fortnightly wipe schedule appears in its tags.
Player numbers
Where does #3 place in the wider field of Rust servers?
Over the last seven days, #3 has #15,414 for player hours, in the top 69% of all ranked servers and #2,590 in Europe.
How many players does #3 usually have?
#3 is offline at the moment; the last time it was seen was 13 hours ago. Over the past seven days, the average player count was 0.
Tags and filters
How should you read the tags on #3?
The game's browser takes its cue from the tags #3 has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp50 (Max players): 50 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^b (Biweekly): Every two weeks it wipes; ^p (PvE): The danger comes from the world, not from other players; EU (Europe): The server browser lists it under Europe. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which lists and filters on Rust Server Score show #3?
These Rust Server Score lists count #3 among them: European Rust servers, graded, Best community servers, graded and Rust PvE servers, graded. It shows under the following filters on the server list: Region: Europe; Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: Biweekly ^b and PvE ^p; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 24 hours.
Map and rules
What settings and rules apply on #3?
The name of #3 gives no gather rate. With no change from the game default, groups take up to 8 players. It runs pve, no PvP between players. The server browser lists it under Community, as a community server. VAC, Valve's anti-cheat, is enabled.
#3 runs which map?
The game generates a procedural map for #3.
How to join
How should you connect to #3?
Enter client.connect 91.122.158.45:26015 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?,v2635,^b,EU,^p,gmrust,cs168909,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp50
Max players50 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Wipe schedule
^b
BiweeklyEvery two weeks it wipes.
Gameplay
^p
PvEThe danger comes from the world, not from other players.
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.
A term to build on. Strongest in standing (F); population is the one to work on (F).