sensors Mode-S transponder
70C0FF
ICAO 24-bit transponder address · allocated to Oman
Currently assigned to A4O-OVD · AIRBUS A-320neo
- Hex
- 70C0FF
- Octal
- 34140377
- Decimal
- 7,389,439
- Country
- OM
- Tail
- A4O-OVD
- Type
- A20N
- Flights observed
- 118
- Distinct callsigns
- 20
- Country
- OM
- Last broadcast
- Jul 26, 21:45 UTC
Last known position
Country allocation
The ICAO 24-bit address 70C0FF 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 |
|---|---|---|---|
| OMS735 | Omskavia Airline | 18 | 2026-07-21 |
| OMS761 | Omskavia Airline | 12 | 2026-07-25 |
| OMS705 | Omskavia Airline | 7 | 2026-07-22 |
| OMS783 | - | 6 | 2026-07-12 |
| OMS537 | Omskavia Airline | 6 | 2026-07-23 |
| OMS784 | - | 5 | 2026-07-13 |
| OMS762 | Omskavia Airline | 5 | 2026-07-26 |
| OMS538 | Omskavia Airline | 5 | 2026-07-23 |
| OMS246 | - | 5 | 2026-07-16 |
| OMS392 | Omskavia Airline | 4 | 2026-07-24 |
| OMS245 | - | 4 | 2026-07-16 |
| OMS214 | - | 4 | 2026-07-12 |
| OMS706 | Omskavia Airline | 3 | 2026-07-19 |
| OMS283 | - | 3 | 2026-07-20 |
| OMS213 | - | 3 | 2026-07-12 |
| OMS838 | Omskavia Airline | 2 | 2026-07-24 |
| OMS837 | Omskavia Airline | 2 | 2026-07-24 |
| OMS505 | - | 2 | 2026-06-28 |
| OMS402 | - | 2 | 2026-07-14 |
| OMS316 | Omskavia Airline | 2 | 2026-06-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | OMS762 | BOM → MCT | Jul 26, 00:55 UTC | Jul 26, 21:45 UTC | 20h 51m |
| 2026-07-25 | OMS761 | MCT → BOM | Jul 25, 22:10 UTC | Jul 25, 23:35 UTC | 1h 25m |
| 2026-07-25 | OMS288 | JED → MCT | Jul 25, 03:55 UTC | Jul 25, 14:05 UTC | 10h 10m |
| 2026-07-24 | OMS838 | TZX → MCT | Jul 24, 18:05 UTC | Jul 24, 22:00 UTC | 3h 55m |
| 2026-07-24 | OMS837 | MCT → TZX | Jul 24, 13:10 UTC | Jul 24, 17:05 UTC | 3h 55m |
| 2026-07-24 | OMS392 | PZU → MCT | Jul 24, 03:40 UTC | Jul 24, 10:20 UTC | 6h 40m |
| 2026-07-23 | OMS538 | MUX → MCT | Jul 23, 23:10 UTC | Jul 23, 23:15 UTC | 5m |
| 2026-07-23 | OMS537 | MCT → MUX | Jul 23, 22:00 UTC | Jul 23, 22:10 UTC | 10m |
| 2026-07-22 | OMS211 | MCT → DMM | Jul 22, 23:55 UTC | Jul 23, 07:25 UTC | 7h 30m |
| 2026-07-22 | OMS705 | MCT → LKO | Jul 22, 11:20 UTC | Jul 22, 22:35 UTC | 11h 15m |
| 2026-07-22 | OMS705 | MCT → LKO | Jul 22, 00:30 UTC | Jul 22, 22:35 UTC | 22h 5m |
| 2026-07-21 | OMS735 | MCT → HYD | Jul 21, 20:25 UTC | Jul 22, 11:20 UTC | 14h 55m |
| 2026-07-20 | OMS283 | - | Jul 20, 15:50 UTC | Jul 21, 11:35 UTC | 19h 45m |
| 2026-07-20 | OMS283 | - | Jul 20, 10:05 UTC | Jul 21, 06:05 UTC | 20h 0m |
| 2026-07-19 | OMS706 | LKO → MCT | Jul 19, 23:50 UTC | Jul 20, 16:15 UTC | 16h 25m |
| 2026-07-19 | OMS705 | - | Jul 19, 10:35 UTC | Jul 19, 22:30 UTC | 11h 55m |
| 2026-07-18 | OMS706 | LKO → MCT | Jul 18, 23:55 UTC | Jul 19, 22:30 UTC | 22h 35m |
| 2026-07-18 | OMS705 | - | Jul 18, 21:40 UTC | Jul 18, 22:35 UTC | 55m |
| 2026-07-18 | OMS392 | PZU → MCT | Jul 18, 03:40 UTC | Jul 18, 10:15 UTC | 6h 35m |
| 2026-07-16 | OMS206 | - | Jul 16, 19:50 UTC | Jul 17, 13:45 UTC | 17h 55m |
| 2026-07-16 | OMS246 | - | Jul 16, 15:49 UTC | Jul 16, 16:09 UTC | 20m |
| 2026-07-16 | OMS245 | - | Jul 16, 13:34 UTC | Jul 16, 14:05 UTC | 30m |
| 2026-07-16 | OMS283 | - | Jul 16, 00:20 UTC | Jul 16, 11:34 UTC | 11h 15m |
| 2026-07-15 | OMS705 | - | Jul 15, 22:00 UTC | Jul 15, 22:50 UTC | 50m |
| 2026-07-15 | OMS153 | - | Jul 15, 09:40 UTC | Jul 15, 09:50 UTC | 10m |
| 2026-07-14 | OMS735 | - | Jul 14, 16:00 UTC | Jul 15, 08:10 UTC | 16h 9m |
| 2026-07-14 | OMS735 | - | Jul 14, 10:35 UTC | Jul 15, 08:10 UTC | 21h 34m |
| 2026-07-14 | OMS735 | - | Jul 14, 05:50 UTC | Jul 15, 00:55 UTC | 19h 4m |
| 2026-07-14 | OMS735 | - | Jul 14, 03:50 UTC | Jul 15, 00:55 UTC | 21h 4m |
| 2026-07-14 | OMS402 | - | Jul 14, 03:35 UTC | Jul 15, 00:55 UTC | 21h 19m |
| 2026-07-13 | OMS401 | - | Jul 13, 22:45 UTC | Jul 14, 01:50 UTC | 3h 5m |
| 2026-07-13 | OMS784 | - | Jul 13, 00:10 UTC | Jul 13, 13:45 UTC | 13h 35m |
| 2026-07-12 | OMS783 | - | Jul 12, 22:50 UTC | Jul 12, 23:00 UTC | 10m |
| 2026-07-12 | OMS783 | - | Jul 12, 20:45 UTC | Jul 12, 22:00 UTC | 1h 15m |
| 2026-07-12 | OMS214 | - | Jul 12, 15:40 UTC | Jul 12, 16:45 UTC | 1h 5m |
| 2026-07-12 | OMS213 | - | Jul 12, 13:01 UTC | Jul 12, 14:05 UTC | 1h 5m |
| 2026-07-11 | OMS735 | - | Jul 11, 20:00 UTC | Jul 12, 10:35 UTC | 14h 35m |
| 2026-07-11 | OMS392 | - | Jul 11, 04:15 UTC | Jul 11, 10:40 UTC | 6h 25m |
| 2026-07-09 | OMS784 | - | Jul 9, 01:35 UTC | Jul 9, 02:20 UTC | 45m |
| 2026-07-09 | OMS784 | - | Jul 9, 00:10 UTC | Jul 9, 00:20 UTC | 10m |
| 2026-07-08 | OMS783 | - | Jul 8, 20:45 UTC | Jul 8, 23:00 UTC | 2h 15m |
| 2026-07-08 | OMS783 | - | Jul 8, 00:40 UTC | Jul 8, 23:00 UTC | 22h 20m |
| 2026-07-07 | OMS761 | - | Jul 7, 21:55 UTC | Jul 7, 23:30 UTC | 1h 35m |
| 2026-07-07 | OMS336 | - | Jul 7, 00:45 UTC | Jul 7, 13:15 UTC | 12h 30m |
| 2026-07-06 | OMS761 | - | Jul 6, 21:55 UTC | Jul 6, 23:25 UTC | 1h 30m |
| 2026-07-05 | OMS735 | - | Jul 5, 19:55 UTC | Jul 6, 12:20 UTC | 16h 25m |
| 2026-07-05 | OMS246 | SHJ → MCT | Jul 5, 15:35 UTC | Jul 5, 16:00 UTC | 25m |
| 2026-07-05 | OMS245 | MCT → SHJ | Jul 5, 13:45 UTC | Jul 5, 14:15 UTC | 30m |
| 2026-07-04 | OMS735 | - | Jul 4, 20:05 UTC | Jul 5, 11:10 UTC | 15h 5m |
| 2026-07-04 | OMS246 | SHJ → MCT | Jul 4, 15:45 UTC | Jul 4, 16:15 UTC | 30m |
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-OVD page for operator, model, and routing details .