sensors Mode-S transponder
8830F2
ICAO 24-bit transponder address · allocated to Thailand
Currently assigned to HS-LGR · BOEING 737-800
- Hex
- 8830F2
- Octal
- 42030362
- Decimal
- 8,925,426
- Country
- TH
- Tail
- HS-LGR
- Type
- B738
- Flights observed
- 183
- Distinct callsigns
- 20
- Country
- TH
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 8830F2 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 |
|---|---|---|---|
| TLM210 | Thai Lion Air | 6 | 2026-06-14 |
| TLM370 | Thai Lion Air | 5 | 2026-05-24 |
| TLM259 | Thai Lion Air | 5 | 2026-05-17 |
| TLM211 | - | 5 | 2026-06-14 |
| TLM116 | Thai Lion Air | 5 | 2026-06-19 |
| TLM965 | Thai Lion Air | 4 | 2026-05-20 |
| TLM809 | Thai Lion Air | 4 | 2026-05-02 |
| TLM364 | Thai Lion Air | 4 | 2026-05-29 |
| TLM105 | Thai Lion Air | 4 | 2026-06-12 |
| TLM104 | Thai Lion Air | 4 | 2026-06-12 |
| TLM761 | Thai Lion Air | 3 | 2026-06-05 |
| TLM755 | - | 3 | 2026-07-01 |
| TLM372 | Thai Lion Air | 3 | 2026-05-16 |
| TLM371 | Thai Lion Air | 3 | 2026-05-24 |
| TLM365 | Thai Lion Air | 3 | 2026-05-29 |
| TLM117 | - | 3 | 2026-06-20 |
| TLM101 | Thai Lion Air | 3 | 2026-05-24 |
| TLM100 | Thai Lion Air | 3 | 2026-05-24 |
| TLM964 | Thai Lion Air | 2 | 2026-05-20 |
| TLM930 | Thai Lion Air | 2 | 2026-05-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-12 | TLM714 | - | Jul 12, 08:30 UTC | Jul 12, 13:50 UTC | 5h 20m |
| 2026-07-12 | TLM707 | - | Jul 12, 06:50 UTC | Jul 12, 07:15 UTC | 25m |
| 2026-07-12 | TLM706 | - | Jul 12, 04:05 UTC | Jul 12, 04:45 UTC | 40m |
| 2026-07-08 | TLM767 | - | Jul 8, 08:00 UTC | Jul 8, 11:00 UTC | 3h 0m |
| 2026-07-08 | TLM754 | - | Jul 8, 03:20 UTC | Jul 8, 06:30 UTC | 3h 10m |
| 2026-07-07 | TLM760 | - | Jul 7, 09:25 UTC | Jul 7, 12:55 UTC | 3h 30m |
| 2026-07-01 | TLM755 | - | Jul 1, 03:20 UTC | Jul 1, 06:30 UTC | 3h 10m |
| 2026-06-26 | TLM766 | - | Jun 26, 08:00 UTC | Jun 26, 11:00 UTC | 3h 0m |
| 2026-06-26 | TLM753 | - | Jun 26, 00:59 UTC | Jun 26, 04:14 UTC | 3h 15m |
| 2026-06-20 | TLM117 | - | Jun 20, 01:09 UTC | Jun 20, 04:20 UTC | 3h 10m |
| 2026-06-19 | TLM116 | DMK → CGK | Jun 19, 14:44 UTC | Jun 19, 14:59 UTC | 15m |
| 2026-06-19 | TLM116 | DMK → CGK | Jun 19, 11:54 UTC | Jun 19, 14:09 UTC | 2h 15m |
| 2026-06-14 | TLM211 | - | Jun 14, 20:35 UTC | Jun 15, 00:35 UTC | 4h 0m |
| 2026-06-14 | TLM210 | DMK → COK | Jun 14, 15:35 UTC | Jun 14, 19:25 UTC | 3h 50m |
| 2026-06-12 | TLM105 | SIN → DMK | Jun 12, 14:05 UTC | Jun 12, 16:00 UTC | 1h 55m |
| 2026-06-12 | TLM104 | DMK → SIN | Jun 12, 10:20 UTC | Jun 12, 12:20 UTC | 2h 0m |
| 2026-06-10 | TLM755 | HKT → DMK | Jun 10, 03:25 UTC | Jun 10, 07:00 UTC | 3h 35m |
| 2026-06-05 | TLM761 | HKT → DMK | Jun 5, 10:05 UTC | Jun 5, 13:25 UTC | 3h 20m |
| 2026-06-03 | TLM7513 | HKT → DMK | Jun 3, 09:10 UTC | Jun 3, 12:45 UTC | 3h 35m |
| 2026-06-03 | TLM7512 | DMK → HKT | Jun 3, 04:55 UTC | Jun 3, 08:05 UTC | 3h 10m |
| 2026-06-03 | TLM117 | CGK → DMK | Jun 3, 00:30 UTC | Jun 3, 03:40 UTC | 3h 10m |
| 2026-06-02 | TLM116 | DMK → CGK | Jun 2, 11:10 UTC | Jun 2, 14:10 UTC | 3h 0m |
| 2026-06-01 | TLM761 | HKT → DMK | Jun 1, 09:30 UTC | Jun 1, 13:00 UTC | 3h 30m |
| 2026-05-30 | TLM930 | DMK → CKG | May 30, 13:55 UTC | May 30, 20:55 UTC | 7h 0m |
| 2026-05-30 | TLM533 | CEI → DMK | May 30, 03:15 UTC | May 30, 04:10 UTC | 55m |
| 2026-05-30 | LGR | - | May 30, 01:20 UTC | May 30, 02:10 UTC | 50m |
| 2026-05-29 | TLM365 | HKG → DMK | May 29, 12:55 UTC | May 29, 15:15 UTC | 2h 20m |
| 2026-05-29 | TLM364 | DMK → HKG | May 29, 10:55 UTC | May 29, 11:15 UTC | 20m |
| 2026-05-29 | TLM364 | DMK → HKG | May 29, 08:40 UTC | May 29, 10:15 UTC | 1h 35m |
| 2026-05-25 | TLM105 | SIN → DMK | May 25, 14:25 UTC | May 25, 16:15 UTC | 1h 50m |
| 2026-05-25 | TLM104 | DMK → SIN | May 25, 10:20 UTC | May 25, 12:25 UTC | 2h 5m |
| 2026-05-24 | TLM243 | CCU → DMK | May 24, 21:30 UTC | May 24, 23:30 UTC | 2h 0m |
| 2026-05-24 | TLM242 | DMK → CCU | May 24, 17:55 UTC | May 24, 19:55 UTC | 2h 0m |
| 2026-05-24 | TLM371 | MFM → DMK | May 24, 16:05 UTC | May 24, 16:45 UTC | 40m |
| 2026-05-24 | TLM370 | DMK → MFM | May 24, 12:55 UTC | May 24, 13:10 UTC | 15m |
| 2026-05-24 | TLM370 | DMK → MFM | May 24, 10:40 UTC | May 24, 11:25 UTC | 45m |
| 2026-05-24 | TLM101 | SIN → DMK | May 24, 04:20 UTC | May 24, 06:20 UTC | 2h 0m |
| 2026-05-24 | TLM100 | DMK → SIN | May 24, 00:50 UTC | May 24, 02:55 UTC | 2h 5m |
| 2026-05-22 | TLM105 | SIN → DMK | May 22, 14:15 UTC | May 22, 16:15 UTC | 2h 0m |
| 2026-05-22 | TLM104 | DMK → SIN | May 22, 10:25 UTC | May 22, 12:05 UTC | 1h 40m |
| 2026-05-20 | TLM965 | CGO → DMK | May 20, 14:00 UTC | May 20, 14:25 UTC | 25m |
| 2026-05-20 | TLM964 | DMK → CGO | May 20, 05:35 UTC | May 20, 06:00 UTC | 25m |
| 2026-05-19 | TLM241 | MAA → DMK | May 19, 16:10 UTC | May 20, 00:05 UTC | 7h 55m |
| 2026-05-18 | TLM965 | CGO → DMK | May 18, 14:00 UTC | May 18, 14:20 UTC | 20m |
| 2026-05-18 | TLM964 | DMK → CGO | May 18, 05:35 UTC | May 18, 05:55 UTC | 20m |
| 2026-05-17 | TLM762 | DMK → HKT | May 17, 11:15 UTC | May 17, 14:30 UTC | 3h 15m |
| 2026-05-17 | TLM259 | DPS → DMK | May 17, 00:30 UTC | May 17, 09:55 UTC | 9h 25m |
| 2026-05-16 | TLM371 | MFM → DMK | May 16, 14:05 UTC | May 16, 16:20 UTC | 2h 15m |
| 2026-05-16 | TLM370 | DMK → MFM | May 16, 10:40 UTC | May 16, 11:25 UTC | 45m |
| 2026-05-16 | TLM373 | MFM → DMK | May 16, 08:46 UTC | May 16, 09:35 UTC | 50m |
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-LGR page for operator, model, and routing details .