sensors Mode-S transponder
7C57D1
ICAO 24-bit transponder address · allocated to Australia
Currently assigned to VH-RMR · PIPER PA-32R-300/301/301T · operated by MAVERICK AVIATION PTY LTD
- Hex
- 7C57D1
- Octal
- 37053721
- Decimal
- 8,148,945
- Country
- AU
- Tail
- VH-RMR
- Type
- P32R
- Flights observed
- 77
- Distinct callsigns
- 1
- Country
- AU
- Last broadcast
- Jul 25, 04:15 UTC
Last known position
Country allocation
The ICAO 24-bit address 7C57D1 falls within the block assigned to Australia (AU) by ICAO Annex 10, Volume III. Every aircraft registered in Australia receives a permanent address from this block at the time of registration; the address stays with the airframe even if the aircraft is re-registered to a different operator within the country.
Callsign history 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| RMR | - | 77 | 2026-07-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | RMR | JAD → JAD | Jul 25, 03:35 UTC | Jul 25, 04:10 UTC | 35m |
| 2026-07-17 | RMR | JAD → JAD | Jul 17, 09:30 UTC | Jul 17, 11:10 UTC | 1h 40m |
| 2026-07-13 | RMR | - | Jul 13, 10:50 UTC | Jul 13, 11:20 UTC | 30m |
| 2026-07-13 | RMR | - | Jul 13, 09:50 UTC | Jul 13, 10:15 UTC | 25m |
| 2026-07-12 | RMR | - | Jul 12, 06:25 UTC | Jul 12, 06:50 UTC | 25m |
| 2026-07-12 | RMR | - | Jul 12, 03:50 UTC | Jul 12, 04:15 UTC | 25m |
| 2026-07-11 | RMR | JAD → JAD | Jul 11, 05:45 UTC | Jul 11, 06:15 UTC | 30m |
| 2026-07-08 | RMR | - | Jul 8, 07:30 UTC | Jul 8, 07:55 UTC | 25m |
| 2026-07-08 | RMR | - | Jul 8, 01:30 UTC | Jul 8, 01:55 UTC | 25m |
| 2026-07-07 | RMR | - | Jul 7, 03:05 UTC | Jul 7, 03:25 UTC | 20m |
| 2026-07-07 | RMR | - | Jul 7, 00:45 UTC | Jul 7, 01:20 UTC | 35m |
| 2026-06-30 | RMR | - | Jun 30, 08:25 UTC | Jun 30, 08:50 UTC | 25m |
| 2026-06-30 | RMR | - | Jun 30, 00:04 UTC | Jun 30, 00:30 UTC | 25m |
| 2026-06-25 | RMR | - | Jun 25, 08:50 UTC | Jun 25, 09:25 UTC | 35m |
| 2026-06-24 | RMR | - | Jun 24, 23:45 UTC | Jun 25, 00:19 UTC | 35m |
| 2026-06-23 | RMR | - | Jun 23, 08:45 UTC | Jun 23, 09:09 UTC | 25m |
| 2026-06-23 | RMR | - | Jun 23, 00:39 UTC | Jun 23, 01:10 UTC | 30m |
| 2026-06-19 | RMR | JAD → JAD | Jun 19, 05:24 UTC | Jun 19, 06:20 UTC | 55m |
| 2026-06-18 | RMR | - | Jun 18, 10:05 UTC | Jun 18, 10:35 UTC | 30m |
| 2026-06-18 | RMR | - | Jun 18, 08:30 UTC | Jun 18, 09:10 UTC | 40m |
| 2026-06-17 | RMR | - | Jun 17, 23:00 UTC | Jun 18, 00:10 UTC | 1h 10m |
| 2026-06-16 | RMR | - | Jun 16, 08:15 UTC | Jun 16, 08:35 UTC | 20m |
| 2026-06-16 | RMR | - | Jun 16, 00:00 UTC | Jun 16, 00:24 UTC | 25m |
| 2026-06-10 | RMR | - | Jun 10, 08:10 UTC | Jun 10, 08:35 UTC | 25m |
| 2026-06-09 | RMR | - | Jun 9, 23:50 UTC | Jun 10, 00:10 UTC | 20m |
| 2026-06-09 | RMR | - | Jun 9, 08:40 UTC | Jun 9, 09:00 UTC | 20m |
| 2026-06-08 | RMR | - | Jun 8, 23:20 UTC | Jun 8, 23:45 UTC | 25m |
| 2026-06-05 | RMR | - | Jun 5, 08:00 UTC | Jun 5, 08:25 UTC | 25m |
| 2026-06-05 | RMR | - | Jun 5, 06:25 UTC | Jun 5, 06:40 UTC | 15m |
| 2026-06-05 | RMR | - | Jun 5, 04:05 UTC | Jun 5, 04:20 UTC | 15m |
| 2026-06-05 | RMR | - | Jun 5, 02:10 UTC | Jun 5, 02:45 UTC | 35m |
| 2026-06-04 | RMR | - | Jun 4, 08:45 UTC | Jun 4, 09:10 UTC | 25m |
| 2026-06-04 | RMR | - | Jun 4, 00:50 UTC | Jun 4, 01:25 UTC | 35m |
| 2026-06-02 | RMR | - | Jun 2, 08:05 UTC | Jun 2, 08:30 UTC | 25m |
| 2026-06-02 | RMR | - | Jun 2, 00:10 UTC | Jun 2, 00:35 UTC | 25m |
| 2026-06-01 | RMR | - | Jun 1, 06:10 UTC | Jun 1, 06:40 UTC | 30m |
| 2026-05-29 | RMR | - | May 29, 03:30 UTC | May 29, 04:00 UTC | 30m |
| 2026-05-28 | RMR | - | May 28, 08:50 UTC | May 28, 09:20 UTC | 30m |
| 2026-05-28 | RMR | - | May 28, 00:40 UTC | May 28, 01:05 UTC | 25m |
| 2026-05-26 | RMR | - | May 26, 08:34 UTC | May 26, 09:09 UTC | 35m |
| 2026-05-25 | RMR | - | May 25, 23:19 UTC | May 25, 23:49 UTC | 30m |
| 2026-05-21 | RMR | - | May 21, 07:55 UTC | May 21, 08:20 UTC | 25m |
| 2026-05-20 | RMR | - | May 20, 23:20 UTC | May 20, 23:50 UTC | 30m |
| 2026-05-19 | RMR | - | May 19, 08:25 UTC | May 19, 08:50 UTC | 25m |
| 2026-05-19 | RMR | - | May 19, 00:00 UTC | May 19, 00:25 UTC | 25m |
| 2026-05-15 | RMR | - | May 15, 08:25 UTC | May 15, 09:10 UTC | 45m |
| 2026-05-14 | RMR | - | May 14, 22:45 UTC | May 14, 23:55 UTC | 1h 10m |
| 2026-05-14 | RMR | - | May 14, 08:40 UTC | May 14, 09:10 UTC | 30m |
| 2026-05-13 | RMR | - | May 13, 23:15 UTC | May 13, 23:45 UTC | 30m |
| 2026-05-13 | RMR | - | May 13, 07:20 UTC | May 13, 07:50 UTC | 30m |
About Mode-S
A Mode-S transponder code (also called an "ICAO 24-bit address" or "hex code") is a 6-character hexadecimal identifier permanently assigned to an aircraft when it's first registered. Unlike callsigns (which change with each flight) or registrations (which can change if an aircraft is sold internationally), the Mode-S address stays with the airframe for the life of the aircraft in that country.
Every ADS-B transmission from an aircraft includes its Mode-S address, making it the most reliable way to identify a specific airframe. Flight-tracking services like Apparatus use the Mode-S address as the primary key for tying position broadcasts, callsigns, and ownership records together.
Prefer a tail-number view? See the VH-RMR page for operator, model, and routing details .