Not ranked yet, so there is no place in the school to report.
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.
Not enough figures yet to write a report. Check back after a few days on the list.
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.
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
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·WW····
·······
·······
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
usual gap0.8 daysbetween real wipes
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Wed 16 SepTue 15 Sep
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
Wed 16 Sep, 11:48 UTC42d ago
1
–
running
0
Tue 15 Sep, 16:10 UTC42d ago
1
–
0.8 days
2
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 sm1. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 46.38.72.109:28015.
How reliable is sm1, and is it up?
At this moment, sm1 is offline; the last time it was seen was 41 days 22 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 14 September 2026.
On what Rust version does sm1 sit?
You will find sm1 on Rust network protocol 2633 and build 162929, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
How frequently does sm1 wipe its map?
sm1 has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 42 days have passed since this world was made.
What happens on sm1 when wipe day arrives?
Recent wipes have peaked at 1 players on average. 0 hours after the latest wipe began, the crowd hit its peak.
Population
What position does sm1 hold in the rankings?
Over the last seven days, sm1 has #13,353 for player hours, in the top – of all ranked servers.
How many players does sm1 usually have?
It has been 41 days 22 hours since sm1 was last seen, and it is offline right now.
Lists and filters
How should you read the tags on sm1?
gmrust (Game mode): Rust survival, played by the standard rules; mp61 (Max players): Its slot count is 61; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): Join only if your game runs protocol 2633; cs162929 (Build): The game build is 162929; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^c (Creative): A sandbox with no gathering: build whatever takes your fancy; ^e (Minigames): Expect minigames: arenas, Bedwars, parkour and more; ^d (Combat training): Practise aim and PvP, loot provided; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded are the tags sm1 publishes, and the game's server browser reads them. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which Rust Server Score filters and lists feature sm1?
These Rust Server Score lists count sm1 among them: Modded Rust servers, graded, Rust combat training servers, graded, Rust build and creative servers and Rust creative servers, scored and graded. You can find it under these server-list filters: Type: Modded; Server tag: Creative ^c, Minigames ^e, Combat training ^d, Modded ^z and Oxide ^o; Group limit: 5 or more.
Server rules
What settings and rules apply on sm1?
You will find no gather rate in the name of sm1. The default of 8 players applies as the group cap. minigames & battle royale is the mode here, parkour, arenas, battle royale and Bedwars. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. VAC, Valve's anti-cheat, is enabled.
Getting in
What is the way to join sm1?
To connect, start Rust, press F1, and type client.connect 46.38.72.109:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp61,ptrak,$r?,v2633,^c,^e,^d,gmrust,cs162929,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp61
Max playersIts slot count is 61.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs162929
BuildThe game build is 162929.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Gameplay
^c
CreativeA sandbox with no gathering: build whatever takes your fancy.
^e
MinigamesExpect minigames: arenas, Bedwars, parkour and more.
^d
Combat trainingPractise aim and PvP, loot provided.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
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.
Not enough figures yet to write a report. Check back after a few days on the list.