Working its way up from the back of the class: #7,707 on player hours.
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.
A steady term.
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
Top 35% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
···
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.
wipe-day peak3players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 0 hours in, with 1 in the queue.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 23 Oct, 23:02 UTC4d ago
3+1 queue
–
running
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 sigma 67. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 77.162.166.238:28015.
How reliable is sigma 67, and is it up?
The server is down: sigma 67 is offline now, with the last sighting 3 days 19 hours ago. It was up 7 of 96 hours over the last 4 full days, which is 7% of the time. The first sighting by Rust Server Score was on 23 October 2026.
What Rust version is sigma 67 on?
The server sigma 67 is on Rust network protocol 2635 and build 168909 under Windows. To join, your game must use the same protocol; Steam handles the update.
Resets
On what schedule does sigma 67 reset?
There are too few wipes on record for sigma 67 to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 4 days 1 hours have passed since this world was made.
What should you expect from wipe day on sigma 67?
Recent wipes have peaked at 3 players on average. The latest wipe peaked 0 hours in, with 1 more players queued at that point.
Population
Where does sigma 67 sit among Rust servers?
In the top 35% of all ranked servers, sigma 67 sits at #7,707 for player hours over the last seven days.
What does the population on sigma 67 look like?
It has been 3 days 19 hours since sigma 67 was last seen, and it is offline right now. The seven-day average is 1 players, with a peak of 3.
Lists and filters
What is meant by the tags on sigma 67?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp0 (Max players): Its slot count is 0; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded are the tags sigma 67 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 sigma 67 appear in the Rust Server Score lists and filters?
These Rust Server Score lists count sigma 67 among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Map and rules
Which rules does sigma 67 enforce, and what are its settings?
You will find no gather rate in the name of sigma 67. The default of 8 players applies as the group cap. survival is the mode here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. 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.
Which map is in play on sigma 67?
A procedural map, generated by the game, is what sigma 67 runs.
Getting in
How do you get onto sigma 67?
To connect, start Rust, press F1, and type client.connect 77.162.166.238:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp0,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp0
Max playersIts slot count is 0.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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.
A steady term.