Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

8832CF

ICAO 24-bit transponder address · allocated to Thailand

Currently assigned to HS-LVO · BOEING 737-900

Hex
8832CF
Octal
42031317
Decimal
8,925,903
Country
TH
Tail
HS-LVO
Type
B739
No current signal · last broadcast 15h ago
Flights observed
337
Distinct callsigns
20
Country
TH
Last broadcast
15h ago

Last known position

Most recent position reported by Mode-S 8832CF.

Country allocation

The ICAO 24-bit address 8832CF 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
TLM392 Thai Lion Air 49 2026-07-03
TLM393 - 44 2026-07-03
TLM511 - 16 2026-07-11
TLM513 Thai Lion Air 15 2026-06-09
TLM512 Thai Lion Air 15 2026-06-09
TLM510 - 15 2026-07-11
TLM705 - 9 2026-06-23
TLM218 Thai Lion Air 9 2026-05-26
TLM719 Thai Lion Air 8 2026-06-04
TLM813 - 7 2026-07-13
TLM735 - 7 2026-07-11
TLM219 Thai Lion Air 7 2026-05-26
TLM962 Thai Lion Air 6 2026-05-07
TLM757 - 6 2026-07-13
TLM734 - 6 2026-07-11
TLM704 - 6 2026-07-14
TLM807 - 5 2026-06-13
TLM365 Thai Lion Air 5 2026-06-12
TLM364 Thai Lion Air 5 2026-06-12
TLM806 Thai Lion Air 4 2026-05-23

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 TLM704 - Jul 14, 01:40 UTCJul 14, 04:55 UTC3h 15m
2026-07-13 TLM813 - Jul 13, 13:30 UTCJul 13, 13:50 UTC20m
2026-07-13 TLM812 - Jul 13, 10:25 UTCJul 13, 11:10 UTC45m
2026-07-13 TLM757 - Jul 13, 08:40 UTCJul 13, 09:15 UTC35m
2026-07-13 TLM756 - Jul 13, 05:40 UTCJul 13, 06:25 UTC45m
2026-07-12 TLM405 - Jul 12, 01:35 UTCJul 12, 05:20 UTC3h 45m
2026-07-11 TLM813 - Jul 11, 13:30 UTCJul 11, 13:45 UTC15m
2026-07-11 TLM812 - Jul 11, 10:30 UTCJul 11, 11:15 UTC45m
2026-07-11 TLM511 - Jul 11, 06:40 UTCJul 11, 07:35 UTC55m
2026-07-11 TLM510 - Jul 11, 04:35 UTCJul 11, 05:31 UTC55m
2026-07-11 TLM735 - Jul 11, 02:50 UTCJul 11, 03:20 UTC30m
2026-07-11 TLM734 - Jul 11, 00:40 UTCJul 11, 01:10 UTC30m
2026-07-09 TLM511 - Jul 9, 06:40 UTCJul 9, 07:35 UTC55m
2026-07-09 TLM510 - Jul 9, 04:45 UTCJul 9, 05:35 UTC50m
2026-07-08 TLM813 - Jul 8, 10:10 UTCJul 8, 14:00 UTC3h 50m
2026-07-08 TLM756 - Jul 8, 05:40 UTCJul 8, 08:45 UTC3h 5m
2026-07-07 TLM704 - Jul 7, 01:35 UTCJul 7, 04:45 UTC3h 10m
2026-07-06 TLM715 - Jul 6, 08:05 UTCJul 6, 11:15 UTC3h 10m
2026-07-06 TLM704 - Jul 6, 01:50 UTCJul 6, 05:00 UTC3h 10m
2026-07-05 TLM724 - Jul 5, 12:50 UTCJul 6, 00:35 UTC11h 45m
2026-07-04 TLM511 - Jul 4, 06:40 UTCJul 4, 07:30 UTC50m
2026-07-04 TLM510 - Jul 4, 04:40 UTCJul 4, 05:30 UTC50m
2026-07-04 TLM601 - Jul 4, 01:00 UTCJul 4, 03:30 UTC2h 30m
2026-07-03 TLM393 - Jul 3, 13:50 UTCJul 3, 16:45 UTC2h 55m
2026-07-03 TLM393 - Jul 3, 08:05 UTCJul 3, 12:10 UTC4h 5m
2026-07-03 TLM392 KHH → CTS Jul 3, 02:40 UTCJul 3, 06:40 UTC4h 0m
2026-07-03 TLM392 KHH → CTS Jul 3, 01:00 UTCJul 3, 01:20 UTC20m
2026-07-02 TLM392 KHH → CTS Jul 2, 22:10 UTCJul 2, 22:45 UTC35m
2026-07-02 TLM515 - Jul 2, 13:20 UTCJul 2, 14:15 UTC55m
2026-07-02 TLM514 - Jul 2, 11:30 UTCJul 2, 12:05 UTC35m
2026-07-02 TLM756 - Jul 2, 06:25 UTCJul 2, 09:50 UTC3h 25m
2026-07-01 TLM393 - Jul 1, 14:25 UTCJul 1, 14:40 UTC15m
2026-07-01 TLM393 - Jul 1, 09:05 UTCJul 1, 13:10 UTC4h 5m
2026-07-01 TLM392 KHH → CTS Jul 1, 04:05 UTCJul 1, 07:40 UTC3h 35m
2026-07-01 TLM392 KHH → CTS Jul 1, 01:00 UTCJul 1, 01:25 UTC25m
2026-06-30 TLM392 KHH → CTS Jun 30, 22:10 UTCJun 30, 22:40 UTC30m
2026-06-29 TLM753 - Jun 29, 00:54 UTCJun 29, 04:04 UTC3h 10m
2026-06-28 TLM511 - Jun 28, 07:54 UTCJun 28, 08:44 UTC50m
2026-06-28 TLM510 - Jun 28, 06:05 UTCJun 28, 06:59 UTC55m
2026-06-26 TLM393 - Jun 26, 13:45 UTCJun 26, 16:35 UTC2h 50m
2026-06-26 TLM393 - Jun 26, 08:20 UTCJun 26, 12:39 UTC4h 20m
2026-06-26 TLM392 KHH → CTS Jun 26, 02:44 UTCJun 26, 06:25 UTC3h 40m
2026-06-25 TLM392 KHH → CTS Jun 25, 22:04 UTCJun 26, 01:20 UTC3h 15m
2026-06-24 TLM393 - Jun 24, 13:50 UTCJun 24, 16:40 UTC2h 50m
2026-06-24 TLM393 - Jun 24, 08:24 UTCJun 24, 12:30 UTC4h 5m
2026-06-24 TLM392 KHH → CTS Jun 24, 02:45 UTCJun 24, 06:35 UTC3h 50m
2026-06-23 TLM392 KHH → CTS Jun 23, 22:10 UTCJun 24, 01:19 UTC3h 10m
2026-06-23 TLM705 - Jun 23, 01:40 UTCJun 23, 04:50 UTC3h 10m
2026-06-22 TLM393 - Jun 22, 13:49 UTCJun 22, 16:45 UTC2h 55m
2026-06-22 TLM393 - Jun 22, 08:00 UTCJun 22, 12:10 UTC4h 10m

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

Mode-S 8832CF frequently asked

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