Working its way up from the back of the class: #15,108 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
41/ 100
F
Slipped a little: down 2,652 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (F); 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 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
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 Project Plagued | Flying Car LOCAL TEST?
Project Plagued | Flying Car LOCAL TEST leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 24.45.218.201:29885.
How reliable is Project Plagued | Flying Car LOCAL TEST, and is it up?
You cannot join now: Project Plagued | Flying Car LOCAL TEST is offline, last seen 12 days 12 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 15 October 2026, Rust Server Score saw it for the first time.
On what Rust version does Project Plagued | Flying Car LOCAL TEST sit?
The server Project Plagued | Flying Car LOCAL TEST is on Rust network protocol 2634 and build 167398 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
How frequently does Project Plagued | Flying Car LOCAL TEST wipe its map?
Project Plagued | Flying Car LOCAL TEST 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. It has been running its current world for 13 days 16 hours.
Player numbers
Where does Project Plagued | Flying Car LOCAL TEST place in the wider field of Rust servers?
In the top 70% of all ranked servers, Project Plagued | Flying Car LOCAL TEST sits at #15,108 for player hours over the last seven days.
Is Project Plagued | Flying Car LOCAL TEST a busy server?
Project Plagued | Flying Car LOCAL TEST is offline at the moment; the last time it was seen was 12 days 12 hours ago.
Lists and filters
What do Project Plagued | Flying Car LOCAL TEST's tags stand for?
You'll see Project Plagued | Flying Car LOCAL TEST tagged with gmrust (Game mode): Survival in the standard Rust style; mp4 (Max players): The server holds 4 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): Join only if your game runs protocol 2634; cs167398 (Build): This runs on build 167398; ptrak (Networking): RakNet handles it, the game's default network layer; $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 in the browser, which picks them up from the server. 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 Project Plagued | Flying Car LOCAL TEST?
Rust Server Score lists that include Project Plagued | Flying Car LOCAL TEST: 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; Last wipe: In the last 2 weeks.
Server rules
How is Project Plagued | Flying Car LOCAL TEST set up, and what rules does it keep?
The name of Project Plagued | Flying Car LOCAL TEST gives no 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. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. You are covered by VAC, Valve's anti-cheat.
How to join
How do you get onto Project Plagued | Flying Car LOCAL TEST?
To connect, start Rust, press F1, and type client.connect 24.45.218.201:29885. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp4,ptrak,$r?,v2634,gmrust,cs167398,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp4
Max playersThe server holds 4 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167398
BuildThis runs on build 167398.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$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 term to build on. Strongest in momentum (F); standing is the one to work on (F).