On the class lists: D (51), with population over 48 hours and no performance mark.
Players now0/ 10% full
7-day average1peak 1
Rank#8,577top 39%
Last wipe1d agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
55/ 100
C−
Room for more players: 1 of 1 on average.
Standingrank on player hours
61/ 100
C
Working its way up from the back of the class: #8,577 on player hours.
Uptimehours on the list, last 48
19/ 100
F
Attendance needs work: on the list only 9 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
100/ 100
A+
Holds its players well after a wipe: 100% of wipes kept half their crowd.
Momentumrank now against a week ago
29/ 100
F
Lost ground: down 3,548 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in wipe hold (A+); 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 39% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
6 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·W·····
W···WWW
·······
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 gap1.3 daysbetween real wipes
on rhythm14%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Sun 18 OctSat 17 OctFri 16 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 26 Oct, 22:41 UTC1d ago
–
–
running
0
Sun 18 Oct, 22:00 UTC9d ago
1
✓ held half
8 days
1
Sat 17 Oct, 14:32 UTC10d ago
1
–
1.3 days
0
Fri 16 Oct, 22:26 UTC11d ago
1
–
0.7 days
1
Fri 16 Oct, 16:21 UTC11d ago
1
–
0.3 days
1
Mon 12 Oct, 13:31 UTC15d ago
1
✓ held half
4.1 days
1
Mon 12 Oct, 01:19 UTC16d ago
1
–
0.5 days
0
Tue 6 Oct, 23:57 UTC21d ago
1
✓ held half
5.1 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 Server Seed 073474 5000. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 75.237.90.124:28015.
How reliable is Server Seed 073474 5000, and is it up?
At this moment, Server Seed 073474 5000 is offline; the last time it was seen was 7 hours ago. It was up 7% of the time over the last 7 full days, 11 of 168 hours. On 6 October 2026, Rust Server Score saw it for the first time.
What Rust version is Server Seed 073474 5000 on?
The server Server Seed 073474 5000 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 cycle
When does Server Seed 073474 5000 wipe, and how often?
There is no next wipe to predict on Server Seed 073474 5000, 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. The world it runs now was created 34 hours.
What should you expect from wipe day on Server Seed 073474 5000?
Across its recent wipes, the busiest moments averaged 1 players. Peak numbers came 0 hours into the latest wipe. Half the peak held until the next wipe in 100% of its recent wipes.
Player numbers
Where does Server Seed 073474 5000 sit among Rust servers?
Over the last seven days, Server Seed 073474 5000 has #8,577 for player hours, in the top 39% of all ranked servers.
What does the population on Server Seed 073474 5000 look like?
The last sighting of Server Seed 073474 5000 was 7 hours ago, and it is offline right now. It peaked at 1 and averaged 1 players over the last seven days. The busiest time in the last 48 hours was 02:00 UTC, with an average of 1 players.
Tags
How should you read the tags on Server Seed 073474 5000?
You'll see Server Seed 073474 5000 tagged with 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): Join only if your game runs protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set 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 Server Seed 073474 5000 appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Server Seed 073474 5000 among them: Best community servers, graded. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 3 days.
Map and rules
Which rules does Server Seed 073474 5000 enforce, and what are its settings?
You will find no gather rate in the name of Server Seed 073474 5000. The default of 8 players applies as the group cap. It runs survival, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it under Community, as a community server. The server runs Valve's anti-cheat, VAC.
Can you tell me which map Server Seed 073474 5000 uses?
The game generates a procedural map for Server Seed 073474 5000.
Connecting
How should you connect to Server Seed 073474 5000?
Enter client.connect 75.237.90.124: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
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
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 wipe hold (A+); uptime is the one to work on (F).