On the class lists: F (43), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average0peak –
Rank#15,344top 69% · #1503 in NA
Last wipe27d agomonthly schedule
Next wipe7d 3hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 100 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,344 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
9/ 100
F
Needs to work on its frame rate: 5 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 1,263 places this week. Nothing a good wipe can't fix.
A term to build on.
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.
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 69% of all ranked servers, top 81% in NA. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···F···
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 3h.
The force wipe · high confidence
usual gap0.8 daysbetween real wipes
wipe-day peak3players, last three wipes
Coming wipes
7d 3hThu 5 Nov, 19:00 UTCFW
35d 3hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Thu 1 OctThu 1 Oct
Players each hour, from the hour of the wipe. The latest peaked at 3, 27 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 1 Oct, 18:12 UTCFW27d ago
3
–
running
0
Thu 1 Oct, 00:02 UTC28d ago
3
–
0.8 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
Where in the world is [US] Projekt Phoenix│PvE/PvP│Beta?
You'll see [US] Projekt Phoenix│PvE/PvP│Beta listed in North America, tagged NA. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 66.51.99.80:28010 is the address to use.
How reliable is [US] Projekt Phoenix│PvE/PvP│Beta, and is it up?
Right now, [US] Projekt Phoenix│PvE/PvP│Beta is online. The uptime it reports puts the last restart at about 1 hours ago. For the last 7 full days, it was up 167 of 168 hours, or 99% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
How well does [US] Projekt Phoenix│PvE/PvP│Beta run?
The average over the last 48 hours was 5 server fps, and it never went below 5. At its peak, it held 146,993 entities, including buildings, deployables and all else in the world. Memory use reached up to 4,542 MB. Lag is what players feel when fps is low and the entity count climbs.
On what Rust version does [US] Projekt Phoenix│PvE/PvP│Beta sit?
The server [US] Projekt Phoenix│PvE/PvP│Beta is on Rust network protocol 2635 and build 168909 under Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
When does [US] Projekt Phoenix│PvE/PvP│Beta wipe, and how often?
The force wipe each month is the only wipe [US] Projekt Phoenix│PvE/PvP│Beta takes. 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 27 days 21 hours. The tags show a monthly wipe schedule.
What should you expect from wipe day on [US] Projekt Phoenix│PvE/PvP│Beta?
The average peak on its recent wipes was 3 players. The crowd on the latest wipe was largest 27 hours after it began.
Population
Where does [US] Projekt Phoenix│PvE/PvP│Beta sit among Rust servers?
In North America, [US] Projekt Phoenix│PvE/PvP│Beta is #1,503, and overall it is #15,344 on player hours over the last seven days, in the top 69% of all ranked servers.
How many players does [US] Projekt Phoenix│PvE/PvP│Beta usually have?
With 100 slots available, [US] Projekt Phoenix│PvE/PvP│Beta currently has 0 players. A seven-day average of 0 players applies here.
Tags
What is meant by the tags on [US] Projekt Phoenix│PvE/PvP│Beta?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp100 (Max players): Its slot count is 100; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; NA (North America): In the server browser it appears under North America are the tags [US] Projekt Phoenix│PvE/PvP│Beta 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 [US] Projekt Phoenix│PvE/PvP│Beta?
These Rust Server Score lists count [US] Projekt Phoenix│PvE/PvP│Beta among them: Modded Rust servers, graded and North America Rust servers, graded. It shows under the following filters on the server list: Region: North America; Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Rules and settings
What settings and rules apply on [US] Projekt Phoenix│PvE/PvP│Beta?
You will find no gather rate in the name of [US] Projekt Phoenix│PvE/PvP│Beta. With no change from the game default, groups take up to 8 players. You get survival here, gather, build and raid, as in 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. VAC, Valve's anti-cheat, is enabled.
[US] Projekt Phoenix│PvE/PvP│Beta runs which map?
[US] Projekt Phoenix│PvE/PvP│Beta runs a game-generated procedural map at size 4,750, seed 938220579. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Connecting
What is the way to join [US] Projekt Phoenix│PvE/PvP│Beta?
To connect, start Rust, press F1, and type client.connect 66.51.99.80:28010. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,^m,NA,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp100
Max playersIts slot count is 100.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
Region
NA
North AmericaIn the server browser it appears under North America.
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); population is the one to work on (F).