A quiet classroom so far: 0 of 69 on average. Plenty of space to grow.
Standingrank on player hours
59/ 100
C−
Working its way up from the back of the class: #9,117 on player hours.
Uptimehours on the list, last 48
21/ 100
F
Attendance needs work: on the list only 10 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
43/ 100
F
Slipped a little: down 1,223 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in standing (C−); 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
Every five minutes, from the Steam server list.
AveragePeak
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 41% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
13 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·W·····
···W···
W·W··WW
·WW·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.5 daysbetween real wipes
on rhythm25%of its recent wipes
wipe-day peak1players, last three wipes
crowd held50%else halves by day 1
The first 48 hours of its last wipes
Thu 22 OctWed 21 OctTue 20 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
Thu 29 Oct, 06:26 UTC3h ago
–
–
running
0
Thu 22 Oct, 18:28 UTC6d ago
1
–
–
0
Wed 21 Oct, 05:51 UTC8d ago
1
–
1.5 days
0
Tue 20 Oct, 18:39 UTC8d ago
1
–
0.5 days
0
Tue 20 Oct, 09:28 UTC9d ago
1
–
0.4 days
1
Fri 16 Oct, 05:34 UTC13d ago
1
halved by day 1
4.2 days
0
Wed 14 Oct, 20:11 UTC14d ago
1
–
1.4 days
0
Tue 13 Oct, 19:47 UTC15d ago
1
–
1 days
0
Sun 11 Oct, 03:57 UTC18d ago
1
–
2.7 days
0
Sat 10 Oct, 05:34 UTC19d ago
1
–
0.9 days
0
Wed 7 Oct, 05:01 UTC22d ago
1
✓ held half
3 days
0
Mon 5 Oct, 01:59 UTC24d ago
1
halved by day 1
2.1 days
1
Thu 1 Oct, 05:28 UTC28d ago
1
–
3.9 days
0
Tue 22 Sep, 08:52 UTC37d ago
1
✓ held half
8.9 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 A Simple Rust Server. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 24.108.106.73:28015.
How reliable is A Simple Rust Server, and is it up?
You cannot join now: A Simple Rust Server is offline, last seen 1 hours ago. It was up 10 of 168 hours over the last 7 full days, which is 6% of the time. It was first seen by Rust Server Score on 21 September 2026.
On what Rust version does A Simple Rust Server sit?
The server A Simple Rust Server is on Rust network protocol 2635 and build 169621 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
When does A Simple Rust Server wipe, and how often?
A Simple Rust Server wipes at times that vary, so no next wipe can be predicted. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 2 hours.
What happens on A Simple Rust Server when wipe day arrives?
Recent wipes have peaked at 1 players on average. The crowd on the latest wipe was largest 0 hours after it began. Above half the peak until the next wipe: that was the pattern in 50% of its recent wipes. The crowd dropped below half by day 1 in the wipes where it did not hold.
Player numbers
What position does A Simple Rust Server hold in the rankings?
Over the last seven days, A Simple Rust Server has #9,117 for player hours, in the top 41% of all ranked servers.
What does the population on A Simple Rust Server look like?
A Simple Rust Server is offline at the moment; the last time it was seen was 1 hours ago. The seven-day average is 0 players, with a peak of 1. The busiest time in the last 48 hours was 17:00 UTC, with an average of 1 players.
Tags and filters
How should you read the tags on A Simple Rust Server?
The game's browser takes its cue from the tags A Simple Rust Server has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp69 (Max players): 69 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs169621 (Build): The game build is 169621; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set. 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 A Simple Rust Server?
These Rust Server Score lists count A Simple Rust Server among them: Best community servers, graded. It shows under the following filters 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 24 hours.
Server rules
Which rules does A Simple Rust Server enforce, and what are its settings?
The name of A Simple Rust Server gives no gather rate. The default of 8 players applies as the group cap. survival is the mode here, 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.
Which map is in play on A Simple Rust Server?
A Simple Rust Server runs a procedural map, which the game generates.
How to join
How should you connect to A Simple Rust Server?
To connect, start Rust, press F1, and type client.connect 24.108.106.73:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp69,ptrak,$r?,v2635,gmrust,cs169621,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp69
Max players69 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs169621
BuildThe game build is 169621.
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 standing (C−); population is the one to work on (F).