Working its way up from the back of the class: #14,109 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
40/ 100
F
Slipped a little: down 2,810 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to 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 60% of all ranked servers, top 81% 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 6d 16h.
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
EU · groups of 150+ · 1x · monthly · 119 on average
23 / 300
Quick answers
from the figures on this page
Server facts
In what location does 123 sit?
You'll see 123 listed in Europe, tagged EU. Rust Server Score takes the server's word for its location and does not trace the hardware. 213.159.197.10:28015 is the address to use.
How reliable is 123, and is it up?
You cannot join now: 123 is offline, last seen 28 days 10 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 1 October 2026, Rust Server Score saw it for the first time.
What Rust version is 123 on?
The server 123 is on Rust network protocol 2633 and build 165217 under Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
When does 123 wipe, and how often?
The next wipe on 123 is a projection from the force wipe. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. It has been running its current world for 28 days 14 hours. Its tags list a monthly wipe schedule.
Player count
Where does 123 sit among Rust servers?
Over the last seven days, 123 has #14,109 for player hours, in the top 60% of all ranked servers and #2,396 in Europe.
Is 123 a busy server?
The last sighting of 123 was 28 days 10 hours ago, and it is offline right now.
Tags
What do 123's tags stand for?
You'll see 123 tagged with gmvanilla (Game mode): Survival, vanilla style; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs165217 (Build): Build number: 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^v (Vanilla): You get the unmodified game: no rate changes, no kits, no rule changes; ^o (Oxide): Oxide (uMod) provides the plugin framework here; EU (Europe): You will find it under Europe in the browser in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does 123 appear in the Rust Server Score lists and filters?
These Rust Server Score lists count 123 among them: European Rust servers, graded, Best community servers, graded and Vanilla Rust servers, graded. It shows under the following filters on the server list: Region: Europe; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Server tag: Monthly ^m, Vanilla ^v and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Map and rules
Which rules does 123 enforce, and what are its settings?
The name of 123 gives no gather rate. The default of 8 players applies as the group cap. survival is the mode here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. Under Community in the server browser you will find this community server. The plugin count runs to Oxide. Vanilla is what it calls itself: you get the unmodified game: no rate changes, no kits, no rule changes. The server runs Valve's anti-cheat, VAC.
123 runs which map?
123 runs a procedural map, which the game generates.
Getting in
How should you connect to 123?
Enter client.connect 213.159.197.10: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 asmp100,ptrak,$r?,v2633,^m,^v,EU,gmvanilla,cs165217,ts8,^o
Game
gmvanilla
Game modeSurvival, vanilla style.
mp100
Max playersThe server holds 100 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs165217
BuildBuild number: 165217.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Difficulty
^v
VanillaYou get the unmodified game: no rate changes, no kits, no rule changes.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
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. Even marks across the subjects, from F to F.