Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

882DA5

ICAO 24-bit transponder address · allocated to Thailand

Currently assigned to HS-KME · BOEING 737-800

Hex
882DA5
Octal
42026645
Decimal
8,924,581
Country
TH
Tail
HS-KME
Type
B738
No current signal · last broadcast 13d ago
Flights observed
235
Distinct callsigns
13
Country
TH
Last broadcast
13d ago

Last known position

Most recent position reported by Mode-S 882DA5.

Country allocation

The ICAO 24-bit address 882DA5 falls within the block assigned to Thailand (TH) by ICAO Annex 10, Volume III. Every aircraft registered in Thailand 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 13 distinct

Callsign Airline Flights Last seen
KMI713 - 48 2026-06-21
KMI714 - 46 2026-06-21
KMI525 - 42 2026-07-04
KMI526 K-Mile Air 30 2026-07-04
KMI725 - 15 2026-06-22
KMI804 - 12 2026-06-21
KMI801 K-Mile Air 12 2026-06-21
KMI803 - 9 2026-06-20
KMI726 - 9 2026-06-22
KMI528 - 5 2026-06-29
KMI802 - 4 2026-05-29
KMI851 - 2 2026-07-05
MKI714 - 1 2026-05-21

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-05 KMI851 - Jul 5, 02:30 UTCJul 5, 02:50 UTC20m
2026-07-04 KMI851 - Jul 4, 23:45 UTCJul 5, 01:55 UTC2h 10m
2026-07-04 KMI526 HKG → BKK Jul 4, 20:50 UTCJul 4, 22:10 UTC1h 20m
2026-07-04 KMI526 HKG → BKK Jul 4, 19:50 UTCJul 4, 20:05 UTC15m
2026-07-04 KMI525 - Jul 4, 17:25 UTCJul 4, 17:30 UTC5m
2026-07-04 KMI525 - Jul 4, 15:55 UTCJul 4, 16:35 UTC40m
2026-07-04 KMI525 - Jul 4, 00:20 UTCJul 4, 01:45 UTC1h 25m
2026-07-03 KMI526 HKG → BKK Jul 3, 21:55 UTCJul 3, 22:20 UTC25m
2026-07-03 KMI526 HKG → BKK Jul 3, 20:00 UTCJul 3, 20:15 UTC15m
2026-07-03 KMI525 - Jul 3, 16:05 UTCJul 3, 17:45 UTC1h 40m
2026-07-02 KMI525 - Jul 2, 23:30 UTCJul 3, 00:55 UTC1h 25m
2026-07-02 KMI526 HKG → BKK Jul 2, 20:55 UTCJul 2, 22:20 UTC1h 25m
2026-07-02 KMI526 HKG → BKK Jul 2, 20:00 UTCJul 2, 20:15 UTC15m
2026-07-02 KMI525 - Jul 2, 16:45 UTCJul 2, 17:10 UTC25m
2026-07-02 KMI525 - Jul 2, 15:45 UTCJul 2, 16:10 UTC25m
2026-07-02 KMI525 - Jul 2, 00:50 UTCJul 2, 01:00 UTC10m
2026-07-01 KMI525 - Jul 1, 23:45 UTCJul 1, 23:55 UTC10m
2026-07-01 KMI526 HKG → BKK Jul 1, 20:45 UTCJul 1, 21:00 UTC15m
2026-07-01 KMI526 HKG → BKK Jul 1, 20:00 UTCJul 1, 20:15 UTC15m
2026-07-01 KMI525 - Jul 1, 15:55 UTCJul 1, 17:15 UTC1h 20m
2026-06-30 KMI525 - Jun 30, 23:45 UTCJul 1, 01:10 UTC1h 25m
2026-06-30 KMI526 HKG → BKK Jun 30, 19:55 UTCJun 30, 22:10 UTC2h 15m
2026-06-30 KMI525 - Jun 30, 15:50 UTCJun 30, 17:15 UTC1h 25m
2026-06-29 KMI525 - Jun 29, 23:49 UTCJun 30, 01:19 UTC1h 30m
2026-06-29 KMI526 HKG → BKK Jun 29, 20:54 UTCJun 29, 22:19 UTC1h 25m
2026-06-29 KMI526 HKG → BKK Jun 29, 20:00 UTCJun 29, 20:09 UTC10m
2026-06-29 KMI528 - Jun 29, 17:10 UTCJun 29, 17:30 UTC20m
2026-06-29 KMI528 - Jun 29, 16:15 UTCJun 29, 16:35 UTC20m
2026-06-28 KMI528 - Jun 28, 00:09 UTCJun 28, 01:29 UTC1h 20m
2026-06-27 KMI526 HKG → BKK Jun 27, 20:49 UTCJun 27, 22:20 UTC1h 30m
2026-06-27 KMI526 HKG → BKK Jun 27, 20:04 UTCJun 27, 20:14 UTC10m
2026-06-27 KMI525 - Jun 27, 15:45 UTCJun 27, 17:14 UTC1h 30m
2026-06-27 KMI525 - Jun 27, 00:39 UTCJun 27, 02:04 UTC1h 25m
2026-06-26 KMI526 HKG → BKK Jun 26, 21:20 UTCJun 26, 22:55 UTC1h 35m
2026-06-26 KMI526 HKG → BKK Jun 26, 20:40 UTCJun 26, 20:50 UTC10m
2026-06-26 KMI525 - Jun 26, 17:09 UTCJun 26, 17:29 UTC20m
2026-06-26 KMI525 - Jun 26, 16:05 UTCJun 26, 16:35 UTC30m
2026-06-25 KMI525 - Jun 25, 23:44 UTCJun 26, 01:10 UTC1h 25m
2026-06-25 KMI526 HKG → BKK Jun 25, 20:09 UTCJun 25, 22:24 UTC2h 15m
2026-06-25 KMI525 - Jun 25, 15:59 UTCJun 25, 17:25 UTC1h 25m
2026-06-24 KMI525 - Jun 24, 23:45 UTCJun 25, 01:04 UTC1h 20m
2026-06-24 KMI526 HKG → BKK Jun 24, 20:30 UTCJun 24, 22:04 UTC1h 35m
2026-06-24 KMI526 HKG → BKK Jun 24, 19:49 UTCJun 24, 19:59 UTC10m
2026-06-24 KMI525 - Jun 24, 17:05 UTCJun 24, 17:40 UTC35m
2026-06-24 KMI525 - Jun 24, 15:59 UTCJun 24, 16:29 UTC30m
2026-06-24 KMI525 - Jun 24, 00:44 UTCJun 24, 01:04 UTC20m
2026-06-23 KMI525 - Jun 23, 23:39 UTCJun 23, 23:55 UTC15m
2026-06-23 KMI526 HKG → BKK Jun 23, 19:44 UTCJun 23, 22:05 UTC2h 20m
2026-06-23 KMI525 - Jun 23, 17:04 UTCJun 23, 17:34 UTC30m
2026-06-23 KMI525 - Jun 23, 16:05 UTCJun 23, 16:29 UTC25m

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

Mode-S 882DA5 frequently asked

What is Mode-S code 882DA5?
882DA5 is an ICAO 24-bit transponder address. Allocated to Thailand. Assigned to HS-KME.
Where is Mode-S 882DA5 registered?
Mode-S code 882DA5 is allocated to Thailand (TH). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 882DA5 broadcasting right now?
No active broadcast right now. Last signal was 13d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 882DA5, octal 42026645, decimal 8,924,581.
What flights does 882DA5 operate?
Mode-S 882DA5 has broadcast 13 distinct callsigns, including KMI713, KMI714, KMI525, KMI526, KMI725.