sensors Mode-S transponder
70C0FD
ICAO 24-bit transponder address · allocated to Oman
Currently assigned to A4O-SG · BOEING 787-9 Dreamliner
- Hex
- 70C0FD
- Octal
- 34140375
- Decimal
- 7,389,437
- Country
- OM
- Tail
- A4O-SG
- Type
- B789
- Flights observed
- 133
- Distinct callsigns
- 9
- Country
- OM
- Last broadcast
- 42m ago
Last known position
Country allocation
The ICAO 24-bit address 70C0FD falls within the block assigned to Oman (OM) by ICAO Annex 10, Volume III. Every aircraft registered in Oman 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 9 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | OMA102 | LHR → MCT | May 29, 20:40 UTC | May 30, 00:55 UTC | 4h 15m |
| 2026-05-28 | OMA101 | MCT → LHR | May 28, 23:20 UTC | May 29, 17:40 UTC | 18h 20m |
| 2026-05-28 | OMA101 | MCT → LHR | May 28, 21:20 UTC | May 29, 17:40 UTC | 20h 20m |
| 2026-05-28 | OMA101 | MCT → LHR | May 28, 20:10 UTC | May 29, 17:40 UTC | 21h 30m |
| 2026-05-27 | OMA101 | MCT → LHR | May 27, 23:20 UTC | May 28, 17:40 UTC | 18h 20m |
| 2026-05-27 | OMA101 | MCT → LHR | May 27, 21:20 UTC | May 28, 17:40 UTC | 20h 20m |
| 2026-05-27 | OMA101 | MCT → LHR | May 27, 20:15 UTC | May 28, 17:40 UTC | 21h 25m |
| 2026-05-26 | OMA101 | MCT → LHR | May 26, 23:19 UTC | May 27, 17:35 UTC | 18h 15m |
| 2026-05-26 | OMA101 | MCT → LHR | May 26, 21:20 UTC | May 27, 17:35 UTC | 20h 15m |
| 2026-05-26 | OMA101 | MCT → LHR | May 26, 20:15 UTC | May 27, 17:35 UTC | 21h 20m |
| 2026-05-26 | OMA101 | MCT → LHR | May 26, 01:14 UTC | May 26, 17:39 UTC | 16h 25m |
| 2026-05-25 | OMA101 | MCT → LHR | May 25, 21:19 UTC | May 26, 17:39 UTC | 20h 20m |
| 2026-05-25 | OMA101 | MCT → LHR | May 25, 20:04 UTC | May 26, 17:39 UTC | 21h 35m |
| 2026-05-24 | OMA143 | MCT → MXP | May 24, 23:20 UTC | May 25, 17:35 UTC | 18h 15m |
| 2026-05-24 | OMA143 | MCT → MXP | May 24, 21:20 UTC | May 25, 17:35 UTC | 20h 15m |
| 2026-05-24 | OMA143 | MCT → MXP | May 24, 20:15 UTC | May 25, 17:35 UTC | 21h 20m |
| 2026-05-23 | OMA101 | MCT → LHR | May 23, 23:20 UTC | May 24, 17:50 UTC | 18h 30m |
| 2026-05-23 | OMA101 | MCT → LHR | May 23, 21:20 UTC | May 24, 17:50 UTC | 20h 30m |
| 2026-05-23 | OMA101 | MCT → LHR | May 23, 20:15 UTC | May 24, 17:50 UTC | 21h 35m |
| 2026-05-22 | OMA101 | MCT → LHR | May 22, 23:20 UTC | May 23, 17:30 UTC | 18h 9m |
| 2026-05-22 | OMA101 | MCT → LHR | May 22, 21:20 UTC | May 23, 17:30 UTC | 20h 10m |
| 2026-05-22 | OMA102 | LHR → MCT | May 22, 20:20 UTC | May 23, 17:30 UTC | 21h 9m |
| 2026-05-22 | OMA101 | MCT → LHR | May 22, 00:00 UTC | May 22, 17:55 UTC | 17h 55m |
| 2026-05-21 | OMA843 | MCT → MNL | May 21, 06:35 UTC | May 21, 13:15 UTC | 6h 40m |
| 2026-05-20 | OMA843 | MCT → MNL | May 20, 15:30 UTC | May 21, 13:15 UTC | 21h 45m |
| 2026-05-20 | OMA843 | MCT → MNL | May 20, 12:05 UTC | May 21, 10:15 UTC | 22h 10m |
| 2026-05-19 | OMA102 | LHR → MCT | May 19, 20:05 UTC | May 20, 10:15 UTC | 14h 11m |
| 2026-05-18 | OMA101 | MCT → LHR | May 18, 23:20 UTC | May 19, 17:55 UTC | 18h 35m |
| 2026-05-18 | OMA101 | MCT → LHR | May 18, 21:20 UTC | May 19, 17:55 UTC | 20h 35m |
| 2026-05-18 | OMA101 | MCT → LHR | May 18, 20:15 UTC | May 19, 17:55 UTC | 21h 40m |
| 2026-05-18 | OMA101 | MCT → LHR | May 18, 10:55 UTC | May 18, 18:10 UTC | 7h 15m |
| 2026-05-17 | OMA104 | LHR → LHR | May 17, 11:20 UTC | May 18, 11:00 UTC | 23h 40m |
| 2026-05-17 | OMA104 | LHR → LHR | May 17, 07:50 UTC | May 17, 11:55 UTC | 4h 5m |
| 2026-05-16 | OMA103 | MCT → MCT | May 16, 11:41 UTC | May 17, 05:40 UTC | 18h 0m |
| 2026-05-16 | OMA850 | CGK → MCT | May 16, 07:45 UTC | May 16, 08:01 UTC | 15m |
| 2026-05-15 | OMA104 | LHR → LHR | May 15, 11:10 UTC | May 16, 04:55 UTC | 17h 44m |
| 2026-05-14 | OMA103 | MCT → MCT | May 14, 12:20 UTC | May 15, 05:45 UTC | 17h 25m |
| 2026-05-13 | OMA815 | MCT → BKK | May 13, 15:45 UTC | May 14, 10:10 UTC | 18h 25m |
| 2026-05-13 | OMA815 | MCT → BKK | May 13, 13:50 UTC | May 14, 10:10 UTC | 20h 20m |
| 2026-05-13 | OMA816 | BKK → MCT | May 13, 12:15 UTC | May 14, 10:10 UTC | 21h 55m |
| 2026-05-12 | OMA102 | LHR → MCT | May 12, 20:15 UTC | May 13, 10:30 UTC | 14h 15m |
| 2026-05-12 | OMA101 | MCT → LHR | May 12, 11:05 UTC | May 12, 18:10 UTC | 7h 5m |
| 2026-05-11 | OMA101 | MCT → LHR | May 11, 21:20 UTC | May 12, 18:10 UTC | 20h 50m |
| 2026-05-11 | OMA101 | MCT → LHR | May 11, 20:15 UTC | May 12, 18:10 UTC | 21h 55m |
| 2026-05-10 | OMA101 | MCT → LHR | May 10, 23:35 UTC | May 11, 17:45 UTC | 18h 11m |
| 2026-05-10 | OMA101 | MCT → LHR | May 10, 21:25 UTC | May 11, 17:45 UTC | 20h 21m |
| 2026-05-10 | OMA102 | LHR → MCT | May 10, 20:00 UTC | May 11, 17:45 UTC | 21h 46m |
| 2026-05-10 | OMA101 | MCT → LHR | May 10, 10:45 UTC | May 10, 17:45 UTC | 7h 0m |
| 2026-05-09 | OMA101 | MCT → LHR | May 9, 16:30 UTC | May 10, 15:15 UTC | 22h 45m |
| 2026-05-09 | OMA816 | BKK → MCT | May 9, 13:20 UTC | May 10, 13:14 UTC | 23h 55m |
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 A4O-SG page for operator, model, and routing details .