sensors Mode-S transponder
70C106
ICAO 24-bit transponder address · allocated to Oman
Currently assigned to A4O-MK · BOEING 737 MAX 8
- Hex
- 70C106
- Octal
- 34140406
- Decimal
- 7,389,446
- Country
- OM
- Tail
- A4O-MK
- Type
- B38M
- Flights observed
- 93
- Distinct callsigns
- 20
- Country
- OM
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 70C106 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 |
|---|---|---|---|
| OMA223 | Oman Air | 9 | 2026-05-23 |
| OMA251 | Oman Air | 5 | 2026-05-15 |
| OMA226 | Oman Air | 5 | 2026-05-15 |
| OMA824 | Oman Air | 4 | 2026-05-24 |
| OMA408 | Oman Air | 4 | 2026-05-29 |
| OMA252 | Oman Air | 4 | 2026-05-16 |
| OMA225 | Oman Air | 4 | 2026-05-15 |
| OMA696 | Oman Air | 3 | 2026-05-22 |
| OMA682 | Oman Air | 3 | 2026-05-07 |
| OMA414 | Oman Air | 3 | 2026-05-10 |
| OMA153 | Oman Air | 3 | 2026-04-22 |
| OMA833 | Oman Air | 2 | 2026-05-17 |
| OMA822 | Oman Air | 2 | 2026-05-22 |
| OMA695 | - | 2 | 2026-04-13 |
| OMA686 | Oman Air | 2 | 2026-04-13 |
| OMA653 | Oman Air | 2 | 2026-04-28 |
| OMA611 | Oman Air | 2 | 2026-05-02 |
| OMA407 | Oman Air | 2 | 2026-04-23 |
| OMA265 | Oman Air | 2 | 2026-05-21 |
| OMA154 | Oman Air | 2 | 2026-04-22 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | OMA408 | CAI → MCT | May 29, 23:45 UTC | May 30, 02:20 UTC | 2h 35m |
| 2026-05-29 | OMA246 | DEL → MCT | May 29, 10:50 UTC | May 29, 21:45 UTC | 10h 55m |
| 2026-05-29 | OMA245 | MCT → DEL | May 29, 08:35 UTC | May 29, 09:25 UTC | 50m |
| 2026-05-28 | OMA669 | - | May 28, 15:15 UTC | May 28, 15:20 UTC | 5m |
| 2026-05-27 | OMA254 | MAA → MCT | May 27, 07:00 UTC | May 27, 11:45 UTC | 4h 45m |
| 2026-05-26 | OMA609 | MCT → DXB | May 26, 10:54 UTC | May 26, 11:20 UTC | 25m |
| 2026-05-25 | OMA124 | MUC → MCT | May 25, 20:24 UTC | May 26, 02:29 UTC | 6h 5m |
| 2026-05-25 | OMA123 | MCT → MUC | May 25, 02:45 UTC | May 25, 18:40 UTC | 15h 55m |
| 2026-05-24 | OMA824 | KUL → MCT | May 24, 16:45 UTC | May 24, 23:46 UTC | 7h 1m |
| 2026-05-24 | OMA824 | KUL → MCT | May 24, 13:30 UTC | May 24, 13:45 UTC | 15m |
| 2026-05-23 | OMA823 | MCT → KUL | May 23, 22:00 UTC | May 24, 11:45 UTC | 13h 45m |
| 2026-05-23 | OMA223 | MCT → COK | May 23, 07:50 UTC | May 23, 08:15 UTC | 25m |
| 2026-05-22 | OMA696 | DMM → MCT | May 22, 18:55 UTC | May 22, 19:45 UTC | 50m |
| 2026-05-22 | OMA822 | KUL → MCT | May 22, 06:20 UTC | May 22, 06:45 UTC | 25m |
| 2026-05-22 | OMA822 | KUL → MCT | May 22, 02:00 UTC | May 22, 02:15 UTC | 15m |
| 2026-05-21 | OMA821 | MCT → KUL | May 21, 18:45 UTC | May 21, 23:40 UTC | 4h 55m |
| 2026-05-21 | OMA266 | LKO → MCT | May 21, 04:35 UTC | May 21, 23:40 UTC | 19h 5m |
| 2026-05-21 | OMA265 | MCT → LKO | May 21, 00:10 UTC | May 21, 02:05 UTC | 1h 55m |
| 2026-05-20 | OMA265 | MCT → LKO | May 20, 05:50 UTC | May 21, 02:05 UTC | 20h 15m |
| 2026-05-20 | OMA818 | BKK → MCT | May 20, 02:10 UTC | May 21, 01:30 UTC | 23h 21m |
| 2026-05-19 | OMA817 | MCT → BKK | May 19, 18:30 UTC | May 19, 23:10 UTC | 4h 40m |
| 2026-05-17 | OMA833 | MCT → HKT | May 17, 04:35 UTC | May 17, 21:50 UTC | 17h 15m |
| 2026-05-16 | OMA166 | IST → MCT | May 16, 16:40 UTC | May 17, 03:05 UTC | 10h 25m |
| 2026-05-16 | OMA165 | MCT → IST | May 16, 14:46 UTC | May 16, 14:55 UTC | 10m |
| 2026-05-16 | OMA252 | MAA → MCT | May 16, 03:00 UTC | May 16, 04:30 UTC | 1h 30m |
| 2026-05-15 | OMA251 | MCT → MAA | May 15, 23:55 UTC | May 16, 01:30 UTC | 1h 35m |
| 2026-05-15 | OMA226 | COK → MCT | May 15, 03:15 UTC | May 15, 03:25 UTC | 10m |
| 2026-05-15 | OMA225 | MCT → COK | May 15, 01:15 UTC | May 15, 01:50 UTC | 35m |
| 2026-05-13 | OMA226 | COK → MCT | May 13, 03:00 UTC | May 13, 03:15 UTC | 15m |
| 2026-05-13 | OMA225 | MCT → COK | May 13, 00:55 UTC | May 13, 01:40 UTC | 45m |
| 2026-05-12 | OMA225 | MCT → COK | May 12, 03:05 UTC | May 13, 01:30 UTC | 22h 25m |
| 2026-05-11 | OMA226 | COK → MCT | May 11, 03:20 UTC | May 11, 03:30 UTC | 10m |
| 2026-05-10 | OMA414 | AMM → MCT | May 10, 12:15 UTC | May 11, 01:40 UTC | 13h 25m |
| 2026-05-10 | OMA252 | MAA → MCT | May 10, 02:55 UTC | May 11, 01:30 UTC | 22h 35m |
| 2026-05-10 | OMA251 | MCT → MAA | May 10, 00:34 UTC | May 10, 01:14 UTC | 40m |
| 2026-05-08 | OMA226 | COK → MCT | May 8, 02:55 UTC | May 8, 03:04 UTC | 10m |
| 2026-05-08 | OMA225 | MCT → COK | May 8, 01:40 UTC | May 8, 01:49 UTC | 10m |
| 2026-05-07 | OMA682 | RUH → MCT | May 7, 18:55 UTC | May 7, 19:15 UTC | 20m |
| 2026-05-07 | OMA223 | MCT → COK | May 7, 07:30 UTC | May 7, 07:40 UTC | 10m |
| 2026-05-06 | OMA824 | KUL → MCT | May 6, 13:30 UTC | May 6, 17:10 UTC | 3h 40m |
| 2026-05-05 | OMA685 | MCT → RUH | May 5, 22:50 UTC | May 6, 11:30 UTC | 12h 40m |
| 2026-05-05 | OMA663 | MCT → DOH | May 5, 11:55 UTC | May 5, 13:40 UTC | 1h 45m |
| 2026-05-03 | OMA833 | MCT → HKT | May 3, 20:20 UTC | May 4, 14:25 UTC | 18h 5m |
| 2026-05-03 | OMA414 | AMM → MCT | May 3, 04:35 UTC | May 3, 17:05 UTC | 12h 30m |
| 2026-05-03 | OMA281 | MCT → BLR | May 3, 01:45 UTC | May 3, 03:10 UTC | 1h 25m |
| 2026-05-02 | OMA611 | MCT → DXB | May 2, 16:40 UTC | May 2, 17:15 UTC | 35m |
| 2026-05-02 | OMA318 | DAC → MCT | May 2, 10:15 UTC | May 2, 11:15 UTC | 1h 0m |
| 2026-05-01 | OMA317 | MCT → DAC | May 1, 14:00 UTC | May 2, 08:50 UTC | 18h 50m |
| 2026-04-30 | OMA252 | MAA → MCT | Apr 30, 02:55 UTC | Apr 30, 17:05 UTC | 14h 10m |
| 2026-04-29 | OMA251 | MCT → MAA | Apr 29, 23:40 UTC | Apr 30, 01:05 UTC | 1h 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-MK page for operator, model, and routing details .