sensors Mode-S transponder
70C100
ICAO 24-bit transponder address · allocated to Oman
Currently assigned to A4O-MF · BOEING 737 MAX 8
- Hex
- 70C100
- Octal
- 34140400
- Decimal
- 7,389,440
- Country
- OM
- Tail
- A4O-MF
- Type
- B38M
- Flights observed
- 115
- Distinct callsigns
- 20
- Country
- OM
- Last broadcast
- 10h ago
Last known position
Country allocation
The ICAO 24-bit address 70C100 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 |
|---|---|---|---|
| OMA824 | Oman Air | 8 | 2026-05-29 |
| OMA823 | Oman Air | 6 | 2026-05-28 |
| OMA694 | Oman Air | 6 | 2026-05-05 |
| OMA832 | Oman Air | 5 | 2026-05-09 |
| OMA223 | Oman Air | 5 | 2026-05-28 |
| OMA251 | Oman Air | 4 | 2026-05-18 |
| OMA226 | Oman Air | 4 | 2026-05-04 |
| OMA147 | Oman Air | 4 | 2026-04-29 |
| OMA124 | Oman Air | 4 | 2026-04-18 |
| OMA123 | Oman Air | 4 | 2026-04-17 |
| OMA822 | Oman Air | 3 | 2026-05-11 |
| OMA693 | Oman Air | 3 | 2026-04-23 |
| OMA414 | Oman Air | 3 | 2026-05-13 |
| OMA408 | Oman Air | 3 | 2026-05-27 |
| OMA282 | Oman Air | 3 | 2026-05-27 |
| OMA242 | Oman Air | 3 | 2026-05-17 |
| OMA241 | Oman Air | 3 | 2026-05-17 |
| OMA224 | Oman Air | 3 | 2026-05-28 |
| OMA166 | Oman Air | 3 | 2026-05-24 |
| OMA831 | Oman Air | 2 | 2026-05-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | OMA824 | KUL → MCT | May 29, 17:05 UTC | May 29, 18:50 UTC | 1h 45m |
| 2026-05-29 | OMA824 | KUL → MCT | May 29, 13:40 UTC | May 29, 13:55 UTC | 15m |
| 2026-05-28 | OMA823 | MCT → KUL | May 28, 23:15 UTC | May 29, 11:50 UTC | 12h 35m |
| 2026-05-28 | OMA407 | MCT → CAI | May 28, 21:15 UTC | May 28, 21:40 UTC | 25m |
| 2026-05-28 | OMA224 | COK → MCT | May 28, 09:00 UTC | May 28, 09:10 UTC | 10m |
| 2026-05-28 | OMA223 | MCT → COK | May 28, 07:40 UTC | May 28, 07:55 UTC | 15m |
| 2026-05-27 | OMA408 | CAI → MCT | May 27, 23:10 UTC | May 27, 23:25 UTC | 15m |
| 2026-05-27 | OMA282 | BLR → MCT | May 27, 04:30 UTC | May 27, 21:40 UTC | 17h 10m |
| 2026-05-26 | OMA281 | MCT → BLR | May 26, 08:24 UTC | May 27, 03:14 UTC | 18h 50m |
| 2026-05-26 | OMA253 | MCT → MAA | May 26, 05:15 UTC | May 26, 06:44 UTC | 1h 30m |
| 2026-05-25 | OMA253 | MCT → MAA | May 25, 10:50 UTC | May 26, 06:44 UTC | 19h 55m |
| 2026-05-24 | OMA166 | IST → MCT | May 24, 17:45 UTC | May 25, 09:10 UTC | 15h 25m |
| 2026-05-24 | OMA166 | IST → MCT | May 24, 16:45 UTC | May 24, 16:55 UTC | 10m |
| 2026-05-24 | OMA165 | MCT → IST | May 24, 14:25 UTC | May 24, 14:40 UTC | 15m |
| 2026-05-24 | OMA202 | BOM → MCT | May 24, 05:00 UTC | May 24, 05:45 UTC | 45m |
| 2026-05-24 | OMA201 | MCT → BOM | May 24, 02:40 UTC | May 24, 03:30 UTC | 50m |
| 2026-05-23 | OMA201 | MCT → BOM | May 23, 04:05 UTC | May 24, 03:30 UTC | 23h 25m |
| 2026-05-22 | OMA166 | IST → MCT | May 22, 17:40 UTC | May 23, 02:00 UTC | 8h 20m |
| 2026-05-22 | OMA165 | MCT → IST | May 22, 14:40 UTC | May 22, 14:50 UTC | 10m |
| 2026-05-21 | OMA252 | MAA → MCT | May 21, 23:45 UTC | May 22, 04:40 UTC | 4h 55m |
| 2026-05-20 | OMA824 | KUL → MCT | May 20, 14:05 UTC | May 21, 08:05 UTC | 18h 0m |
| 2026-05-20 | OMA824 | KUL → MCT | May 20, 13:50 UTC | May 21, 08:05 UTC | 18h 15m |
| 2026-05-20 | OMA823 | MCT → KUL | May 20, 06:40 UTC | May 20, 12:05 UTC | 5h 25m |
| 2026-05-18 | OMA408 | CAI → MCT | May 18, 23:35 UTC | May 18, 23:45 UTC | 10m |
| 2026-05-18 | OMA407 | MCT → CAI | May 18, 03:15 UTC | May 18, 21:50 UTC | 18h 34m |
| 2026-05-18 | OMA251 | MCT → MAA | May 18, 00:05 UTC | May 18, 21:50 UTC | 21h 44m |
| 2026-05-17 | OMA251 | MCT → MAA | May 17, 23:50 UTC | May 18, 21:50 UTC | 21h 59m |
| 2026-05-17 | OMA242 | DEL → MCT | May 17, 04:50 UTC | May 18, 03:35 UTC | 22h 45m |
| 2026-05-17 | OMA241 | MCT → DEL | May 17, 01:25 UTC | May 17, 02:05 UTC | 40m |
| 2026-05-16 | OMA224 | COK → MCT | May 16, 09:16 UTC | May 16, 09:25 UTC | 10m |
| 2026-05-16 | OMA223 | MCT → COK | May 16, 06:20 UTC | May 16, 07:55 UTC | 1h 35m |
| 2026-05-15 | OMA223 | MCT → COK | May 15, 10:25 UTC | May 16, 07:55 UTC | 21h 30m |
| 2026-05-15 | OMA223 | MCT → COK | May 15, 08:10 UTC | May 16, 07:55 UTC | 23h 45m |
| 2026-05-14 | OMA686 | RUH → MCT | May 14, 18:55 UTC | May 15, 10:35 UTC | 15h 40m |
| 2026-05-14 | OMA686 | RUH → MCT | May 14, 14:40 UTC | May 15, 10:35 UTC | 19h 55m |
| 2026-05-14 | OMA406 | CAI → MCT | May 14, 04:00 UTC | May 15, 02:00 UTC | 22h 0m |
| 2026-05-13 | OMA414 | AMM → MCT | May 13, 16:05 UTC | May 14, 14:50 UTC | 22h 45m |
| 2026-05-13 | OMA414 | AMM → MCT | May 13, 15:45 UTC | May 14, 04:00 UTC | 12h 15m |
| 2026-05-13 | OMA414 | AMM → MCT | May 13, 03:10 UTC | May 13, 16:25 UTC | 13h 15m |
| 2026-05-12 | OMA251 | MCT → MAA | May 12, 06:35 UTC | May 13, 01:20 UTC | 18h 45m |
| 2026-05-11 | OMA834 | HKT → MCT | May 11, 22:30 UTC | May 12, 08:15 UTC | 9h 45m |
| 2026-05-11 | OMA822 | KUL → MCT | May 11, 01:40 UTC | May 11, 22:35 UTC | 20h 55m |
| 2026-05-10 | OMA821 | MCT → KUL | May 10, 13:14 UTC | May 10, 23:44 UTC | 10h 30m |
| 2026-05-10 | OMA282 | BLR → MCT | May 10, 04:34 UTC | May 10, 05:00 UTC | 25m |
| 2026-05-09 | OMA832 | HKT → MCT | May 9, 09:00 UTC | May 10, 03:00 UTC | 18h 0m |
| 2026-05-08 | OMA832 | HKT → MCT | May 8, 18:25 UTC | May 9, 18:00 UTC | 23h 35m |
| 2026-05-08 | OMA832 | HKT → MCT | May 8, 16:35 UTC | May 9, 16:00 UTC | 23h 25m |
| 2026-05-08 | OMA831 | MCT → HKT | May 8, 10:14 UTC | May 9, 09:25 UTC | 23h 10m |
| 2026-05-08 | OMA832 | HKT → MCT | May 8, 02:55 UTC | May 8, 18:30 UTC | 15h 35m |
| 2026-05-08 | OMA251 | MCT → MAA | May 8, 00:49 UTC | May 8, 01:19 UTC | 30m |
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-MF page for operator, model, and routing details .