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
- 43
- Distinct callsigns
- 19
- Country
- OM
- Last broadcast
- 6h ago
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 19 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| OMS272 | Omskavia Airline | 7 | 2026-05-09 |
| OMA265 | Oman Air | 5 | 2026-05-30 |
| OMS214 | Omskavia Airline | 3 | 2026-05-06 |
| OMS212 | Omskavia Airline | 3 | 2026-05-09 |
| OMA211 | Oman Air | 3 | 2026-05-26 |
| OMS522 | Omskavia Airline | 2 | 2026-05-03 |
| OMA694 | Oman Air | 2 | 2026-04-29 |
| OMA693 | Oman Air | 2 | 2026-04-29 |
| OMA318 | Oman Air | 2 | 2026-06-02 |
| OMA317 | Oman Air | 2 | 2026-06-02 |
| OMA266 | Oman Air | 2 | 2026-04-17 |
| 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 |
| OMA235 | Oman Air | 1 | 2026-04-25 |
| OMA231 | Oman Air | 1 | 2026-04-25 |
| OMA212 | Oman Air | 1 | 2026-05-26 |
Recent flights last 43
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | OMA318 | DAC → MCT | Jun 2, 10:15 UTC | Jun 2, 13:20 UTC | 3h 5m |
| 2026-06-02 | OMA317 | MCT → DAC | Jun 2, 05:55 UTC | Jun 2, 09:00 UTC | 3h 5m |
| 2026-05-30 | OMA265 | MCT → LKO | May 30, 16:40 UTC | May 31, 01:11 UTC | 8h 31m |
| 2026-05-26 | OMA212 | TRV → MCT | May 26, 03:15 UTC | May 26, 03:40 UTC | 25m |
| 2026-05-26 | OMA211 | MCT → TRV | May 26, 00:04 UTC | May 26, 02:04 UTC | 2h 0m |
| 2026-05-09 | OMS272 | MED → MCT | May 9, 22:10 UTC | May 10, 11:30 UTC | 13h 20m |
| 2026-05-09 | OMS212 | DMM → MCT | May 9, 09:50 UTC | May 10, 07:25 UTC | 21h 35m |
| 2026-05-09 | OMS212 | DMM → MCT | May 9, 07:00 UTC | May 10, 00:24 UTC | 17h 25m |
| 2026-05-08 | OMS212 | DMM → MCT | May 8, 21:05 UTC | May 9, 10:50 UTC | 13h 45m |
| 2026-05-08 | OMS272 | MED → MCT | May 8, 10:59 UTC | May 9, 09:45 UTC | 22h 45m |
| 2026-05-07 | OMS272 | MED → MCT | May 7, 23:55 UTC | May 8, 23:25 UTC | 23h 30m |
| 2026-05-07 | OMS272 | MED → MCT | May 7, 15:50 UTC | May 8, 11:34 UTC | 19h 45m |
| 2026-05-07 | OMS272 | MED → MCT | May 7, 15:35 UTC | May 8, 11:34 UTC | 19h 59m |
| 2026-05-06 | OMS214 | DMM → MCT | May 6, 23:50 UTC | May 7, 15:50 UTC | 16h 0m |
| 2026-05-06 | OMS214 | DMM → MCT | May 6, 15:50 UTC | May 7, 15:45 UTC | 23h 55m |
| 2026-05-06 | OMS214 | DMM → MCT | May 6, 15:35 UTC | May 6, 23:50 UTC | 8h 14m |
| 2026-05-05 | OMS521 | MCT → LHE | May 5, 21:20 UTC | May 5, 23:35 UTC | 2h 15m |
| 2026-05-04 | OMS274 | MED → MCT | May 4, 23:55 UTC | May 5, 13:40 UTC | 13h 45m |
| 2026-05-04 | OMS273 | MCT → MED | May 4, 12:05 UTC | May 5, 08:30 UTC | 20h 26m |
| 2026-05-04 | OMS272 | MED → MCT | May 4, 11:20 UTC | May 5, 08:30 UTC | 21h 11m |
| 2026-05-03 | OMS272 | MED → MCT | May 3, 22:09 UTC | May 4, 12:10 UTC | 14h 0m |
| 2026-05-03 | OMS522 | LHE → MCT | May 3, 01:00 UTC | May 3, 22:15 UTC | 21h 14m |
| 2026-05-02 | OMS522 | LHE → MCT | May 2, 21:35 UTC | May 3, 01:10 UTC | 3h 35m |
| 2026-04-29 | OMA694 | DMM → MCT | Apr 29, 13:25 UTC | Apr 29, 14:25 UTC | 1h 0m |
| 2026-04-29 | OMA693 | MCT → DMM | Apr 29, 10:50 UTC | Apr 29, 11:55 UTC | 1h 5m |
| 2026-04-28 | OMA166 | IST → MCT | Apr 28, 16:45 UTC | Apr 28, 20:45 UTC | 4h 0m |
| 2026-04-28 | OMA165 | MCT → IST | Apr 28, 10:15 UTC | Apr 28, 14:55 UTC | 4h 40m |
| 2026-04-28 | OMA265 | MCT → LKO | Apr 28, 01:00 UTC | Apr 28, 01:45 UTC | 45m |
| 2026-04-27 | OMA265 | MCT → LKO | Apr 27, 01:30 UTC | Apr 27, 02:15 UTC | 45m |
| 2026-04-26 | OMA166 | IST → MCT | Apr 26, 17:20 UTC | Apr 26, 21:40 UTC | 4h 20m |
| 2026-04-26 | OMA165 | MCT → IST | Apr 26, 00:45 UTC | Apr 26, 15:05 UTC | 14h 20m |
| 2026-04-25 | OMA235 | MCT → HYD | Apr 25, 11:50 UTC | Apr 26, 10:45 UTC | 22h 55m |
| 2026-04-25 | OMA231 | MCT → HYD | Apr 25, 08:15 UTC | Apr 26, 04:25 UTC | 20h 10m |
| 2026-04-24 | OMA694 | DMM → MCT | Apr 24, 14:05 UTC | Apr 24, 15:20 UTC | 1h 15m |
| 2026-04-24 | OMA693 | MCT → DMM | Apr 24, 03:30 UTC | Apr 24, 12:45 UTC | 9h 15m |
| 2026-04-24 | OMA211 | MCT → TRV | Apr 24, 01:40 UTC | Apr 24, 02:05 UTC | 25m |
| 2026-04-20 | OMA318 | DAC → MCT | Apr 20, 10:45 UTC | Apr 21, 04:35 UTC | 17h 50m |
| 2026-04-20 | OMA317 | MCT → DAC | Apr 20, 07:55 UTC | Apr 20, 08:55 UTC | 1h 0m |
| 2026-04-18 | OMA211 | MCT → TRV | Apr 18, 01:25 UTC | Apr 18, 01:45 UTC | 20m |
| 2026-04-17 | OMA266 | LKO → MCT | Apr 17, 03:55 UTC | Apr 17, 05:00 UTC | 1h 6m |
| 2026-04-17 | OMA265 | MCT → LKO | Apr 17, 01:35 UTC | Apr 17, 02:25 UTC | 50m |
| 2026-04-16 | OMA266 | LKO → MCT | Apr 16, 03:24 UTC | Apr 16, 04:29 UTC | 1h 5m |
| 2026-04-16 | OMA265 | MCT → LKO | Apr 16, 01:25 UTC | Apr 16, 02:09 UTC | 45m |
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 .