Working its way up from the back of the class: #14,370 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
42/ 100
F
Slipped a little: down 2,335 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to 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.
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.
Average fpsLowest fpsWipe
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.
Average fpsLowest fpsWipe
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.
Average fpsLowest fpsWipe
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, measured since 14 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 66% of all ranked servers. Ranked on player hours over the last seven days.
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
No region is published for slayworld1. Rust Server Score takes the server's word for its location and does not trace the hardware. 157.85.90.150:21509 is the address to use.
Is slayworld1 up, and how steady is its uptime?
The server is down: slayworld1 is offline now, with the last sighting 14 days 9 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 14 October 2026.
On what Rust version does slayworld1 sit?
The server slayworld1 is on Rust network protocol 2634 and build 167781 under Linux. To join, your game must use the same protocol; Steam handles the update.
Resets
When does slayworld1 wipe, and how often?
There are too few wipes on record for slayworld1 to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 14 days 20 hours have passed since this world was made.
Population
Where does slayworld1 sit among Rust servers?
Over the last seven days, slayworld1 has #14,370 for player hours, in the top 66% of all ranked servers.
How many players does slayworld1 usually have?
It has been 14 days 9 hours since slayworld1 was last seen, and it is offline right now.
Lists and filters
What is meant by the tags on slayworld1?
gmrust (Game mode): Survival in the standard Rust style; mp40 (Max players): Its slot count is 40; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): This runs on build 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server are the tags slayworld1 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.
Where does slayworld1 appear in the Rust Server Score lists and filters?
Rust Server Score lists that include slayworld1: 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.
Rules and settings
What settings and rules apply on slayworld1?
You will find no gather rate in the name of slayworld1. With no change from the game default, groups take up to 8 players. It runs survival, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. The server does not run VAC, Valve's anti-cheat.
Can you tell me which map slayworld1 uses?
A procedural map of size 1,500 and seed 50000, generated by the game, is what slayworld1 runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Getting in
How do you get onto slayworld1?
To connect, start Rust, press F1, and type client.connect 157.85.90.150:21509. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp40,ptrak,$r?,v2634,gmrust,cs167781,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp40
Max playersIts slot count is 40.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildThis runs on build 167781.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
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. Even marks across the subjects, from F to F.