sensors Mode-S transponder
70C0F9
ICAO 24-bit transponder address · allocated to Oman
Currently assigned to A4O-SF · BOEING 787-9 Dreamliner
- Hex
- 70C0F9
- Octal
- 34140371
- Decimal
- 7,389,433
- Country
- OM
- Tail
- A4O-SF
- Type
- B789
- Flights observed
- 69
- Distinct callsigns
- 10
- Country
- OM
- Last broadcast
- 55m ago
Current position
Country allocation
The ICAO 24-bit address 70C0F9 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 10 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| OMA101 | Oman Air | 17 | 2026-05-20 |
| OMA103 | Oman Air | 15 | 2026-05-30 |
| OMA104 | Oman Air | 12 | 2026-05-25 |
| OMA102 | Oman Air | 12 | 2026-05-21 |
| OMA817 | Oman Air | 3 | 2026-05-18 |
| OMA816 | Oman Air | 3 | 2026-05-06 |
| OMA815 | Oman Air | 3 | 2026-05-06 |
| OMA818 | Oman Air | 2 | 2026-05-19 |
| OMA202 | Oman Air | 1 | 2026-04-24 |
| OMA201 | Oman Air | 1 | 2026-04-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | OMA103 | MCT → MCT | May 30, 00:50 UTC | May 30, 02:15 UTC | 1h 25m |
| 2026-05-25 | OMA104 | LHR → LHR | May 25, 07:50 UTC | May 25, 14:35 UTC | 6h 45m |
| 2026-05-24 | OMA103 | MCT → MCT | May 24, 10:20 UTC | May 25, 05:20 UTC | 19h 0m |
| 2026-05-24 | OMA104 | LHR → LHR | May 24, 08:20 UTC | May 25, 05:20 UTC | 21h 0m |
| 2026-05-24 | OMA104 | LHR → LHR | May 24, 07:45 UTC | May 25, 05:20 UTC | 21h 35m |
| 2026-05-23 | OMA103 | MCT → MCT | May 23, 10:20 UTC | May 24, 05:25 UTC | 19h 5m |
| 2026-05-23 | OMA103 | MCT → MCT | May 23, 08:20 UTC | May 24, 05:25 UTC | 21h 5m |
| 2026-05-23 | OMA103 | MCT → MCT | May 23, 08:05 UTC | May 24, 05:25 UTC | 21h 20m |
| 2026-05-22 | OMA103 | MCT → MCT | May 22, 12:30 UTC | May 23, 05:30 UTC | 17h 0m |
| 2026-05-21 | OMA102 | LHR → MCT | May 21, 20:10 UTC | May 22, 10:25 UTC | 14h 15m |
| 2026-05-20 | OMA101 | MCT → LHR | May 20, 22:20 UTC | May 21, 17:35 UTC | 19h 15m |
| 2026-05-20 | OMA102 | LHR → MCT | May 20, 20:20 UTC | May 21, 17:35 UTC | 21h 15m |
| 2026-05-20 | OMA102 | LHR → MCT | May 20, 20:05 UTC | May 21, 17:35 UTC | 21h 30m |
| 2026-05-20 | OMA101 | MCT → LHR | May 20, 13:00 UTC | May 20, 17:55 UTC | 4h 55m |
| 2026-05-19 | OMA818 | BKK → MCT | May 19, 02:05 UTC | May 19, 06:30 UTC | 4h 25m |
| 2026-05-18 | OMA817 | MCT → BKK | May 18, 19:05 UTC | May 18, 23:25 UTC | 4h 20m |
| 2026-05-18 | OMA817 | MCT → BKK | May 18, 02:20 UTC | May 18, 23:25 UTC | 21h 4m |
| 2026-05-17 | OMA102 | LHR → MCT | May 17, 22:20 UTC | May 18, 19:55 UTC | 21h 34m |
| 2026-05-17 | OMA102 | LHR → MCT | May 17, 20:20 UTC | May 18, 19:55 UTC | 23h 34m |
| 2026-05-16 | OMA101 | MCT → LHR | May 16, 22:20 UTC | May 17, 18:01 UTC | 19h 41m |
| 2026-05-16 | OMA101 | MCT → LHR | May 16, 20:25 UTC | May 17, 18:01 UTC | 21h 35m |
| 2026-05-16 | OMA101 | MCT → LHR | May 16, 00:20 UTC | May 16, 18:25 UTC | 18h 6m |
| 2026-05-15 | OMA101 | MCT → LHR | May 15, 22:20 UTC | May 16, 18:25 UTC | 20h 6m |
| 2026-05-15 | OMA101 | MCT → LHR | May 15, 21:05 UTC | May 16, 18:25 UTC | 21h 21m |
| 2026-05-15 | OMA101 | MCT → LHR | May 15, 00:20 UTC | May 15, 19:15 UTC | 18h 54m |
| 2026-05-14 | OMA102 | LHR → MCT | May 14, 22:30 UTC | May 15, 19:15 UTC | 20h 44m |
| 2026-05-13 | OMA101 | MCT → LHR | May 13, 22:20 UTC | May 14, 18:10 UTC | 19h 50m |
| 2026-05-13 | OMA102 | LHR → MCT | May 13, 21:05 UTC | May 14, 18:10 UTC | 21h 5m |
| 2026-05-13 | OMA101 | MCT → LHR | May 13, 12:50 UTC | May 13, 18:00 UTC | 5h 10m |
| 2026-05-11 | OMA104 | LHR → LHR | May 11, 07:35 UTC | May 11, 13:45 UTC | 6h 10m |
| 2026-05-10 | OMA103 | MCT → MCT | May 10, 22:05 UTC | May 11, 05:30 UTC | 7h 25m |
| 2026-05-10 | OMA103 | MCT → MCT | May 10, 01:39 UTC | May 10, 22:30 UTC | 20h 50m |
| 2026-05-09 | OMA102 | LHR → MCT | May 9, 22:20 UTC | May 10, 22:15 UTC | 23h 55m |
| 2026-05-09 | OMA102 | LHR → MCT | May 9, 20:00 UTC | May 10, 01:55 UTC | 5h 55m |
| 2026-05-09 | OMA101 | MCT → LHR | May 9, 14:15 UTC | May 9, 17:40 UTC | 3h 25m |
| 2026-05-08 | OMA104 | LHR → LHR | May 8, 07:44 UTC | May 8, 14:00 UTC | 6h 15m |
| 2026-05-08 | OMA103 | MCT → MCT | May 8, 02:19 UTC | May 8, 05:20 UTC | 3h 0m |
| 2026-05-06 | OMA816 | BKK → MCT | May 6, 12:35 UTC | May 6, 15:10 UTC | 2h 35m |
| 2026-05-06 | OMA815 | MCT → BKK | May 6, 08:01 UTC | May 6, 10:40 UTC | 2h 40m |
| 2026-05-05 | OMA818 | BKK → MCT | May 5, 02:01 UTC | May 5, 04:00 UTC | 2h 0m |
| 2026-05-04 | OMA817 | MCT → BKK | May 4, 21:05 UTC | May 4, 23:10 UTC | 2h 5m |
| 2026-05-04 | OMA104 | LHR → LHR | May 4, 07:40 UTC | May 4, 14:25 UTC | 6h 45m |
| 2026-05-03 | OMA103 | MCT → MCT | May 3, 22:45 UTC | May 4, 05:35 UTC | 6h 50m |
| 2026-05-03 | OMA104 | LHR → LHR | May 3, 08:05 UTC | May 3, 15:00 UTC | 6h 55m |
| 2026-05-02 | OMA103 | MCT → MCT | May 2, 22:15 UTC | May 3, 05:35 UTC | 7h 19m |
| 2026-05-02 | OMA104 | LHR → LHR | May 2, 08:00 UTC | May 2, 14:50 UTC | 6h 50m |
| 2026-05-01 | OMA103 | MCT → MCT | May 1, 22:35 UTC | May 2, 05:30 UTC | 6h 55m |
| 2026-04-30 | OMA816 | BKK → MCT | Apr 30, 12:30 UTC | Apr 30, 14:40 UTC | 2h 10m |
| 2026-04-29 | OMA815 | MCT → BKK | Apr 29, 14:20 UTC | Apr 30, 10:05 UTC | 19h 44m |
| 2026-04-29 | OMA816 | BKK → MCT | Apr 29, 12:30 UTC | Apr 30, 10:05 UTC | 21h 34m |
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-SF page for operator, model, and routing details .