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.
No daily history yet.
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
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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
The region code for SAC smoke test is us4, but no region is published. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 159.250.33.110:28030.
How reliable is SAC smoke test, and is it up?
At this moment, SAC smoke test is offline; the last time it was seen was 41 days 21 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 17 September 2026.
What Rust version is SAC smoke test on?
Rust network protocol 2623 and build 147942 on Windows is what SAC smoke test runs. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
When does SAC smoke test wipe, and how often?
The record holds too few of SAC smoke test's wipes to tell its rhythm. 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 41 days 21 hours.
Player count
Where does SAC smoke test sit among Rust servers?
In the top – of all ranked servers, SAC smoke test sits at #15,413 for player hours over the last seven days.
Is SAC smoke test a busy server?
It has been 41 days 21 hours since SAC smoke test was last seen, and it is offline right now.
Tags
What is meant by the tags on SAC smoke test?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp2 (Max players): Its slot count is 2; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2623 (Protocol): Join only if your game runs protocol 2623; cs147942 (Build): Build number: 147942; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $rus4 (Region code): Region code: us4 are the tags SAC smoke test publishes, and the game's server browser reads them. 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 Rust Server Score filters and lists feature SAC smoke test?
These Rust Server Score lists count SAC smoke test 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.
Rules and settings
How is SAC smoke test set up, and what rules does it keep?
You will find no gather rate in the name of SAC smoke test. The group limit stays at the game's default of 8 players. You get survival here, 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. You are covered by VAC, Valve's anti-cheat.
SAC smoke test runs which map?
The game generates a procedural map for SAC smoke test.
Connecting
What is the way to join SAC smoke test?
To connect, start Rust, press F1, and type client.connect 159.250.33.110:28030. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp2,ptrak,$rus4,v2623,gmrust,cs147942,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp2
Max playersIts slot count is 2.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2623
ProtocolJoin only if your game runs protocol 2623.
cs147942
BuildBuild number: 147942.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$rus4
Region codeRegion code: us4.
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.