sensors Mode-S transponder
70C0CC
ICAO 24-bit transponder address · allocated to Oman
Currently assigned to A4O-BT · BOEING 737-900
- Hex
- 70C0CC
- Octal
- 34140314
- Decimal
- 7,389,388
- Country
- OM
- Tail
- A4O-BT
- Type
- B739
- Flights observed
- 165
- Distinct callsigns
- 20
- Country
- OM
- Last broadcast
- Jul 26, 10:10 UTC
Current position
Country allocation
The ICAO 24-bit address 70C0CC 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 |
|---|---|---|---|
| OMA203 | Oman Air | 30 | 2026-07-26 |
| OMA676 | - | 17 | 2026-07-14 |
| OMA674 | - | 15 | 2026-07-20 |
| OMA204 | Oman Air | 13 | 2026-07-26 |
| OMA672 | Oman Air | 9 | 2026-07-22 |
| OMA317 | - | 7 | 2026-06-22 |
| OMA265 | - | 7 | 2026-06-19 |
| OMA201 | - | 7 | 2026-07-15 |
| OMA405 | Oman Air | 6 | 2026-06-01 |
| OMA266 | - | 6 | 2026-06-20 |
| OMA231 | Oman Air | 4 | 2026-05-28 |
| OMA202 | - | 4 | 2026-07-13 |
| OMA690 | - | 3 | 2026-07-21 |
| OMA662 | Oman Air | 3 | 2026-06-26 |
| OMA406 | Oman Air | 3 | 2026-05-08 |
| OMA168 | Oman Air | 3 | 2026-07-24 |
| OMA167 | Oman Air | 3 | 2026-07-24 |
| OMA675 | Oman Air | 2 | 2026-07-22 |
| OMA661 | Oman Air | 2 | 2026-06-26 |
| OMA318 | - | 2 | 2026-06-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | OMA204 | BOM → MCT | Jul 26, 09:45 UTC | Jul 26, 10:10 UTC | 25m |
| 2026-07-26 | OMA203 | MCT → BOM | Jul 26, 00:45 UTC | Jul 26, 08:05 UTC | 7h 21m |
| 2026-07-25 | OMA252 | MAA → MCT | Jul 25, 03:10 UTC | Jul 25, 19:20 UTC | 16h 10m |
| 2026-07-24 | OMA251 | MCT → MAA | Jul 24, 23:50 UTC | Jul 25, 01:25 UTC | 1h 35m |
| 2026-07-24 | OMA168 | TZX → MCT | Jul 24, 14:25 UTC | Jul 24, 18:40 UTC | 4h 15m |
| 2026-07-24 | OMA167 | MCT → TZX | Jul 24, 12:45 UTC | Jul 24, 13:00 UTC | 15m |
| 2026-07-24 | OMA167 | MCT → TZX | Jul 24, 04:35 UTC | Jul 24, 10:35 UTC | 6h 0m |
| 2026-07-24 | OMA281 | MCT → BLR | Jul 24, 01:50 UTC | Jul 24, 03:25 UTC | 1h 35m |
| 2026-07-23 | OMA694 | - | Jul 23, 16:35 UTC | Jul 23, 17:35 UTC | 1h 0m |
| 2026-07-23 | OMA693 | - | Jul 23, 14:40 UTC | Jul 23, 14:55 UTC | 15m |
| 2026-07-23 | OMA204 | BOM → MCT | Jul 23, 10:10 UTC | Jul 23, 10:40 UTC | 30m |
| 2026-07-23 | OMA203 | MCT → BOM | Jul 23, 07:40 UTC | Jul 23, 08:35 UTC | 55m |
| 2026-07-23 | OMA408 | CAI → MCT | Jul 23, 00:55 UTC | Jul 23, 01:15 UTC | 20m |
| 2026-07-22 | OMA407 | MCT → CAI | Jul 22, 20:00 UTC | Jul 22, 21:05 UTC | 1h 5m |
| 2026-07-22 | OMA675 | MCT → JED | Jul 22, 11:25 UTC | Jul 22, 11:40 UTC | 15m |
| 2026-07-22 | OMA672 | JED → MCT | Jul 22, 04:15 UTC | Jul 22, 05:25 UTC | 1h 10m |
| 2026-07-21 | OMA690 | - | Jul 21, 12:45 UTC | Jul 21, 13:40 UTC | 55m |
| 2026-07-20 | OMA674 | - | Jul 20, 09:55 UTC | Jul 21, 01:20 UTC | 15h 25m |
| 2026-07-20 | OMA203 | MCT → BOM | Jul 20, 06:45 UTC | Jul 20, 08:05 UTC | 1h 20m |
| 2026-07-19 | OMA203 | MCT → BOM | Jul 19, 09:20 UTC | Jul 20, 08:05 UTC | 22h 45m |
| 2026-07-18 | OMA203 | MCT → BOM | Jul 18, 23:35 UTC | Jul 19, 07:55 UTC | 8h 20m |
| 2026-07-18 | OMA203 | MCT → BOM | Jul 18, 09:30 UTC | Jul 19, 07:55 UTC | 22h 25m |
| 2026-07-17 | OMA203 | - | Jul 17, 14:00 UTC | Jul 18, 08:05 UTC | 18h 6m |
| 2026-07-17 | OMA203 | - | Jul 17, 12:45 UTC | Jul 18, 08:05 UTC | 19h 21m |
| 2026-07-17 | OMA672 | - | Jul 17, 04:44 UTC | Jul 17, 10:50 UTC | 6h 5m |
| 2026-07-16 | OMA672 | - | Jul 16, 09:20 UTC | Jul 17, 05:25 UTC | 20h 5m |
| 2026-07-16 | OMA203 | - | Jul 16, 06:50 UTC | Jul 16, 08:05 UTC | 1h 15m |
| 2026-07-15 | OMA674 | - | Jul 15, 18:50 UTC | Jul 16, 01:10 UTC | 6h 20m |
| 2026-07-15 | OMA674 | - | Jul 15, 05:10 UTC | Jul 16, 01:10 UTC | 20h 0m |
| 2026-07-15 | OMA201 | - | Jul 15, 02:50 UTC | Jul 15, 03:40 UTC | 50m |
| 2026-07-14 | OMA676 | - | Jul 14, 11:35 UTC | Jul 14, 17:50 UTC | 6h 15m |
| 2026-07-13 | OMA202 | - | Jul 13, 05:15 UTC | Jul 13, 05:31 UTC | 15m |
| 2026-07-13 | OMA201 | - | Jul 13, 02:55 UTC | Jul 13, 03:45 UTC | 50m |
| 2026-07-12 | OMA664 | DOH → MCT | Jul 12, 13:20 UTC | Jul 12, 14:10 UTC | 50m |
| 2026-07-12 | OMA663 | - | Jul 12, 11:05 UTC | Jul 12, 11:55 UTC | 50m |
| 2026-07-11 | OMA202 | - | Jul 11, 04:55 UTC | Jul 11, 15:00 UTC | 10h 5m |
| 2026-07-10 | OMA201 | - | Jul 10, 09:55 UTC | Jul 11, 03:30 UTC | 17h 35m |
| 2026-07-10 | OMA674 | - | Jul 10, 01:00 UTC | Jul 10, 01:55 UTC | 55m |
| 2026-07-09 | OMA676 | - | Jul 9, 11:20 UTC | Jul 9, 17:20 UTC | 6h 0m |
| 2026-07-09 | OMA202 | - | Jul 9, 05:00 UTC | Jul 9, 05:25 UTC | 25m |
| 2026-07-08 | OMA201 | - | Jul 8, 11:40 UTC | Jul 9, 03:30 UTC | 15h 50m |
| 2026-07-07 | OMA676 | - | Jul 7, 16:40 UTC | Jul 8, 11:50 UTC | 19h 10m |
| 2026-07-06 | OMA674 | - | Jul 6, 23:30 UTC | Jul 7, 00:25 UTC | 55m |
| 2026-07-06 | OMA204 | - | Jul 6, 13:35 UTC | Jul 6, 18:35 UTC | 5h 0m |
| 2026-07-06 | OMA203 | - | Jul 6, 11:30 UTC | Jul 6, 11:55 UTC | 25m |
| 2026-07-06 | OMA203 | - | Jul 6, 07:20 UTC | Jul 6, 09:15 UTC | 1h 55m |
| 2026-07-05 | OMA674 | - | Jul 5, 18:55 UTC | Jul 6, 00:55 UTC | 6h 0m |
| 2026-07-05 | OMA624 | - | Jul 5, 16:10 UTC | Jul 5, 16:30 UTC | 20m |
| 2026-07-05 | OMA623 | - | Jul 5, 14:10 UTC | Jul 5, 14:35 UTC | 25m |
| 2026-07-05 | OMA204 | - | Jul 5, 10:25 UTC | Jul 5, 11:25 UTC | 1h 0m |
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-BT page for operator, model, and routing details .