Use the Admin Radar Plugin on Rust

Admin Radar, by nivex, gives staff an on-screen radar for a Rust server: labels over players, boxes, stashes, vehicles and other entities, drawn with a refresh time and a distance you choose. It is a moderation tool for spotting cheating, and it only shows to the person using it.

Checked against Admin Radar 5.4.4 on uMod, October 2026 (released 2 October 2026). uMod describes it as a radar for admins to help detect cheaters and other entities. It compiled and loaded on our test Carbon server on the current Rust build.

Install it

Open the Plugins tab, stay on Store, search for AdminRadar and press Install. How to install Oxide/uMod plugins on your Rust server covers the tab and config window.

On Oxide, a newly installed plugin stays unloaded until you restart the server or type oxide.load AdminRadar in the Console. On Carbon it loads by itself within seconds, and oxide.load does nothing there, so use c.load AdminRadar, c.unload AdminRadar and c.reload AdminRadar. Permissions only exist once the plugin has loaded, so grant them afterwards.

Who can use it

The plugin checks access in this order:

1. If Restrict Access To Steam64 IDs in the config lists any IDs, only those players can use it.
2. Otherwise, anyone holding the permission adminradar.allowed can.
3. Otherwise, anyone whose admin level is at least Restrict Access To Auth Level, which is 1 by default. Level 1 is a moderator and level 2 is an owner, set with moderatorid and ownerid as described in Rust server.cfg and admin commands.

To give a non-admin access, grant the permission from the Console, using their SteamID64:

oxide.grant user 76561198000000001 adminradar.allowed

On Carbon, oxide.grant does nothing. Use c.grant with the same arguments, for example c.grant user 76561198000000001 adminradar.allowed. Treat this permission like admin access. The radar shows where other players and their stashes are, and the plugin's code sets the in-game admin flag on a non-admin holder while the radar is on and clears it again afterwards.

The plugin registers two more permissions. adminradar.list lets /radar list print who is using the radar, and adminradar.auto starts the radar for that player each time they wake up in game.

Using the radar

These are chat commands, typed in game:

• /radar turns the radar on with the defaults, which are a 5 second refresh and a 500 metre distance. The same command turns it off again.
• /radar <seconds> <metres> <filters> sets the refresh, the distance and what to show, for example /radar 1 1000 box loot stash or /radar 0.5 400 all.
• /radar help lists the filters available on your version.
• /radar f reuses your previous filters.
• /radar online shows only the boxes of online players when the box filter is on.
• /radar ui shows or hides the quick-toggle buttons, /radar vision shows where players are looking, and /radar ext shows extended information for players.
• /radar drops shows dropped items within a set distance.

Both the chat command and a second name for it are settings, Chat Command and Second Command, and both default to radar.

Limits and settings

The first load writes oxide/config/AdminRadar.json (carbon/configs on Carbon). Edit it in the Config window on the Plugins tab. Useful settings:

• Max Active Filters is set per level: owners 0, moderators 4 and holders of adminradar.allowed 2. A limit above zero also drops the all filter. In the plugin's code the refresh and distance are read first, then everything typed after /radar is cut to the limit with args.Take(limit), so those two numbers use up part of it. A moderator limit of 4 leaves two filters after /radar 1 500.
• Default Distance is 500 and Default Refresh Time is 5, in metres and seconds. Minimum Refresh Time is 1, and the radar never refreshes faster than that, so a request for 0.5 seconds runs at 1.
• Deactivate Radar After X Seconds Inactive is 300, so an idle radar switches itself off.
• Re-use Cooldown, Seconds is 0, which means no cooldown.

Common problems

1. "You are not allowed to use this command." You have an admin level but the access order above does not let you in, for instance because the Steam64 list is not empty.
2. The command does nothing for a player with no access. The plugin answers a player who has no admin level with "Unknown command", as though it did not exist.
3. Fewer filters appear than you typed. Check Max Active Filters for your level.
4. The radar switched off by itself. That is the inactivity timer above.