sensors Mode-S transponder
70C13C
ICAO 24-bit transponder address · allocated to Oman
Currently assigned to A4O-OXE · AIRBUS A-321neo
- Hex
- 70C13C
- Octal
- 34140474
- Decimal
- 7,389,500
- Country
- OM
- Tail
- A4O-OXE
- Type
- A21N
- Flights observed
- 54
- Distinct callsigns
- 18
- Country
- OM
- Last broadcast
- 14d ago
Last known position
Country allocation
The ICAO 24-bit address 70C13C 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 18 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| OMS498 | Omskavia Airline | 16 | 2026-05-02 |
| OMS497 | Omskavia Airline | 16 | 2026-05-01 |
| OMS402 | Omskavia Airline | 3 | 2026-05-03 |
| OMS401 | Omskavia Airline | 3 | 2026-05-03 |
| OMS284 | Omskavia Airline | 2 | 2026-05-01 |
| OMS274 | - | 2 | 2026-04-16 |
| OMS991 | - | 1 | 2026-05-16 |
| OMS404 | Omskavia Airline | 1 | 2026-05-04 |
| OMS403 | Omskavia Airline | 1 | 2026-05-04 |
| OMS316 | Omskavia Airline | 1 | 2026-04-25 |
| OMS294 | Omskavia Airline | 1 | 2026-04-21 |
| OMS285 | Omskavia Airline | 1 | 2026-04-15 |
| OMS273 | Omskavia Airline | 1 | 2026-04-16 |
| OMS272 | - | 1 | 2026-04-17 |
| OMS271 | Omskavia Airline | 1 | 2026-04-17 |
| OMS214 | Omskavia Airline | 1 | 2026-04-23 |
| OMS212 | Omskavia Airline | 1 | 2026-05-02 |
| OMS206 | Omskavia Airline | 1 | 2026-04-20 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-16 | OMS991 | - | May 16, 06:16 UTC | May 16, 08:51 UTC | 2h 35m |
| 2026-05-04 | OMS404 | CGP → MCT | May 4, 17:30 UTC | May 4, 18:55 UTC | 1h 26m |
| 2026-05-04 | OMS403 | MCT → CGP | May 4, 15:10 UTC | May 4, 16:10 UTC | 1h 0m |
| 2026-05-03 | OMS402 | CGP → MCT | May 3, 03:15 UTC | May 3, 14:05 UTC | 10h 49m |
| 2026-05-03 | OMS401 | MCT → CGP | May 3, 00:40 UTC | May 3, 01:40 UTC | 1h 0m |
| 2026-05-02 | OMS212 | DMM → MCT | May 2, 10:15 UTC | May 2, 11:30 UTC | 1h 15m |
| 2026-05-02 | OMS498 | DAC → MCT | May 2, 00:10 UTC | May 2, 07:50 UTC | 7h 40m |
| 2026-05-01 | OMS497 | MCT → DAC | May 1, 21:45 UTC | May 1, 22:45 UTC | 1h 0m |
| 2026-05-01 | OMS284 | JED → MCT | May 1, 05:15 UTC | May 1, 11:20 UTC | 6h 5m |
| 2026-04-29 | OMS498 | DAC → MCT | Apr 29, 23:40 UTC | Apr 30, 12:30 UTC | 12h 50m |
| 2026-04-29 | OMS497 | MCT → DAC | Apr 29, 06:19 UTC | Apr 29, 22:20 UTC | 16h 1m |
| 2026-04-29 | OMS497 | MCT → DAC | Apr 29, 01:05 UTC | Apr 29, 22:20 UTC | 21h 16m |
| 2026-04-29 | OMS498 | DAC → MCT | Apr 29, 00:15 UTC | Apr 29, 22:20 UTC | 22h 6m |
| 2026-04-28 | OMS497 | MCT → DAC | Apr 28, 21:45 UTC | Apr 28, 22:40 UTC | 55m |
| 2026-04-28 | OMS402 | CGP → MCT | Apr 28, 03:50 UTC | Apr 28, 17:00 UTC | 13h 10m |
| 2026-04-27 | OMS401 | MCT → CGP | Apr 27, 11:45 UTC | Apr 28, 02:05 UTC | 14h 20m |
| 2026-04-27 | OMS498 | DAC → MCT | Apr 27, 00:25 UTC | Apr 27, 12:35 UTC | 12h 10m |
| 2026-04-26 | OMS497 | MCT → DAC | Apr 26, 22:00 UTC | Apr 26, 22:55 UTC | 55m |
| 2026-04-26 | OMS402 | CGP → MCT | Apr 26, 03:30 UTC | Apr 26, 16:40 UTC | 13h 10m |
| 2026-04-26 | OMS401 | MCT → CGP | Apr 26, 01:05 UTC | Apr 26, 01:55 UTC | 50m |
| 2026-04-25 | OMS316 | SPX → MCT | Apr 25, 16:55 UTC | Apr 25, 19:50 UTC | 2h 55m |
| 2026-04-25 | OMS498 | DAC → MCT | Apr 25, 00:05 UTC | Apr 25, 15:05 UTC | 15h 0m |
| 2026-04-24 | OMS497 | MCT → DAC | Apr 24, 21:50 UTC | Apr 24, 22:50 UTC | 1h 0m |
| 2026-04-24 | OMS498 | DAC → MCT | Apr 24, 00:25 UTC | Apr 24, 11:35 UTC | 11h 10m |
| 2026-04-23 | OMS497 | MCT → DAC | Apr 23, 22:05 UTC | Apr 23, 23:05 UTC | 1h 0m |
| 2026-04-23 | OMS214 | DMM → MCT | Apr 23, 14:45 UTC | Apr 23, 16:00 UTC | 1h 15m |
| 2026-04-23 | OMS498 | DAC → MCT | Apr 23, 01:50 UTC | Apr 23, 12:15 UTC | 10h 25m |
| 2026-04-22 | OMS497 | MCT → DAC | Apr 22, 21:40 UTC | Apr 22, 22:40 UTC | 1h 0m |
| 2026-04-21 | OMS498 | DAC → MCT | Apr 21, 23:55 UTC | Apr 22, 12:15 UTC | 12h 20m |
| 2026-04-21 | OMS497 | MCT → DAC | Apr 21, 21:50 UTC | Apr 21, 22:40 UTC | 50m |
| 2026-04-21 | OMS294 | AHB → MCT | Apr 21, 16:10 UTC | Apr 21, 16:20 UTC | 10m |
| 2026-04-20 | OMS206 | RUH → MCT | Apr 20, 13:40 UTC | Apr 20, 19:05 UTC | 5h 25m |
| 2026-04-20 | OMS284 | JED → MCT | Apr 20, 10:40 UTC | Apr 20, 11:35 UTC | 55m |
| 2026-04-19 | OMS498 | DAC → MCT | Apr 19, 00:30 UTC | Apr 19, 12:25 UTC | 11h 54m |
| 2026-04-18 | OMS497 | MCT → DAC | Apr 18, 22:20 UTC | Apr 18, 23:15 UTC | 55m |
| 2026-04-17 | OMS498 | DAC → MCT | Apr 17, 23:40 UTC | Apr 18, 17:25 UTC | 17h 45m |
| 2026-04-17 | OMS497 | MCT → DAC | Apr 17, 21:25 UTC | Apr 17, 22:30 UTC | 1h 5m |
| 2026-04-17 | OMS272 | - | Apr 17, 11:25 UTC | Apr 17, 12:20 UTC | 55m |
| 2026-04-17 | OMS271 | MCT → MED | Apr 17, 06:55 UTC | Apr 17, 07:15 UTC | 20m |
| 2026-04-16 | OMS498 | DAC → MCT | Apr 16, 23:55 UTC | Apr 17, 01:10 UTC | 1h 15m |
| 2026-04-16 | OMS497 | MCT → DAC | Apr 16, 21:39 UTC | Apr 16, 22:40 UTC | 1h 0m |
| 2026-04-16 | OMS274 | - | Apr 16, 13:20 UTC | Apr 16, 13:30 UTC | 10m |
| 2026-04-16 | OMS274 | - | Apr 16, 12:34 UTC | Apr 16, 12:45 UTC | 10m |
| 2026-04-16 | OMS273 | MCT → MED | Apr 16, 07:24 UTC | Apr 16, 08:35 UTC | 1h 10m |
| 2026-04-15 | OMS498 | DAC → MCT | Apr 15, 23:40 UTC | Apr 16, 00:40 UTC | 1h 0m |
| 2026-04-15 | OMS497 | MCT → DAC | Apr 15, 21:20 UTC | Apr 15, 22:20 UTC | 1h 0m |
| 2026-04-15 | OMS285 | MCT → JED | Apr 15, 09:55 UTC | Apr 15, 10:55 UTC | 1h 0m |
| 2026-04-15 | OMS498 | DAC → MCT | Apr 15, 00:55 UTC | Apr 15, 01:20 UTC | 25m |
| 2026-04-15 | OMS498 | DAC → MCT | Apr 15, 00:20 UTC | Apr 15, 00:50 UTC | 30m |
| 2026-04-14 | OMS497 | MCT → DAC | Apr 14, 22:55 UTC | Apr 14, 23:05 UTC | 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-OXE page for operator, model, and routing details .