Working its way up from the back of the class: #16,008 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
32/ 100
F
Lost ground: down 5,701 places this week. A strong wipe could turn it round.
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 6 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 72% of all ranked servers, and #635 of the quad servers (top 77%). 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
In what location does Rust 10x | Local Test | Quad sit?
Rust 10x | Local Test | Quad leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 169.1.170.115:28015.
How dependable is Rust 10x | Local Test | Quad, and is it online at the moment?
The server is down: Rust 10x | Local Test | Quad is offline now, with the last sighting 22 days 2 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. The first sighting by Rust Server Score was on 6 October 2026.
What Rust version is Rust 10x | Local Test | Quad on?
You will find Rust 10x | Local Test | Quad on Rust network protocol 2634 and build 166494, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
How frequently does Rust 10x | Local Test | Quad wipe its map?
Rust 10x | Local Test | Quad 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. The world it runs now was created 23 days 22 hours.
Player count
Where does Rust 10x | Local Test | Quad place in the wider field of Rust servers?
In the top 72% of all ranked servers, Rust 10x | Local Test | Quad sits at #16,008 for player hours over the last seven days. It comes #635 among servers in the quad group.
What does the population on Rust 10x | Local Test | Quad look like?
Rust 10x | Local Test | Quad is offline at the moment; the last time it was seen was 22 days 2 hours ago.
Tags and filters
What is meant by the tags on Rust 10x | Local Test | Quad?
The game's browser takes its cue from the tags Rust 10x | Local Test | Quad has set: gmrust (Game mode): Survival in the standard Rust style; mp10 (Max players): Its slot count is 10; ts4 (Group limit): Teams cap out at 4; v2634 (Protocol): Join only if your game runs protocol 2634; cs166494 (Build): This runs on build 166494; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): Plugin framework: Carbon. 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 Rust 10x | Local Test | Quad appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Rust 10x | Local Test | Quad among them: 10x Rust servers, graded and Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: Quad; Gather rate: 10x.
Server rules
Which rules does Rust 10x | Local Test | Quad enforce, and what are its settings?
Rust 10x | Local Test | Quad sets gather at 10x, as its name suggests. You can have up to 4 players in a group (quad). You get survival here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Carbon. You are covered by VAC, Valve's anti-cheat.
Which map is in play on Rust 10x | Local Test | Quad?
A procedural map of size 3,500 and seed 1012026, generated by the game, is what Rust 10x | Local Test | Quad runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
How should you connect to Rust 10x | Local Test | Quad?
Enter client.connect 169.1.170.115:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2634,gmrust,cs166494,ts4,^z,^y
Game
gmrust
Game modeSurvival in the standard Rust style.
mp10
Max playersIts slot count is 10.
ts4
Group limitTeams cap out at 4.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs166494
BuildThis runs on build 166494.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Mods and access
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
^y
CarbonPlugin framework: Carbon.
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.