sensors Mode-S transponder
8A0576
ICAO 24-bit transponder address · allocated to Indonesia
Currently assigned to PK-LEF · AIRBUS A-330-300
- Hex
- 8A0576
- Octal
- 42402566
- Decimal
- 9,045,366
- Country
- ID
- Tail
- PK-LEF
- Type
- A333
- Flights observed
- 39
- Distinct callsigns
- 18
- Country
- ID
- Last broadcast
- Jul 24, 02:55 UTC
Last known position
Country allocation
The ICAO 24-bit address 8A0576 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 18 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| LNI085 | - | 8 | 2026-07-01 |
| LNI083 | Lion Mentari Airlines | 7 | 2026-07-20 |
| LNI082 | Lion Mentari Airlines | 3 | 2026-07-23 |
| LNI373 | Lion Mentari Airlines | 2 | 2026-06-19 |
| LNI209 | Lion Mentari Airlines | 2 | 2026-04-23 |
| LNI111 | - | 2 | 2026-06-25 |
| LNI081 | - | 2 | 2026-07-09 |
| LNI024 | Lion Mentari Airlines | 2 | 2026-05-14 |
| LNI012 | Lion Mentari Airlines | 2 | 2026-05-17 |
| LNI3972 | - | 1 | 2026-07-02 |
| LNI372 | Lion Mentari Airlines | 1 | 2026-05-06 |
| LNI212 | - | 1 | 2026-06-26 |
| LNI112 | - | 1 | 2026-06-22 |
| LNI080 | - | 1 | 2026-04-13 |
| LNI077 | - | 1 | 2026-06-22 |
| LNI033 | Lion Mentari Airlines | 1 | 2026-05-03 |
| LNI020 | Lion Mentari Airlines | 1 | 2026-04-30 |
| LNI015 | Lion Mentari Airlines | 1 | 2026-05-03 |
Recent flights last 39
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-23 | LNI082 | BTH → JED | Jul 23, 08:55 UTC | Jul 24, 02:55 UTC | 18h 0m |
| 2026-07-20 | LNI083 | JED → BTH | Jul 20, 08:15 UTC | Jul 21, 01:40 UTC | 17h 24m |
| 2026-07-16 | LNI082 | - | Jul 16, 09:00 UTC | Jul 17, 01:49 UTC | 16h 50m |
| 2026-07-13 | LNI083 | - | Jul 13, 08:25 UTC | Jul 14, 01:55 UTC | 17h 30m |
| 2026-07-09 | LNI081 | - | Jul 9, 08:50 UTC | Jul 10, 01:35 UTC | 16h 45m |
| 2026-07-06 | LNI083 | - | Jul 6, 08:25 UTC | Jul 7, 01:35 UTC | 17h 10m |
| 2026-07-02 | LNI082 | - | Jul 2, 09:30 UTC | Jul 3, 02:05 UTC | 16h 35m |
| 2026-07-02 | LNI3972 | - | Jul 2, 06:25 UTC | Jul 2, 07:10 UTC | 45m |
| 2026-07-01 | LNI085 | - | Jul 1, 10:45 UTC | Jul 2, 01:00 UTC | 14h 15m |
| 2026-07-01 | LNI085 | - | Jul 1, 00:05 UTC | Jul 1, 21:50 UTC | 21h 45m |
| 2026-06-30 | LNI085 | - | Jun 30, 20:40 UTC | Jul 1, 11:15 UTC | 14h 35m |
| 2026-06-30 | LNI085 | - | Jun 30, 13:55 UTC | Jul 1, 11:15 UTC | 21h 20m |
| 2026-06-30 | LNI085 | - | Jun 30, 10:55 UTC | Jul 1, 00:40 UTC | 13h 45m |
| 2026-06-29 | LNI083 | - | Jun 29, 21:54 UTC | Jun 30, 21:25 UTC | 23h 31m |
| 2026-06-29 | LNI083 | - | Jun 29, 18:19 UTC | Jun 30, 14:00 UTC | 19h 41m |
| 2026-06-29 | LNI083 | - | Jun 29, 08:14 UTC | Jun 29, 22:35 UTC | 14h 20m |
| 2026-06-29 | LNI083 | - | Jun 29, 02:09 UTC | Jun 29, 22:35 UTC | 20h 25m |
| 2026-06-27 | LNI085 | - | Jun 27, 08:05 UTC | Jun 27, 21:40 UTC | 13h 35m |
| 2026-06-26 | LNI212 | - | Jun 26, 07:35 UTC | Jun 26, 08:54 UTC | 1h 20m |
| 2026-06-25 | LNI111 | - | Jun 25, 10:09 UTC | Jun 26, 05:19 UTC | 19h 10m |
| 2026-06-25 | LNI111 | - | Jun 25, 06:40 UTC | Jun 26, 05:19 UTC | 22h 40m |
| 2026-06-22 | LNI077 | - | Jun 22, 13:10 UTC | Jun 23, 07:15 UTC | 18h 5m |
| 2026-06-22 | LNI112 | - | Jun 22, 09:10 UTC | Jun 22, 09:30 UTC | 20m |
| 2026-06-19 | LNI373 | BTH → CGK | Jun 19, 10:39 UTC | Jun 19, 11:59 UTC | 1h 20m |
| 2026-05-17 | LNI012 | CGK → DPS | May 17, 10:25 UTC | May 17, 15:15 UTC | 4h 50m |
| 2026-05-14 | LNI024 | CGK → DPS | May 14, 04:30 UTC | May 14, 05:15 UTC | 45m |
| 2026-05-08 | LNI373 | BTH → CGK | May 8, 09:44 UTC | May 8, 10:44 UTC | 1h 0m |
| 2026-05-06 | LNI372 | UPG → CGK | May 6, 11:50 UTC | May 6, 12:45 UTC | 55m |
| 2026-05-03 | LNI015 | DPS → CGK | May 3, 15:05 UTC | May 3, 15:20 UTC | 15m |
| 2026-05-03 | LNI012 | CGK → DPS | May 3, 10:25 UTC | May 3, 11:00 UTC | 35m |
| 2026-05-03 | LNI033 | DPS → CGK | May 3, 08:10 UTC | May 3, 08:40 UTC | 30m |
| 2026-05-01 | LNI024 | CGK → DPS | May 1, 04:35 UTC | May 1, 05:20 UTC | 45m |
| 2026-04-30 | LNI020 | CGK → DPS | Apr 30, 21:50 UTC | May 1, 02:40 UTC | 4h 50m |
| 2026-04-23 | LNI209 | KNO → CGK | Apr 23, 01:10 UTC | Apr 23, 01:25 UTC | 15m |
| 2026-04-22 | LNI209 | KNO → CGK | Apr 22, 23:45 UTC | Apr 23, 00:20 UTC | 35m |
| 2026-04-13 | LNI085 | - | Apr 13, 22:00 UTC | Apr 13, 22:40 UTC | 40m |
| 2026-04-13 | LNI085 | - | Apr 13, 18:45 UTC | Apr 13, 19:20 UTC | 35m |
| 2026-04-13 | LNI080 | - | Apr 13, 08:35 UTC | Apr 13, 09:05 UTC | 30m |
| 2026-04-12 | LNI081 | - | Apr 12, 18:00 UTC | Apr 12, 18:15 UTC | 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 PK-LEF page for operator, model, and routing details .