sensors Mode-S transponder
70C11C
ICAO 24-bit transponder address · allocated to Oman
Currently assigned to A4O-MO · BOEING 737 MAX 8
- Hex
- 70C11C
- Octal
- 34140434
- Decimal
- 7,389,468
- Country
- OM
- Tail
- A4O-MO
- Type
- B38M
- Flights observed
- 75
- Distinct callsigns
- 20
- Country
- OM
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 70C11C 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 |
|---|---|---|---|
| OMA166 | Oman Air | 14 | 2026-05-10 |
| OMA265 | Oman Air | 12 | 2026-05-14 |
| OMA165 | Oman Air | 7 | 2026-05-09 |
| OMA266 | Oman Air | 6 | 2026-05-14 |
| OMS214 | Omskavia Airline | 5 | 2026-05-28 |
| OMA318 | Oman Air | 4 | 2026-04-15 |
| OMA212 | Oman Air | 4 | 2026-05-08 |
| OMA694 | Oman Air | 3 | 2026-04-27 |
| OMA693 | Oman Air | 3 | 2026-04-27 |
| OMA680 | Oman Air | 3 | 2026-05-01 |
| OMS563 | Omskavia Airline | 2 | 2026-05-20 |
| OMA317 | Oman Air | 2 | 2026-04-15 |
| OMA211 | Oman Air | 2 | 2026-05-02 |
| OMS564 | Omskavia Airline | 1 | 2026-05-19 |
| OMS538 | Omskavia Airline | 1 | 2026-05-21 |
| OMS537 | Omskavia Airline | 1 | 2026-05-21 |
| OMS506 | Omskavia Airline | 1 | 2026-05-15 |
| OMS213 | Omskavia Airline | 1 | 2026-05-21 |
| OMS205 | Omskavia Airline | 1 | 2026-05-23 |
| OMA678 | Oman Air | 1 | 2026-04-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-28 | OMS214 | DMM → MCT | May 28, 15:20 UTC | May 28, 23:30 UTC | 8h 10m |
| 2026-05-27 | OMS214 | DMM → MCT | May 27, 15:20 UTC | May 27, 23:15 UTC | 7h 55m |
| 2026-05-26 | OMS214 | DMM → MCT | May 26, 15:24 UTC | May 26, 21:29 UTC | 6h 5m |
| 2026-05-23 | OMS205 | MCT → RUH | May 23, 09:50 UTC | May 23, 23:15 UTC | 13h 26m |
| 2026-05-22 | OMS214 | DMM → MCT | May 22, 15:25 UTC | May 23, 10:00 UTC | 18h 35m |
| 2026-05-21 | OMS538 | MUX → MCT | May 21, 23:30 UTC | May 21, 23:35 UTC | 5m |
| 2026-05-21 | OMS537 | MCT → MUX | May 21, 22:20 UTC | May 21, 22:30 UTC | 10m |
| 2026-05-21 | OMS214 | DMM → MCT | May 21, 15:40 UTC | May 21, 16:35 UTC | 55m |
| 2026-05-21 | OMS213 | MCT → DMM | May 21, 13:45 UTC | May 21, 14:15 UTC | 30m |
| 2026-05-20 | OMS563 | MCT → ISB | May 20, 21:05 UTC | May 20, 23:40 UTC | 2h 35m |
| 2026-05-19 | OMS564 | ISB → MCT | May 19, 23:35 UTC | May 20, 21:10 UTC | 21h 36m |
| 2026-05-19 | OMS563 | MCT → ISB | May 19, 21:10 UTC | May 19, 23:40 UTC | 2h 30m |
| 2026-05-15 | OMS506 | SKT → MCT | May 15, 22:15 UTC | May 16, 00:35 UTC | 2h 20m |
| 2026-05-14 | OMA266 | LKO → MCT | May 14, 04:30 UTC | May 14, 05:30 UTC | 1h 0m |
| 2026-05-14 | OMA265 | MCT → LKO | May 14, 00:15 UTC | May 14, 02:00 UTC | 1h 45m |
| 2026-05-13 | OMA265 | MCT → LKO | May 13, 05:05 UTC | May 14, 02:00 UTC | 20h 55m |
| 2026-05-13 | OMA265 | MCT → LKO | May 13, 04:35 UTC | May 14, 02:00 UTC | 21h 25m |
| 2026-05-13 | OMA265 | MCT → LKO | May 13, 00:15 UTC | May 13, 02:05 UTC | 1h 50m |
| 2026-05-12 | OMA266 | LKO → MCT | May 12, 04:50 UTC | May 12, 14:35 UTC | 9h 45m |
| 2026-05-11 | OMA266 | LKO → MCT | May 11, 04:35 UTC | May 11, 05:30 UTC | 55m |
| 2026-05-10 | OMA166 | IST → MCT | May 10, 16:44 UTC | May 11, 02:00 UTC | 9h 15m |
| 2026-05-09 | OMA165 | MCT → IST | May 9, 19:25 UTC | May 10, 13:49 UTC | 18h 25m |
| 2026-05-09 | OMA166 | IST → MCT | May 9, 17:05 UTC | May 10, 13:49 UTC | 20h 45m |
| 2026-05-09 | OMA166 | IST → MCT | May 9, 16:50 UTC | May 10, 13:49 UTC | 21h 0m |
| 2026-05-09 | OMA166 | IST → MCT | May 9, 10:20 UTC | May 10, 00:39 UTC | 14h 20m |
| 2026-05-09 | OMA166 | IST → MCT | May 9, 04:15 UTC | May 10, 00:39 UTC | 20h 25m |
| 2026-05-09 | OMA265 | MCT → LKO | May 9, 01:55 UTC | May 9, 02:45 UTC | 50m |
| 2026-05-08 | OMA212 | TRV → MCT | May 8, 03:14 UTC | May 8, 03:24 UTC | 10m |
| 2026-05-07 | OMA166 | IST → MCT | May 7, 16:40 UTC | May 8, 02:04 UTC | 9h 24m |
| 2026-05-07 | OMA265 | MCT → LKO | May 7, 01:15 UTC | May 7, 02:15 UTC | 1h 0m |
| 2026-05-05 | OMA166 | IST → MCT | May 5, 16:25 UTC | May 6, 02:05 UTC | 9h 40m |
| 2026-05-05 | OMA165 | MCT → IST | May 5, 14:20 UTC | May 5, 14:35 UTC | 15m |
| 2026-05-05 | OMA165 | MCT → IST | May 5, 10:25 UTC | May 5, 12:35 UTC | 2h 10m |
| 2026-05-04 | OMA265 | MCT → LKO | May 4, 14:00 UTC | May 5, 02:50 UTC | 12h 51m |
| 2026-05-04 | OMA266 | LKO → MCT | May 4, 05:05 UTC | May 5, 02:50 UTC | 21h 46m |
| 2026-05-04 | OMA266 | LKO → MCT | May 4, 04:39 UTC | May 5, 02:50 UTC | 22h 11m |
| 2026-05-04 | OMA265 | MCT → LKO | May 4, 01:05 UTC | May 4, 02:04 UTC | 1h 0m |
| 2026-05-03 | OMA166 | IST → MCT | May 3, 16:25 UTC | May 3, 20:40 UTC | 4h 15m |
| 2026-05-03 | OMA265 | MCT → LKO | May 3, 00:50 UTC | May 3, 01:55 UTC | 1h 5m |
| 2026-05-02 | OMA212 | TRV → MCT | May 2, 03:10 UTC | May 2, 03:20 UTC | 10m |
| 2026-05-02 | OMA211 | MCT → TRV | May 2, 01:40 UTC | May 2, 02:00 UTC | 20m |
| 2026-05-01 | OMA680 | MED → MCT | May 1, 11:35 UTC | May 1, 17:20 UTC | 5h 45m |
| 2026-04-30 | OMA166 | IST → MCT | Apr 30, 16:40 UTC | Apr 30, 20:45 UTC | 4h 5m |
| 2026-04-30 | OMA212 | TRV → MCT | Apr 30, 03:20 UTC | Apr 30, 13:50 UTC | 10h 30m |
| 2026-04-30 | OMA211 | MCT → TRV | Apr 30, 01:45 UTC | Apr 30, 02:05 UTC | 20m |
| 2026-04-29 | OMA680 | MED → MCT | Apr 29, 12:30 UTC | Apr 29, 17:30 UTC | 5h 0m |
| 2026-04-27 | OMA694 | DMM → MCT | Apr 27, 14:05 UTC | Apr 27, 15:00 UTC | 55m |
| 2026-04-27 | OMA693 | MCT → DMM | Apr 27, 11:30 UTC | Apr 27, 11:50 UTC | 20m |
| 2026-04-25 | OMA680 | MED → MCT | Apr 25, 12:25 UTC | Apr 25, 17:40 UTC | 5h 15m |
| 2026-04-24 | OMA166 | IST → MCT | Apr 24, 17:00 UTC | Apr 24, 21:30 UTC | 4h 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-MO page for operator, model, and routing details .