On the class lists: D (49), with population over 48 hours and no performance mark.
Players now0/ 10% full
7-day average1peak 1
Rank#10,422top 47%
Last wipe1d agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
56/ 100
C−
Room for more players: 1 of 1 on average.
Standingrank on player hours
53/ 100
D
Working its way up from the back of the class: #10,422 on player hours.
Uptimehours on the list, last 48
6/ 100
F
Attendance needs work: on the list only 3 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
50/ 100
D
Keeps a fair share of its players through a wipe: 50% of wipes kept half their crowd.
Momentumrank now against a week ago
73/ 100
B−
Climbing fast: up 4,751 places this week.
A term to build on.
Strongest in momentum (B−); uptime 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.
AveragePeakWipe
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 47% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
11 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
··WW···
·····WW
·W··WW·
···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 gap4 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak0players, last three wipes
crowd held50%else halves by day 3
The first 48 hours of its last wipes
Wed 21 OctThu 15 OctSat 10 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 45 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 26 Oct, 19:11 UTC1d ago
–
–
running
0
Wed 21 Oct, 22:56 UTC6d ago
1
halved by day 3
4.8 days
0
Thu 15 Oct, 15:01 UTC13d ago
0
–
6.3 days
0
Sat 10 Oct, 16:18 UTC18d ago
0
–
4.9 days
0
Fri 9 Oct, 15:24 UTC19d ago
1
–
1 days
1
Tue 6 Oct, 13:44 UTC22d ago
1
✓ held half
3.1 days
1
Sun 4 Oct, 14:41 UTC24d ago
1
–
2 days
1
Sat 3 Oct, 10:50 UTC25d ago
1
–
1.2 days
0
Thu 24 Sep, 10:53 UTC34d ago
1
halved by day 1
9 days
0
Wed 23 Sep, 08:02 UTC35d ago
0
–
1.1 days
0
Thu 17 Sep, 20:22 UTC40d ago
0
–
5.5 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
No region is published for 123. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 104.28.198.244:28015.
How reliable is 123, and is it up?
At this moment, 123 is offline; the last time it was seen was 45 hours ago. It was up 6 of 168 hours over the last 7 full days, which is 4% of the time. It was first seen by Rust Server Score on 14 September 2026.
What Rust version is 123 on?
Rust network protocol 2635 and build 168909 on Windows is what 123 runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does 123 reset?
There is no next wipe to predict on 123, as it wipes at irregular times. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 47 hours have passed since this world was made.
What should you expect from wipe day on 123?
Recent wipes have peaked at 0 players on average. 45 hours after the latest wipe began, the crowd hit its peak. The crowd stayed above half that peak, right through to the next wipe, in 50% of its recent wipes. The crowd dropped below half by day 3 in the wipes where it did not hold.
Player numbers
Where does 123 place in the wider field of Rust servers?
Over the last seven days, 123 has #10,422 for player hours, in the top 47% of all ranked servers.
What does the population on 123 look like?
It has been 45 hours since 123 was last seen, and it is offline right now. Averaging 1 players over seven days, it peaked at 1. Over the last 48 hours, the peak hour was 20:00 UTC, averaging 1 players.
Tags and filters
What is meant by the tags on 123?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp1 (Max players): Its slot count is 1; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server are the tags 123 publishes, and the game's server browser reads them. 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?
Rust Server Score lists that include 123: 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?
You will find no gather rate in the name of 123. The group limit stays at the game's default of 8 players. You get survival here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Under Community in the server browser you will find this community server. You are covered by VAC, Valve's anti-cheat.
Which map is in play on 123?
123 runs a procedural map, which the game generates.
Getting in
How do you get onto 123?
Enter client.connect 104.28.198.244: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 asmp1,ptrak,$r?,v2635,gmrust,cs168909,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp1
Max playersIts slot count is 1.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
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 (B−); uptime is the one to work on (F).