sensors Mode-S transponder

70C103

ICAO 24-bit transponder address · allocated to Oman

Currently assigned to A4O-MI · BOEING 737 MAX 8

Hex
70C103
Octal
34140403
Decimal
7,389,443
Country
OM
Tail
A4O-MI
Type
B38M
No current signal · last broadcast 1d ago
Flights observed
154
Distinct callsigns
20
Country
OM
Last broadcast
1d ago

Last known position

Most recent position reported by Mode-S 70C103.

Country allocation

The ICAO 24-bit address 70C103 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
OMA225 - 7 2026-07-12
OMA223 - 6 2026-06-26
OMA833 - 5 2026-07-12
OMA681 - 5 2026-06-29
OMA612 - 5 2026-07-10
OMA282 - 5 2026-07-01
OMA224 - 5 2026-06-26
OMA147 Oman Air 5 2026-06-10
OMA832 - 4 2026-07-11
OMA685 - 4 2026-07-10
OMA664 Oman Air 4 2026-07-10
OMA663 - 4 2026-07-10
OMA611 - 4 2026-07-10
OMA281 - 4 2026-07-01
OMA123 - 4 2026-06-27
OMA831 - 3 2026-07-02
OMA824 Oman Air 3 2026-05-13
OMA823 - 3 2026-06-24
OMA686 - 3 2026-07-11
OMA682 Oman Air 3 2026-06-17

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-13 OMA636 - Jul 13, 17:10 UTCJul 13, 17:40 UTC30m
2026-07-13 OMA635 - Jul 13, 15:00 UTCJul 13, 15:40 UTC40m
2026-07-12 OMA833 - Jul 12, 20:20 UTCJul 13, 06:05 UTC9h 45m
2026-07-12 OMA414 - Jul 12, 15:25 UTCJul 12, 16:35 UTC1h 10m
2026-07-12 OMA414 - Jul 12, 13:50 UTCJul 12, 14:20 UTC30m
2026-07-12 OMA413 - Jul 12, 09:35 UTCJul 12, 12:25 UTC2h 50m
2026-07-12 OMA225 - Jul 12, 01:45 UTCJul 12, 01:55 UTC10m
2026-07-11 OMA832 - Jul 11, 16:15 UTCJul 11, 17:40 UTC1h 25m
2026-07-11 OMA686 - Jul 11, 01:15 UTCJul 11, 02:30 UTC1h 15m
2026-07-10 OMA685 - Jul 10, 22:10 UTCJul 10, 23:05 UTC55m
2026-07-10 OMA612 - Jul 10, 18:30 UTCJul 10, 18:55 UTC25m
2026-07-10 OMA611 - Jul 10, 16:35 UTCJul 10, 17:00 UTC25m
2026-07-10 OMA664 DOH → MCT Jul 10, 13:25 UTCJul 10, 14:10 UTC45m
2026-07-10 OMA663 - Jul 10, 10:55 UTCJul 10, 11:45 UTC50m
2026-07-10 OMA202 - Jul 10, 05:25 UTCJul 10, 06:20 UTC55m
2026-07-10 OMA201 - Jul 10, 03:15 UTCJul 10, 04:10 UTC55m
2026-07-08 OMA242 - Jul 8, 03:30 UTCJul 8, 04:10 UTC40m
2026-07-08 OMA241 - Jul 8, 01:25 UTCJul 8, 02:15 UTC50m
2026-07-06 OMA833 - Jul 6, 21:25 UTCJul 7, 11:55 UTC14h 30m
2026-07-06 OMA414 - Jul 6, 14:15 UTCJul 6, 17:05 UTC2h 50m
2026-07-06 OMA413 - Jul 6, 10:00 UTCJul 6, 13:10 UTC3h 10m
2026-07-06 OMA235 - Jul 6, 00:15 UTCJul 6, 06:45 UTC6h 30m
2026-07-05 OMA612 - Jul 5, 18:35 UTCJul 5, 19:00 UTC25m
2026-07-05 OMA611 - Jul 5, 16:35 UTCJul 5, 17:00 UTC25m
2026-07-04 OMA832 - Jul 4, 07:20 UTCJul 4, 17:35 UTC10h 15m
2026-07-03 OMA670 - Jul 3, 16:50 UTCJul 3, 17:40 UTC50m
2026-07-03 OMA669 - Jul 3, 14:30 UTCJul 3, 15:25 UTC55m
2026-07-02 OMA832 - Jul 2, 17:50 UTCJul 3, 08:15 UTC14h 25m
2026-07-02 OMA831 - Jul 2, 08:05 UTCJul 2, 18:10 UTC10h 5m
2026-07-01 OMA612 DXB → MCT Jul 1, 18:45 UTCJul 1, 19:10 UTC25m
2026-07-01 OMA611 MCT → DXB Jul 1, 16:35 UTCJul 1, 17:05 UTC30m
2026-07-01 OMA664 DOH → MCT Jul 1, 13:20 UTCJul 1, 14:05 UTC45m
2026-07-01 OMA663 MCT → DOH Jul 1, 11:00 UTCJul 1, 11:50 UTC50m
2026-07-01 OMA282 - Jul 1, 04:45 UTCJul 1, 06:00 UTC1h 15m
2026-07-01 OMA281 - Jul 1, 01:50 UTCJul 1, 03:20 UTC1h 30m
2026-06-30 OMA612 DXB → MCT Jun 30, 18:35 UTCJun 30, 19:00 UTC25m
2026-06-30 OMA611 MCT → DXB Jun 30, 16:50 UTCJun 30, 17:15 UTC25m
2026-06-30 OMA664 DOH → MCT Jun 30, 13:20 UTCJun 30, 14:10 UTC50m
2026-06-29 OMA663 MCT → DOH Jun 29, 18:44 UTCJun 30, 11:50 UTC17h 6m
2026-06-29 OMA681 - Jun 29, 15:19 UTCJun 30, 11:50 UTC20h 31m
2026-06-29 OMA204 - Jun 29, 11:39 UTCJun 29, 12:00 UTC20m
2026-06-29 OMA203 - Jun 29, 09:14 UTCJun 29, 10:15 UTC1h 0m
2026-06-28 OMA604 - Jun 28, 07:14 UTCJun 28, 07:34 UTC20m
2026-06-28 OMA603 - Jun 28, 04:55 UTCJun 28, 05:20 UTC25m
2026-06-27 OMA124 - Jun 27, 19:09 UTCJun 28, 01:10 UTC6h 0m
2026-06-27 OMA123 - Jun 27, 10:00 UTCJun 27, 16:20 UTC6h 20m
2026-06-27 OMA604 - Jun 27, 07:15 UTCJun 27, 07:39 UTC25m
2026-06-27 OMA603 - Jun 27, 04:54 UTCJun 27, 05:19 UTC25m
2026-06-26 OMA685 - Jun 26, 22:14 UTCJun 27, 02:04 UTC3h 50m
2026-06-26 OMA670 DOH → MCT Jun 26, 16:49 UTCJun 26, 17:40 UTC50m

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-MI page for operator, model, and routing details .

Mode-S 70C103 frequently asked

What is Mode-S code 70C103?
70C103 is an ICAO 24-bit transponder address. Allocated to Oman. Assigned to A4O-MI.
Where is Mode-S 70C103 registered?
Mode-S code 70C103 is allocated to Oman (OM). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 70C103 broadcasting right now?
No active broadcast right now. Last signal was 1d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 70C103, octal 34140403, decimal 7,389,443.
What flights does 70C103 operate?
Mode-S 70C103 has broadcast 20 distinct callsigns, including OMA225, OMA223, OMA833, OMA681, OMA612.