Working its way up from the back of the class: #15,998 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
53/ 100
D
Moving up: up 899 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.
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
You won't see a region from insprd local test, whose region code is fra. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 80.187.121.74:28015 is the address to use.
How reliable is insprd local test, and is it up?
The server is down: insprd local test is offline now, with the last sighting 24 days 20 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. The first sighting by Rust Server Score was on 1 October 2026.
What Rust version is insprd local test on?
The server insprd local test is on Rust network protocol 2634 and build 166494 under Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
How frequently does insprd local test wipe its map?
insprd 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 26 days 14 hours.
Player count
Where does insprd local test sit among Rust servers?
Over the last seven days, insprd local test has #15,998 for player hours, in the top 70% of all ranked servers.
How many players does insprd local test usually have?
It has been 24 days 20 hours since insprd local test was last seen, and it is offline right now.
Lists and filters
How should you read the tags on insprd local test?
gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): 50 slots are available; ts10 (Group limit): No team may go above 10; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166494 (Build): The game build is 166494; ptrak (Networking): RakNet handles it, the game's default network layer; $rfra (Region code): It is filed under the region code fra; ^c (Creative): No gathering here: it is a sandbox where you build what you want; ^e (Minigames): Minigames here include arenas, Bedwars and parkour; ^d (Combat training): You are given the loot; the point is aim and PvP practice; ^j (Battle royale): Gather loot and battle while the zone tightens; ^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 are the tags insprd local test 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.
Where does insprd local test appear in the Rust Server Score lists and filters?
Rust Server Score lists that include insprd local test: Modded Rust servers, graded, Rust combat training servers, graded, Rust build and creative servers and Rust creative servers, scored and graded. These filters bring it up on the server list: Type: Modded; Server tag: Creative ^c, Minigames ^e, Combat training ^d, Battle royale ^j, Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules and settings
Which rules does insprd local test enforce, and what are its settings?
You will find no gather rate in the name of insprd local test. A group here can reach 10 players. It runs minigames & battle royale, battle royale, arenas, parkour and Bedwars. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. You are covered by VAC, Valve's anti-cheat.
Getting in
How should you connect to insprd local test?
Enter client.connect 80.187.121.74:28015 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,ptrak,$rfra,v2634,^c,^e,^d,^j,gmrust,cs166494,ts10,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max players50 slots are available.
ts10
Group limitNo team may go above 10.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166494
BuildThe game build is 166494.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$rfra
Region codeIt is filed under the region code fra.
Gameplay
^c
CreativeNo gathering here: it is a sandbox where you build what you want.
^e
MinigamesMinigames here include arenas, Bedwars and parkour.
^d
Combat trainingYou are given the loot; the point is aim and PvP practice.
^j
Battle royaleGather loot and battle while the zone tightens.
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).