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
- 58
- Distinct callsigns
- 20
- Country
- OM
- Last broadcast
- 12m ago
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 |
|---|---|---|---|
| OMA676 | Oman Air | 10 | 2026-05-15 |
| OMA203 | Oman Air | 8 | 2026-05-29 |
| OMA674 | Oman Air | 5 | 2026-05-05 |
| OMA405 | Oman Air | 5 | 2026-05-19 |
| OMA265 | Oman Air | 4 | 2026-05-29 |
| OMA231 | Oman Air | 4 | 2026-05-28 |
| OMA204 | Oman Air | 4 | 2026-05-16 |
| OMA406 | Oman Air | 3 | 2026-05-08 |
| OMA672 | Oman Air | 2 | 2026-05-01 |
| OMA266 | Oman Air | 2 | 2026-05-30 |
| OMA235 | Oman Air | 2 | 2026-05-27 |
| OMA690 | Oman Air | 1 | 2026-04-18 |
| OMA662 | Oman Air | 1 | 2026-04-29 |
| OMA661 | Oman Air | 1 | 2026-04-28 |
| OMA612 | Oman Air | 1 | 2026-04-30 |
| OMA611 | Oman Air | 1 | 2026-04-30 |
| OMA2406 | - | 1 | 2026-05-23 |
| OMA212 | Oman Air | 1 | 2026-05-18 |
| OMA211 | Oman Air | 1 | 2026-05-18 |
| OMA201 | Oman Air | 1 | 2026-04-22 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | OMA266 | LKO → MCT | May 30, 03:20 UTC | May 30, 05:00 UTC | 1h 40m |
| 2026-05-29 | OMA265 | MCT → LKO | May 29, 09:30 UTC | May 30, 01:55 UTC | 16h 25m |
| 2026-05-29 | OMA203 | MCT → BOM | May 29, 06:40 UTC | May 29, 07:55 UTC | 1h 15m |
| 2026-05-28 | OMA203 | MCT → BOM | May 28, 11:20 UTC | May 29, 07:55 UTC | 20h 35m |
| 2026-05-28 | OMA231 | MCT → HYD | May 28, 07:35 UTC | May 29, 07:00 UTC | 23h 25m |
| 2026-05-27 | OMA231 | MCT → HYD | May 27, 18:35 UTC | May 28, 12:15 UTC | 17h 40m |
| 2026-05-27 | OMA231 | MCT → HYD | May 27, 16:20 UTC | May 28, 12:15 UTC | 19h 55m |
| 2026-05-27 | OMA235 | MCT → HYD | May 27, 00:04 UTC | May 27, 14:45 UTC | 14h 40m |
| 2026-05-26 | OMA235 | MCT → HYD | May 26, 09:29 UTC | May 27, 05:04 UTC | 19h 35m |
| 2026-05-26 | OMA203 | MCT → BOM | May 26, 06:29 UTC | May 26, 07:45 UTC | 1h 15m |
| 2026-05-24 | OMA266 | LKO → MCT | May 24, 04:45 UTC | May 24, 05:40 UTC | 55m |
| 2026-05-24 | OMA265 | MCT → LKO | May 24, 00:15 UTC | May 24, 02:05 UTC | 1h 50m |
| 2026-05-23 | OMA265 | MCT → LKO | May 23, 05:05 UTC | May 24, 02:05 UTC | 21h 1m |
| 2026-05-23 | OMA265 | MCT → LKO | May 23, 04:30 UTC | May 24, 02:05 UTC | 21h 36m |
| 2026-05-23 | OMA2406 | - | May 23, 02:25 UTC | May 24, 01:00 UTC | 22h 35m |
| 2026-05-19 | OMA405 | MCT → CAI | May 19, 12:15 UTC | May 19, 14:40 UTC | 2h 25m |
| 2026-05-18 | OMA212 | TRV → MCT | May 18, 03:25 UTC | May 18, 15:10 UTC | 11h 45m |
| 2026-05-18 | OMA211 | MCT → TRV | May 18, 00:10 UTC | May 18, 02:05 UTC | 1h 55m |
| 2026-05-16 | OMA204 | BOM → MCT | May 16, 09:21 UTC | May 16, 09:51 UTC | 30m |
| 2026-05-15 | OMA676 | JED → MCT | May 15, 16:55 UTC | May 16, 07:41 UTC | 14h 46m |
| 2026-05-14 | OMA231 | MCT → HYD | May 14, 07:15 UTC | May 14, 07:45 UTC | 30m |
| 2026-05-12 | OMA203 | MCT → BOM | May 12, 06:40 UTC | May 12, 23:20 UTC | 16h 40m |
| 2026-05-08 | OMA406 | CAI → MCT | May 8, 16:40 UTC | May 8, 19:15 UTC | 2h 35m |
| 2026-05-08 | OMA405 | MCT → CAI | May 8, 12:04 UTC | May 8, 15:10 UTC | 3h 5m |
| 2026-05-07 | OMA405 | MCT → CAI | May 7, 19:05 UTC | May 8, 15:10 UTC | 20h 5m |
| 2026-05-05 | OMA674 | JED → MCT | May 5, 23:10 UTC | May 6, 14:40 UTC | 15h 30m |
| 2026-05-04 | OMA204 | BOM → MCT | May 4, 10:05 UTC | May 4, 10:20 UTC | 15m |
| 2026-05-04 | OMA203 | MCT → BOM | May 4, 07:05 UTC | May 4, 07:50 UTC | 45m |
| 2026-05-03 | OMA674 | JED → MCT | May 3, 23:25 UTC | May 4, 00:25 UTC | 1h 0m |
| 2026-05-03 | OMA204 | BOM → MCT | May 3, 09:25 UTC | May 3, 09:40 UTC | 15m |
| 2026-05-03 | OMA203 | MCT → BOM | May 3, 07:05 UTC | May 3, 07:50 UTC | 45m |
| 2026-05-02 | OMA674 | JED → MCT | May 2, 23:40 UTC | May 3, 00:40 UTC | 1h 0m |
| 2026-05-02 | OMA204 | BOM → MCT | May 2, 09:25 UTC | May 2, 09:35 UTC | 10m |
| 2026-05-02 | OMA203 | MCT → BOM | May 2, 07:05 UTC | May 2, 07:45 UTC | 40m |
| 2026-05-01 | OMA676 | JED → MCT | May 1, 16:40 UTC | May 1, 17:35 UTC | 55m |
| 2026-05-01 | OMA672 | JED → MCT | May 1, 03:50 UTC | May 1, 04:55 UTC | 1h 5m |
| 2026-04-30 | OMA612 | DXB → MCT | Apr 30, 18:50 UTC | Apr 30, 19:15 UTC | 25m |
| 2026-04-30 | OMA611 | MCT → DXB | Apr 30, 16:55 UTC | Apr 30, 17:25 UTC | 30m |
| 2026-04-29 | OMA662 | DOH → MCT | Apr 29, 18:50 UTC | Apr 29, 19:40 UTC | 50m |
| 2026-04-28 | OMA661 | MCT → DOH | Apr 28, 23:20 UTC | Apr 29, 17:25 UTC | 18h 6m |
| 2026-04-28 | OMA674 | JED → MCT | Apr 28, 09:35 UTC | Apr 29, 00:15 UTC | 14h 40m |
| 2026-04-28 | OMA203 | MCT → BOM | Apr 28, 07:10 UTC | Apr 28, 07:55 UTC | 45m |
| 2026-04-27 | OMA676 | JED → MCT | Apr 27, 04:50 UTC | Apr 27, 17:35 UTC | 12h 45m |
| 2026-04-26 | OMA676 | JED → MCT | Apr 26, 16:55 UTC | Apr 26, 17:45 UTC | 50m |
| 2026-04-26 | OMA672 | JED → MCT | Apr 26, 04:15 UTC | Apr 26, 05:10 UTC | 55m |
| 2026-04-25 | OMA676 | JED → MCT | Apr 25, 18:15 UTC | Apr 25, 19:10 UTC | 55m |
| 2026-04-22 | OMA406 | CAI → MCT | Apr 22, 16:55 UTC | Apr 22, 19:55 UTC | 3h 0m |
| 2026-04-22 | OMA405 | MCT → CAI | Apr 22, 05:05 UTC | Apr 22, 15:20 UTC | 10h 15m |
| 2026-04-22 | OMA201 | MCT → BOM | Apr 22, 02:55 UTC | Apr 22, 03:35 UTC | 40m |
| 2026-04-21 | OMA676 | JED → MCT | Apr 21, 16:40 UTC | Apr 21, 17:30 UTC | 50m |
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 .