On the class lists: C− (58), with population over 48 hours and no performance mark.
Players now0/ 160% full
7-day average3peak 5
Rank#1,757top 8%
Last wipe53d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
19/ 100
F
A quiet classroom so far: 3 of 16 on average. Plenty of space to grow.
Standingrank on player hours
92/ 100
A
Well up the rankings: #1,757 on player hours.
Uptimehours on the list, last 48
94/ 100
A
Good attendance: on the list 45 of the last 48 hours.
Performanceserver fps, last 48 hours
16/ 100
F
Needs to work on its frame rate: 10 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
46/ 100
D
Slipped a little: down 151 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in uptime (A); performance 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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 8% 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
Where in the world is Outpost Network #3 [ 2x Solo/Duo/Trio ] FULLWIPED 30.08?
No region is published for Outpost Network #3 [ 2x Solo/Duo/Trio ] FULLWIPED 30.08. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 37.60.224.119:29915.
Is Outpost Network #3 [ 2x Solo/Duo/Trio ] FULLWIPED 30.08 up, and how steady is its uptime?
Right now, Outpost Network #3 [ 2x Solo/Duo/Trio ] FULLWIPED 30.08 is online. The uptime it reports puts the last restart at about 6 days 10 hours ago. For the last 7 full days, it was up 167 of 168 hours, or 99% of the time. It was first seen by Rust Server Score on 13 September 2026.
Is Outpost Network #3 [ 2x Solo/Duo/Trio ] FULLWIPED 30.08 smooth to play on?
It averaged 10 server fps over the last 48 hours, with a low of 2. At its peak, it held 2,747 entities, including buildings, deployables and all else in the world. Up to 706 MB of memory was used. When fps is low and entities climb, that is lag to players.
On what Rust version does Outpost Network #3 [ 2x Solo/Duo/Trio ] FULLWIPED 30.08 sit?
Rust network protocol 2633 and build 163207 on Linux is what Outpost Network #3 [ 2x Solo/Duo/Trio ] FULLWIPED 30.08 runs. To join, your game must use the same protocol; Steam handles the update.
Resets
On what schedule does Outpost Network #3 [ 2x Solo/Duo/Trio ] FULLWIPED 30.08 reset?
Outpost Network #3 [ 2x Solo/Duo/Trio ] FULLWIPED 30.08 has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 53 days 23 hours have passed since this world was made.
Player count
What position does Outpost Network #3 [ 2x Solo/Duo/Trio ] FULLWIPED 30.08 hold in the rankings?
Over the last seven days, Outpost Network #3 [ 2x Solo/Duo/Trio ] FULLWIPED 30.08 has #1,757 for player hours, in the top 8% of all ranked servers.
How many players does Outpost Network #3 [ 2x Solo/Duo/Trio ] FULLWIPED 30.08 usually have?
Right now, 0 players are on Outpost Network #3 [ 2x Solo/Duo/Trio ] FULLWIPED 30.08, which has 16 slots. Averaging 3 players over seven days, it peaked at 5.
Tags and filters
How should you read the tags on Outpost Network #3 [ 2x Solo/Duo/Trio ] FULLWIPED 30.08?
The game's browser takes its cue from the tags Outpost Network #3 [ 2x Solo/Duo/Trio ] FULLWIPED 30.08 has set: gmrust (Game mode): Survival in the standard Rust style; mp16 (Max players): The server holds 16 slots; 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; cs163207 (Build): This runs on build 163207; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show Outpost Network #3 [ 2x Solo/Duo/Trio ] FULLWIPED 30.08?
Rust Server Score lists that include Outpost Network #3 [ 2x Solo/Duo/Trio ] FULLWIPED 30.08: 2x Rust servers, graded and Best community servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Gather rate: 2x.
Rules and settings
What settings and rules apply on Outpost Network #3 [ 2x Solo/Duo/Trio ] FULLWIPED 30.08?
The name of Outpost Network #3 [ 2x Solo/Duo/Trio ] FULLWIPED 30.08 points to a 2x gather rate. The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. 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 Outpost Network #3 [ 2x Solo/Duo/Trio ] FULLWIPED 30.08 uses?
A procedural map of size 1,000 and seed 1337, generated by the game, is what Outpost Network #3 [ 2x Solo/Duo/Trio ] FULLWIPED 30.08 runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
How do you get onto Outpost Network #3 [ 2x Solo/Duo/Trio ] FULLWIPED 30.08?
To connect, start Rust, press F1, and type client.connect 37.60.224.119:29915. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp16,ptrak,$r?,v2633,gmrust,cs163207,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp16
Max playersThe server holds 16 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs163207
BuildThis runs on build 163207.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$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 uptime (A); performance is the one to work on (F).