sensors Mode-S transponder
70C107
ICAO 24-bit transponder address · allocated to Oman
Currently assigned to A4O-ML · BOEING 737 MAX 8
- Hex
- 70C107
- Octal
- 34140407
- Decimal
- 7,389,447
- Country
- OM
- Tail
- A4O-ML
- Type
- B38M
- Flights observed
- 86
- Distinct callsigns
- 20
- Country
- OM
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 70C107 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 |
|---|---|---|---|
| OMA226 | Oman Air | 5 | 2026-05-07 |
| OMA225 | Oman Air | 5 | 2026-05-07 |
| OMA684 | Oman Air | 4 | 2026-05-05 |
| OMA653 | Oman Air | 4 | 2026-04-25 |
| OMA833 | Oman Air | 3 | 2026-05-16 |
| OMA822 | Oman Air | 3 | 2026-05-18 |
| OMA821 | Oman Air | 3 | 2026-05-17 |
| OMA654 | Oman Air | 3 | 2026-04-25 |
| OMA283 | Oman Air | 3 | 2026-05-25 |
| OMA253 | Oman Air | 3 | 2026-05-11 |
| OMA251 | Oman Air | 3 | 2026-05-26 |
| OMA834 | Oman Air | 2 | 2026-05-24 |
| OMA824 | - | 2 | 2026-04-13 |
| OMA688 | Oman Air | 2 | 2026-05-02 |
| OMA686 | Oman Air | 2 | 2026-05-14 |
| OMA656 | Oman Air | 2 | 2026-05-03 |
| OMA655 | Oman Air | 2 | 2026-05-03 |
| OMA612 | Oman Air | 2 | 2026-04-22 |
| OMA611 | Oman Air | 2 | 2026-04-22 |
| OMA407 | Oman Air | 2 | 2026-05-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-27 | OMA252 | MAA → MCT | May 27, 02:44 UTC | May 27, 04:24 UTC | 1h 40m |
| 2026-05-26 | OMA251 | MCT → MAA | May 26, 09:49 UTC | May 27, 01:24 UTC | 15h 35m |
| 2026-05-25 | OMA283 | MCT → BLR | May 25, 23:04 UTC | May 26, 08:19 UTC | 9h 15m |
| 2026-05-25 | OMA407 | MCT → CAI | May 25, 01:55 UTC | May 25, 21:35 UTC | 19h 40m |
| 2026-05-24 | OMA407 | MCT → CAI | May 24, 23:00 UTC | May 25, 21:35 UTC | 22h 34m |
| 2026-05-24 | OMA834 | HKT → MCT | May 24, 06:00 UTC | May 25, 02:20 UTC | 20h 20m |
| 2026-05-23 | OMA834 | HKT → MCT | May 23, 20:15 UTC | May 24, 06:30 UTC | 10h 15m |
| 2026-05-23 | OMA204 | BOM → MCT | May 23, 09:50 UTC | May 24, 06:30 UTC | 20h 40m |
| 2026-05-23 | OMA203 | MCT → BOM | May 23, 06:35 UTC | May 23, 07:50 UTC | 1h 15m |
| 2026-05-21 | OMA816 | BKK → MCT | May 21, 12:25 UTC | May 22, 02:05 UTC | 13h 40m |
| 2026-05-21 | OMA815 | MCT → BKK | May 21, 05:25 UTC | May 21, 10:00 UTC | 4h 35m |
| 2026-05-19 | OMA166 | IST → MCT | May 19, 17:00 UTC | May 19, 17:10 UTC | 10m |
| 2026-05-19 | OMA165 | MCT → IST | May 19, 03:10 UTC | May 19, 15:00 UTC | 11h 50m |
| 2026-05-18 | OMA251 | MCT → MAA | May 18, 19:05 UTC | May 19, 01:20 UTC | 6h 15m |
| 2026-05-18 | OMA822 | KUL → MCT | May 18, 01:35 UTC | May 18, 05:15 UTC | 3h 40m |
| 2026-05-17 | OMA821 | MCT → KUL | May 17, 05:00 UTC | May 17, 23:45 UTC | 18h 45m |
| 2026-05-16 | OMA833 | MCT → HKT | May 16, 20:15 UTC | May 17, 19:10 UTC | 22h 55m |
| 2026-05-16 | OMA833 | MCT → HKT | May 16, 03:30 UTC | May 16, 21:40 UTC | 18h 10m |
| 2026-05-16 | OMA241 | MCT → DEL | May 16, 01:05 UTC | May 16, 01:50 UTC | 45m |
| 2026-05-14 | OMA223 | MCT → COK | May 14, 23:20 UTC | May 15, 07:45 UTC | 8h 25m |
| 2026-05-14 | OMA686 | RUH → MCT | May 14, 01:50 UTC | May 14, 21:35 UTC | 19h 45m |
| 2026-05-14 | OMA686 | RUH → MCT | May 14, 01:35 UTC | May 14, 21:35 UTC | 20h 0m |
| 2026-05-13 | OMA676 | JED → MCT | May 13, 16:45 UTC | May 14, 11:35 UTC | 18h 50m |
| 2026-05-12 | OMA254 | MAA → MCT | May 12, 08:25 UTC | May 12, 09:00 UTC | 35m |
| 2026-05-11 | OMA253 | MCT → MAA | May 11, 16:20 UTC | May 12, 06:45 UTC | 14h 26m |
| 2026-05-09 | OMA694 | DMM → MCT | May 9, 13:25 UTC | May 10, 05:00 UTC | 15h 35m |
| 2026-05-09 | OMA693 | MCT → DMM | May 9, 11:50 UTC | May 9, 12:05 UTC | 15m |
| 2026-05-09 | OMA252 | MAA → MCT | May 9, 03:15 UTC | May 9, 03:25 UTC | 10m |
| 2026-05-09 | OMA251 | MCT → MAA | May 9, 00:45 UTC | May 9, 01:15 UTC | 30m |
| 2026-05-07 | OMA226 | COK → MCT | May 7, 03:20 UTC | May 7, 03:40 UTC | 20m |
| 2026-05-07 | OMA225 | MCT → COK | May 7, 01:25 UTC | May 7, 01:55 UTC | 30m |
| 2026-05-06 | OMA224 | COK → MCT | May 6, 09:15 UTC | May 6, 09:25 UTC | 10m |
| 2026-05-06 | OMA223 | MCT → COK | May 6, 07:45 UTC | May 6, 08:01 UTC | 15m |
| 2026-05-05 | OMA684 | RUH → MCT | May 5, 11:00 UTC | May 5, 14:10 UTC | 3h 10m |
| 2026-05-05 | OMA226 | COK → MCT | May 5, 02:55 UTC | May 5, 03:05 UTC | 10m |
| 2026-05-05 | OMA225 | MCT → COK | May 5, 01:35 UTC | May 5, 01:45 UTC | 10m |
| 2026-05-04 | OMA664 | DOH → MCT | May 4, 13:20 UTC | May 4, 14:05 UTC | 45m |
| 2026-05-04 | OMA663 | MCT → DOH | May 4, 10:55 UTC | May 4, 11:50 UTC | 55m |
| 2026-05-04 | OMA822 | KUL → MCT | May 4, 05:25 UTC | May 4, 06:50 UTC | 1h 25m |
| 2026-05-04 | OMA822 | KUL → MCT | May 4, 01:50 UTC | May 4, 02:00 UTC | 10m |
| 2026-05-03 | OMA821 | MCT → KUL | May 3, 18:40 UTC | May 3, 23:39 UTC | 5h 0m |
| 2026-05-03 | OMA656 | BAH → MCT | May 3, 13:20 UTC | May 3, 14:15 UTC | 55m |
| 2026-05-03 | OMA655 | MCT → BAH | May 3, 11:10 UTC | May 3, 12:10 UTC | 1h 0m |
| 2026-05-02 | OMA688 | RUH → MCT | May 2, 12:40 UTC | May 2, 17:00 UTC | 4h 20m |
| 2026-05-01 | OMA696 | DMM → MCT | May 1, 18:55 UTC | May 1, 19:50 UTC | 55m |
| 2026-05-01 | OMA695 | MCT → DMM | May 1, 16:25 UTC | May 1, 17:40 UTC | 1h 15m |
| 2026-05-01 | OMA656 | BAH → MCT | May 1, 13:35 UTC | May 1, 14:20 UTC | 45m |
| 2026-04-30 | OMA655 | MCT → BAH | Apr 30, 20:30 UTC | May 1, 12:20 UTC | 15h 50m |
| 2026-04-30 | OMA684 | RUH → MCT | Apr 30, 11:05 UTC | Apr 30, 14:55 UTC | 3h 50m |
| 2026-04-30 | OMA226 | COK → MCT | Apr 30, 03:00 UTC | Apr 30, 03:10 UTC | 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-ML page for operator, model, and routing details .