Working its way up from the back of the class: #16,173 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
48/ 100
D
Slipped a little: down 660 places this week. Nothing a good wipe can't fix.
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.
AveragePeakWipe
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.
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.
This server has not answered a direct query in the last 30 days.
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.
This server has not answered a direct query in the last 60 days.
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.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 71% 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
In what location does Project Plagued Iron Valley 2500 WIPE READINESS LOCAL sit?
No region is published for Project Plagued Iron Valley 2500 WIPE READINESS LOCAL. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 24.45.218.201:29525.
Is Project Plagued Iron Valley 2500 WIPE READINESS LOCAL up, and how steady is its uptime?
You cannot join now: Project Plagued Iron Valley 2500 WIPE READINESS LOCAL is offline, last seen 33 days 10 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 20 September 2026, Rust Server Score saw it for the first time.
Which Rust version is Project Plagued Iron Valley 2500 WIPE READINESS LOCAL running?
You will find Project Plagued Iron Valley 2500 WIPE READINESS LOCAL on Rust network protocol 2633 and build 162989, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does Project Plagued Iron Valley 2500 WIPE READINESS LOCAL reset?
The record holds too few of Project Plagued Iron Valley 2500 WIPE READINESS LOCAL's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 37 days 17 hours.
Player count
Where does Project Plagued Iron Valley 2500 WIPE READINESS LOCAL sit among Rust servers?
Over the last seven days, Project Plagued Iron Valley 2500 WIPE READINESS LOCAL has #16,173 for player hours, in the top 71% of all ranked servers.
Is Project Plagued Iron Valley 2500 WIPE READINESS LOCAL a busy server?
The last sighting of Project Plagued Iron Valley 2500 WIPE READINESS LOCAL was 33 days 10 hours ago, and it is offline right now.
Tags and filters
What is meant by the tags on Project Plagued Iron Valley 2500 WIPE READINESS LOCAL?
You'll see Project Plagued Iron Valley 2500 WIPE READINESS LOCAL tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp5 (Max players): The server holds 5 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): Join only if your game runs protocol 2633; cs162989 (Build): This runs on build 162989; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded in the browser, which picks them up from the server. 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.
Which lists and filters on Rust Server Score show Project Plagued Iron Valley 2500 WIPE READINESS LOCAL?
Rust Server Score lists that include Project Plagued Iron Valley 2500 WIPE READINESS LOCAL: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
Which rules does Project Plagued Iron Valley 2500 WIPE READINESS LOCAL enforce, and what are its settings?
Nothing in the name of Project Plagued Iron Valley 2500 WIPE READINESS LOCAL states a gather rate. 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. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. VAC, Valve's anti-cheat, is enabled.
Connecting
How should you connect to Project Plagued Iron Valley 2500 WIPE READINESS LOCAL?
To connect, start Rust, press F1, and type client.connect 24.45.218.201:29525. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp5,ptrak,$r?,v2633,gmrust,cs162989,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp5
Max playersThe server holds 5 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs162989
BuildThis runs on build 162989.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it 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 term to build on. Strongest in momentum (D); standing is the one to work on (F).