sensors Mode-S transponder

8A0A64

ICAO 24-bit transponder address · allocated to Indonesia

Currently assigned to PK-MGI · BOEING 737-800

Hex
8A0A64
Octal
42405144
Decimal
9,046,628
Country
ID
Tail
PK-MGI
Type
B738
No current signal · last broadcast 1h ago
Flights observed
134
Distinct callsigns
4
Country
ID
Last broadcast
1h ago

Last known position

Most recent position reported by Mode-S 8A0A64.

Country allocation

The ICAO 24-bit address 8A0A64 falls within the block assigned to Indonesia (ID) by ICAO Annex 10, Volume III. Every aircraft registered in Indonesia 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 4 distinct

Callsign Airline Flights Last seen
MYU6012 - 57 2026-07-13
MYU6011 - 51 2026-07-14
MYU6014 - 25 2026-06-22
6011 - 1 2026-07-13

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 MYU6011 - Jul 14, 00:35 UTCJul 14, 00:55 UTC20m
2026-07-13 6011 - Jul 13, 20:35 UTCJul 13, 20:50 UTC15m
2026-07-13 MYU6012 - Jul 13, 17:50 UTCJul 13, 18:10 UTC20m
2026-07-13 MYU6012 - Jul 13, 13:30 UTCJul 13, 15:05 UTC1h 35m
2026-07-09 MYU6011 - Jul 9, 01:40 UTCJul 9, 01:55 UTC15m
2026-07-08 MYU6011 - Jul 8, 21:35 UTCJul 8, 21:50 UTC15m
2026-07-08 MYU6012 - Jul 8, 17:15 UTCJul 8, 17:40 UTC25m
2026-07-08 MYU6012 - Jul 8, 13:00 UTCJul 8, 14:35 UTC1h 35m
2026-07-08 MYU6011 - Jul 8, 00:35 UTCJul 8, 00:45 UTC10m
2026-07-07 MYU6011 - Jul 7, 20:30 UTCJul 7, 20:45 UTC15m
2026-07-07 MYU6012 - Jul 7, 17:30 UTCJul 7, 17:50 UTC20m
2026-07-07 MYU6012 - Jul 7, 13:10 UTCJul 7, 14:45 UTC1h 35m
2026-07-06 MYU6011 - Jul 6, 20:25 UTCJul 6, 20:40 UTC15m
2026-07-06 MYU6012 - Jul 6, 17:50 UTCJul 6, 18:10 UTC20m
2026-07-06 MYU6012 - Jul 6, 14:25 UTCJul 6, 14:50 UTC25m
2026-06-22 MYU6014 - Jun 22, 10:55 UTCJun 22, 12:25 UTC1h 30m
2026-06-18 MYU6011 - Jun 18, 00:40 UTCJun 18, 00:55 UTC15m
2026-06-17 MYU6011 - Jun 17, 20:40 UTCJun 17, 20:55 UTC15m
2026-06-17 MYU6012 - Jun 17, 17:30 UTCJun 17, 17:45 UTC15m
2026-06-17 MYU6012 - Jun 17, 13:10 UTCJun 17, 14:40 UTC1h 30m
2026-06-17 MYU6011 HKG → HKG Jun 17, 00:50 UTCJun 17, 01:05 UTC15m
2026-06-16 MYU6011 HKG → HKG Jun 16, 20:45 UTCJun 16, 21:00 UTC15m
2026-06-16 MYU6012 - Jun 16, 18:05 UTCJun 16, 18:20 UTC15m
2026-06-16 MYU6012 - Jun 16, 14:39 UTCJun 16, 14:50 UTC10m
2026-06-16 MYU6014 - Jun 16, 10:35 UTCJun 16, 12:14 UTC1h 40m
2026-06-15 MYU6011 HKG → HKG Jun 15, 20:59 UTCJun 15, 21:14 UTC15m
2026-06-15 MYU6012 - Jun 15, 17:59 UTCJun 15, 18:15 UTC15m
2026-06-15 MYU6014 - Jun 15, 10:20 UTCJun 15, 14:50 UTC4h 30m
2026-06-11 MYU6011 HKG → HKG Jun 11, 00:30 UTCJun 11, 00:45 UTC15m
2026-06-10 MYU6011 HKG → HKG Jun 10, 20:30 UTCJun 10, 20:45 UTC15m
2026-06-10 MYU6012 - Jun 10, 17:55 UTCJun 10, 18:20 UTC25m
2026-06-10 MYU6012 - Jun 10, 13:35 UTCJun 10, 15:05 UTC1h 30m
2026-06-10 MYU6011 HKG → HKG Jun 10, 00:45 UTCJun 10, 01:00 UTC15m
2026-06-09 MYU6011 HKG → HKG Jun 9, 20:40 UTCJun 9, 20:55 UTC15m
2026-06-09 MYU6012 - Jun 9, 18:20 UTCJun 9, 18:45 UTC25m
2026-06-09 MYU6012 - Jun 9, 13:15 UTCJun 9, 14:50 UTC1h 35m
2026-06-09 MYU6011 HKG → HKG Jun 9, 00:50 UTCJun 9, 01:10 UTC20m
2026-06-08 MYU6011 HKG → HKG Jun 8, 20:50 UTCJun 8, 21:00 UTC10m
2026-06-08 MYU6012 - Jun 8, 17:45 UTCJun 8, 18:10 UTC25m
2026-06-08 MYU6012 - Jun 8, 13:25 UTCJun 8, 14:55 UTC1h 30m
2026-06-04 MYU6011 HKG → HKG Jun 4, 00:25 UTCJun 4, 00:45 UTC20m
2026-06-03 MYU6011 HKG → HKG Jun 3, 20:30 UTCJun 3, 20:45 UTC15m
2026-06-03 MYU6012 - Jun 3, 17:45 UTCJun 3, 18:05 UTC20m
2026-06-03 MYU6012 - Jun 3, 13:25 UTCJun 3, 14:55 UTC1h 30m
2026-06-02 MYU6011 HKG → HKG Jun 2, 20:20 UTCJun 2, 20:30 UTC10m
2026-06-02 MYU6012 - Jun 2, 17:25 UTCJun 2, 17:50 UTC25m
2026-06-02 MYU6012 - Jun 2, 13:05 UTCJun 2, 14:45 UTC1h 40m
2026-06-01 MYU6011 HKG → HKG Jun 1, 20:50 UTCJun 1, 21:05 UTC15m
2026-06-01 MYU6012 - Jun 1, 18:35 UTCJun 1, 18:55 UTC20m
2026-06-01 MYU6012 - Jun 1, 14:20 UTCJun 1, 15:50 UTC1h 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 PK-MGI page for operator, model, and routing details .

Mode-S 8A0A64 frequently asked

What is Mode-S code 8A0A64?
8A0A64 is an ICAO 24-bit transponder address. Allocated to Indonesia. Assigned to PK-MGI.
Where is Mode-S 8A0A64 registered?
Mode-S code 8A0A64 is allocated to Indonesia (ID). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 8A0A64 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 8A0A64, octal 42405144, decimal 9,046,628.
What flights does 8A0A64 operate?
Mode-S 8A0A64 has broadcast 4 distinct callsigns, including MYU6012, MYU6011, MYU6014, 6011.