On the class lists: F (43), with population over 48 hours and no performance mark.
Players now1/ 1100% full
7-day average1peak 1
Rank#12,668top 57%
Last wipe2d agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
67/ 100
C+
Draws a healthy crowd: 1 of 1 on average.
Standingrank on player hours
43/ 100
F
Working its way up from the back of the class: #12,668 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
unmarked
–
No rank a week ago to compare with.
A fair term, with more to come.
Strongest in population (C+); 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.
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 57% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
5 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
··W····
·······
W····W·
·······
··W····
W···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap8.1 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak0players, last three wipes
The first 48 hours of its last wipes
Mon 26 OctWed 21 OctSat 10 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 5 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 26 Oct, 19:11 UTC2d ago
1
–
running
0
Wed 21 Oct, 22:56 UTC7d ago
–
–
4.8 days
0
Sat 10 Oct, 15:43 UTC18d ago
0
–
11.3 days
1
Mon 5 Oct, 19:17 UTC23d ago
–
–
4.9 days
0
Wed 23 Sep, 12:03 UTC36d ago
0
–
12.3 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
You'll find no region listed by 123. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 104.28.230.242:28015.
How reliable is 123, and is it up?
You cannot join now: 123 is offline, last seen 2 days 12 hours ago. For the last 7 full days, it was up 2 of 168 hours, or 1% of the time. On 15 September 2026, Rust Server Score saw it for the first time.
On what Rust version does 123 sit?
The server 123 is on Rust network protocol 2635 and build 168909 under Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
On what schedule does 123 reset?
123 wipes at times that vary, so no next wipe can be predicted. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 2 days 18 hours.
What happens on 123 when wipe day arrives?
Across its recent wipes, the busiest moments averaged 0 players. The crowd on the latest wipe was largest 5 hours after it began.
Player numbers
What position does 123 hold in the rankings?
Over the last seven days, 123 has #12,668 for player hours, in the top 57% of all ranked servers.
What does the population on 123 look like?
It has been 2 days 12 hours since 123 was last seen, and it is offline right now. The seven-day average is 1 players, with a peak of 1.
Tags and filters
What is meant by the tags on 123?
You'll see 123 tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp1 (Max players): 1 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here 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.
Which lists and filters on Rust Server Score show 123?
These Rust Server Score lists count 123 among them: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 3 days.
Rules and settings
How is 123 set up, and what rules does it keep?
Nothing in the name of 123 states a gather rate. The group limit stays at the game's default of 8 players. It runs survival, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it under Community, as a community server. You are covered by VAC, Valve's anti-cheat.
123 runs which map?
The game generates a procedural map for 123.
Connecting
What is the way to join 123?
To connect, start Rust, press F1, and type client.connect 104.28.230.242:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp1,ptrak,$r?,v2635,gmrust,cs168909,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp1
Max players1 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
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 fair term, with more to come. Strongest in population (C+); standing is the one to work on (F).