Working its way up from the back of the class: #14,392 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
22/ 100
F
Lost ground: down 7,983 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); momentum 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
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 60% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
······W
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.
usual gap1.2 daysbetween real wipes
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Mon 28 SepSun 27 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
Mon 28 Sep, 12:41 UTC30d ago
1
–
running
1
Sun 27 Sep, 07:49 UTC32d ago
1
–
1.2 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
Server Local Saya 3500 leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. 182.11.130.163:28015 is the address to use.
Is Server Local Saya 3500 up, and how steady is its uptime?
You cannot join now: Server Local Saya 3500 is offline, last seen 28 days 19 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 27 September 2026.
Which Rust version is Server Local Saya 3500 running?
The server Server Local Saya 3500 is on Rust network protocol 2633 and build 165217 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does Server Local Saya 3500 wipe, and how often?
There are too few wipes on record for Server Local Saya 3500 to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 30 days 21 hours have passed since this world was made.
What happens on Server Local Saya 3500 when wipe day arrives?
The average peak on its recent wipes was 1 players. The crowd on the latest wipe was largest 0 hours after it began.
Player count
Where does Server Local Saya 3500 place in the wider field of Rust servers?
In the top 60% of all ranked servers, Server Local Saya 3500 sits at #14,392 for player hours over the last seven days.
What does the population on Server Local Saya 3500 look like?
It has been 28 days 19 hours since Server Local Saya 3500 was last seen, and it is offline right now.
Tags
What do Server Local Saya 3500's tags stand for?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp5 (Max players): 5 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): Join only if your game runs protocol 2633; cs165217 (Build): This runs on build 165217; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server are the tags Server Local Saya 3500 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 Server Local Saya 3500 appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Server Local Saya 3500 among them: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Map and rules
What settings and rules apply on Server Local Saya 3500?
The name of Server Local Saya 3500 gives no gather rate. The group limit stays at the game's default of 8 players. survival is the mode here, gather and build and raid: the standard game. Raiding and PvP are both permitted. You will see it in the Community section of the server browser, since it is a community server. The server does not run VAC, Valve's anti-cheat.
Can you tell me which map Server Local Saya 3500 uses?
The game generates a procedural map for Server Local Saya 3500.
Connecting
How do you get onto Server Local Saya 3500?
To connect, start Rust, press F1, and type client.connect 182.11.130.163:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp5,ptrak,$r?,v2633,gmrust,cs165217,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp5
Max players5 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs165217
BuildThis runs on build 165217.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$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. Strongest in standing (F); momentum is the one to work on (F).