sensors Mode-S transponder
70C11E
ICAO 24-bit transponder address · allocated to Oman
Currently assigned to A4O-MQ · BOEING 737 MAX 8
- Hex
- 70C11E
- Octal
- 34140436
- Decimal
- 7,389,470
- Country
- OM
- Tail
- A4O-MQ
- Type
- B38M
- Flights observed
- 78
- Distinct callsigns
- 20
- Country
- OM
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 70C11E 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 |
|---|---|---|---|
| OMS437 | Omskavia Airline | 11 | 2026-05-27 |
| OMS438 | Omskavia Airline | 10 | 2026-05-30 |
| OMS272 | Omskavia Airline | 6 | 2026-05-24 |
| OMS274 | Omskavia Airline | 5 | 2026-06-02 |
| OMS522 | Omskavia Airline | 3 | 2026-05-30 |
| OMS212 | Omskavia Airline | 3 | 2026-05-21 |
| OMS206 | Omskavia Airline | 3 | 2026-05-09 |
| OMA265 | Oman Air | 3 | 2026-05-01 |
| OMA166 | Oman Air | 3 | 2026-04-25 |
| OMS245 | Omskavia Airline | 2 | 2026-05-19 |
| OMA680 | - | 2 | 2026-04-17 |
| OMA679 | - | 2 | 2026-04-17 |
| OMA678 | Oman Air | 2 | 2026-04-27 |
| OMA318 | Oman Air | 2 | 2026-04-28 |
| OMA317 | Oman Air | 2 | 2026-04-28 |
| OMA211 | Oman Air | 2 | 2026-04-22 |
| OMA165 | Oman Air | 2 | 2026-04-25 |
| OMS706 | Omskavia Airline | 1 | 2026-06-01 |
| OMS705 | Omskavia Airline | 1 | 2026-06-01 |
| OMS564 | Omskavia Airline | 1 | 2026-05-03 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | OMS274 | MED → MCT | Jun 2, 08:10 UTC | Jun 2, 23:35 UTC | 15h 25m |
| 2026-06-01 | OMS706 | LKO → MCT | Jun 1, 23:35 UTC | Jun 2, 23:30 UTC | 23h 55m |
| 2026-06-01 | OMS705 | MCT → LKO | Jun 1, 20:40 UTC | Jun 1, 22:25 UTC | 1h 45m |
| 2026-05-30 | OMS522 | LHE → MCT | May 30, 23:10 UTC | May 30, 23:40 UTC | 30m |
| 2026-05-30 | OMS438 | CMB → MCT | May 30, 00:05 UTC | May 30, 21:30 UTC | 21h 25m |
| 2026-05-29 | OMS214 | DMM → MCT | May 29, 15:15 UTC | May 29, 22:05 UTC | 6h 50m |
| 2026-05-28 | OMS538 | MUX → MCT | May 28, 23:10 UTC | May 28, 23:15 UTC | 5m |
| 2026-05-28 | OMS537 | MCT → MUX | May 28, 22:00 UTC | May 28, 22:15 UTC | 15m |
| 2026-05-27 | OMS438 | CMB → MCT | May 27, 23:50 UTC | May 28, 00:15 UTC | 25m |
| 2026-05-27 | OMS437 | MCT → CMB | May 27, 21:25 UTC | May 27, 22:05 UTC | 40m |
| 2026-05-26 | OMS438 | CMB → MCT | May 26, 23:54 UTC | May 27, 21:30 UTC | 21h 35m |
| 2026-05-26 | OMS437 | MCT → CMB | May 26, 21:14 UTC | May 26, 21:59 UTC | 45m |
| 2026-05-25 | OMS437 | MCT → CMB | May 25, 23:30 UTC | May 26, 21:29 UTC | 22h 0m |
| 2026-05-25 | OMS205 | MCT → RUH | May 25, 10:25 UTC | May 25, 23:30 UTC | 13h 4m |
| 2026-05-24 | OMS272 | MED → MCT | May 24, 13:05 UTC | May 25, 10:30 UTC | 21h 25m |
| 2026-05-23 | OMS272 | MED → MCT | May 23, 23:10 UTC | May 24, 13:30 UTC | 14h 20m |
| 2026-05-23 | OMS438 | CMB → MCT | May 23, 00:10 UTC | May 23, 21:15 UTC | 21h 5m |
| 2026-05-22 | OMS437 | MCT → CMB | May 22, 13:20 UTC | May 22, 22:10 UTC | 8h 50m |
| 2026-05-21 | OMS272 | MED → MCT | May 21, 23:30 UTC | May 22, 21:30 UTC | 22h 0m |
| 2026-05-21 | OMS212 | DMM → MCT | May 21, 08:55 UTC | May 21, 23:30 UTC | 14h 35m |
| 2026-05-20 | OMS437 | MCT → CMB | May 20, 21:20 UTC | May 21, 00:45 UTC | 3h 25m |
| 2026-05-19 | OMS522 | LHE → MCT | May 19, 22:45 UTC | May 20, 21:30 UTC | 22h 46m |
| 2026-05-19 | OMS521 | MCT → LHE | May 19, 21:05 UTC | May 19, 21:10 UTC | 5m |
| 2026-05-19 | OMS245 | MCT → SHJ | May 19, 13:55 UTC | May 19, 14:20 UTC | 25m |
| 2026-05-19 | OMS438 | CMB → MCT | May 19, 00:35 UTC | May 19, 01:20 UTC | 45m |
| 2026-05-18 | OMS272 | MED → MCT | May 18, 11:05 UTC | May 18, 22:30 UTC | 11h 24m |
| 2026-05-17 | OMS272 | MED → MCT | May 17, 23:25 UTC | May 18, 11:40 UTC | 12h 15m |
| 2026-05-16 | OMS274 | MED → MCT | May 16, 12:11 UTC | May 16, 21:30 UTC | 9h 20m |
| 2026-05-14 | OMS522 | LHE → MCT | May 14, 22:55 UTC | May 14, 23:25 UTC | 30m |
| 2026-05-14 | OMS274 | MED → MCT | May 14, 12:35 UTC | May 14, 21:15 UTC | 8h 40m |
| 2026-05-14 | OMS274 | MED → MCT | May 14, 00:20 UTC | May 14, 21:15 UTC | 20h 55m |
| 2026-05-13 | OMS274 | MED → MCT | May 13, 21:50 UTC | May 14, 21:15 UTC | 23h 25m |
| 2026-05-13 | OMS272 | MED → MCT | May 13, 11:25 UTC | May 14, 00:20 UTC | 12h 55m |
| 2026-05-13 | OMS438 | CMB → MCT | May 13, 00:10 UTC | May 13, 21:50 UTC | 21h 40m |
| 2026-05-12 | OMS437 | MCT → CMB | May 12, 21:25 UTC | May 13, 11:35 UTC | 14h 10m |
| 2026-05-11 | OMS437 | MCT → CMB | May 11, 21:35 UTC | May 12, 21:30 UTC | 23h 55m |
| 2026-05-11 | OMS437 | MCT → CMB | May 11, 06:55 UTC | May 11, 22:05 UTC | 15h 11m |
| 2026-05-11 | OMS437 | MCT → CMB | May 11, 00:05 UTC | May 11, 22:05 UTC | 22h 1m |
| 2026-05-10 | OMS437 | MCT → CMB | May 10, 10:30 UTC | May 10, 21:59 UTC | 11h 30m |
| 2026-05-09 | OMS206 | RUH → MCT | May 9, 23:25 UTC | May 10, 21:30 UTC | 22h 5m |
| 2026-05-09 | OMS206 | RUH → MCT | May 9, 12:50 UTC | May 10, 10:35 UTC | 21h 45m |
| 2026-05-09 | OMS206 | RUH → MCT | May 9, 10:00 UTC | May 9, 23:25 UTC | 13h 25m |
| 2026-05-07 | OMS212 | DMM → MCT | May 7, 10:20 UTC | May 7, 23:34 UTC | 13h 14m |
| 2026-05-07 | OMS438 | CMB → MCT | May 7, 00:00 UTC | May 7, 23:29 UTC | 23h 30m |
| 2026-05-06 | OMS438 | CMB → MCT | May 6, 21:40 UTC | May 7, 21:20 UTC | 23h 41m |
| 2026-05-06 | OMS438 | CMB → MCT | May 6, 21:20 UTC | May 7, 10:45 UTC | 13h 25m |
| 2026-05-06 | OMS438 | CMB → MCT | May 6, 11:05 UTC | May 7, 00:45 UTC | 13h 39m |
| 2026-05-05 | OMS437 | MCT → CMB | May 5, 23:45 UTC | May 6, 22:00 UTC | 22h 14m |
| 2026-05-05 | OMS245 | MCT → SHJ | May 5, 14:10 UTC | May 5, 14:40 UTC | 30m |
| 2026-05-04 | OMS212 | DMM → MCT | May 4, 16:10 UTC | May 5, 10:45 UTC | 18h 36m |
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-MQ page for operator, model, and routing details .