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
- 134
- Distinct callsigns
- 20
- Country
- OM
- Last broadcast
- 1d ago
Last known 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 | - | 21 | 2026-07-06 |
| OMA676 | - | 16 | 2026-07-09 |
| OMA674 | - | 12 | 2026-07-10 |
| OMA204 | - | 11 | 2026-07-06 |
| OMA317 | - | 7 | 2026-06-22 |
| OMA265 | - | 7 | 2026-06-19 |
| OMA672 | - | 6 | 2026-07-03 |
| OMA405 | Oman Air | 6 | 2026-06-01 |
| OMA266 | - | 6 | 2026-06-20 |
| OMA201 | - | 6 | 2026-07-13 |
| OMA231 | Oman Air | 4 | 2026-05-28 |
| OMA202 | - | 4 | 2026-07-13 |
| OMA662 | Oman Air | 3 | 2026-06-26 |
| OMA406 | Oman Air | 3 | 2026-05-08 |
| OMA690 | - | 2 | 2026-06-29 |
| OMA661 | Oman Air | 2 | 2026-06-26 |
| OMA318 | - | 2 | 2026-06-23 |
| OMA235 | Oman Air | 2 | 2026-05-27 |
| OMA168 | Oman Air | 2 | 2026-07-03 |
| OMA685 | - | 1 | 2026-06-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 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 |
| 2026-07-05 | OMA203 | - | Jul 5, 06:45 UTC | Jul 5, 08:00 UTC | 1h 15m |
| 2026-07-04 | OMA674 | - | Jul 4, 10:05 UTC | Jul 5, 01:05 UTC | 15h 0m |
| 2026-07-04 | OMA203 | - | Jul 4, 07:15 UTC | Jul 4, 08:10 UTC | 55m |
| 2026-07-03 | OMA168 | TZX → MCT | Jul 3, 16:25 UTC | Jul 3, 17:35 UTC | 1h 10m |
| 2026-07-03 | OMA168 | TZX → MCT | Jul 3, 13:50 UTC | Jul 3, 15:20 UTC | 1h 30m |
| 2026-07-03 | OMA167 | MCT → TZX | Jul 3, 08:25 UTC | Jul 3, 12:35 UTC | 4h 10m |
| 2026-07-03 | OMA672 | - | Jul 3, 00:10 UTC | Jul 3, 06:35 UTC | 6h 25m |
| 2026-06-30 | OMA674 | - | Jun 30, 18:35 UTC | Jul 1, 00:55 UTC | 6h 20m |
| 2026-06-29 | OMA690 | - | Jun 29, 17:05 UTC | Jun 30, 13:40 UTC | 20h 36m |
| 2026-06-29 | OMA676 | - | Jun 29, 16:39 UTC | Jun 30, 13:00 UTC | 20h 21m |
| 2026-06-29 | OMA676 | - | Jun 29, 11:35 UTC | Jun 30, 07:45 UTC | 20h 11m |
| 2026-06-27 | OMA204 | - | Jun 27, 09:29 UTC | Jun 27, 09:50 UTC | 20m |
| 2026-06-27 | OMA203 | - | Jun 27, 07:04 UTC | Jun 27, 07:55 UTC | 50m |
| 2026-06-26 | OMA662 | DOH → MCT | Jun 26, 18:44 UTC | Jun 26, 19:35 UTC | 50m |
| 2026-06-26 | OMA661 | MCT → DOH | Jun 26, 16:35 UTC | Jun 26, 17:29 UTC | 55m |
| 2026-06-26 | OMA204 | - | Jun 26, 09:30 UTC | Jun 26, 09:55 UTC | 25m |
| 2026-06-25 | OMA685 | - | Jun 25, 22:10 UTC | Jun 26, 07:55 UTC | 9h 45m |
| 2026-06-24 | OMA675 | MCT → JED | Jun 24, 11:50 UTC | Jun 24, 17:05 UTC | 5h 15m |
| 2026-06-23 | OMA318 | - | Jun 23, 10:10 UTC | Jun 24, 00:30 UTC | 14h 20m |
| 2026-06-22 | OMA317 | - | Jun 22, 16:40 UTC | Jun 23, 08:35 UTC | 15h 55m |
| 2026-06-20 | OMA676 | - | Jun 20, 16:34 UTC | Jun 21, 01:10 UTC | 8h 35m |
| 2026-06-20 | OMA676 | - | Jun 20, 05:19 UTC | Jun 21, 01:10 UTC | 19h 50m |
| 2026-06-20 | OMA266 | - | Jun 20, 04:24 UTC | Jun 21, 01:10 UTC | 20h 45m |
| 2026-06-19 | OMA265 | - | Jun 19, 16:29 UTC | Jun 20, 02:09 UTC | 9h 40m |
| 2026-06-18 | OMA318 | - | Jun 18, 10:40 UTC | Jun 18, 13:10 UTC | 2h 30m |
| 2026-06-17 | OMA317 | - | Jun 17, 13:30 UTC | Jun 18, 08:50 UTC | 19h 20m |
| 2026-06-17 | OMA317 | - | Jun 17, 11:05 UTC | Jun 18, 08:50 UTC | 21h 45m |
| 2026-06-17 | OMA317 | DAC → DAC | Jun 17, 10:55 UTC | Jun 18, 08:50 UTC | 21h 55m |
| 2026-06-16 | OMA317 | - | Jun 16, 23:20 UTC | Jun 17, 09:20 UTC | 10h 0m |
| 2026-06-16 | OMA317 | - | Jun 16, 13:04 UTC | Jun 17, 09:20 UTC | 20h 16m |
| 2026-06-16 | OMA317 | - | Jun 16, 12:50 UTC | Jun 17, 09:20 UTC | 20h 31m |
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 .