sensors Mode-S transponder
E80242
ICAO 24-bit transponder address · allocated to Chile
Currently assigned to CC-CXG · BOEING 767-300
- Hex
- E80242
- Octal
- 72001102
- Decimal
- 15,204,930
- Country
- CL
- Tail
- CC-CXG
- Type
- B763
- Flights observed
- 177
- Distinct callsigns
- 20
- Country
- CL
- Last broadcast
- 48m ago
Last known position
Country allocation
The ICAO 24-bit address E80242 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 |
|---|---|---|---|
| LPE2483 | - | 19 | 2026-07-13 |
| LPE2482 | - | 18 | 2026-07-12 |
| LPE2468 | - | 18 | 2026-07-14 |
| LPE2469 | - | 16 | 2026-07-10 |
| LPE2476 | LAN Peru | 14 | 2026-06-17 |
| LPE2698 | - | 11 | 2026-07-13 |
| LPE2477 | LAN Peru | 11 | 2026-06-10 |
| LPE2695 | - | 10 | 2026-07-13 |
| LPE2478 | - | 10 | 2026-07-08 |
| LPE2694 | - | 9 | 2026-07-11 |
| LPE2479 | - | 9 | 2026-07-08 |
| LPE2699 | - | 8 | 2026-07-12 |
| LPE2481 | - | 7 | 2026-07-07 |
| LPE2480 | - | 7 | 2026-07-07 |
| MPTO | - | 2 | 2026-04-15 |
| LPE2691 | - | 2 | 2026-06-28 |
| LPE2690 | LAN Peru | 2 | 2026-06-05 |
| LPE2693 | LAN Peru | 1 | 2026-05-22 |
| LPE2511 | LAN Peru | 1 | 2026-06-16 |
| LPE2412 | LAN Peru | 1 | 2026-04-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | LPE2468 | - | Jul 14, 06:00 UTC | Jul 14, 06:30 UTC | 30m |
| 2026-07-13 | LPE2695 | - | Jul 13, 22:30 UTC | Jul 14, 03:35 UTC | 5h 5m |
| 2026-07-13 | LPE2698 | - | Jul 13, 13:55 UTC | Jul 13, 19:00 UTC | 5h 5m |
| 2026-07-13 | LPE2483 | - | Jul 13, 03:40 UTC | Jul 13, 09:40 UTC | 6h 0m |
| 2026-07-12 | LPE2482 | - | Jul 12, 17:35 UTC | Jul 12, 23:55 UTC | 6h 20m |
| 2026-07-12 | LPE2699 | - | Jul 12, 04:25 UTC | Jul 12, 09:10 UTC | 4h 45m |
| 2026-07-11 | LPE2694 | - | Jul 11, 19:05 UTC | Jul 12, 00:20 UTC | 5h 15m |
| 2026-07-11 | LPE2699 | - | Jul 11, 05:55 UTC | Jul 11, 10:55 UTC | 5h 0m |
| 2026-07-10 | - | - | Jul 10, 19:15 UTC | Jul 11, 00:30 UTC | 5h 16m |
| 2026-07-10 | LPE2469 | - | Jul 10, 04:25 UTC | Jul 10, 11:25 UTC | 7h 0m |
| 2026-07-09 | LPE2468 | - | Jul 9, 05:45 UTC | Jul 9, 13:05 UTC | 7h 20m |
| 2026-07-08 | LPE2479 | - | Jul 8, 18:55 UTC | Jul 9, 02:25 UTC | 7h 30m |
| 2026-07-08 | LPE2478 | - | Jul 8, 06:30 UTC | Jul 8, 14:40 UTC | 8h 10m |
| 2026-07-07 | LPE2481 | - | Jul 7, 21:35 UTC | Jul 8, 02:30 UTC | 4h 55m |
| 2026-07-07 | LPE2480 | - | Jul 7, 05:55 UTC | Jul 7, 11:00 UTC | 5h 5m |
| 2026-07-06 | LPE2695 | - | Jul 6, 21:55 UTC | Jul 7, 02:45 UTC | 4h 50m |
| 2026-07-06 | LPE2698 | LIM → MIA | Jul 6, 13:50 UTC | Jul 6, 19:10 UTC | 5h 20m |
| 2026-07-06 | LPE2483 | - | Jul 6, 03:25 UTC | Jul 6, 09:25 UTC | 6h 0m |
| 2026-07-05 | LPE2482 | LIM → ATL | Jul 5, 17:45 UTC | Jul 6, 00:05 UTC | 6h 20m |
| 2026-07-04 | LPE2479 | - | Jul 4, 18:55 UTC | Jul 5, 02:45 UTC | 7h 50m |
| 2026-07-04 | LPE2478 | LIM → LAX | Jul 4, 06:20 UTC | Jul 4, 14:15 UTC | 7h 55m |
| 2026-07-03 | LPE2469 | - | Jul 3, 04:30 UTC | Jul 3, 08:10 UTC | 3h 40m |
| 2026-07-02 | LPE2468 | LIM → JFK | Jul 2, 07:10 UTC | Jul 2, 14:40 UTC | 7h 30m |
| 2026-07-01 | LPE2481 | - | Jul 1, 23:30 UTC | Jul 2, 04:20 UTC | 4h 50m |
| 2026-06-30 | LPE2480 | - | Jun 30, 19:15 UTC | Jul 1, 11:10 UTC | 15h 55m |
| 2026-06-30 | LPE2478 | LIM → LAX | Jun 30, 13:10 UTC | Jun 30, 14:45 UTC | 1h 35m |
| 2026-06-28 | LPE2691 | - | Jun 28, 18:19 UTC | Jun 28, 22:15 UTC | 3h 55m |
| 2026-06-27 | LPE2468 | LIM → JFK | Jun 27, 21:25 UTC | Jun 28, 12:55 UTC | 15h 30m |
| 2026-06-27 | LPE2483 | - | Jun 27, 03:30 UTC | Jun 27, 18:49 UTC | 15h 20m |
| 2026-06-26 | LPE2482 | LIM → ATL | Jun 26, 20:40 UTC | Jun 27, 00:00 UTC | 3h 20m |
| 2026-06-25 | LPE2699 | - | Jun 25, 04:35 UTC | Jun 25, 06:14 UTC | 1h 40m |
| 2026-06-24 | LPE2694 | LIM → MIA | Jun 24, 06:35 UTC | Jun 25, 00:35 UTC | 18h 0m |
| 2026-06-24 | LPE2469 | - | Jun 24, 04:34 UTC | Jun 25, 00:35 UTC | 20h 0m |
| 2026-06-24 | LPE2469 | JFK → MIA | Jun 24, 04:15 UTC | Jun 25, 00:35 UTC | 20h 20m |
| 2026-06-22 | LPE2468 | LIM → JFK | Jun 22, 21:25 UTC | Jun 23, 13:05 UTC | 15h 40m |
| 2026-06-22 | LPE2698 | LIM → MIA | Jun 22, 04:19 UTC | Jun 22, 18:49 UTC | 14h 30m |
| 2026-06-21 | LPE2694 | LIM → MIA | Jun 21, 06:50 UTC | Jun 22, 01:29 UTC | 18h 40m |
| 2026-06-21 | LPE2699 | MIA → MIA | Jun 21, 05:10 UTC | Jun 22, 01:29 UTC | 20h 20m |
| 2026-06-20 | LPE2483 | - | Jun 20, 04:34 UTC | Jun 21, 00:10 UTC | 19h 35m |
| 2026-06-20 | LPE2483 | ATL → MIA | Jun 20, 03:39 UTC | Jun 21, 00:10 UTC | 20h 30m |
| 2026-06-19 | LPE2482 | LIM → ATL | Jun 19, 04:34 UTC | Jun 20, 00:04 UTC | 19h 30m |
| 2026-06-18 | LPE2694 | LIM → MIA | Jun 18, 04:40 UTC | Jun 19, 00:10 UTC | 19h 29m |
| 2026-06-17 | LPE2476 | LIM → LAX | Jun 17, 21:50 UTC | Jun 18, 01:40 UTC | 3h 50m |
| 2026-06-16 | LPE2479 | - | Jun 16, 22:55 UTC | Jun 17, 22:20 UTC | 23h 25m |
| 2026-06-16 | LPE2478 | LIM → LAX | Jun 16, 12:00 UTC | Jun 16, 20:20 UTC | 8h 21m |
| 2026-06-16 | LPE2511 | LIM → AQP | Jun 16, 03:25 UTC | Jun 16, 09:20 UTC | 5h 55m |
| 2026-06-15 | LPE2482 | LIM → ATL | Jun 15, 17:34 UTC | Jun 16, 00:05 UTC | 6h 30m |
| 2026-06-15 | LPE2483 | - | Jun 15, 04:34 UTC | Jun 15, 10:35 UTC | 6h 0m |
| 2026-06-14 | LPE2482 | LIM → ATL | Jun 14, 17:40 UTC | Jun 14, 23:59 UTC | 6h 20m |
| 2026-06-14 | LPE2469 | - | Jun 14, 04:15 UTC | Jun 14, 11:20 UTC | 7h 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-CXG page for operator, model, and routing details .