sensors Mode-S transponder

8832D5

ICAO 24-bit transponder address · allocated to Thailand

Currently assigned to HS-LVU · BOEING 737-900

Hex
8832D5
Octal
42031325
Decimal
8,925,909
Country
TH
Tail
HS-LVU
Type
B739
No current signal · last broadcast 7h ago
Flights observed
348
Distinct callsigns
20
Country
TH
Last broadcast
7h ago

Last known position

Most recent position reported by Mode-S 8832D5.

Country allocation

The ICAO 24-bit address 8832D5 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 20 distinct

Callsign Airline Flights Last seen
TLM390 - 16 2026-07-04
TLM391 - 14 2026-07-04
TLM364 - 14 2026-06-21
TLM397 - 12 2026-07-09
TLM365 - 12 2026-06-21
TLM396 - 11 2026-07-09
TLM399 - 9 2026-07-03
TLM217 Thai Lion Air 8 2026-05-27
TLM515 - 7 2026-07-12
TLM514 - 7 2026-07-12
TLM513 - 7 2026-07-14
TLM707 - 6 2026-06-18
TLM605 - 6 2026-07-05
TLM604 - 6 2026-07-05
TLM521 Thai Lion Air 6 2026-06-26
TLM520 - 6 2026-06-26
TLM508 - 6 2026-07-14
TLM398 Thai Lion Air 6 2026-07-03
TLM920 Thai Lion Air 5 2026-05-30
TLM715 Thai Lion Air 5 2026-06-01

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 TLM716 - Jul 14, 11:20 UTCJul 14, 14:35 UTC3h 15m
2026-07-14 TLM513 - Jul 14, 08:20 UTCJul 14, 09:20 UTC1h 0m
2026-07-14 TLM508 - Jul 14, 04:05 UTCJul 14, 05:20 UTC1h 15m
2026-07-12 TLM515 - Jul 12, 11:35 UTCJul 12, 12:25 UTC50m
2026-07-12 TLM514 - Jul 12, 09:45 UTCJul 12, 10:40 UTC55m
2026-07-12 TLM511 - Jul 12, 06:30 UTCJul 12, 07:25 UTC55m
2026-07-12 TLM510 - Jul 12, 04:35 UTCJul 12, 05:25 UTC50m
2026-07-12 TLM734 - Jul 12, 00:35 UTCJul 12, 03:10 UTC2h 35m
2026-07-11 TLM105 - Jul 11, 14:05 UTCJul 11, 16:05 UTC2h 0m
2026-07-11 TLM104 - Jul 11, 10:35 UTCJul 11, 12:30 UTC1h 55m
2026-07-10 TLM515 - Jul 10, 11:55 UTCJul 10, 12:45 UTC50m
2026-07-10 TLM514 - Jul 10, 10:10 UTCJul 10, 11:00 UTC50m
2026-07-10 TLM509 - Jul 10, 06:20 UTCJul 10, 07:10 UTC50m
2026-07-10 TLM508 - Jul 10, 04:20 UTCJul 10, 05:15 UTC55m
2026-07-09 TLM397 - Jul 9, 09:20 UTCJul 9, 12:25 UTC3h 5m
2026-07-09 TLM397 KIX → TPE Jul 9, 05:20 UTCJul 9, 07:45 UTC2h 25m
2026-07-09 TLM396 - Jul 9, 03:10 UTCJul 9, 04:00 UTC50m
2026-07-09 TLM396 - Jul 9, 01:35 UTCJul 9, 01:50 UTC15m
2026-07-08 TLM396 - Jul 8, 20:15 UTCJul 8, 23:35 UTC3h 20m
2026-07-06 TLM756 - Jul 6, 05:30 UTCJul 6, 08:40 UTC3h 10m
2026-07-06 TLM533 - Jul 6, 03:50 UTCJul 6, 04:20 UTC30m
2026-07-06 TLM532 - Jul 6, 01:20 UTCJul 6, 02:20 UTC1h 0m
2026-07-05 TLM647 - Jul 5, 10:35 UTCJul 5, 11:15 UTC40m
2026-07-05 TLM646 - Jul 5, 08:55 UTCJul 5, 09:30 UTC35m
2026-07-05 TLM605 - Jul 5, 06:10 UTCJul 5, 06:50 UTC40m
2026-07-05 TLM604 - Jul 5, 04:25 UTCJul 5, 05:05 UTC40m
2026-07-04 TLM717 - Jul 4, 12:05 UTCJul 4, 15:25 UTC3h 20m
2026-07-04 TLM391 - Jul 4, 05:50 UTCJul 4, 08:45 UTC2h 55m
2026-07-04 TLM391 - Jul 4, 03:35 UTCJul 4, 04:25 UTC50m
2026-07-04 TLM390 - Jul 4, 01:35 UTCJul 4, 01:45 UTC10m
2026-07-04 TLM390 - Jul 4, 00:20 UTCJul 4, 00:45 UTC25m
2026-07-03 TLM390 - Jul 3, 20:00 UTCJul 3, 23:05 UTC3h 5m
2026-07-03 TLM399 - Jul 3, 09:10 UTCJul 3, 12:25 UTC3h 15m
2026-07-03 TLM399 - Jul 3, 07:15 UTCJul 3, 07:45 UTC30m
2026-07-03 TLM399 - Jul 3, 05:10 UTCJul 3, 05:55 UTC45m
2026-07-03 TLM398 DMK → TPE Jul 3, 01:00 UTCJul 3, 03:10 UTC2h 10m
2026-07-02 TLM398 DMK → TPE Jul 2, 20:15 UTCJul 2, 23:40 UTC3h 25m
2026-06-30 TLM397 - Jun 30, 08:55 UTCJun 30, 12:00 UTC3h 5m
2026-06-30 TLM397 KIX → TPE Jun 30, 04:50 UTCJun 30, 07:25 UTC2h 35m
2026-06-30 TLM396 - Jun 30, 01:30 UTCJun 30, 03:35 UTC2h 5m
2026-06-29 TLM396 - Jun 29, 20:15 UTCJun 29, 23:34 UTC3h 20m
2026-06-29 TLM545 - Jun 29, 13:34 UTCJun 29, 14:29 UTC55m
2026-06-29 TLM544 - Jun 29, 11:35 UTCJun 29, 12:34 UTC1h 0m
2026-06-29 TLM513 - Jun 29, 08:24 UTCJun 29, 09:20 UTC55m
2026-06-29 TLM512 - Jun 29, 06:14 UTCJun 29, 07:05 UTC50m
2026-06-29 TLM704 - Jun 29, 01:39 UTCJun 29, 05:04 UTC3h 25m
2026-06-28 TLM105 - Jun 28, 13:59 UTCJun 28, 15:55 UTC1h 55m
2026-06-28 TLM104 - Jun 28, 10:19 UTCJun 28, 12:29 UTC2h 10m
2026-06-28 TLM391 - Jun 28, 05:55 UTCJun 28, 08:50 UTC2h 55m
2026-06-28 TLM391 KHH → KHH Jun 28, 00:39 UTCJun 28, 04:55 UTC4h 15m

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

Mode-S 8832D5 frequently asked

What is Mode-S code 8832D5?
8832D5 is an ICAO 24-bit transponder address. Allocated to Thailand. Assigned to HS-LVU.
Where is Mode-S 8832D5 registered?
Mode-S code 8832D5 is allocated to Thailand (TH). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 8832D5 broadcasting right now?
No active broadcast right now. Last signal was 7h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 8832D5, octal 42031325, decimal 8,925,909.
What flights does 8832D5 operate?
Mode-S 8832D5 has broadcast 20 distinct callsigns, including TLM390, TLM391, TLM364, TLM397, TLM365.