On the class lists: D (49), with population over 48 hours and no performance mark.
Players now3/ 506% full
7-day average1peak 3
Rank#3,749top 17%
Last wipe5h agono schedule published
Next wipe6d 16hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
1/ 100
F
A quiet classroom so far: 1 of 50 on average. Plenty of space to grow.
Standingrank on player hours
83/ 100
B+
Holds a respectable place: #3,749 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
85/ 100
A−
Mostly smooth: 51 server fps on average.
Wipeskeeping the crowd after a wipe
33/ 100
F
Needs to keep more players after wipe day: 33% of wipes kept half their crowd.
Momentumrank now against a week ago
32/ 100
F
Lost ground: down 1,359 places this week. A strong wipe could turn it round.
A fair term, with more to come.
Strongest in uptime (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.
AveragePeakWipe
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Server fpsWipe
EntitiesWipe
Memory, MBWipe
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 17% of all ranked servers, and #140 of the solo servers (top 62%). Ranked on player hours over the last seven days.
Attendance: the wipe record
4 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
·······
···F···
·······
···W···
·······
···W·
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
a steady gap
Next wipe Thursday 5 November, 19:00 UTC, in 6d 16h.
The force wipe · high confidence
usual gap14 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak3players, last three wipes
crowd held33%else halves by day 10.5
Coming wipes
6d 16hThu 5 Nov, 19:00 UTCFW
13d 17hThu 12 Nov, 19:40 UTC
27d 16hThu 26 Nov, 18:41 UTC
34d 16hThu 3 Dec, 19:00 UTCFW
41d 15hThu 10 Dec, 17:42 UTC
The first 48 hours of its last wipes
Thu 15 OctThu 1 OctThu 17 Sep
Players each hour, from the hour of the wipe. The latest peaked at 5, 29 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 29 Oct, 20:40 UTC5h ago
–
–
running
0
Thu 15 Oct, 22:25 UTC14d ago
5
halved by day 11
13.9 days
0
Thu 1 Oct, 18:31 UTCFW28d ago
2
✓ held half
14.2 days
0
Thu 17 Sep, 19:30 UTC42d ago
3
halved by day 10
14 days
1
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 Last Wolf Sanctuary 2x Bi-weekly | Solo Only?
Last Wolf Sanctuary 2x Bi-weekly | Solo Only leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 64.42.177.222:28015.
How dependable is Last Wolf Sanctuary 2x Bi-weekly | Solo Only, and is it online at the moment?
Right now, Last Wolf Sanctuary 2x Bi-weekly | Solo Only is online. According to its reported uptime, the last restart was about 4 hours ago. It was up 99% of the time over the last 7 full days, 167 of 168 hours. On 13 September 2026, Rust Server Score saw it for the first time.
Does Last Wolf Sanctuary 2x Bi-weekly | Solo Only perform well?
The average over the last 48 hours was 51 server fps, and it never went below 36. Buildings, deployables and everything else in the world added up to as many as 139,556 entities. At its highest, it used 4,431 MB of memory. Players feel lag when fps drops and entities pile up.
On what Rust version does Last Wolf Sanctuary 2x Bi-weekly | Solo Only sit?
Rust network protocol 2635 and build 168909 on Windows is what Last Wolf Sanctuary 2x Bi-weekly | Solo Only runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
How frequently does Last Wolf Sanctuary 2x Bi-weekly | Solo Only wipe its map?
The gap between Last Wolf Sanctuary 2x Bi-weekly | Solo Only's wipes has been about 14 days recently. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. It has been running its current world for 5 hours.
What should you expect from wipe day on Last Wolf Sanctuary 2x Bi-weekly | Solo Only?
Recent wipes have peaked at 3 players on average. Peak numbers came 29 hours into the latest wipe. The crowd stayed above half that peak, right through to the next wipe, in 33% of its recent wipes. Day 10.5 is when it sank below half in the wipes that did not hold.
Population
Where does Last Wolf Sanctuary 2x Bi-weekly | Solo Only sit among Rust servers?
Over the last seven days, Last Wolf Sanctuary 2x Bi-weekly | Solo Only has #3,749 for player hours, in the top 17% of all ranked servers. It comes #140 among servers in the solo group.
What does the population on Last Wolf Sanctuary 2x Bi-weekly | Solo Only look like?
Last Wolf Sanctuary 2x Bi-weekly | Solo Only is showing 3 players right now, with 50 slots in total. It peaked at 3 and averaged 1 players over the last seven days. Over the last 48 hours, the peak hour was 23:00 UTC, averaging 2 players.
Tags
How should you read the tags on Last Wolf Sanctuary 2x Bi-weekly | Solo Only?
The game's browser takes its cue from the tags Last Wolf Sanctuary 2x Bi-weekly | Solo Only has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp50 (Max players): 50 slots are available; ts1 (Group limit): A team can hold 1 players at most; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which Rust Server Score filters and lists feature Last Wolf Sanctuary 2x Bi-weekly | Solo Only?
Rust Server Score lists that include Last Wolf Sanctuary 2x Bi-weekly | Solo Only: 2x Rust servers, graded, Modded Rust servers, graded and Solo Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: Solo; Last wipe: In the last 24 hours; Gather rate: 2x.
Map and rules
Which rules does Last Wolf Sanctuary 2x Bi-weekly | Solo Only enforce, and what are its settings?
Going by its name, Last Wolf Sanctuary 2x Bi-weekly | Solo Only runs 2x gather. No teams are allowed: it is solo only. survival is the mode here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
Last Wolf Sanctuary 2x Bi-weekly | Solo Only runs which map?
The game generates the procedural map on Last Wolf Sanctuary 2x Bi-weekly | Solo Only at size 4,500 with seed 1158910588. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
What is the way to join Last Wolf Sanctuary 2x Bi-weekly | Solo Only?
Enter client.connect 64.42.177.222:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. You can find its website at https://discord.com/invite/2bfYK3Sr.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2635,gmrust,cs168909,ts1,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp50
Max players50 slots are available.
ts1
Group limitA team can hold 1 players at most.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
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 fair term, with more to come. Strongest in uptime (A+); population is the one to work on (F).