Working its way up from the back of the class: #15,316 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
51/ 100
D
Moving up: up 332 places this week.
A term to build on.
Strongest in momentum (D); standing 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.
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 18 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 70% 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
Next wipe Thursday 5 November, 19:00 UTC, in 7d 21h.
The 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
You won't see a region from Project Saga PVE Rust, whose region code is ca1. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 165.23.83.98:28017.
How reliable is Project Saga PVE Rust, and is it up?
You cannot join now: Project Saga PVE Rust is offline, last seen 10 days 9 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 18 October 2026, Rust Server Score saw it for the first time.
Which Rust version is Project Saga PVE Rust running?
You will find Project Saga PVE Rust on Rust network protocol 2582 and build 115870, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
On what schedule does Project Saga PVE Rust reset?
The next wipe on Project Saga PVE Rust is a projection from the force wipe. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. The world it runs now was created 600 days 22 hours. Its tags record that it wipes monthly.
Player numbers
Where does Project Saga PVE Rust place in the wider field of Rust servers?
In the top 70% of all ranked servers, Project Saga PVE Rust sits at #15,316 for player hours over the last seven days.
How many players does Project Saga PVE Rust usually have?
The last sighting of Project Saga PVE Rust was 10 days 9 hours ago, and it is offline right now.
Lists and filters
How should you read the tags on Project Saga PVE Rust?
gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): The server holds 50 slots; v2582 (Protocol): To get in, your game needs to be on the same version: the protocol is 2582; cs115870 (Build): Build number: 115870; ptsw (Networking): 'sw' is the network layer here; $rca1 (Region code): It is filed under the region code ca1; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded are the tags Project Saga PVE Rust publishes, and the game's server browser reads them. 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 lists and filters on Rust Server Score show Project Saga PVE Rust?
Rust Server Score lists that include Project Saga PVE Rust: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Wipe schedule: Monthly.
Map and rules
Which rules does Project Saga PVE Rust enforce, and what are its settings?
You will find no gather rate in the name of Project Saga PVE Rust. No group limit is published. survival is the mode here, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. The server runs Valve's anti-cheat, VAC.
Project Saga PVE Rust runs which map?
A procedural map of size 4,500 and seed 1337, generated by the game, is what Project Saga PVE Rust runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Connecting
How should you connect to Project Saga PVE Rust?
Enter client.connect 165.23.83.98:28017 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,ptsw,$rca1,v2582,^m,gmrust,cs115870,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp50
Max playersThe server holds 50 slots.
v2582
ProtocolTo get in, your game needs to be on the same version: the protocol is 2582.
cs115870
BuildBuild number: 115870.
ptsw
Networking'sw' is the network layer here.
$rca1
Region codeIt is filed under the region code ca1.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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 term to build on. Strongest in momentum (D); standing is the one to work on (F).