sensors Mode-S transponder
E8041E
ICAO 24-bit transponder address · allocated to Chile
Currently assigned to CC-BAL · AIRBUS A-320
- Hex
- E8041E
- Octal
- 72002036
- Decimal
- 15,205,406
- Country
- CL
- Tail
- CC-BAL
- Type
- A320
- Flights observed
- 79
- Distinct callsigns
- 20
- Country
- CL
- Last broadcast
- 51m ago
Current position
Country allocation
The ICAO 24-bit address E8041E falls within the block assigned to Chile (CL) by ICAO Annex 10, Volume III. Every aircraft registered in Chile 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 |
|---|---|---|---|
| LPE2415 | LAN Peru | 6 | 2026-04-25 |
| LPE2453 | LAN Peru | 5 | 2026-05-06 |
| LPE2414 | LAN Peru | 5 | 2026-04-25 |
| LPE2398 | LAN Peru | 5 | 2026-05-07 |
| LPE2425 | LAN Peru | 4 | 2026-05-28 |
| LPE2460 | LAN Peru | 3 | 2026-04-23 |
| LPE2424 | LAN Peru | 3 | 2026-05-28 |
| LPE2399 | LAN Peru | 3 | 2026-05-07 |
| LPE2092 | LAN Peru | 3 | 2026-05-06 |
| LPE2091 | LAN Peru | 3 | 2026-05-06 |
| LPE2454 | LAN Peru | 2 | 2026-04-21 |
| LPE2452 | LAN Peru | 2 | 2026-04-16 |
| LPE2388 | LAN Peru | 2 | 2026-05-01 |
| LPE2369 | LAN Peru | 2 | 2026-05-02 |
| LPE2243 | LAN Peru | 2 | 2026-04-19 |
| LPE2087 | LAN Peru | 2 | 2026-04-26 |
| LPE2465 | LAN Peru | 1 | 2026-04-26 |
| LPE2461 | LAN Peru | 1 | 2026-04-18 |
| LPE2459 | - | 1 | 2026-04-13 |
| LPE2458 | LAN Peru | 1 | 2026-04-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | LPE2395 | FLN → LIM | May 30, 07:20 UTC | May 30, 07:30 UTC | 10m |
| 2026-05-30 | LPE2394 | LIM → FLN | May 30, 03:55 UTC | May 30, 05:20 UTC | 1h 25m |
| 2026-05-29 | LPE2338 | LIM → PIU | May 29, 20:30 UTC | May 29, 23:15 UTC | 2h 45m |
| 2026-05-28 | LPE2306 | LIM → PIU | May 28, 23:40 UTC | May 29, 17:45 UTC | 18h 5m |
| 2026-05-28 | LPE2425 | TUC → LIM | May 28, 22:40 UTC | May 29, 17:45 UTC | 19h 5m |
| 2026-05-28 | LPE2424 | LIM → TUC | May 28, 17:25 UTC | May 28, 19:00 UTC | 1h 35m |
| 2026-05-27 | LPE2052 | LIM → TBP | May 27, 15:50 UTC | May 27, 18:55 UTC | 3h 5m |
| 2026-05-25 | LAN1995 | MEX → BOG | May 25, 22:55 UTC | May 25, 23:40 UTC | 45m |
| 2026-05-08 | LAN1996 | LIM → BQN | May 8, 06:50 UTC | May 8, 07:29 UTC | 40m |
| 2026-05-07 | LPE2399 | COR → LIM | May 7, 10:55 UTC | May 8, 02:59 UTC | 16h 5m |
| 2026-05-07 | LPE2398 | LIM → COR | May 7, 08:30 UTC | May 7, 09:10 UTC | 40m |
| 2026-05-06 | LPE2453 | PUJ → LIM | May 6, 15:25 UTC | May 7, 01:40 UTC | 10h 15m |
| 2026-05-06 | LPE2092 | TPP → LIM | May 6, 02:01 UTC | May 6, 02:40 UTC | 40m |
| 2026-05-06 | LPE2091 | LIM → TPP | May 6, 00:01 UTC | May 6, 00:50 UTC | 50m |
| 2026-05-05 | LPE2092 | TPP → LIM | May 5, 01:50 UTC | May 5, 02:25 UTC | 35m |
| 2026-05-04 | LPE2091 | LIM → TPP | May 4, 07:20 UTC | May 5, 00:45 UTC | 17h 26m |
| 2026-05-03 | LPE2446 | LIM → MBJ | May 3, 17:35 UTC | May 4, 03:05 UTC | 9h 30m |
| 2026-05-03 | LPE2399 | COR → LIM | May 3, 11:05 UTC | May 3, 11:50 UTC | 45m |
| 2026-05-02 | LPE2398 | LIM → COR | May 2, 23:20 UTC | May 3, 09:40 UTC | 10h 19m |
| 2026-05-02 | LPE2369 | LIM → AEP | May 2, 21:00 UTC | May 2, 21:25 UTC | 25m |
| 2026-05-02 | LPE2125 | LIM → PIU | May 2, 12:30 UTC | May 2, 15:35 UTC | 3h 5m |
| 2026-05-01 | LPE2453 | PUJ → LIM | May 1, 15:45 UTC | May 2, 02:00 UTC | 10h 15m |
| 2026-05-01 | LPE2388 | LIM → UIO | May 1, 06:20 UTC | May 1, 12:45 UTC | 6h 25m |
| 2026-04-30 | LPE2136 | TRU → LIM | Apr 30, 22:40 UTC | Apr 30, 23:05 UTC | 25m |
| 2026-04-30 | LPE2135 | LIM → TRU | Apr 30, 21:00 UTC | Apr 30, 21:30 UTC | 30m |
| 2026-04-30 | LPE2382 | LIM → UIO | Apr 30, 14:15 UTC | Apr 30, 19:05 UTC | 4h 50m |
| 2026-04-30 | LPE2271 | CIX → LIM | Apr 30, 11:35 UTC | Apr 30, 12:10 UTC | 35m |
| 2026-04-30 | LPE2270 | LIM → CIX | Apr 30, 09:45 UTC | Apr 30, 10:20 UTC | 35m |
| 2026-04-30 | LPE2092 | TPP → LIM | Apr 30, 02:00 UTC | Apr 30, 02:40 UTC | 40m |
| 2026-04-30 | LPE2091 | LIM → TPP | Apr 30, 00:00 UTC | Apr 30, 00:50 UTC | 50m |
| 2026-04-28 | LPE2368 | EZE → LIM | Apr 28, 23:14 UTC | Apr 28, 23:45 UTC | 30m |
| 2026-04-28 | LPE2369 | LIM → AEP | Apr 28, 21:00 UTC | Apr 28, 21:35 UTC | 35m |
| 2026-04-28 | LPE2251 | LIM → TYL | Apr 28, 11:05 UTC | Apr 28, 14:15 UTC | 3h 10m |
| 2026-04-27 | LPE2316 | LIM → PIU | Apr 27, 11:05 UTC | Apr 27, 20:05 UTC | 9h 0m |
| 2026-04-26 | LPE2465 | LIM → EZE | Apr 26, 21:20 UTC | Apr 27, 09:20 UTC | 12h 0m |
| 2026-04-26 | LPE2087 | LIM → TPP | Apr 26, 19:55 UTC | Apr 26, 20:20 UTC | 25m |
| 2026-04-26 | LPE2087 | LIM → TPP | Apr 26, 00:10 UTC | Apr 26, 20:20 UTC | 20h 10m |
| 2026-04-25 | LPE2415 | LIM → SCL | Apr 25, 21:35 UTC | Apr 26, 20:20 UTC | 22h 45m |
| 2026-04-25 | LPE2415 | LIM → SCL | Apr 25, 20:35 UTC | Apr 26, 00:15 UTC | 3h 40m |
| 2026-04-25 | LPE2414 | LIM → GIG | Apr 25, 09:05 UTC | Apr 25, 19:20 UTC | 10h 15m |
| 2026-04-24 | LPE2231 | LIM → IQT | Apr 24, 11:15 UTC | Apr 25, 09:30 UTC | 22h 15m |
| 2026-04-24 | LPE2131 | LIM → TRU | Apr 24, 10:00 UTC | Apr 24, 10:10 UTC | 10m |
| 2026-04-23 | LPE2460 | LIM → PUJ | Apr 23, 10:35 UTC | Apr 24, 03:05 UTC | 16h 30m |
| 2026-04-22 | LPE2398 | LIM → COR | Apr 22, 17:20 UTC | Apr 23, 08:55 UTC | 15h 35m |
| 2026-04-22 | LPE2398 | LIM → COR | Apr 22, 10:55 UTC | Apr 23, 08:55 UTC | 22h 0m |
| 2026-04-21 | LPE2455 | CUN → LIM | Apr 21, 23:40 UTC | Apr 22, 08:40 UTC | 9h 0m |
| 2026-04-21 | LPE2454 | LIM → CUN | Apr 21, 20:45 UTC | Apr 21, 20:55 UTC | 10m |
| 2026-04-21 | LPE2454 | LIM → CUN | Apr 21, 01:35 UTC | Apr 21, 19:40 UTC | 18h 5m |
| 2026-04-20 | LPE2425 | TUC → LIM | Apr 20, 23:35 UTC | Apr 21, 19:40 UTC | 20h 5m |
| 2026-04-20 | LPE2425 | TUC → LIM | Apr 20, 22:35 UTC | Apr 21, 19:40 UTC | 21h 5m |
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 CC-BAL page for operator, model, and routing details .