sensors Mode-S transponder
70C102
ICAO 24-bit transponder address · allocated to Oman
Currently assigned to A4O-MH · BOEING 737 MAX 8
- Hex
- 70C102
- Octal
- 34140402
- Decimal
- 7,389,442
- Country
- OM
- Tail
- A4O-MH
- Type
- B38M
- Flights observed
- 63
- Distinct callsigns
- 20
- Country
- OM
- Last broadcast
- 14h ago
Last known position
Country allocation
The ICAO 24-bit address 70C102 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 | 5 | 2026-05-13 |
| OMA684 | Oman Air | 5 | 2026-05-23 |
| OMA281 | Oman Air | 5 | 2026-05-25 |
| OMA282 | Oman Air | 4 | 2026-05-25 |
| OMA252 | Oman Air | 3 | 2026-05-21 |
| OMA226 | Oman Air | 3 | 2026-05-26 |
| OMA225 | Oman Air | 3 | 2026-05-26 |
| OMA831 | Oman Air | 2 | 2026-05-15 |
| OMA696 | Oman Air | 2 | 2026-05-29 |
| OMA695 | Oman Air | 2 | 2026-05-29 |
| OMA683 | - | 2 | 2026-04-14 |
| OMA681 | Oman Air | 2 | 2026-05-01 |
| OMA253 | Oman Air | 2 | 2026-05-29 |
| OMA251 | Oman Air | 2 | 2026-05-20 |
| OMA148 | Oman Air | 2 | 2026-05-22 |
| OMA123 | Oman Air | 2 | 2026-04-27 |
| OMA832 | Oman Air | 1 | 2026-04-13 |
| OMA694 | Oman Air | 1 | 2026-05-26 |
| OMA693 | Oman Air | 1 | 2026-05-26 |
| OMA686 | Oman Air | 1 | 2026-04-21 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | OMA696 | DMM → MCT | May 29, 18:40 UTC | May 29, 19:20 UTC | 40m |
| 2026-05-29 | OMA695 | MCT → DMM | May 29, 17:05 UTC | May 29, 17:15 UTC | 10m |
| 2026-05-29 | OMA253 | MCT → MAA | May 29, 00:40 UTC | May 29, 11:50 UTC | 11h 10m |
| 2026-05-28 | OMA184 | SVO → MCT | May 28, 20:05 UTC | May 28, 20:25 UTC | 20m |
| 2026-05-27 | OMA154 | ZRH → MCT | May 27, 19:00 UTC | May 28, 01:05 UTC | 6h 5m |
| 2026-05-26 | OMA153 | MCT → ZRH | May 26, 22:59 UTC | May 27, 17:05 UTC | 18h 6m |
| 2026-05-26 | OMA694 | DMM → MCT | May 26, 13:19 UTC | May 26, 21:44 UTC | 8h 25m |
| 2026-05-26 | OMA693 | MCT → DMM | May 26, 11:00 UTC | May 26, 12:00 UTC | 1h 0m |
| 2026-05-26 | OMA226 | COK → MCT | May 26, 02:49 UTC | May 26, 03:15 UTC | 25m |
| 2026-05-26 | OMA225 | MCT → COK | May 26, 01:34 UTC | May 26, 01:44 UTC | 10m |
| 2026-05-25 | OMA282 | BLR → MCT | May 25, 04:15 UTC | May 25, 05:30 UTC | 1h 15m |
| 2026-05-25 | OMA281 | MCT → BLR | May 25, 02:40 UTC | May 25, 03:10 UTC | 30m |
| 2026-05-24 | OMA408 | CAI → MCT | May 24, 02:40 UTC | May 24, 03:10 UTC | 30m |
| 2026-05-23 | OMA684 | RUH → MCT | May 23, 13:55 UTC | May 23, 21:35 UTC | 7h 40m |
| 2026-05-23 | OMA684 | RUH → MCT | May 23, 00:35 UTC | May 23, 21:35 UTC | 21h 0m |
| 2026-05-22 | OMA148 | FCO → MCT | May 22, 20:35 UTC | May 23, 19:05 UTC | 22h 30m |
| 2026-05-22 | OMA148 | FCO → MCT | May 22, 19:40 UTC | May 23, 14:30 UTC | 18h 49m |
| 2026-05-22 | OMA147 | MCT → FCO | May 22, 02:50 UTC | May 22, 17:50 UTC | 15h 0m |
| 2026-05-22 | OMA225 | MCT → COK | May 22, 00:00 UTC | May 22, 01:25 UTC | 1h 25m |
| 2026-05-21 | OMA252 | MAA → MCT | May 21, 02:55 UTC | May 22, 01:25 UTC | 22h 30m |
| 2026-05-20 | OMA251 | MCT → MAA | May 20, 10:30 UTC | May 21, 01:15 UTC | 14h 45m |
| 2026-05-20 | OMA245 | MCT → DEL | May 20, 08:30 UTC | May 20, 09:10 UTC | 40m |
| 2026-05-19 | OMA407 | MCT → CAI | May 19, 19:45 UTC | May 19, 22:20 UTC | 2h 35m |
| 2026-05-18 | OMA282 | BLR → MCT | May 18, 04:40 UTC | May 18, 04:55 UTC | 15m |
| 2026-05-17 | OMA281 | MCT → BLR | May 17, 06:35 UTC | May 18, 03:10 UTC | 20h 35m |
| 2026-05-17 | OMA266 | LKO → MCT | May 17, 04:45 UTC | May 18, 03:10 UTC | 22h 25m |
| 2026-05-17 | OMA265 | MCT → LKO | May 17, 00:20 UTC | May 17, 02:05 UTC | 1h 45m |
| 2026-05-15 | OMA831 | MCT → HKT | May 15, 08:20 UTC | May 15, 18:25 UTC | 10h 4m |
| 2026-05-13 | OMA833 | MCT → HKT | May 13, 22:30 UTC | May 14, 06:15 UTC | 7h 45m |
| 2026-05-13 | OMA833 | MCT → HKT | May 13, 04:35 UTC | May 13, 23:10 UTC | 18h 35m |
| 2026-05-13 | OMA833 | MCT → HKT | May 13, 04:25 UTC | May 13, 23:10 UTC | 18h 45m |
| 2026-05-13 | OMA281 | MCT → BLR | May 13, 02:35 UTC | May 13, 03:10 UTC | 35m |
| 2026-05-09 | OMA684 | RUH → MCT | May 9, 11:10 UTC | May 9, 14:15 UTC | 3h 5m |
| 2026-05-09 | OMA226 | COK → MCT | May 9, 03:00 UTC | May 9, 03:15 UTC | 15m |
| 2026-05-08 | OMA684 | RUH → MCT | May 8, 13:50 UTC | May 9, 01:45 UTC | 11h 55m |
| 2026-05-07 | OMA833 | MCT → HKT | May 7, 21:25 UTC | May 8, 14:10 UTC | 16h 45m |
| 2026-05-07 | OMA833 | MCT → HKT | May 7, 03:40 UTC | May 7, 22:00 UTC | 18h 20m |
| 2026-05-07 | OMA241 | MCT → DEL | May 7, 01:20 UTC | May 7, 02:00 UTC | 40m |
| 2026-05-05 | OMA661 | MCT → DOH | May 5, 00:40 UTC | May 5, 17:45 UTC | 17h 5m |
| 2026-05-04 | OMA282 | BLR → MCT | May 4, 04:39 UTC | May 5, 00:45 UTC | 20h 6m |
| 2026-05-04 | OMA281 | MCT → BLR | May 4, 01:44 UTC | May 4, 03:15 UTC | 1h 30m |
| 2026-05-03 | OMA223 | MCT → COK | May 3, 07:25 UTC | May 3, 07:55 UTC | 30m |
| 2026-05-02 | OMA226 | COK → MCT | May 2, 03:10 UTC | May 2, 03:30 UTC | 20m |
| 2026-05-02 | OMA225 | MCT → COK | May 2, 01:30 UTC | May 2, 01:40 UTC | 10m |
| 2026-05-01 | OMA681 | MCT → RUH | May 1, 07:15 UTC | May 1, 20:30 UTC | 13h 15m |
| 2026-04-29 | OMA696 | DMM → MCT | Apr 29, 18:35 UTC | Apr 29, 19:35 UTC | 1h 0m |
| 2026-04-29 | OMA695 | MCT → DMM | Apr 29, 10:10 UTC | Apr 29, 17:01 UTC | 6h 50m |
| 2026-04-29 | OMA253 | MCT → MAA | Apr 29, 07:10 UTC | Apr 29, 08:34 UTC | 1h 25m |
| 2026-04-27 | OMA124 | MUC → MCT | Apr 27, 21:20 UTC | Apr 28, 03:20 UTC | 6h 0m |
| 2026-04-27 | OMA123 | MCT → MUC | Apr 27, 16:20 UTC | Apr 27, 19:50 UTC | 3h 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-MH page for operator, model, and routing details .