On the class lists: F (36), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak –
Rank#15,411top 69%
Last wipe16d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 50 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,411 on player hours.
Uptimehours on the list, last 48
98/ 100
A+
Excellent attendance: on the list 47 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 111 server fps on average.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 238 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in performance (A+); population 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
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 8 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 69% 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 gap3.2 daysbetween real wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 1
The first 48 hours of its last wipes
Mon 12 OctThu 8 Oct
Players each hour, from the hour of the wipe. The latest peaked at 2, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 12 Oct, 00:19 UTC16d ago
2
–
running
1
Thu 8 Oct, 20:30 UTC19d ago
3
halved by day 1
3.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
In what location does [US|EU] Public Solo/Duo Server sit?
The name of [US|EU] Public Solo/Duo Server points to North America, though no region tag is set. Rust Server Score takes the server's word for its location and does not trace the hardware. 167.160.89.85:28015 is the address to use.
Is [US|EU] Public Solo/Duo Server up, and how steady is its uptime?
Right now, [US|EU] Public Solo/Duo Server is online. According to its reported uptime, the last restart was about 15 days 23 hours ago. For the last 7 full days, it was up 168 of 168 hours, or 100% of the time. It was first seen by Rust Server Score on 8 October 2026.
How well does [US|EU] Public Solo/Duo Server run?
The average over the last 48 hours was 111 server fps, and it never went below 96. Up to 40,926 entities were in the world, covering buildings, deployables and the rest. At its highest, it used 3,154 MB of memory. Players feel lag when fps drops and entities pile up.
On what Rust version does [US|EU] Public Solo/Duo Server sit?
The server [US|EU] Public Solo/Duo Server is on Rust network protocol 2634 and build 167398 under Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
How frequently does [US|EU] Public Solo/Duo Server wipe its map?
There are too few wipes on record for [US|EU] Public Solo/Duo Server 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. 16 days 1 hours have passed since this world was made.
What happens on [US|EU] Public Solo/Duo Server when wipe day arrives?
The average peak on its recent wipes was 2 players. The crowd on the latest wipe was largest 1 hours after it began. The crowd stayed above half that peak, right through to the next wipe, in 0% of its recent wipes. Day 1 is when it sank below half in the wipes that did not hold.
Player numbers
What position does [US|EU] Public Solo/Duo Server hold in the rankings?
Over the last seven days, [US|EU] Public Solo/Duo Server has #15,411 for player hours, in the top 69% of all ranked servers.
Is [US|EU] Public Solo/Duo Server a busy server?
[US|EU] Public Solo/Duo Server is showing 0 players right now, with 50 slots in total. A seven-day average of 0 players applies here.
Lists and filters
How should you read the tags on [US|EU] Public Solo/Duo Server?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp50 (Max players): Its slot count is 50; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167398 (Build): Build number: 167398; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here are the tags [US|EU] Public Solo/Duo Server 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 [US|EU] Public Solo/Duo Server appear in the Rust Server Score lists and filters?
Rust Server Score lists that include [US|EU] Public Solo/Duo Server: Best community servers, graded and North America Rust servers, graded. You can find it under these server-list filters: Region: North America; Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Map and rules
How is [US|EU] Public Solo/Duo Server set up, and what rules does it keep?
You will find no gather rate in the name of [US|EU] Public Solo/Duo Server. The group limit stays at the game's default of 8 players. You get survival here, gather, build and raid, as in the standard game. You can raid other players and fight them. The server browser lists it under Community, as a community server. The server runs Valve's anti-cheat, VAC.
Which map is in play on [US|EU] Public Solo/Duo Server?
A procedural map of size 2,800 and seed 346781, generated by the game, is what [US|EU] Public Solo/Duo Server runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
How should you connect to [US|EU] Public Solo/Duo Server?
Enter client.connect 167.160.89.85: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 asmp50,ptrak,$r?,v2634,gmrust,cs167398,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp50
Max playersIts slot count is 50.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167398
BuildBuild number: 167398.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
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 performance (A+); population is the one to work on (F).