Working its way up from the back of the class: #15,471 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
17/ 100
F
Lost ground: down 10,170 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); momentum 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.
AveragePeak
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
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. You can connect at 80.187.122.75:28015.
How dependable is insprd local test, and is it online at the moment?
At this moment, insprd local test is offline; the last time it was seen was 34 days 12 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 17 September 2026.
Which Rust version is insprd local test running?
You will find insprd local test on Rust network protocol 2633 and build 163794, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
How frequently does insprd local test wipe its map?
The record holds too few of insprd local test's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 47 days 1 hours.
Population
Where does insprd local test place in the wider field of Rust servers?
In the top 71% of all ranked servers, insprd local test sits at #15,471 for player hours over the last seven days.
How many players does insprd local test usually have?
It has been 34 days 12 hours since insprd local test was last seen, and it is offline right now.
Tags and filters
What do insprd local test's tags stand for?
You'll see insprd local test tagged with gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): Its slot count is 50; ts10 (Group limit): A team can hold 10 players at most; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs163794 (Build): Build number: 163794; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $rfra (Region code): fra is the region code this server uses; ^c (Creative): Build freely in this sandbox, with no gathering to do; ^e (Minigames): It hosts minigames such as arenas, Bedwars and parkour; ^d (Combat training): Practise aim and PvP, loot provided; ^j (Battle royale): Fight as the zone closes, looting as you go; ^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 insprd local test?
These Rust Server Score lists count insprd local test among them: 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
How is insprd local test set up, and what rules does it keep?
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, parkour, arenas, battle royale and Bedwars. 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.
Connecting
How do you get onto insprd local test?
To connect, start Rust, press F1, and type client.connect 80.187.122.75:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$rfra,v2633,^c,^e,^d,^j,gmrust,cs163794,ts10,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp50
Max playersIts slot count is 50.
ts10
Group limitA team can hold 10 players at most.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs163794
BuildBuild number: 163794.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$rfra
Region codefra is the region code this server uses.
Gameplay
^c
CreativeBuild freely in this sandbox, with no gathering to do.
^e
MinigamesIt hosts minigames such as arenas, Bedwars and parkour.
^d
Combat trainingPractise aim and PvP, loot provided.
^j
Battle royaleFight as the zone closes, looting as you go.
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 standing (F); momentum is the one to work on (F).