sensors Mode-S transponder
70C11F
ICAO 24-bit transponder address · allocated to Oman
Currently assigned to A4O-MR · BOEING 737 MAX 8
- Hex
- 70C11F
- Octal
- 34140437
- Decimal
- 7,389,471
- Country
- OM
- Tail
- A4O-MR
- Type
- B38M
- Flights observed
- 144
- Distinct callsigns
- 20
- Country
- OM
- Last broadcast
- Jul 26, 19:25 UTC
Last known position
Country allocation
The ICAO 24-bit address 70C11F 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 |
|---|---|---|---|
| OMA317 | Oman Air | 24 | 2026-07-23 |
| OMA265 | Oman Air | 21 | 2026-07-25 |
| OMA211 | Oman Air | 18 | 2026-07-18 |
| OMA318 | Oman Air | 14 | 2026-07-23 |
| OMA266 | Oman Air | 13 | 2026-07-24 |
| OMA212 | - | 12 | 2026-07-18 |
| OMS272 | Omskavia Airline | 7 | 2026-05-09 |
| OMS214 | Omskavia Airline | 3 | 2026-05-06 |
| OMS212 | Omskavia Airline | 3 | 2026-05-09 |
| OMA679 | Oman Air | 3 | 2026-07-25 |
| OMS522 | Omskavia Airline | 2 | 2026-05-03 |
| OMA694 | Oman Air | 2 | 2026-04-29 |
| OMA693 | Oman Air | 2 | 2026-04-29 |
| OMA618 | - | 2 | 2026-07-24 |
| OMA236 | Oman Air | 2 | 2026-07-19 |
| OMA166 | Oman Air | 2 | 2026-04-28 |
| OMA165 | Oman Air | 2 | 2026-04-28 |
| OMS521 | Omskavia Airline | 1 | 2026-05-05 |
| OMS274 | Omskavia Airline | 1 | 2026-05-04 |
| OMS273 | Omskavia Airline | 1 | 2026-05-04 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | OMA648 | KWI → MCT | Jul 26, 18:20 UTC | Jul 26, 19:25 UTC | 1h 5m |
| 2026-07-26 | OMA647 | MCT → KWI | Jul 26, 06:10 UTC | Jul 26, 16:30 UTC | 10h 21m |
| 2026-07-25 | OMA265 | MCT → LKO | Jul 25, 11:45 UTC | Jul 26, 03:30 UTC | 15h 45m |
| 2026-07-25 | OMA679 | MCT → MED | Jul 25, 02:45 UTC | Jul 26, 01:45 UTC | 23h 0m |
| 2026-07-24 | OMA618 | - | Jul 24, 14:00 UTC | Jul 25, 11:45 UTC | 21h 45m |
| 2026-07-24 | OMA266 | LKO → MCT | Jul 24, 04:55 UTC | Jul 24, 12:10 UTC | 7h 15m |
| 2026-07-23 | OMA318 | DAC → MCT | Jul 23, 10:30 UTC | Jul 24, 02:20 UTC | 15h 50m |
| 2026-07-23 | OMA317 | MCT → DAC | Jul 23, 05:50 UTC | Jul 23, 08:55 UTC | 3h 5m |
| 2026-07-22 | OMA317 | MCT → DAC | Jul 22, 12:10 UTC | Jul 23, 08:55 UTC | 20h 45m |
| 2026-07-21 | OMA618 | - | Jul 21, 13:25 UTC | Jul 22, 01:55 UTC | 12h 30m |
| 2026-07-21 | OMA266 | LKO → MCT | Jul 21, 04:50 UTC | Jul 21, 11:35 UTC | 6h 45m |
| 2026-07-20 | OMA318 | DAC → MCT | Jul 20, 10:20 UTC | Jul 21, 02:10 UTC | 15h 49m |
| 2026-07-19 | OMA317 | MCT → DAC | Jul 19, 19:15 UTC | Jul 20, 09:05 UTC | 13h 50m |
| 2026-07-19 | OMA236 | HYD → MCT | Jul 19, 00:45 UTC | Jul 19, 11:35 UTC | 10h 50m |
| 2026-07-18 | OMA212 | - | Jul 18, 03:20 UTC | Jul 18, 03:30 UTC | 10m |
| 2026-07-18 | OMA211 | MCT → TRV | Jul 18, 01:45 UTC | Jul 18, 02:00 UTC | 15m |
| 2026-07-17 | OMA266 | - | Jul 17, 05:04 UTC | Jul 17, 18:34 UTC | 13h 30m |
| 2026-07-16 | OMA265 | - | Jul 16, 14:25 UTC | Jul 17, 02:25 UTC | 12h 0m |
| 2026-07-16 | OMA211 | - | Jul 16, 02:00 UTC | Jul 16, 02:20 UTC | 20m |
| 2026-07-15 | OMA318 | - | Jul 15, 10:40 UTC | Jul 15, 13:35 UTC | 2h 55m |
| 2026-07-14 | OMA317 | - | Jul 14, 12:45 UTC | Jul 15, 09:10 UTC | 20h 24m |
| 2026-07-14 | OMA317 | - | Jul 14, 10:40 UTC | Jul 15, 09:10 UTC | 22h 29m |
| 2026-07-14 | OMA317 | - | Jul 14, 05:40 UTC | Jul 14, 09:05 UTC | 3h 25m |
| 2026-07-13 | OMA678 | - | Jul 13, 18:10 UTC | Jul 14, 00:35 UTC | 6h 25m |
| 2026-07-13 | OMA266 | - | Jul 13, 04:35 UTC | Jul 14, 00:35 UTC | 20h 0m |
| 2026-07-13 | OMA265 | - | Jul 13, 00:30 UTC | Jul 13, 02:20 UTC | 1h 50m |
| 2026-07-12 | OMA265 | - | Jul 12, 04:50 UTC | Jul 13, 02:20 UTC | 21h 30m |
| 2026-07-11 | OMA265 | - | Jul 11, 13:30 UTC | Jul 12, 02:05 UTC | 12h 35m |
| 2026-07-10 | OMA679 | - | Jul 10, 11:35 UTC | Jul 11, 02:05 UTC | 14h 30m |
| 2026-07-09 | OMA211 | - | Jul 9, 14:05 UTC | Jul 10, 02:55 UTC | 12h 50m |
| 2026-07-09 | OMA212 | - | Jul 9, 03:25 UTC | Jul 9, 03:35 UTC | 10m |
| 2026-07-09 | OMA211 | - | Jul 9, 02:00 UTC | Jul 9, 02:15 UTC | 15m |
| 2026-07-08 | OMA679 | - | Jul 8, 11:50 UTC | Jul 8, 16:55 UTC | 5h 5m |
| 2026-07-08 | OMA212 | - | Jul 8, 03:20 UTC | Jul 8, 03:30 UTC | 10m |
| 2026-07-08 | OMA211 | - | Jul 8, 01:50 UTC | Jul 8, 02:05 UTC | 15m |
| 2026-07-07 | OMA318 | - | Jul 7, 10:25 UTC | Jul 7, 13:30 UTC | 3h 5m |
| 2026-07-07 | OMA317 | - | Jul 7, 05:35 UTC | Jul 7, 08:45 UTC | 3h 10m |
| 2026-07-06 | OMA677 | - | Jul 6, 17:55 UTC | Jul 7, 00:25 UTC | 6h 30m |
| 2026-07-06 | OMA266 | - | Jul 6, 04:40 UTC | Jul 6, 05:30 UTC | 50m |
| 2026-07-05 | OMA318 | - | Jul 5, 10:15 UTC | Jul 6, 01:55 UTC | 15h 40m |
| 2026-07-04 | OMA317 | - | Jul 4, 14:30 UTC | Jul 5, 09:00 UTC | 18h 30m |
| 2026-07-04 | OMA266 | - | Jul 4, 04:40 UTC | Jul 4, 14:35 UTC | 9h 55m |
| 2026-07-03 | OMA265 | - | Jul 3, 13:20 UTC | Jul 4, 02:00 UTC | 12h 40m |
| 2026-07-03 | OMA617 | - | Jul 3, 10:55 UTC | Jul 3, 11:35 UTC | 40m |
| 2026-07-03 | OMA212 | - | Jul 3, 03:25 UTC | Jul 3, 03:35 UTC | 10m |
| 2026-07-03 | OMA211 | - | Jul 3, 01:45 UTC | Jul 3, 02:25 UTC | 40m |
| 2026-07-02 | OMA212 | - | Jul 2, 03:30 UTC | Jul 3, 01:45 UTC | 22h 15m |
| 2026-07-01 | OMA318 | - | Jul 1, 10:45 UTC | Jul 2, 02:20 UTC | 15h 35m |
| 2026-06-30 | OMA317 | - | Jun 30, 13:50 UTC | Jul 1, 08:50 UTC | 19h 0m |
| 2026-06-30 | OMA317 | - | Jun 30, 11:50 UTC | Jul 1, 08:50 UTC | 21h 0m |
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-MR page for operator, model, and routing details .