sensors Mode-S transponder
70C0E0
ICAO 24-bit transponder address · allocated to Oman
Currently assigned to A4O-BAC · BOEING 737-800
- Hex
- 70C0E0
- Octal
- 34140340
- Decimal
- 7,389,408
- Country
- OM
- Tail
- A4O-BAC
- Type
- B738
- Flights observed
- 66
- Distinct callsigns
- 20
- Country
- OM
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 70C0E0 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 |
|---|---|---|---|
| OMA245 | Oman Air | 11 | 2026-05-13 |
| OMA246 | Oman Air | 8 | 2026-05-14 |
| OMA241 | Oman Air | 7 | 2026-05-10 |
| OMA242 | Oman Air | 5 | 2026-05-11 |
| OMA405 | Oman Air | 3 | 2026-05-10 |
| OMA612 | Oman Air | 2 | 2026-05-01 |
| OMA611 | Oman Air | 2 | 2026-05-01 |
| OMA251 | Oman Air | 2 | 2026-05-29 |
| OMA202 | Oman Air | 2 | 2026-05-20 |
| OMA201 | Oman Air | 2 | 2026-05-20 |
| OMA931 | Oman Air | 1 | 2026-04-20 |
| OMA690 | Oman Air | 1 | 2026-05-16 |
| OMA685 | Oman Air | 1 | 2026-05-04 |
| OMA684 | Oman Air | 1 | 2026-04-29 |
| OMA676 | Oman Air | 1 | 2026-04-20 |
| OMA664 | Oman Air | 1 | 2026-05-02 |
| OMA663 | Oman Air | 1 | 2026-05-02 |
| OMA662 | Oman Air | 1 | 2026-04-25 |
| OMA661 | Oman Air | 1 | 2026-04-25 |
| OMA655 | Oman Air | 1 | 2026-05-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | OMA252 | MAA → MCT | May 30, 02:50 UTC | May 30, 03:15 UTC | 25m |
| 2026-05-29 | OMA251 | MCT → MAA | May 29, 04:05 UTC | May 30, 01:05 UTC | 21h 0m |
| 2026-05-29 | OMA251 | MCT → MAA | May 29, 03:35 UTC | May 30, 01:05 UTC | 21h 30m |
| 2026-05-28 | OMA204 | BOM → MCT | May 28, 09:25 UTC | May 29, 02:05 UTC | 16h 40m |
| 2026-05-27 | OMA203 | MCT → BOM | May 27, 22:35 UTC | May 28, 08:10 UTC | 9h 35m |
| 2026-05-21 | OMA231 | MCT → HYD | May 21, 07:40 UTC | May 21, 12:15 UTC | 4h 35m |
| 2026-05-20 | OMA202 | BOM → MCT | May 20, 05:10 UTC | May 20, 05:25 UTC | 15m |
| 2026-05-20 | OMA201 | MCT → BOM | May 20, 02:35 UTC | May 20, 03:40 UTC | 1h 5m |
| 2026-05-16 | OMA690 | JED → MCT | May 16, 12:35 UTC | May 16, 13:01 UTC | 25m |
| 2026-05-14 | OMA246 | DEL → MCT | May 14, 11:05 UTC | May 15, 00:20 UTC | 13h 15m |
| 2026-05-13 | OMA245 | MCT → DEL | May 13, 14:05 UTC | May 14, 09:15 UTC | 19h 10m |
| 2026-05-13 | OMA245 | MCT → DEL | May 13, 13:35 UTC | May 14, 09:15 UTC | 19h 40m |
| 2026-05-12 | OMA284 | BLR → MCT | May 12, 09:40 UTC | May 12, 10:10 UTC | 30m |
| 2026-05-12 | OMA283 | MCT → BLR | May 12, 07:45 UTC | May 12, 08:15 UTC | 30m |
| 2026-05-11 | OMA242 | DEL → MCT | May 11, 03:40 UTC | May 11, 05:30 UTC | 1h 50m |
| 2026-05-10 | OMA241 | MCT → DEL | May 10, 18:45 UTC | May 11, 02:10 UTC | 7h 25m |
| 2026-05-10 | OMA405 | MCT → CAI | May 10, 12:05 UTC | May 10, 14:45 UTC | 2h 40m |
| 2026-05-09 | OMA242 | DEL → MCT | May 9, 03:45 UTC | May 9, 04:10 UTC | 25m |
| 2026-05-09 | OMA241 | MCT → DEL | May 9, 01:30 UTC | May 9, 02:30 UTC | 1h 0m |
| 2026-05-08 | OMA655 | MCT → BAH | May 8, 13:05 UTC | May 8, 13:15 UTC | 10m |
| 2026-05-07 | OMA265 | MCT → LKO | May 7, 10:40 UTC | May 8, 01:59 UTC | 15h 20m |
| 2026-05-07 | OMA245 | MCT → DEL | May 7, 08:30 UTC | May 7, 09:15 UTC | 45m |
| 2026-05-06 | OMA282 | BLR → MCT | May 6, 04:40 UTC | May 6, 05:00 UTC | 20m |
| 2026-05-05 | OMA246 | DEL → MCT | May 5, 11:05 UTC | May 6, 03:10 UTC | 16h 5m |
| 2026-05-05 | OMA245 | MCT → DEL | May 5, 08:35 UTC | May 5, 09:25 UTC | 50m |
| 2026-05-04 | OMA685 | MCT → RUH | May 4, 23:05 UTC | May 4, 23:15 UTC | 10m |
| 2026-05-04 | OMA405 | MCT → CAI | May 4, 11:10 UTC | May 4, 14:45 UTC | 3h 35m |
| 2026-05-03 | OMA246 | DEL → MCT | May 3, 10:35 UTC | May 3, 20:00 UTC | 9h 25m |
| 2026-05-03 | OMA245 | MCT → DEL | May 3, 08:25 UTC | May 3, 09:05 UTC | 40m |
| 2026-05-02 | OMA664 | DOH → MCT | May 2, 13:20 UTC | May 2, 14:00 UTC | 40m |
| 2026-05-02 | OMA663 | MCT → DOH | May 2, 03:30 UTC | May 2, 11:50 UTC | 8h 20m |
| 2026-05-02 | OMA241 | MCT → DEL | May 2, 01:15 UTC | May 2, 02:00 UTC | 45m |
| 2026-05-01 | OMA612 | DXB → MCT | May 1, 18:35 UTC | May 1, 19:00 UTC | 25m |
| 2026-05-01 | OMA611 | MCT → DXB | May 1, 16:35 UTC | May 1, 17:00 UTC | 25m |
| 2026-05-01 | OMA610 | DXB → MCT | May 1, 13:25 UTC | May 1, 13:45 UTC | 20m |
| 2026-05-01 | OMA609 | MCT → DXB | May 1, 10:45 UTC | May 1, 11:10 UTC | 25m |
| 2026-05-01 | OMA242 | DEL → MCT | May 1, 03:35 UTC | May 1, 04:10 UTC | 35m |
| 2026-05-01 | OMA241 | MCT → DEL | May 1, 01:30 UTC | May 1, 02:15 UTC | 45m |
| 2026-04-30 | OMA246 | DEL → MCT | Apr 30, 10:50 UTC | Apr 30, 19:55 UTC | 9h 5m |
| 2026-04-30 | OMA245 | MCT → DEL | Apr 30, 08:25 UTC | Apr 30, 09:00 UTC | 35m |
| 2026-04-29 | OMA684 | RUH → MCT | Apr 29, 10:35 UTC | Apr 29, 15:00 UTC | 4h 25m |
| 2026-04-28 | OMA242 | DEL → MCT | Apr 28, 04:10 UTC | Apr 28, 04:40 UTC | 30m |
| 2026-04-27 | OMA241 | MCT → DEL | Apr 27, 10:45 UTC | Apr 28, 02:15 UTC | 15h 30m |
| 2026-04-27 | OMA245 | MCT → DEL | Apr 27, 08:30 UTC | Apr 27, 09:20 UTC | 50m |
| 2026-04-26 | OMA202 | BOM → MCT | Apr 26, 05:05 UTC | Apr 26, 05:25 UTC | 20m |
| 2026-04-26 | OMA201 | MCT → BOM | Apr 26, 03:05 UTC | Apr 26, 03:40 UTC | 35m |
| 2026-04-25 | OMA662 | DOH → MCT | Apr 25, 18:50 UTC | Apr 25, 19:40 UTC | 50m |
| 2026-04-25 | OMA661 | MCT → DOH | Apr 25, 16:30 UTC | Apr 25, 17:25 UTC | 55m |
| 2026-04-25 | OMA246 | DEL → MCT | Apr 25, 10:50 UTC | Apr 25, 11:25 UTC | 35m |
| 2026-04-25 | OMA245 | MCT → DEL | Apr 25, 08:45 UTC | Apr 25, 09:20 UTC | 35m |
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-BAC page for operator, model, and routing details .