sensors Mode-S transponder
7C48A4
ICAO 24-bit transponder address · allocated to Australia
Currently assigned to VH-OMU · CESSNA 172 Skyhawk · operated by AIR GOLD COAST PTY. LTD.
- Hex
- 7C48A4
- Octal
- 37044244
- Decimal
- 8,145,060
- Country
- AU
- Tail
- VH-OMU
- Type
- C172
- Flights observed
- 50
- Distinct callsigns
- 1
- Country
- AU
- Last broadcast
- 16h ago
Last known position
Country allocation
The ICAO 24-bit address 7C48A4 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 |
|---|---|---|---|
| OMU | - | 50 | 2026-05-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | OMU | - | May 30, 04:50 UTC | May 30, 05:15 UTC | 25m |
| 2026-05-30 | OMU | - | May 30, 02:25 UTC | May 30, 03:20 UTC | 55m |
| 2026-05-29 | OMU | - | May 29, 23:05 UTC | May 30, 01:35 UTC | 2h 30m |
| 2026-05-21 | OMU | - | May 21, 04:15 UTC | May 21, 05:20 UTC | 1h 5m |
| 2026-05-21 | OMU | - | May 21, 01:30 UTC | May 21, 02:50 UTC | 1h 20m |
| 2026-05-20 | OMU | - | May 20, 22:50 UTC | May 20, 23:50 UTC | 1h 0m |
| 2026-05-20 | OMU | - | May 20, 05:10 UTC | May 20, 06:00 UTC | 50m |
| 2026-05-20 | OMU | - | May 20, 03:10 UTC | May 20, 04:35 UTC | 1h 25m |
| 2026-05-20 | OMU | - | May 20, 00:45 UTC | May 20, 01:20 UTC | 35m |
| 2026-05-19 | OMU | - | May 19, 22:05 UTC | May 19, 22:55 UTC | 50m |
| 2026-05-18 | OMU | - | May 18, 21:40 UTC | May 18, 22:30 UTC | 50m |
| 2026-05-11 | OMU | - | May 11, 00:45 UTC | May 11, 01:25 UTC | 40m |
| 2026-05-10 | OMU | - | May 10, 22:55 UTC | May 11, 00:05 UTC | 1h 10m |
| 2026-05-09 | OMU | - | May 9, 21:45 UTC | May 9, 22:10 UTC | 25m |
| 2026-05-09 | OMU | - | May 9, 05:20 UTC | May 9, 06:10 UTC | 50m |
| 2026-05-09 | OMU | - | May 9, 02:55 UTC | May 9, 03:35 UTC | 40m |
| 2026-05-08 | OMU | - | May 8, 23:40 UTC | May 9, 01:40 UTC | 2h 0m |
| 2026-05-07 | OMU | TWB → OOL | May 7, 23:24 UTC | May 8, 01:14 UTC | 1h 50m |
| 2026-05-07 | OMU | - | May 7, 21:50 UTC | May 7, 23:19 UTC | 1h 30m |
| 2026-05-07 | OMU | - | May 7, 04:00 UTC | May 7, 05:00 UTC | 1h 0m |
| 2026-05-07 | OMU | - | May 7, 01:50 UTC | May 7, 02:40 UTC | 50m |
| 2026-05-06 | OMU | - | May 6, 23:45 UTC | May 7, 00:55 UTC | 1h 10m |
| 2026-05-06 | OMU | - | May 6, 22:10 UTC | May 6, 23:00 UTC | 50m |
| 2026-05-05 | OMU | - | May 5, 04:00 UTC | May 5, 06:10 UTC | 2h 10m |
| 2026-05-05 | OMU | - | May 5, 01:55 UTC | May 5, 02:35 UTC | 40m |
| 2026-05-05 | OMU | - | May 5, 00:10 UTC | May 5, 00:35 UTC | 25m |
| 2026-05-04 | OMU | - | May 4, 05:55 UTC | May 4, 06:20 UTC | 25m |
| 2026-05-04 | OMU | - | May 4, 03:24 UTC | May 4, 03:49 UTC | 25m |
| 2026-05-02 | OMU | - | May 2, 22:20 UTC | May 3, 01:50 UTC | 3h 30m |
| 2026-05-02 | OMU | - | May 2, 02:00 UTC | May 2, 03:55 UTC | 1h 55m |
| 2026-04-20 | OMU | - | Apr 20, 05:00 UTC | Apr 20, 05:30 UTC | 30m |
| 2026-04-20 | OMU | - | Apr 20, 02:50 UTC | Apr 20, 04:00 UTC | 1h 10m |
| 2026-04-18 | OMU | - | Apr 18, 05:35 UTC | Apr 18, 06:10 UTC | 35m |
| 2026-04-18 | OMU | - | Apr 18, 03:25 UTC | Apr 18, 04:20 UTC | 55m |
| 2026-04-18 | OMU | - | Apr 18, 02:45 UTC | Apr 18, 03:20 UTC | 35m |
| 2026-04-18 | OMU | - | Apr 18, 00:50 UTC | Apr 18, 01:20 UTC | 30m |
| 2026-04-17 | OMU | - | Apr 17, 23:30 UTC | Apr 18, 00:00 UTC | 30m |
| 2026-04-17 | OMU | - | Apr 17, 03:20 UTC | Apr 17, 03:45 UTC | 25m |
| 2026-04-17 | OMU | - | Apr 17, 02:50 UTC | Apr 17, 03:15 UTC | 25m |
| 2026-04-16 | OMU | - | Apr 16, 23:20 UTC | Apr 17, 00:00 UTC | 40m |
| 2026-04-16 | OMU | - | Apr 16, 22:45 UTC | Apr 16, 23:10 UTC | 25m |
| 2026-04-16 | OMU | - | Apr 16, 04:24 UTC | Apr 16, 05:05 UTC | 40m |
| 2026-04-16 | OMU | - | Apr 16, 02:45 UTC | Apr 16, 03:04 UTC | 20m |
| 2026-04-15 | OMU | - | Apr 15, 05:25 UTC | Apr 15, 05:50 UTC | 25m |
| 2026-04-15 | OMU | - | Apr 15, 03:45 UTC | Apr 15, 04:10 UTC | 25m |
| 2026-04-14 | OMU | - | Apr 14, 23:10 UTC | Apr 15, 00:40 UTC | 1h 30m |
| 2026-04-14 | OMU | - | Apr 14, 22:00 UTC | Apr 14, 22:45 UTC | 45m |
| 2026-04-13 | OMU | - | Apr 13, 21:30 UTC | Apr 13, 23:40 UTC | 2h 10m |
| 2026-04-13 | OMU | - | Apr 13, 04:50 UTC | Apr 13, 06:10 UTC | 1h 20m |
| 2026-04-13 | OMU | - | Apr 13, 02:35 UTC | Apr 13, 03:50 UTC | 1h 15m |
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-OMU page for operator, model, and routing details .