sensors Mode-S transponder
70C0F6
ICAO 24-bit transponder address · allocated to Oman
Currently assigned to A4O-SE · BOEING 787-9 Dreamliner
- Hex
- 70C0F6
- Octal
- 34140366
- Decimal
- 7,389,430
- Country
- OM
- Tail
- A4O-SE
- Type
- B789
- Flights observed
- 65
- Distinct callsigns
- 20
- Country
- OM
- Last broadcast
- 15d ago
Last known position
Country allocation
The ICAO 24-bit address 70C0F6 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| OMA843 | Oman Air | 7 | 2026-04-24 |
| OMA844 | Oman Air | 5 | 2026-04-25 |
| OMA817 | Oman Air | 5 | 2026-05-08 |
| OMA849 | Oman Air | 4 | 2026-05-08 |
| OMA821 | Oman Air | 4 | 2026-05-09 |
| OMA172 | Oman Air | 4 | 2026-05-12 |
| OMA153 | Oman Air | 4 | 2026-04-17 |
| OMA850 | Oman Air | 3 | 2026-05-08 |
| OMA816 | Oman Air | 3 | 2026-05-02 |
| OMA815 | Oman Air | 3 | 2026-05-02 |
| OMA171 | Oman Air | 3 | 2026-05-11 |
| OMA154 | Oman Air | 3 | 2026-04-18 |
| OMA132 | Oman Air | 3 | 2026-05-10 |
| OMA131 | Oman Air | 3 | 2026-05-10 |
| OMA822 | Oman Air | 2 | 2026-04-17 |
| OMA818 | Oman Air | 2 | 2026-05-09 |
| OMA317 | Oman Air | 2 | 2026-05-04 |
| OMA7014 | - | 1 | 2026-05-14 |
| OMA318 | Oman Air | 1 | 2026-05-04 |
| OMA143 | Oman Air | 1 | 2026-05-11 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-14 | OMA7014 | - | May 14, 12:05 UTC | May 14, 15:25 UTC | 3h 20m |
| 2026-05-12 | OMA172 | AMS → MCT | May 12, 18:50 UTC | May 12, 22:31 UTC | 3h 40m |
| 2026-05-11 | OMA171 | MCT → CMN | May 11, 21:45 UTC | May 12, 17:10 UTC | 19h 25m |
| 2026-05-11 | OMA143 | MCT → MXP | May 11, 16:05 UTC | May 11, 20:05 UTC | 4h 0m |
| 2026-05-10 | OMA132 | CDG → MCT | May 10, 21:54 UTC | May 11, 04:20 UTC | 6h 25m |
| 2026-05-10 | OMA131 | MCT → CDG | May 10, 01:55 UTC | May 10, 17:30 UTC | 15h 35m |
| 2026-05-09 | OMA821 | MCT → KUL | May 9, 20:25 UTC | May 10, 00:00 UTC | 3h 35m |
| 2026-05-09 | OMA821 | MCT → KUL | May 9, 03:55 UTC | May 10, 00:00 UTC | 20h 5m |
| 2026-05-09 | OMA818 | BKK → MCT | May 9, 02:15 UTC | May 10, 00:00 UTC | 21h 45m |
| 2026-05-08 | OMA817 | MCT → BKK | May 8, 22:05 UTC | May 8, 23:15 UTC | 1h 10m |
| 2026-05-08 | OMA817 | MCT → BKK | May 8, 11:34 UTC | May 8, 21:35 UTC | 10h 0m |
| 2026-05-08 | OMA850 | CGK → MCT | May 8, 07:29 UTC | May 8, 07:44 UTC | 15m |
| 2026-05-08 | OMA849 | MCT → CGK | May 8, 05:05 UTC | May 8, 05:14 UTC | 10m |
| 2026-05-07 | OMA849 | MCT → CGK | May 7, 12:30 UTC | May 8, 04:34 UTC | 16h 4m |
| 2026-05-06 | OMA118 | FRA → MCT | May 6, 18:30 UTC | May 7, 10:45 UTC | 16h 15m |
| 2026-05-06 | OMA117 | MCT → FRA | May 6, 01:45 UTC | May 6, 16:45 UTC | 15h 0m |
| 2026-05-05 | OMA821 | MCT → KUL | May 5, 20:20 UTC | May 5, 23:55 UTC | 3h 35m |
| 2026-05-04 | OMA318 | DAC → MCT | May 4, 10:40 UTC | May 4, 11:50 UTC | 1h 10m |
| 2026-05-04 | OMA317 | MCT → DAC | May 4, 07:45 UTC | May 4, 08:55 UTC | 1h 10m |
| 2026-05-02 | OMA816 | BKK → MCT | May 2, 12:20 UTC | May 2, 14:50 UTC | 2h 30m |
| 2026-05-02 | OMA815 | MCT → BKK | May 2, 08:00 UTC | May 2, 10:20 UTC | 2h 20m |
| 2026-05-01 | OMA132 | CDG → MCT | May 1, 20:00 UTC | May 2, 02:10 UTC | 6h 10m |
| 2026-05-01 | OMA131 | MCT → CDG | May 1, 02:20 UTC | May 1, 17:30 UTC | 15h 10m |
| 2026-04-30 | OMA817 | MCT → BKK | Apr 30, 10:30 UTC | Apr 30, 23:20 UTC | 12h 50m |
| 2026-04-30 | OMA317 | MCT → DAC | Apr 30, 07:40 UTC | Apr 30, 08:35 UTC | 55m |
| 2026-04-27 | OMA816 | BKK → MCT | Apr 27, 12:30 UTC | Apr 27, 14:45 UTC | 2h 15m |
| 2026-04-27 | OMA815 | MCT → BKK | Apr 27, 08:25 UTC | Apr 27, 10:25 UTC | 2h 0m |
| 2026-04-26 | OMA818 | BKK → MCT | Apr 26, 02:15 UTC | Apr 26, 04:40 UTC | 2h 25m |
| 2026-04-25 | OMA817 | MCT → BKK | Apr 25, 04:40 UTC | Apr 25, 23:20 UTC | 18h 40m |
| 2026-04-25 | OMA844 | MNL → MCT | Apr 25, 02:15 UTC | Apr 25, 23:20 UTC | 21h 5m |
| 2026-04-25 | OMA844 | MNL → MCT | Apr 25, 00:05 UTC | Apr 25, 23:20 UTC | 23h 15m |
| 2026-04-24 | OMA843 | MCT → MNL | Apr 24, 07:05 UTC | Apr 24, 13:15 UTC | 6h 10m |
| 2026-04-23 | OMA172 | AMS → MCT | Apr 23, 19:20 UTC | Apr 24, 02:05 UTC | 6h 45m |
| 2026-04-23 | OMA171 | MCT → CMN | Apr 23, 02:05 UTC | Apr 23, 17:30 UTC | 15h 25m |
| 2026-04-22 | OMA817 | MCT → BKK | Apr 22, 23:10 UTC | Apr 22, 23:30 UTC | 20m |
| 2026-04-22 | OMA844 | MNL → MCT | Apr 22, 04:00 UTC | Apr 22, 22:05 UTC | 18h 5m |
| 2026-04-22 | OMA844 | MNL → MCT | Apr 22, 02:10 UTC | Apr 22, 22:05 UTC | 19h 55m |
| 2026-04-22 | OMA844 | MNL → MCT | Apr 22, 00:05 UTC | Apr 22, 22:05 UTC | 22h 0m |
| 2026-04-21 | OMA843 | MCT → MNL | Apr 21, 08:15 UTC | Apr 21, 12:55 UTC | 4h 40m |
| 2026-04-20 | OMA132 | CDG → MCT | Apr 20, 20:10 UTC | Apr 21, 02:15 UTC | 6h 5m |
| 2026-04-20 | OMA131 | MCT → CDG | Apr 20, 00:25 UTC | Apr 20, 18:30 UTC | 18h 6m |
| 2026-04-19 | OMA843 | MCT → MNL | Apr 19, 08:50 UTC | Apr 19, 13:45 UTC | 4h 55m |
| 2026-04-18 | OMA843 | MCT → MNL | Apr 18, 15:35 UTC | Apr 19, 13:45 UTC | 22h 10m |
| 2026-04-18 | OMA843 | MCT → MNL | Apr 18, 14:05 UTC | Apr 19, 13:30 UTC | 23h 25m |
| 2026-04-18 | OMA816 | - | Apr 18, 13:15 UTC | Apr 18, 13:30 UTC | 15m |
| 2026-04-18 | OMA815 | MCT → BKK | Apr 18, 09:05 UTC | Apr 18, 11:40 UTC | 2h 35m |
| 2026-04-18 | OMA154 | ZRH → MCT | Apr 18, 00:40 UTC | Apr 18, 01:20 UTC | 40m |
| 2026-04-17 | OMA154 | ZRH → MCT | Apr 17, 21:25 UTC | Apr 17, 21:55 UTC | 30m |
| 2026-04-17 | OMA154 | ZRH → MCT | Apr 17, 19:35 UTC | Apr 17, 21:20 UTC | 1h 45m |
| 2026-04-17 | OMA153 | MCT → ZRH | Apr 17, 17:25 UTC | Apr 17, 17:50 UTC | 25m |
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-SE page for operator, model, and routing details .