sensors Mode-S transponder
70C0DF
ICAO 24-bit transponder address · allocated to Oman
Currently assigned to A4O-BAB · BOEING 737-800
- Hex
- 70C0DF
- Octal
- 34140337
- Decimal
- 7,389,407
- Country
- OM
- Tail
- A4O-BAB
- Type
- B738
- Flights observed
- 68
- Distinct callsigns
- 20
- Country
- OM
- Last broadcast
- 9h ago
Last known position
Country allocation
The ICAO 24-bit address 70C0DF 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 | 9 | 2026-05-18 |
| OMA241 | Oman Air | 8 | 2026-05-21 |
| OMA246 | Oman Air | 6 | 2026-05-18 |
| OMA696 | Oman Air | 5 | 2026-05-13 |
| OMA695 | Oman Air | 5 | 2026-05-13 |
| OMA405 | Oman Air | 5 | 2026-05-28 |
| OMA242 | Oman Air | 5 | 2026-05-22 |
| OMA406 | Oman Air | 4 | 2026-05-28 |
| OMA414 | Oman Air | 3 | 2026-05-04 |
| OMA690 | Oman Air | 2 | 2026-04-16 |
| OMA664 | Oman Air | 2 | 2026-05-13 |
| OMA611 | Oman Air | 2 | 2026-05-14 |
| OMA225 | Oman Air | 2 | 2026-05-30 |
| OMA685 | Oman Air | 1 | 2026-04-25 |
| OMA684 | Oman Air | 1 | 2026-05-19 |
| OMA663 | Oman Air | 1 | 2026-05-03 |
| OMA662 | Oman Air | 1 | 2026-04-23 |
| OMA661 | Oman Air | 1 | 2026-04-23 |
| OMA612 | Oman Air | 1 | 2026-04-25 |
| OMA413 | Oman Air | 1 | 2026-04-15 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | OMA226 | COK → MCT | May 30, 03:00 UTC | May 30, 03:25 UTC | 25m |
| 2026-05-30 | OMA225 | MCT → COK | May 30, 00:00 UTC | May 30, 01:40 UTC | 1h 40m |
| 2026-05-28 | OMA406 | CAI → MCT | May 28, 16:20 UTC | May 28, 19:00 UTC | 2h 40m |
| 2026-05-28 | OMA405 | MCT → CAI | May 28, 14:30 UTC | May 28, 14:50 UTC | 20m |
| 2026-05-22 | OMA242 | DEL → MCT | May 22, 03:35 UTC | May 22, 19:10 UTC | 15h 35m |
| 2026-05-21 | OMA241 | MCT → DEL | May 21, 16:55 UTC | May 22, 02:05 UTC | 9h 10m |
| 2026-05-21 | OMA241 | MCT → DEL | May 21, 04:30 UTC | May 22, 02:05 UTC | 21h 35m |
| 2026-05-21 | OMA241 | MCT → DEL | May 21, 03:05 UTC | May 22, 01:45 UTC | 22h 40m |
| 2026-05-20 | OMA225 | MCT → COK | May 20, 23:55 UTC | May 21, 01:40 UTC | 1h 45m |
| 2026-05-20 | OMA405 | MCT → CAI | May 20, 14:45 UTC | May 20, 15:00 UTC | 15m |
| 2026-05-19 | OMA684 | RUH → MCT | May 19, 14:35 UTC | May 19, 15:15 UTC | 40m |
| 2026-05-18 | OMA246 | DEL → MCT | May 18, 10:45 UTC | May 18, 12:35 UTC | 1h 50m |
| 2026-05-18 | OMA245 | MCT → DEL | May 18, 08:20 UTC | May 18, 09:05 UTC | 45m |
| 2026-05-17 | OMA245 | MCT → DEL | May 17, 11:50 UTC | May 18, 09:05 UTC | 21h 15m |
| 2026-05-17 | OMA246 | DEL → MCT | May 17, 10:40 UTC | May 18, 09:05 UTC | 22h 25m |
| 2026-05-17 | OMA245 | MCT → DEL | May 17, 08:20 UTC | May 17, 09:00 UTC | 40m |
| 2026-05-14 | OMA611 | MCT → DXB | May 14, 16:50 UTC | May 14, 17:05 UTC | 15m |
| 2026-05-13 | OMA696 | DMM → MCT | May 13, 19:20 UTC | May 13, 20:00 UTC | 40m |
| 2026-05-13 | OMA695 | MCT → DMM | May 13, 17:40 UTC | May 13, 17:50 UTC | 10m |
| 2026-05-13 | OMA664 | DOH → MCT | May 13, 13:20 UTC | May 13, 14:05 UTC | 45m |
| 2026-05-13 | OMA242 | DEL → MCT | May 13, 03:50 UTC | May 13, 04:25 UTC | 35m |
| 2026-05-12 | OMA241 | MCT → DEL | May 12, 10:45 UTC | May 13, 02:15 UTC | 15h 30m |
| 2026-05-12 | OMA245 | MCT → DEL | May 12, 08:30 UTC | May 12, 09:10 UTC | 40m |
| 2026-05-08 | OMA696 | DMM → MCT | May 8, 20:25 UTC | May 8, 21:25 UTC | 1h 0m |
| 2026-05-08 | OMA695 | MCT → DMM | May 8, 17:20 UTC | May 8, 17:30 UTC | 10m |
| 2026-05-06 | OMA242 | DEL → MCT | May 6, 03:50 UTC | May 6, 16:40 UTC | 12h 50m |
| 2026-05-05 | OMA241 | MCT → DEL | May 5, 08:40 UTC | May 6, 02:15 UTC | 17h 35m |
| 2026-05-05 | OMA241 | MCT → DEL | May 5, 06:25 UTC | May 6, 02:15 UTC | 19h 50m |
| 2026-05-04 | OMA414 | AMM → MCT | May 4, 16:05 UTC | May 5, 08:50 UTC | 16h 46m |
| 2026-05-04 | OMA414 | AMM → MCT | May 4, 10:20 UTC | May 5, 08:50 UTC | 22h 31m |
| 2026-05-04 | OMA242 | DEL → MCT | May 4, 03:30 UTC | May 4, 16:25 UTC | 12h 55m |
| 2026-05-03 | OMA696 | DMM → MCT | May 3, 18:50 UTC | May 4, 01:50 UTC | 7h 0m |
| 2026-05-03 | OMA695 | MCT → DMM | May 3, 16:20 UTC | May 3, 17:29 UTC | 1h 10m |
| 2026-05-03 | OMA664 | DOH → MCT | May 3, 13:20 UTC | May 3, 14:10 UTC | 50m |
| 2026-05-03 | OMA663 | MCT → DOH | May 3, 03:50 UTC | May 3, 11:50 UTC | 8h 0m |
| 2026-05-02 | OMA241 | MCT → DEL | May 2, 08:10 UTC | May 3, 01:50 UTC | 17h 40m |
| 2026-04-26 | OMA246 | DEL → MCT | Apr 26, 10:55 UTC | Apr 26, 11:25 UTC | 30m |
| 2026-04-26 | OMA245 | MCT → DEL | Apr 26, 08:35 UTC | Apr 26, 09:30 UTC | 55m |
| 2026-04-25 | OMA685 | MCT → RUH | Apr 25, 22:05 UTC | Apr 26, 02:55 UTC | 4h 50m |
| 2026-04-25 | OMA612 | DXB → MCT | Apr 25, 18:35 UTC | Apr 25, 19:00 UTC | 25m |
| 2026-04-25 | OMA611 | MCT → DXB | Apr 25, 16:30 UTC | Apr 25, 17:00 UTC | 30m |
| 2026-04-24 | OMA696 | DMM → MCT | Apr 24, 18:50 UTC | Apr 24, 20:00 UTC | 1h 10m |
| 2026-04-24 | OMA695 | MCT → DMM | Apr 24, 11:10 UTC | Apr 24, 17:30 UTC | 6h 20m |
| 2026-04-23 | OMA245 | MCT → DEL | Apr 23, 22:15 UTC | Apr 24, 09:40 UTC | 11h 25m |
| 2026-04-23 | OMA662 | DOH → MCT | Apr 23, 18:55 UTC | Apr 23, 19:40 UTC | 45m |
| 2026-04-23 | OMA661 | MCT → DOH | Apr 23, 16:40 UTC | Apr 23, 17:35 UTC | 55m |
| 2026-04-22 | OMA246 | DEL → MCT | Apr 22, 11:55 UTC | Apr 22, 12:25 UTC | 30m |
| 2026-04-22 | OMA245 | MCT → DEL | Apr 22, 08:35 UTC | Apr 22, 09:25 UTC | 50m |
| 2026-04-21 | OMA406 | CAI → MCT | Apr 21, 18:50 UTC | Apr 21, 19:40 UTC | 50m |
| 2026-04-21 | OMA405 | MCT → CAI | Apr 21, 11:55 UTC | Apr 21, 15:05 UTC | 3h 10m |
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-BAB page for operator, model, and routing details .