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