sensors Mode-S transponder
70C104
ICAO 24-bit transponder address · allocated to Oman
Currently assigned to A4O-MJ · BOEING 737 MAX 8
- Hex
- 70C104
- Octal
- 34140404
- Decimal
- 7,389,444
- Country
- OM
- Tail
- A4O-MJ
- Type
- B38M
- Flights observed
- 88
- Distinct callsigns
- 20
- Country
- OM
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 70C104 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 |
|---|---|---|---|
| OMA223 | Oman Air | 6 | 2026-05-22 |
| OMA685 | Oman Air | 5 | 2026-04-22 |
| OMA123 | Oman Air | 5 | 2026-05-23 |
| OMA694 | Oman Air | 4 | 2026-05-12 |
| OMA225 | Oman Air | 4 | 2026-05-16 |
| OMA147 | Oman Air | 4 | 2026-05-20 |
| OMA824 | Oman Air | 3 | 2026-04-29 |
| OMA823 | Oman Air | 3 | 2026-04-29 |
| OMA693 | Oman Air | 3 | 2026-05-28 |
| OMA686 | Oman Air | 3 | 2026-05-08 |
| OMA684 | Oman Air | 3 | 2026-05-02 |
| OMA413 | Oman Air | 3 | 2026-04-26 |
| OMA284 | Oman Air | 3 | 2026-05-21 |
| OMA148 | Oman Air | 3 | 2026-05-20 |
| OMA124 | Oman Air | 3 | 2026-05-23 |
| OMA821 | Oman Air | 2 | 2026-05-02 |
| OMA682 | Oman Air | 2 | 2026-05-24 |
| OMA414 | Oman Air | 2 | 2026-04-27 |
| OMA408 | Oman Air | 2 | 2026-05-09 |
| OMA407 | Oman Air | 2 | 2026-05-09 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-28 | OMA662 | DOH → MCT | May 28, 18:50 UTC | May 28, 19:30 UTC | 40m |
| 2026-05-28 | OMA693 | MCT → DMM | May 28, 11:35 UTC | May 28, 11:55 UTC | 20m |
| 2026-05-26 | OMA663 | MCT → DOH | May 26, 11:05 UTC | May 26, 12:00 UTC | 55m |
| 2026-05-24 | OMA682 | RUH → MCT | May 24, 16:15 UTC | May 24, 19:40 UTC | 3h 25m |
| 2026-05-23 | OMA124 | MUC → MCT | May 23, 20:15 UTC | May 24, 07:50 UTC | 11h 35m |
| 2026-05-23 | OMA123 | MCT → MUC | May 23, 01:55 UTC | May 23, 18:30 UTC | 16h 35m |
| 2026-05-22 | OMA123 | MCT → MUC | May 22, 19:05 UTC | May 23, 18:30 UTC | 23h 25m |
| 2026-05-22 | OMA224 | COK → MCT | May 22, 09:05 UTC | May 23, 02:10 UTC | 17h 5m |
| 2026-05-22 | OMA223 | MCT → COK | May 22, 07:30 UTC | May 22, 07:55 UTC | 25m |
| 2026-05-21 | OMA223 | MCT → COK | May 21, 11:05 UTC | May 22, 07:55 UTC | 20h 50m |
| 2026-05-21 | OMA284 | BLR → MCT | May 21, 09:50 UTC | May 22, 07:55 UTC | 22h 5m |
| 2026-05-20 | OMA148 | FCO → MCT | May 20, 19:35 UTC | May 21, 08:35 UTC | 13h 0m |
| 2026-05-20 | OMA147 | MCT → FCO | May 20, 04:50 UTC | May 20, 17:55 UTC | 13h 5m |
| 2026-05-19 | OMA281 | MCT → BLR | May 19, 18:00 UTC | May 20, 03:05 UTC | 9h 5m |
| 2026-05-19 | OMA284 | BLR → MCT | May 19, 09:50 UTC | May 19, 11:15 UTC | 1h 25m |
| 2026-05-19 | OMA283 | MCT → BLR | May 19, 01:35 UTC | May 19, 08:10 UTC | 6h 35m |
| 2026-05-18 | OMA124 | MUC → MCT | May 18, 20:20 UTC | May 18, 23:35 UTC | 3h 15m |
| 2026-05-18 | OMA123 | MCT → MUC | May 18, 12:35 UTC | May 18, 18:55 UTC | 6h 19m |
| 2026-05-17 | OMA226 | COK → MCT | May 17, 03:10 UTC | May 17, 03:30 UTC | 20m |
| 2026-05-16 | OMA225 | MCT → COK | May 16, 16:50 UTC | May 17, 02:00 UTC | 9h 10m |
| 2026-05-16 | OMA405 | MCT → CAI | May 16, 14:35 UTC | May 16, 14:55 UTC | 20m |
| 2026-05-12 | OMA694 | DMM → MCT | May 12, 13:35 UTC | May 13, 01:40 UTC | 12h 5m |
| 2026-05-11 | OMA696 | DMM → MCT | May 11, 19:00 UTC | May 11, 19:50 UTC | 50m |
| 2026-05-11 | OMA282 | BLR → MCT | May 11, 04:30 UTC | May 11, 05:00 UTC | 30m |
| 2026-05-10 | OMA254 | MAA → MCT | May 10, 10:15 UTC | May 11, 03:10 UTC | 16h 55m |
| 2026-05-09 | OMA408 | CAI → MCT | May 9, 23:55 UTC | May 10, 08:30 UTC | 8h 35m |
| 2026-05-09 | OMA407 | MCT → CAI | May 9, 19:10 UTC | May 9, 21:30 UTC | 2h 20m |
| 2026-05-08 | OMA686 | RUH → MCT | May 8, 16:10 UTC | May 9, 02:30 UTC | 10h 20m |
| 2026-05-08 | OMA223 | MCT → COK | May 8, 07:24 UTC | May 8, 07:34 UTC | 10m |
| 2026-05-07 | OMA405 | MCT → CAI | May 7, 14:30 UTC | May 7, 14:45 UTC | 15m |
| 2026-05-06 | OMA252 | MAA → MCT | May 6, 03:15 UTC | May 6, 03:35 UTC | 20m |
| 2026-05-06 | OMA251 | MCT → MAA | May 6, 01:10 UTC | May 6, 01:30 UTC | 20m |
| 2026-05-04 | OMA833 | MCT → HKT | May 4, 21:40 UTC | May 4, 23:00 UTC | 1h 20m |
| 2026-05-03 | OMA154 | ZRH → MCT | May 3, 18:45 UTC | May 4, 01:05 UTC | 6h 20m |
| 2026-05-03 | OMA153 | MCT → ZRH | May 3, 02:00 UTC | May 3, 17:05 UTC | 15h 4m |
| 2026-05-02 | OMA821 | MCT → KUL | May 2, 23:30 UTC | May 2, 23:50 UTC | 20m |
| 2026-05-02 | OMA821 | MCT → KUL | May 2, 18:55 UTC | May 2, 20:05 UTC | 1h 10m |
| 2026-05-02 | OMA684 | RUH → MCT | May 2, 10:20 UTC | May 2, 14:40 UTC | 4h 20m |
| 2026-05-01 | OMA223 | MCT → COK | May 1, 07:35 UTC | May 1, 07:50 UTC | 15m |
| 2026-04-30 | OMA408 | CAI → MCT | Apr 30, 23:45 UTC | May 1, 02:40 UTC | 2h 55m |
| 2026-04-30 | OMA407 | MCT → CAI | Apr 30, 18:50 UTC | Apr 30, 21:55 UTC | 3h 5m |
| 2026-04-30 | OMA694 | DMM → MCT | Apr 30, 13:35 UTC | Apr 30, 14:35 UTC | 1h 0m |
| 2026-04-29 | OMA693 | MCT → DMM | Apr 29, 17:05 UTC | Apr 30, 11:55 UTC | 18h 50m |
| 2026-04-29 | OMA824 | KUL → MCT | Apr 29, 13:55 UTC | Apr 30, 11:55 UTC | 22h 0m |
| 2026-04-29 | OMA823 | MCT → KUL | Apr 29, 06:29 UTC | Apr 29, 11:20 UTC | 4h 51m |
| 2026-04-28 | OMA694 | DMM → MCT | Apr 28, 13:50 UTC | Apr 28, 14:45 UTC | 55m |
| 2026-04-28 | OMA252 | MAA → MCT | Apr 28, 02:45 UTC | Apr 28, 11:25 UTC | 8h 40m |
| 2026-04-27 | OMA251 | MCT → MAA | Apr 27, 23:55 UTC | Apr 28, 01:10 UTC | 1h 15m |
| 2026-04-27 | OMA414 | AMM → MCT | Apr 27, 16:15 UTC | Apr 27, 17:15 UTC | 1h 0m |
| 2026-04-26 | OMA413 | MCT → AMM | Apr 26, 21:45 UTC | Apr 27, 12:55 UTC | 15h 10m |
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-MJ page for operator, model, and routing details .