sensors Mode-S transponder
70C0FC
ICAO 24-bit transponder address · allocated to Oman
Currently assigned to A4O-ME · BOEING 737 MAX 8
- Hex
- 70C0FC
- Octal
- 34140374
- Decimal
- 7,389,436
- Country
- OM
- Tail
- A4O-ME
- Type
- B38M
- Flights observed
- 70
- Distinct callsigns
- 20
- Country
- OM
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 70C0FC 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 |
|---|---|---|---|
| OMA823 | Oman Air | 6 | 2026-05-22 |
| OMA824 | Oman Air | 5 | 2026-05-22 |
| OMA831 | Oman Air | 4 | 2026-05-06 |
| OMA833 | Oman Air | 3 | 2026-05-29 |
| OMA685 | Oman Air | 3 | 2026-05-16 |
| OMA408 | Oman Air | 3 | 2026-05-03 |
| OMA407 | Oman Air | 3 | 2026-05-02 |
| OMA252 | Oman Air | 3 | 2026-05-07 |
| OMA242 | Oman Air | 3 | 2026-05-28 |
| OMA822 | Oman Air | 2 | 2026-04-27 |
| OMA816 | Oman Air | 2 | 2026-05-31 |
| OMA676 | Oman Air | 2 | 2026-05-26 |
| OMA254 | Oman Air | 2 | 2026-05-24 |
| OMA251 | Oman Air | 2 | 2026-05-06 |
| OMA241 | Oman Air | 2 | 2026-05-28 |
| OMA235 | Oman Air | 2 | 2026-05-19 |
| OMA231 | Oman Air | 2 | 2026-05-16 |
| OMA226 | Oman Air | 2 | 2026-05-23 |
| OMA223 | Oman Air | 2 | 2026-05-29 |
| OMA832 | Oman Air | 1 | 2026-04-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-31 | OMA816 | BKK → MCT | May 31, 13:05 UTC | Jun 1, 07:50 UTC | 18h 45m |
| 2026-05-31 | OMA816 | BKK → MCT | May 31, 12:20 UTC | Jun 1, 07:50 UTC | 19h 30m |
| 2026-05-31 | OMA815 | MCT → BKK | May 31, 09:05 UTC | May 31, 10:20 UTC | 1h 15m |
| 2026-05-30 | OMA184 | SVO → MCT | May 30, 20:00 UTC | May 30, 20:25 UTC | 25m |
| 2026-05-29 | OMA833 | MCT → HKT | May 29, 21:35 UTC | May 30, 13:20 UTC | 15h 45m |
| 2026-05-29 | OMA833 | MCT → HKT | May 29, 17:05 UTC | May 30, 13:20 UTC | 20h 15m |
| 2026-05-29 | OMA833 | MCT → HKT | May 29, 16:25 UTC | May 30, 13:20 UTC | 20h 55m |
| 2026-05-29 | OMA669 | - | May 29, 15:10 UTC | May 29, 15:20 UTC | 10m |
| 2026-05-29 | OMA223 | MCT → COK | May 29, 06:05 UTC | May 29, 07:45 UTC | 1h 40m |
| 2026-05-28 | OMA242 | DEL → MCT | May 28, 03:30 UTC | May 28, 05:20 UTC | 1h 50m |
| 2026-05-28 | OMA241 | MCT → DEL | May 28, 01:15 UTC | May 28, 01:50 UTC | 35m |
| 2026-05-27 | OMA223 | MCT → COK | May 27, 07:35 UTC | May 27, 07:50 UTC | 15m |
| 2026-05-26 | OMA676 | JED → MCT | May 26, 16:30 UTC | May 27, 01:19 UTC | 8h 50m |
| 2026-05-26 | OMA676 | JED → MCT | May 26, 00:39 UTC | May 26, 22:59 UTC | 22h 20m |
| 2026-05-24 | OMA696 | DMM → MCT | May 24, 19:05 UTC | May 24, 20:00 UTC | 55m |
| 2026-05-24 | OMA254 | MAA → MCT | May 24, 10:05 UTC | May 24, 11:45 UTC | 1h 40m |
| 2026-05-24 | OMA253 | MCT → MAA | May 24, 07:00 UTC | May 24, 08:30 UTC | 1h 30m |
| 2026-05-23 | OMA226 | COK → MCT | May 23, 02:55 UTC | May 23, 03:20 UTC | 25m |
| 2026-05-22 | OMA824 | KUL → MCT | May 22, 13:55 UTC | May 23, 01:40 UTC | 11h 45m |
| 2026-05-22 | OMA823 | MCT → KUL | May 22, 11:15 UTC | May 22, 11:40 UTC | 25m |
| 2026-05-22 | OMA823 | MCT → KUL | May 22, 06:40 UTC | May 22, 08:05 UTC | 1h 25m |
| 2026-05-21 | OMA242 | DEL → MCT | May 21, 03:35 UTC | May 21, 03:55 UTC | 20m |
| 2026-05-20 | OMA241 | MCT → DEL | May 20, 17:25 UTC | May 21, 01:40 UTC | 8h 15m |
| 2026-05-20 | OMA165 | MCT → IST | May 20, 14:25 UTC | May 20, 14:35 UTC | 10m |
| 2026-05-19 | OMA235 | MCT → HYD | May 19, 11:15 UTC | May 20, 04:45 UTC | 17h 31m |
| 2026-05-19 | OMA235 | MCT → HYD | May 19, 07:30 UTC | May 20, 04:45 UTC | 21h 16m |
| 2026-05-17 | OMA254 | MAA → MCT | May 17, 10:25 UTC | May 17, 19:25 UTC | 9h 0m |
| 2026-05-16 | OMA685 | MCT → RUH | May 16, 22:15 UTC | May 17, 08:30 UTC | 10h 15m |
| 2026-05-16 | OMA685 | MCT → RUH | May 16, 12:05 UTC | May 17, 08:30 UTC | 20h 25m |
| 2026-05-16 | OMA231 | MCT → HYD | May 16, 07:25 UTC | May 17, 02:25 UTC | 19h 0m |
| 2026-05-15 | OMA231 | MCT → HYD | May 15, 16:35 UTC | May 16, 12:40 UTC | 20h 6m |
| 2026-05-15 | OMA824 | KUL → MCT | May 15, 13:35 UTC | May 16, 12:40 UTC | 23h 5m |
| 2026-05-14 | OMA823 | MCT → KUL | May 14, 23:00 UTC | May 15, 11:45 UTC | 12h 45m |
| 2026-05-14 | OMA694 | DMM → MCT | May 14, 13:35 UTC | May 15, 11:45 UTC | 22h 10m |
| 2026-05-13 | OMA406 | CAI → MCT | May 13, 16:45 UTC | May 13, 19:30 UTC | 2h 45m |
| 2026-05-13 | OMA405 | MCT → CAI | May 13, 12:15 UTC | May 13, 15:10 UTC | 2h 55m |
| 2026-05-07 | OMA252 | MAA → MCT | May 7, 03:15 UTC | May 7, 03:35 UTC | 20m |
| 2026-05-06 | OMA251 | MCT → MAA | May 6, 09:45 UTC | May 7, 01:20 UTC | 15h 34m |
| 2026-05-06 | OMA831 | MCT → HKT | May 6, 01:05 UTC | May 7, 01:00 UTC | 23h 54m |
| 2026-05-03 | OMA686 | RUH → MCT | May 3, 09:35 UTC | May 4, 03:30 UTC | 17h 55m |
| 2026-05-03 | OMA831 | MCT → HKT | May 3, 08:15 UTC | May 4, 03:30 UTC | 19h 15m |
| 2026-05-03 | OMA408 | CAI → MCT | May 3, 01:55 UTC | May 3, 02:50 UTC | 55m |
| 2026-05-02 | OMA408 | CAI → MCT | May 2, 23:35 UTC | May 2, 23:45 UTC | 10m |
| 2026-05-02 | OMA407 | MCT → CAI | May 2, 18:45 UTC | May 2, 21:35 UTC | 2h 50m |
| 2026-05-01 | OMA685 | MCT → RUH | May 1, 22:10 UTC | May 2, 02:45 UTC | 4h 35m |
| 2026-04-30 | OMA242 | DEL → MCT | Apr 30, 03:35 UTC | Apr 30, 04:10 UTC | 35m |
| 2026-04-29 | OMA832 | HKT → MCT | Apr 29, 08:25 UTC | Apr 30, 02:15 UTC | 17h 50m |
| 2026-04-28 | OMA612 | DXB → MCT | Apr 28, 18:35 UTC | Apr 28, 18:55 UTC | 20m |
| 2026-04-28 | OMA611 | MCT → DXB | Apr 28, 16:35 UTC | Apr 28, 17:00 UTC | 25m |
| 2026-04-27 | OMA822 | KUL → MCT | Apr 27, 04:50 UTC | Apr 27, 06:25 UTC | 1h 35m |
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-ME page for operator, model, and routing details .