sensors Mode-S transponder
70C149
ICAO 24-bit transponder address · allocated to Oman
Currently assigned to A4O-OXI · AIRBUS A-321neo
- Hex
- 70C149
- Octal
- 34140511
- Decimal
- 7,389,513
- Country
- OM
- Tail
- A4O-OXI
- Type
- A21N
- Flights observed
- 247
- Distinct callsigns
- 20
- Country
- OM
- Last broadcast
- Jul 26, 02:35 UTC
Last known position
Country allocation
The ICAO 24-bit address 70C149 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 |
|---|---|---|---|
| OMS497 | - | 41 | 2026-07-12 |
| OMS498 | - | 28 | 2026-07-13 |
| OMS402 | Omskavia Airline | 26 | 2026-07-25 |
| OMS401 | Omskavia Airline | 25 | 2026-07-24 |
| OMS466 | Omskavia Airline | 11 | 2026-07-18 |
| OMS465 | - | 11 | 2026-07-18 |
| OMS856 | Omskavia Airline | 9 | 2026-07-25 |
| OMS464 | Omskavia Airline | 9 | 2026-07-23 |
| OMS463 | Omskavia Airline | 9 | 2026-07-22 |
| OMS284 | - | 9 | 2026-07-17 |
| OMS855 | Omskavia Airline | 6 | 2026-07-25 |
| OMS838 | Omskavia Airline | 6 | 2026-07-20 |
| OMS795 | - | 4 | 2026-06-28 |
| OMS783 | Omskavia Airline | 4 | 2026-05-17 |
| OMS812 | - | 3 | 2026-07-08 |
| OMS811 | - | 3 | 2026-07-08 |
| OMS784 | Omskavia Airline | 3 | 2026-05-18 |
| OMS404 | - | 3 | 2026-07-23 |
| OMS286 | Omskavia Airline | 3 | 2026-06-19 |
| OMS272 | - | 3 | 2026-07-15 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | OMS856 | SJJ → MCT | Jul 25, 21:30 UTC | Jul 26, 02:35 UTC | 5h 5m |
| 2026-07-25 | OMS855 | MCT → SJJ | Jul 25, 14:35 UTC | Jul 25, 19:45 UTC | 5h 10m |
| 2026-07-25 | OMS402 | CGP → MCT | Jul 25, 05:10 UTC | Jul 25, 06:05 UTC | 55m |
| 2026-07-25 | OMS402 | CGP → MCT | Jul 25, 03:10 UTC | Jul 25, 04:00 UTC | 50m |
| 2026-07-24 | OMS401 | MCT → CGP | Jul 24, 08:55 UTC | Jul 25, 01:50 UTC | 16h 55m |
| 2026-07-24 | OMS401 | MCT → CGP | Jul 24, 03:30 UTC | Jul 25, 01:50 UTC | 22h 20m |
| 2026-07-23 | OMS404 | - | Jul 23, 17:15 UTC | Jul 24, 02:10 UTC | 8h 55m |
| 2026-07-23 | OMS464 | BKK → MCT | Jul 23, 04:10 UTC | Jul 23, 16:00 UTC | 11h 50m |
| 2026-07-22 | OMS463 | MCT → BKK | Jul 22, 10:20 UTC | Jul 23, 02:40 UTC | 16h 20m |
| 2026-07-22 | OMS463 | MCT → BKK | Jul 22, 04:20 UTC | Jul 23, 02:40 UTC | 22h 20m |
| 2026-07-22 | OMS463 | MCT → BKK | Jul 22, 03:30 UTC | Jul 23, 02:15 UTC | 22h 45m |
| 2026-07-21 | OMS401 | MCT → CGP | Jul 21, 22:50 UTC | Jul 22, 02:00 UTC | 3h 10m |
| 2026-07-20 | OMS838 | TZX → MCT | Jul 20, 19:35 UTC | Jul 20, 22:00 UTC | 2h 25m |
| 2026-07-20 | OMS838 | TZX → MCT | Jul 20, 18:00 UTC | Jul 20, 19:30 UTC | 1h 30m |
| 2026-07-20 | OMS837 | - | Jul 20, 16:35 UTC | Jul 20, 16:45 UTC | 10m |
| 2026-07-20 | OMS402 | - | Jul 20, 03:00 UTC | Jul 20, 15:55 UTC | 12h 55m |
| 2026-07-19 | OMS401 | MCT → CGP | Jul 19, 22:25 UTC | Jul 20, 01:40 UTC | 3h 15m |
| 2026-07-18 | OMS466 | BKK → MCT | Jul 18, 21:15 UTC | Jul 19, 12:25 UTC | 15h 10m |
| 2026-07-18 | OMS465 | - | Jul 18, 15:10 UTC | Jul 18, 19:55 UTC | 4h 45m |
| 2026-07-17 | OMS284 | - | Jul 17, 16:40 UTC | Jul 18, 11:35 UTC | 18h 56m |
| 2026-07-17 | OMS901 | - | Jul 17, 15:49 UTC | Jul 18, 11:35 UTC | 19h 46m |
| 2026-07-17 | OMS901 | - | Jul 17, 08:20 UTC | Jul 18, 06:25 UTC | 22h 6m |
| 2026-07-17 | OMS464 | - | Jul 17, 06:20 UTC | Jul 18, 06:15 UTC | 23h 56m |
| 2026-07-17 | OMS464 | - | Jul 17, 04:20 UTC | Jul 18, 02:09 UTC | 21h 50m |
| 2026-07-17 | OMS464 | - | Jul 17, 04:14 UTC | Jul 18, 02:09 UTC | 21h 55m |
| 2026-07-16 | OMS463 | - | Jul 16, 21:55 UTC | Jul 17, 02:50 UTC | 4h 55m |
| 2026-07-16 | OMS206 | - | Jul 16, 09:05 UTC | Jul 16, 14:05 UTC | 5h 0m |
| 2026-07-15 | OMS856 | - | Jul 15, 21:20 UTC | Jul 16, 02:30 UTC | 5h 10m |
| 2026-07-15 | OMS855 | - | Jul 15, 14:25 UTC | Jul 15, 19:45 UTC | 5h 20m |
| 2026-07-15 | OMS272 | - | Jul 15, 00:10 UTC | Jul 15, 12:25 UTC | 12h 15m |
| 2026-07-14 | OMS272 | - | Jul 14, 16:20 UTC | Jul 15, 12:25 UTC | 20h 4m |
| 2026-07-14 | OMS272 | - | Jul 14, 15:40 UTC | Jul 15, 12:25 UTC | 20h 44m |
| 2026-07-14 | OMS284 | - | Jul 14, 05:45 UTC | Jul 14, 11:40 UTC | 5h 55m |
| 2026-07-13 | OMS856 | - | Jul 13, 21:30 UTC | Jul 14, 02:45 UTC | 5h 15m |
| 2026-07-13 | OMS855 | - | Jul 13, 14:45 UTC | Jul 13, 19:45 UTC | 5h 0m |
| 2026-07-13 | OMS498 | - | Jul 13, 00:05 UTC | Jul 13, 12:25 UTC | 12h 20m |
| 2026-07-12 | OMS497 | - | Jul 12, 19:50 UTC | Jul 12, 22:55 UTC | 3h 5m |
| 2026-07-12 | OMS402 | - | Jul 12, 03:50 UTC | Jul 12, 16:45 UTC | 12h 55m |
| 2026-07-11 | OMS401 | - | Jul 11, 08:55 UTC | Jul 12, 02:01 UTC | 17h 5m |
| 2026-07-11 | OMS401 | - | Jul 11, 02:20 UTC | Jul 12, 02:01 UTC | 23h 40m |
| 2026-07-11 | OMS498 | - | Jul 11, 00:20 UTC | Jul 11, 23:45 UTC | 23h 25m |
| 2026-07-11 | OMS498 | - | Jul 11, 00:10 UTC | Jul 11, 09:00 UTC | 8h 50m |
| 2026-07-10 | OMS497 | - | Jul 10, 08:40 UTC | Jul 10, 22:50 UTC | 14h 10m |
| 2026-07-10 | OMS497 | - | Jul 10, 02:35 UTC | Jul 10, 22:50 UTC | 20h 15m |
| 2026-07-10 | OMS497 | - | Jul 10, 01:00 UTC | Jul 10, 22:50 UTC | 21h 50m |
| 2026-07-09 | OMS464 | - | Jul 9, 04:20 UTC | Jul 9, 23:15 UTC | 18h 55m |
| 2026-07-08 | OMS463 | - | Jul 8, 22:00 UTC | Jul 9, 02:50 UTC | 4h 50m |
| 2026-07-08 | OMS812 | - | Jul 8, 12:20 UTC | Jul 8, 17:50 UTC | 5h 30m |
| 2026-07-08 | OMS811 | - | Jul 8, 05:05 UTC | Jul 8, 11:05 UTC | 6h 0m |
| 2026-07-07 | OMS902 | - | Jul 7, 15:30 UTC | Jul 8, 01:55 UTC | 10h 25m |
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-OXI page for operator, model, and routing details .