sensors Mode-S transponder
70C101
ICAO 24-bit transponder address · allocated to Oman
Currently assigned to A4O-MG · BOEING 737 MAX 8
- Hex
- 70C101
- Octal
- 34140401
- Decimal
- 7,389,441
- Country
- OM
- Tail
- A4O-MG
- Type
- B38M
- Flights observed
- 93
- Distinct callsigns
- 20
- Country
- OM
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 70C101 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 |
|---|---|---|---|
| OMA831 | Oman Air | 7 | 2026-05-04 |
| OMA682 | Oman Air | 6 | 2026-05-05 |
| OMA832 | Oman Air | 5 | 2026-04-30 |
| OMA223 | Oman Air | 5 | 2026-05-25 |
| OMA824 | Oman Air | 4 | 2026-05-08 |
| OMA686 | Oman Air | 4 | 2026-05-18 |
| OMA148 | Oman Air | 4 | 2026-04-16 |
| OMA695 | Oman Air | 3 | 2026-04-27 |
| OMA251 | Oman Air | 3 | 2026-05-25 |
| OMA224 | Oman Air | 3 | 2026-05-25 |
| OMA123 | Oman Air | 3 | 2026-05-29 |
| OMA823 | Oman Air | 2 | 2026-05-08 |
| OMA696 | Oman Air | 2 | 2026-04-27 |
| OMA685 | Oman Air | 2 | 2026-04-16 |
| OMA684 | Oman Air | 2 | 2026-05-16 |
| OMA681 | Oman Air | 2 | 2026-05-18 |
| OMA284 | Oman Air | 2 | 2026-05-28 |
| OMA283 | Oman Air | 2 | 2026-05-28 |
| OMA281 | Oman Air | 2 | 2026-05-28 |
| OMA252 | Oman Air | 2 | 2026-05-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | OMA124 | MUC → MCT | May 29, 20:20 UTC | May 30, 01:45 UTC | 5h 25m |
| 2026-05-29 | OMA123 | MCT → MUC | May 29, 04:20 UTC | May 29, 18:40 UTC | 14h 20m |
| 2026-05-28 | OMA281 | MCT → BLR | May 28, 11:05 UTC | May 29, 03:00 UTC | 15h 55m |
| 2026-05-28 | OMA284 | BLR → MCT | May 28, 10:00 UTC | May 28, 10:15 UTC | 15m |
| 2026-05-28 | OMA283 | MCT → BLR | May 28, 06:50 UTC | May 28, 08:20 UTC | 1h 30m |
| 2026-05-26 | OMA166 | IST → MCT | May 26, 16:45 UTC | May 26, 18:45 UTC | 2h 0m |
| 2026-05-26 | OMA165 | MCT → IST | May 26, 14:14 UTC | May 26, 14:24 UTC | 10m |
| 2026-05-26 | OMA252 | MAA → MCT | May 26, 03:05 UTC | May 26, 04:39 UTC | 1h 35m |
| 2026-05-25 | OMA251 | MCT → MAA | May 25, 15:55 UTC | May 26, 01:20 UTC | 9h 24m |
| 2026-05-25 | OMA224 | COK → MCT | May 25, 09:05 UTC | May 25, 09:15 UTC | 10m |
| 2026-05-25 | OMA223 | MCT → COK | May 25, 07:45 UTC | May 25, 07:55 UTC | 10m |
| 2026-05-24 | OMA226 | COK → MCT | May 24, 03:15 UTC | May 24, 03:40 UTC | 25m |
| 2026-05-23 | OMA225 | MCT → COK | May 23, 10:30 UTC | May 24, 01:55 UTC | 15h 25m |
| 2026-05-22 | OMA154 | ZRH → MCT | May 22, 20:45 UTC | May 23, 09:00 UTC | 12h 15m |
| 2026-05-22 | OMA153 | MCT → ZRH | May 22, 15:45 UTC | May 22, 19:10 UTC | 3h 25m |
| 2026-05-22 | OMA282 | BLR → MCT | May 22, 04:30 UTC | May 22, 13:50 UTC | 9h 20m |
| 2026-05-21 | OMA281 | MCT → BLR | May 21, 13:20 UTC | May 22, 03:20 UTC | 14h 0m |
| 2026-05-21 | OMA818 | BKK → MCT | May 21, 02:05 UTC | May 21, 06:35 UTC | 4h 30m |
| 2026-05-20 | OMA817 | MCT → BKK | May 20, 03:15 UTC | May 20, 23:10 UTC | 19h 56m |
| 2026-05-19 | OMA251 | MCT → MAA | May 19, 15:15 UTC | May 20, 01:35 UTC | 10h 20m |
| 2026-05-19 | OMA224 | COK → MCT | May 19, 08:00 UTC | May 19, 08:10 UTC | 10m |
| 2026-05-18 | OMA681 | MCT → RUH | May 18, 15:50 UTC | May 19, 06:45 UTC | 14h 54m |
| 2026-05-18 | OMA686 | RUH → MCT | May 18, 01:40 UTC | May 18, 16:15 UTC | 14h 35m |
| 2026-05-16 | OMA684 | RUH → MCT | May 16, 13:41 UTC | May 16, 21:50 UTC | 8h 10m |
| 2026-05-15 | OMA684 | RUH → MCT | May 15, 14:25 UTC | May 16, 14:05 UTC | 23h 40m |
| 2026-05-15 | OMA252 | MAA → MCT | May 15, 02:50 UTC | May 15, 14:45 UTC | 11h 55m |
| 2026-05-14 | OMA284 | BLR → MCT | May 14, 10:05 UTC | May 15, 01:25 UTC | 15h 20m |
| 2026-05-14 | OMA283 | MCT → BLR | May 14, 07:45 UTC | May 14, 08:40 UTC | 55m |
| 2026-05-13 | OMA686 | RUH → MCT | May 13, 01:20 UTC | May 13, 01:55 UTC | 35m |
| 2026-05-12 | OMA223 | MCT → COK | May 12, 06:40 UTC | May 12, 06:55 UTC | 15m |
| 2026-05-09 | OMA676 | JED → MCT | May 9, 16:30 UTC | May 9, 16:50 UTC | 20m |
| 2026-05-08 | OMA824 | KUL → MCT | May 8, 18:20 UTC | May 9, 16:50 UTC | 22h 30m |
| 2026-05-08 | OMA824 | KUL → MCT | May 8, 18:05 UTC | May 8, 19:40 UTC | 1h 35m |
| 2026-05-08 | OMA824 | KUL → MCT | May 8, 14:55 UTC | May 8, 15:10 UTC | 15m |
| 2026-05-08 | OMA823 | MCT → KUL | May 8, 11:09 UTC | May 8, 11:30 UTC | 20m |
| 2026-05-07 | OMA654 | BAH → MCT | May 7, 19:15 UTC | May 8, 07:50 UTC | 12h 35m |
| 2026-05-07 | OMA653 | MCT → BAH | May 7, 17:35 UTC | May 7, 17:55 UTC | 20m |
| 2026-05-06 | OMA833 | MCT → HKT | May 6, 08:01 UTC | May 6, 23:10 UTC | 15h 9m |
| 2026-05-05 | OMA682 | RUH → MCT | May 5, 16:20 UTC | May 6, 10:35 UTC | 18h 15m |
| 2026-05-05 | OMA682 | RUH → MCT | May 5, 00:20 UTC | May 5, 19:30 UTC | 19h 10m |
| 2026-05-04 | OMA251 | MCT → MAA | May 4, 23:55 UTC | May 5, 19:30 UTC | 19h 35m |
| 2026-05-04 | OMA831 | MCT → HKT | May 4, 08:20 UTC | May 5, 03:35 UTC | 19h 16m |
| 2026-05-04 | OMA831 | MCT → HKT | May 4, 08:10 UTC | May 5, 03:35 UTC | 19h 26m |
| 2026-05-03 | OMA831 | MCT → HKT | May 3, 18:20 UTC | May 4, 18:15 UTC | 23h 55m |
| 2026-05-03 | OMA831 | MCT → HKT | May 3, 16:55 UTC | May 4, 10:00 UTC | 17h 5m |
| 2026-05-03 | OMA824 | KUL → MCT | May 3, 13:45 UTC | May 4, 10:00 UTC | 20h 15m |
| 2026-05-03 | OMA823 | MCT → KUL | May 3, 06:40 UTC | May 3, 11:25 UTC | 4h 45m |
| 2026-05-02 | OMA686 | RUH → MCT | May 2, 08:45 UTC | May 3, 02:50 UTC | 18h 5m |
| 2026-05-02 | OMA831 | MCT → HKT | May 2, 07:25 UTC | May 3, 02:50 UTC | 19h 25m |
| 2026-05-01 | OMA154 | ZRH → MCT | May 1, 18:50 UTC | May 2, 00:55 UTC | 6h 5m |
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-MG page for operator, model, and routing details .