Test your own drone's Remote ID

Building, integrating or retrofitting Remote ID? DroneScout shows exactly what your drone broadcasts — every message, every field, the radio transport and the signal strength — and flags missing mandatory fields. Free, on the phone you already have.

Free to download. Optional Silver, Gold and Platinum subscriptions. · Last updated: 2026-10-10

Why test with a receiver

A Remote ID module that passes on the bench can still fail in the air: an operator ID that was never filled in, a take-off position that drifts, an antenna that goes deaf in one direction, or a transport that ordinary receivers ignore. Some of these problems exist in products that are on sale with an FAA-accepted Declaration of Compliance — see Why some drones show up late or with missing details. The quickest way to find them is to look at your broadcast the way a police officer or a member of the public will: with a phone.

DroneScout decodes ASTM F3411 (the FAA's means of compliance), ASD-STAN EN 4709-002 (EU) and China's GB 46750-2025, over Bluetooth Legacy, Bluetooth Long Range S8, Wi-Fi Beacon and Wi-Fi NaN. Everything below is in the free version.

What DroneScout shows you

Tap your drone on the map to open its details.

Basic tab:

• Compliant: a green check when the mandatory fields are present, a warning sign when one is missing (more below).
• Type: the radio transport this drone was received on — Bluetooth Legacy, Bluetooth Long Range, Wi-Fi Beacon or Wi-Fi NaN.
• Signal strength (RSSI) in dBm, and the standard it was decoded as.
• First seen and last seen, status (airborne or grounded), height and height type, speed, operator ID, category and class.

Full tab: every field of every message type — Basic ID, Location, Self ID, System, Operator ID and Auth — as decoded, with a count of how many packets of each type have been received, and Msg Δ, the average time between received messages. A message type stuck at zero is never being sent; a count that rises much more slowly than the others points to a message rate problem.

Export: Export raw messages in the Full tab saves every received message to CSV, to attach to a bug report or compare between firmware versions. The share icon in the details header exports the flight track to GPX.

How the compliance check works

DroneScout checks the latest received packet against the mandatory fields of the rules that apply where the drone reports it is:

• US and Japan: a serial number in the ANSI/CTA-2063-A format, a valid position with speed and timestamp, geodetic (WGS-84) altitude, and the rest of the mandatory System data.
• EU (EASA), the UK and Singapore: also a valid 16-character operator registration number, and height above take-off — the field pilots most often leave empty in practice.
• China (GB 46750-2025): serial number and registration ID, operator position, position type, altitude and classification.

The drone needs to be in the air with a GPS fix for a fair result. This is a quick confidence check, not a certification test: it doesn't measure transmit power, timing accuracy or position accuracy, and it doesn't check track direction or vertical speed. Tap the ? next to Compliant in the app for the details.

Test the range, not just the fields

Most real-world Remote ID problems are about the radio, not the data. A simple field test:

1. Walk away from the hovering drone and watch the RSSI and last seen. Compare with a drone you know is good, at the same distance.
2. Rotate the drone a full turn at a fixed distance. If it disappears in some directions, the antenna pattern has deep gaps — a common problem with small integrated antennas.
3. Check every transport you claim. A phone shows which transport each drone arrived on; if your module should send Bluetooth Long Range but you only ever see Legacy, something is wrong.
4. Mind the receiver. An iPhone receives only Bluetooth Legacy, and Android throttles Wi-Fi scanning to about twice a minute. DroneScout Bridge receives every transport — including 5 GHz Wi-Fi on the ds110 — so a missing drone is the transmitter's fault, not the phone's. See See more drones on Android.

From the people who build Remote ID modules

DroneScout is made by BlueMark Innovations, which has built Remote ID transmitters and receivers since 2022. The DroneBeacon db300 is, as of October 2026, the only Standard Remote ID module on the U.S. DoW/DoD Blue UAS Framework: NDAA compliant, FCC certified, ASTM F3411-22a and ASD-STAN EN 4709-002, Bluetooth 4 Legacy and Bluetooth 5 Long Range, with MAVLink and DroneCAN for ArduPilot and PX4. Approved components like the db300 don't need to be assessed again in your drone's Blue UAS review. More: db300 Blue UAS Remote ID module.

Questions about integrating Remote ID, or a custom version of the app for your drones: [email protected].