sensors Mode-S transponder
70C0DE
ICAO 24-bit transponder address · allocated to Oman
Currently assigned to A4O-BAA · BOEING 737-800
- Hex
- 70C0DE
- Octal
- 34140336
- Decimal
- 7,389,406
- Country
- OM
- Tail
- A4O-BAA
- Type
- B738
- Flights observed
- 79
- Distinct callsigns
- 20
- Country
- OM
- Last broadcast
- 23h ago
Last known position
Country allocation
The ICAO 24-bit address 70C0DE 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 | 13 | 2026-05-27 |
| OMA242 | Oman Air | 12 | 2026-05-26 |
| OMA241 | Oman Air | 11 | 2026-05-26 |
| OMA246 | Oman Air | 8 | 2026-05-27 |
| OMA405 | Oman Air | 7 | 2026-05-02 |
| OMA406 | Oman Air | 4 | 2026-05-05 |
| OMA696 | Oman Air | 3 | 2026-05-10 |
| OMA414 | Oman Air | 3 | 2026-05-29 |
| OMA674 | Oman Air | 2 | 2026-04-30 |
| OMA654 | Oman Air | 2 | 2026-05-21 |
| OMA612 | Oman Air | 2 | 2026-04-21 |
| OMA611 | Oman Air | 2 | 2026-04-21 |
| OMA695 | - | 1 | 2026-04-15 |
| OMA686 | Oman Air | 1 | 2026-04-21 |
| OMA413 | Oman Air | 1 | 2026-04-17 |
| OMA254 | Oman Air | 1 | 2026-05-03 |
| OMA253 | Oman Air | 1 | 2026-05-02 |
| OMA236 | Oman Air | 1 | 2026-05-28 |
| OMA232 | Oman Air | 1 | 2026-05-23 |
| OMA204 | Oman Air | 1 | 2026-04-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | OMA414 | AMM → MCT | May 29, 15:50 UTC | May 29, 16:20 UTC | 30m |
| 2026-05-28 | OMA236 | HYD → MCT | May 28, 10:50 UTC | May 29, 04:40 UTC | 17h 50m |
| 2026-05-27 | OMA245 | MCT → DEL | May 27, 19:05 UTC | May 28, 09:25 UTC | 14h 20m |
| 2026-05-27 | OMA246 | DEL → MCT | May 27, 11:35 UTC | May 28, 09:25 UTC | 21h 50m |
| 2026-05-27 | OMA246 | DEL → MCT | May 27, 10:45 UTC | May 28, 09:25 UTC | 22h 40m |
| 2026-05-26 | OMA245 | MCT → DEL | May 26, 16:35 UTC | May 27, 09:15 UTC | 16h 40m |
| 2026-05-26 | OMA242 | DEL → MCT | May 26, 03:45 UTC | May 26, 14:45 UTC | 11h 0m |
| 2026-05-26 | OMA241 | MCT → DEL | May 26, 01:20 UTC | May 26, 02:15 UTC | 55m |
| 2026-05-24 | OMA246 | DEL → MCT | May 24, 10:50 UTC | May 24, 11:20 UTC | 30m |
| 2026-05-24 | OMA245 | MCT → DEL | May 24, 08:40 UTC | May 24, 09:15 UTC | 35m |
| 2026-05-23 | OMA245 | MCT → DEL | May 23, 11:35 UTC | May 24, 09:15 UTC | 21h 40m |
| 2026-05-23 | OMA232 | HYD → MCT | May 23, 11:15 UTC | May 24, 09:15 UTC | 22h 0m |
| 2026-05-21 | OMA654 | BAH → MCT | May 21, 18:25 UTC | May 22, 04:25 UTC | 10h 0m |
| 2026-05-20 | OMA242 | DEL → MCT | May 20, 03:50 UTC | May 20, 04:20 UTC | 30m |
| 2026-05-19 | OMA241 | MCT → DEL | May 19, 15:00 UTC | May 20, 02:05 UTC | 11h 5m |
| 2026-05-19 | OMA242 | DEL → MCT | May 19, 03:35 UTC | May 20, 02:05 UTC | 22h 30m |
| 2026-05-19 | OMA241 | MCT → DEL | May 19, 01:25 UTC | May 19, 02:15 UTC | 50m |
| 2026-05-18 | OMA242 | DEL → MCT | May 18, 03:40 UTC | May 19, 02:15 UTC | 22h 34m |
| 2026-05-18 | OMA241 | MCT → DEL | May 18, 01:15 UTC | May 18, 02:05 UTC | 50m |
| 2026-05-17 | OMA202 | BOM → MCT | May 17, 04:55 UTC | May 17, 05:10 UTC | 15m |
| 2026-05-16 | OMA654 | BAH → MCT | May 16, 17:55 UTC | May 16, 18:35 UTC | 40m |
| 2026-05-15 | OMA245 | MCT → DEL | May 15, 16:25 UTC | May 16, 09:16 UTC | 16h 51m |
| 2026-05-15 | OMA242 | DEL → MCT | May 15, 03:40 UTC | May 15, 04:10 UTC | 30m |
| 2026-05-13 | OMA246 | DEL → MCT | May 13, 10:40 UTC | May 13, 12:30 UTC | 1h 50m |
| 2026-05-13 | OMA245 | MCT → DEL | May 13, 08:25 UTC | May 13, 09:00 UTC | 35m |
| 2026-05-12 | OMA245 | MCT → DEL | May 12, 11:15 UTC | May 13, 09:00 UTC | 21h 45m |
| 2026-05-12 | OMA242 | DEL → MCT | May 12, 03:25 UTC | May 12, 11:20 UTC | 7h 55m |
| 2026-05-10 | OMA696 | DMM → MCT | May 10, 19:54 UTC | May 11, 14:50 UTC | 18h 55m |
| 2026-05-10 | OMA246 | DEL → MCT | May 10, 10:45 UTC | May 10, 12:30 UTC | 1h 45m |
| 2026-05-10 | OMA245 | MCT → DEL | May 10, 08:25 UTC | May 10, 09:05 UTC | 40m |
| 2026-05-09 | OMA245 | MCT → DEL | May 9, 10:40 UTC | May 10, 09:05 UTC | 22h 25m |
| 2026-05-09 | OMA245 | MCT → DEL | May 9, 08:30 UTC | May 9, 09:35 UTC | 1h 5m |
| 2026-05-08 | OMA242 | DEL → MCT | May 8, 03:30 UTC | May 8, 04:00 UTC | 30m |
| 2026-05-08 | OMA241 | MCT → DEL | May 8, 01:09 UTC | May 8, 01:49 UTC | 40m |
| 2026-05-05 | OMA406 | CAI → MCT | May 5, 16:25 UTC | May 5, 19:00 UTC | 2h 35m |
| 2026-05-05 | OMA242 | DEL → MCT | May 5, 03:30 UTC | May 5, 14:45 UTC | 11h 15m |
| 2026-05-04 | OMA241 | MCT → DEL | May 4, 15:15 UTC | May 5, 02:30 UTC | 11h 16m |
| 2026-05-03 | OMA254 | MAA → MCT | May 3, 10:05 UTC | May 3, 11:35 UTC | 1h 30m |
| 2026-05-02 | OMA253 | MCT → MAA | May 2, 16:55 UTC | May 3, 08:20 UTC | 15h 24m |
| 2026-05-02 | OMA405 | MCT → CAI | May 2, 11:50 UTC | May 2, 14:55 UTC | 3h 5m |
| 2026-05-01 | OMA406 | CAI → MCT | May 1, 19:50 UTC | May 1, 20:00 UTC | 10m |
| 2026-05-01 | OMA405 | MCT → CAI | May 1, 15:00 UTC | May 1, 15:15 UTC | 15m |
| 2026-04-30 | OMA674 | JED → MCT | Apr 30, 23:20 UTC | May 1, 00:20 UTC | 1h 0m |
| 2026-04-30 | OMA204 | BOM → MCT | Apr 30, 09:00 UTC | Apr 30, 09:15 UTC | 15m |
| 2026-04-29 | OMA203 | MCT → BOM | Apr 29, 18:40 UTC | Apr 30, 07:40 UTC | 12h 59m |
| 2026-04-29 | OMA405 | MCT → CAI | Apr 29, 11:45 UTC | Apr 29, 14:50 UTC | 3h 5m |
| 2026-04-28 | OMA405 | MCT → CAI | Apr 28, 11:55 UTC | Apr 28, 14:55 UTC | 3h 0m |
| 2026-04-27 | OMA242 | DEL → MCT | Apr 27, 04:30 UTC | Apr 27, 04:50 UTC | 20m |
| 2026-04-27 | OMA241 | MCT → DEL | Apr 27, 01:25 UTC | Apr 27, 02:10 UTC | 45m |
| 2026-04-25 | OMA406 | CAI → MCT | Apr 25, 16:55 UTC | Apr 25, 19:50 UTC | 2h 55m |
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-BAA page for operator, model, and routing details .