Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

70C102

ICAO 24-bit transponder address · allocated to Oman

Currently assigned to A4O-MH · BOEING 737 MAX 8

Hex
70C102
Octal
34140402
Decimal
7,389,442
Country
OM
Tail
A4O-MH
Type
B38M
No current signal · last broadcast 1h ago
Flights observed
153
Distinct callsigns
20
Country
OM
Last broadcast
1h ago

Last known position

Most recent position reported by Mode-S 70C102.

Country allocation

The ICAO 24-bit address 70C102 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
OMA833 - 10 2026-07-13
OMA823 - 7 2026-07-11
OMA684 - 7 2026-07-04
OMA824 - 6 2026-07-12
OMA281 Oman Air 6 2026-06-02
OMA282 Oman Air 5 2026-06-03
OMA253 - 5 2026-06-15
OMA252 - 5 2026-06-18
OMA225 - 5 2026-07-04
OMA831 Oman Air 4 2026-06-29
OMA695 Oman Air 4 2026-06-26
OMA226 Oman Air 4 2026-06-08
OMA167 - 4 2026-07-09
OMA123 - 4 2026-06-19
OMA696 Oman Air 3 2026-06-26
OMA683 Oman Air 3 2026-06-08
OMA681 Oman Air 3 2026-06-01
OMA664 Oman Air 3 2026-07-02
OMA663 Oman Air 3 2026-07-02
OMA661 Oman Air 3 2026-06-24

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 OMA184 SVO → SVO Jul 14, 20:50 UTCJul 14, 21:15 UTC25m
2026-07-13 OMA833 - Jul 13, 21:35 UTCJul 14, 07:55 UTC10h 20m
2026-07-12 OMA824 - Jul 12, 13:45 UTCJul 12, 18:30 UTC4h 45m
2026-07-11 OMA823 - Jul 11, 16:35 UTCJul 12, 12:01 UTC19h 25m
2026-07-11 OMA892 - Jul 11, 13:10 UTCJul 12, 12:01 UTC22h 50m
2026-07-11 OMA891 - Jul 11, 05:50 UTCJul 11, 11:30 UTC5h 40m
2026-07-10 OMA154 - Jul 10, 19:30 UTCJul 11, 01:40 UTC6h 10m
2026-07-10 OMA153 - Jul 10, 10:15 UTCJul 10, 16:55 UTC6h 40m
2026-07-09 OMA833 - Jul 9, 20:20 UTCJul 10, 06:30 UTC10h 10m
2026-07-09 OMA168 - Jul 9, 12:40 UTCJul 9, 16:40 UTC4h 0m
2026-07-09 OMA167 - Jul 9, 10:35 UTCJul 9, 10:55 UTC20m
2026-07-09 OMA167 - Jul 9, 07:20 UTCJul 9, 08:20 UTC1h 0m
2026-07-08 OMA414 - Jul 8, 14:10 UTCJul 8, 16:55 UTC2h 45m
2026-07-08 OMA413 - Jul 8, 09:45 UTCJul 8, 12:40 UTC2h 55m
2026-07-07 OMA168 - Jul 7, 12:35 UTCJul 7, 16:40 UTC4h 5m
2026-07-07 OMA167 - Jul 7, 10:55 UTCJul 7, 11:05 UTC10m
2026-07-07 OMA167 - Jul 7, 07:20 UTCJul 7, 10:05 UTC2h 45m
2026-07-06 OMA824 - Jul 6, 13:40 UTCJul 6, 18:20 UTC4h 40m
2026-07-05 OMA823 - Jul 5, 16:55 UTCJul 6, 12:00 UTC19h 5m
2026-07-05 OMA823 - Jul 5, 13:40 UTCJul 6, 12:00 UTC22h 20m
2026-07-04 OMA412 - Jul 4, 21:05 UTCJul 5, 11:50 UTC14h 45m
2026-07-04 OMA411 - Jul 4, 17:05 UTCJul 4, 20:00 UTC2h 55m
2026-07-04 OMA684 - Jul 4, 03:05 UTCJul 4, 15:10 UTC12h 5m
2026-07-04 OMA225 - Jul 4, 01:40 UTCJul 4, 01:50 UTC10m
2026-07-03 OMA824 - Jul 3, 13:40 UTCJul 3, 18:25 UTC4h 45m
2026-07-03 OMA823 - Jul 3, 06:30 UTCJul 3, 11:35 UTC5h 5m
2026-07-02 OMA182 - Jul 2, 16:45 UTCJul 3, 02:50 UTC10h 5m
2026-07-02 OMA664 DOH → MCT Jul 2, 13:20 UTCJul 2, 14:05 UTC45m
2026-07-02 OMA663 MCT → DOH Jul 2, 11:00 UTCJul 2, 11:50 UTC50m
2026-07-01 OMA406 - Jul 1, 16:20 UTCJul 1, 19:30 UTC3h 10m
2026-07-01 OMA405 - Jul 1, 11:15 UTCJul 1, 14:20 UTC3h 5m
2026-06-29 OMA831 MCT → HKT Jun 29, 07:50 UTCJun 29, 18:10 UTC10h 20m
2026-06-28 OMA831 MCT → HKT Jun 28, 17:04 UTCJun 29, 08:39 UTC15h 35m
2026-06-28 OMA824 - Jun 28, 13:45 UTCJun 29, 08:39 UTC18h 55m
2026-06-28 OMA823 - Jun 28, 06:40 UTCJun 28, 11:50 UTC5h 10m
2026-06-27 OMA408 - Jun 27, 23:10 UTCJun 28, 02:25 UTC3h 15m
2026-06-27 OMA407 - Jun 27, 18:04 UTCJun 27, 21:15 UTC3h 10m
2026-06-27 OMA684 RUH → MCT Jun 27, 10:29 UTCJun 27, 14:54 UTC4h 25m
2026-06-26 OMA696 DMM → MCT Jun 26, 18:49 UTCJun 26, 19:45 UTC55m
2026-06-26 OMA695 MCT → DMM Jun 26, 16:24 UTCJun 26, 17:29 UTC1h 5m
2026-06-26 OMA254 - Jun 26, 10:15 UTCJun 26, 11:49 UTC1h 35m
2026-06-25 OMA408 - Jun 25, 23:09 UTCJun 26, 08:30 UTC9h 20m
2026-06-25 OMA407 - Jun 25, 18:10 UTCJun 25, 21:35 UTC3h 25m
2026-06-25 OMA242 - Jun 25, 03:34 UTCJun 25, 15:24 UTC11h 50m
2026-06-25 OMA241 - Jun 25, 01:19 UTCJun 25, 01:59 UTC40m
2026-06-24 OMA661 MCT → DOH Jun 24, 10:35 UTCJun 24, 17:20 UTC6h 45m
2026-06-24 OMA245 - Jun 24, 08:39 UTCJun 24, 09:19 UTC40m
2026-06-22 OMA833 - Jun 22, 21:35 UTCJun 23, 07:40 UTC10h 5m
2026-06-22 OMA670 DOH → MCT Jun 22, 16:54 UTCJun 22, 17:44 UTC50m
2026-06-22 OMA669 - Jun 22, 14:24 UTCJun 22, 15:14 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-MH page for operator, model, and routing details .

Mode-S 70C102 frequently asked

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