sensors Mode-S transponder
70C0F8
ICAO 24-bit transponder address · allocated to Oman
Currently assigned to A4O-MB · BOEING 737 MAX 8
- Hex
- 70C0F8
- Octal
- 34140370
- Decimal
- 7,389,432
- Country
- OM
- Tail
- A4O-MB
- Type
- B38M
- Flights observed
- 84
- Distinct callsigns
- 20
- Country
- OM
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 70C0F8 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 |
|---|---|---|---|
| OMA833 | Oman Air | 6 | 2026-05-28 |
| OMA251 | Oman Air | 6 | 2026-05-27 |
| OMA407 | Oman Air | 5 | 2026-05-11 |
| OMA283 | Oman Air | 5 | 2026-05-15 |
| OMA686 | Oman Air | 4 | 2026-05-11 |
| OMA241 | Oman Air | 4 | 2026-05-13 |
| OMA223 | Oman Air | 4 | 2026-05-26 |
| OMA685 | Oman Air | 3 | 2026-05-10 |
| OMA681 | - | 3 | 2026-04-19 |
| OMA408 | Oman Air | 3 | 2026-04-27 |
| OMA282 | Oman Air | 3 | 2026-06-01 |
| OMA166 | Oman Air | 3 | 2026-05-31 |
| OMA823 | Oman Air | 2 | 2026-04-21 |
| OMA694 | Oman Air | 2 | 2026-05-23 |
| OMA654 | Oman Air | 2 | 2026-05-05 |
| OMA653 | Oman Air | 2 | 2026-05-05 |
| OMA284 | Oman Air | 2 | 2026-05-09 |
| OMA281 | Oman Air | 2 | 2026-05-15 |
| OMA252 | Oman Air | 2 | 2026-05-04 |
| OMA242 | Oman Air | 2 | 2026-05-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | OMA406 | CAI → MCT | Jun 2, 16:45 UTC | Jun 2, 19:25 UTC | 2h 40m |
| 2026-06-02 | OMA822 | KUL → MCT | Jun 2, 02:20 UTC | Jun 2, 07:10 UTC | 4h 50m |
| 2026-06-01 | OMA821 | MCT → KUL | Jun 1, 23:25 UTC | Jun 1, 23:50 UTC | 25m |
| 2026-06-01 | OMA282 | BLR → MCT | Jun 1, 05:45 UTC | Jun 1, 19:05 UTC | 13h 20m |
| 2026-06-01 | OMA282 | BLR → MCT | Jun 1, 04:40 UTC | Jun 1, 04:50 UTC | 10m |
| 2026-05-31 | OMA166 | IST → MCT | May 31, 17:20 UTC | Jun 1, 03:25 UTC | 10h 5m |
| 2026-05-30 | OMA165 | MCT → IST | May 30, 20:45 UTC | May 31, 15:40 UTC | 18h 55m |
| 2026-05-30 | OMA166 | IST → MCT | May 30, 18:05 UTC | May 31, 15:40 UTC | 21h 35m |
| 2026-05-30 | OMA166 | IST → MCT | May 30, 16:50 UTC | May 31, 15:40 UTC | 22h 50m |
| 2026-05-30 | OMA818 | BKK → MCT | May 30, 02:15 UTC | May 30, 14:40 UTC | 12h 25m |
| 2026-05-29 | OMA817 | MCT → BKK | May 29, 13:15 UTC | May 29, 23:10 UTC | 9h 55m |
| 2026-05-28 | OMA833 | MCT → HKT | May 28, 20:35 UTC | May 29, 06:40 UTC | 10h 5m |
| 2026-05-28 | OMA833 | MCT → HKT | May 28, 04:15 UTC | May 28, 22:10 UTC | 17h 55m |
| 2026-05-28 | OMA833 | MCT → HKT | May 28, 03:05 UTC | May 28, 22:10 UTC | 19h 5m |
| 2026-05-27 | OMA251 | MCT → MAA | May 27, 23:40 UTC | May 28, 01:05 UTC | 1h 25m |
| 2026-05-27 | OMA251 | MCT → MAA | May 27, 03:04 UTC | May 28, 01:05 UTC | 22h 1m |
| 2026-05-26 | OMA225 | MCT → COK | May 26, 08:19 UTC | May 27, 01:49 UTC | 17h 30m |
| 2026-05-26 | OMA223 | MCT → COK | May 26, 06:39 UTC | May 26, 06:59 UTC | 20m |
| 2026-05-24 | OMA833 | MCT → HKT | May 24, 14:40 UTC | May 25, 06:20 UTC | 15h 40m |
| 2026-05-24 | OMA833 | MCT → HKT | May 24, 11:30 UTC | May 25, 06:20 UTC | 18h 50m |
| 2026-05-23 | OMA694 | DMM → MCT | May 23, 14:05 UTC | May 24, 11:35 UTC | 21h 30m |
| 2026-05-23 | OMA694 | DMM → MCT | May 23, 13:55 UTC | May 24, 11:35 UTC | 21h 40m |
| 2026-05-22 | OMA833 | MCT → HKT | May 22, 21:40 UTC | May 23, 07:45 UTC | 10h 4m |
| 2026-05-19 | OMA254 | MAA → MCT | May 19, 08:35 UTC | May 19, 10:10 UTC | 1h 35m |
| 2026-05-19 | OMA253 | MCT → MAA | May 19, 05:20 UTC | May 19, 06:45 UTC | 1h 25m |
| 2026-05-17 | OMA224 | COK → MCT | May 17, 09:05 UTC | May 17, 10:40 UTC | 1h 35m |
| 2026-05-17 | OMA223 | MCT → COK | May 17, 06:05 UTC | May 17, 07:55 UTC | 1h 50m |
| 2026-05-16 | OMA223 | MCT → COK | May 16, 10:31 UTC | May 17, 07:55 UTC | 21h 24m |
| 2026-05-15 | OMA283 | MCT → BLR | May 15, 16:25 UTC | May 16, 08:41 UTC | 16h 16m |
| 2026-05-15 | OMA282 | BLR → MCT | May 15, 04:40 UTC | May 16, 02:15 UTC | 21h 34m |
| 2026-05-15 | OMA281 | MCT → BLR | May 15, 02:35 UTC | May 15, 03:10 UTC | 35m |
| 2026-05-14 | OMA281 | MCT → BLR | May 14, 04:05 UTC | May 15, 03:10 UTC | 23h 5m |
| 2026-05-14 | OMA242 | DEL → MCT | May 14, 03:45 UTC | May 14, 04:20 UTC | 35m |
| 2026-05-13 | OMA241 | MCT → DEL | May 13, 16:00 UTC | May 14, 01:55 UTC | 9h 55m |
| 2026-05-13 | OMA241 | MCT → DEL | May 13, 04:30 UTC | May 14, 01:55 UTC | 21h 25m |
| 2026-05-13 | OMA235 | MCT → HYD | May 13, 00:05 UTC | May 13, 19:35 UTC | 19h 30m |
| 2026-05-11 | OMA407 | MCT → CAI | May 11, 22:05 UTC | May 11, 22:15 UTC | 10m |
| 2026-05-11 | OMA686 | RUH → MCT | May 11, 02:05 UTC | May 11, 22:15 UTC | 20h 11m |
| 2026-05-11 | OMA686 | RUH → MCT | May 11, 01:55 UTC | May 11, 22:15 UTC | 20h 21m |
| 2026-05-10 | OMA685 | MCT → RUH | May 10, 22:45 UTC | May 11, 02:15 UTC | 3h 30m |
| 2026-05-10 | OMA685 | MCT → RUH | May 10, 04:04 UTC | May 11, 02:15 UTC | 22h 10m |
| 2026-05-10 | OMA242 | DEL → MCT | May 10, 03:45 UTC | May 11, 02:00 UTC | 22h 15m |
| 2026-05-09 | OMA241 | MCT → DEL | May 9, 18:10 UTC | May 10, 02:14 UTC | 8h 5m |
| 2026-05-09 | OMA284 | BLR → MCT | May 9, 09:45 UTC | May 9, 10:15 UTC | 30m |
| 2026-05-09 | OMA283 | MCT → BLR | May 9, 08:00 UTC | May 9, 08:20 UTC | 20m |
| 2026-05-08 | OMA661 | MCT → DOH | May 8, 08:09 UTC | May 8, 17:55 UTC | 9h 45m |
| 2026-05-06 | OMA246 | DEL → MCT | May 6, 10:40 UTC | May 6, 11:15 UTC | 35m |
| 2026-05-05 | OMA654 | BAH → MCT | May 5, 19:10 UTC | May 6, 09:15 UTC | 14h 5m |
| 2026-05-05 | OMA653 | MCT → BAH | May 5, 17:25 UTC | May 5, 18:00 UTC | 35m |
| 2026-05-05 | OMA284 | BLR → MCT | May 5, 09:50 UTC | May 5, 16:35 UTC | 6h 45m |
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-MB page for operator, model, and routing details .