sensors Mode-S transponder
E80275
ICAO 24-bit transponder address · allocated to Chile
Currently assigned to CC-BFR · AIRBUS A-320
- Hex
- E80275
- Octal
- 72001165
- Decimal
- 15,204,981
- Country
- CL
- Tail
- CC-BFR
- Type
- A320
- Flights observed
- 175
- Distinct callsigns
- 20
- Country
- CL
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address E80275 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 |
|---|---|---|---|
| LPE2395 | - | 7 | 2026-06-29 |
| LPE2402 | LAN Peru | 5 | 2026-04-27 |
| LPE2297 | - | 5 | 2026-06-13 |
| LPE2296 | - | 5 | 2026-06-13 |
| LPE2399 | - | 4 | 2026-07-09 |
| LPE2398 | - | 4 | 2026-07-09 |
| LPE2394 | - | 4 | 2026-06-29 |
| LPE2375 | LAN Peru | 4 | 2026-06-07 |
| LPE2082 | - | 4 | 2026-06-16 |
| LPE2464 | LAN Peru | 3 | 2026-05-29 |
| LPE2429 | - | 3 | 2026-07-12 |
| LPE2387 | LAN Peru | 3 | 2026-05-16 |
| LPE2376 | LAN Peru | 3 | 2026-06-07 |
| LPE2369 | - | 3 | 2026-06-17 |
| LPE2302 | LAN Peru | 3 | 2026-06-10 |
| LPE2279 | - | 3 | 2026-07-06 |
| LPE2251 | LAN Peru | 3 | 2026-07-02 |
| LPE2214 | - | 3 | 2026-07-07 |
| LPE2213 | - | 3 | 2026-07-07 |
| LPE2465 | LAN Peru | 2 | 2026-05-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-12 | LPE2429 | - | Jul 12, 11:45 UTC | Jul 13, 04:05 UTC | 16h 20m |
| 2026-07-11 | LNE1436 | - | Jul 11, 16:05 UTC | Jul 12, 09:05 UTC | 17h 0m |
| 2026-07-11 | LPE2491 | - | Jul 11, 13:10 UTC | Jul 11, 14:25 UTC | 1h 15m |
| 2026-07-10 | LPE2455 | - | Jul 10, 22:40 UTC | Jul 11, 03:10 UTC | 4h 30m |
| 2026-07-10 | LPE2454 | - | Jul 10, 16:10 UTC | Jul 10, 21:15 UTC | 5h 5m |
| 2026-07-10 | LPE2433 | - | Jul 10, 10:40 UTC | Jul 10, 11:25 UTC | 45m |
| 2026-07-10 | LPE2432 | - | Jul 10, 08:15 UTC | Jul 10, 09:05 UTC | 50m |
| 2026-07-10 | LPE2138 | - | Jul 10, 03:00 UTC | Jul 10, 03:25 UTC | 25m |
| 2026-07-09 | LPE2399 | - | Jul 9, 10:55 UTC | Jul 10, 01:35 UTC | 14h 40m |
| 2026-07-09 | LPE2398 | - | Jul 9, 08:00 UTC | Jul 9, 09:20 UTC | 1h 20m |
| 2026-07-07 | LPE2214 | - | Jul 7, 04:45 UTC | Jul 7, 05:15 UTC | 30m |
| 2026-07-07 | LPE2213 | - | Jul 7, 02:50 UTC | Jul 7, 03:25 UTC | 35m |
| 2026-07-06 | LPE2304 | - | Jul 6, 22:15 UTC | Jul 7, 01:05 UTC | 2h 50m |
| 2026-07-06 | LPE2060 | - | Jul 6, 13:55 UTC | Jul 6, 14:20 UTC | 25m |
| 2026-07-06 | LPE2059 | LIM → ATA | Jul 6, 12:30 UTC | Jul 6, 12:40 UTC | 10m |
| 2026-07-06 | LPE2279 | - | Jul 6, 03:40 UTC | Jul 6, 04:10 UTC | 30m |
| 2026-07-06 | LPE2278 | - | Jul 6, 01:30 UTC | Jul 6, 02:05 UTC | 35m |
| 2026-07-05 | LPE2470 | LIM → GIG | Jul 5, 13:40 UTC | Jul 5, 23:50 UTC | 10h 10m |
| 2026-07-04 | LPE2399 | - | Jul 4, 10:45 UTC | Jul 4, 12:20 UTC | 1h 35m |
| 2026-07-04 | LPE2398 | - | Jul 4, 07:50 UTC | Jul 4, 08:55 UTC | 1h 5m |
| 2026-07-03 | LPE2399 | - | Jul 3, 10:40 UTC | Jul 4, 03:20 UTC | 16h 40m |
| 2026-07-03 | LPE2398 | - | Jul 3, 07:55 UTC | Jul 3, 09:05 UTC | 1h 10m |
| 2026-07-02 | LPE2251 | LIM → TYL | Jul 2, 11:05 UTC | Jul 2, 14:05 UTC | 3h 0m |
| 2026-07-01 | LPE2461 | - | Jul 1, 20:20 UTC | Jul 2, 03:10 UTC | 6h 50m |
| 2026-06-30 | LPE2365 | - | Jun 30, 10:55 UTC | Jun 30, 11:15 UTC | 20m |
| 2026-06-30 | LPE2364 | - | Jun 30, 09:05 UTC | Jun 30, 09:30 UTC | 25m |
| 2026-06-29 | LPE2395 | - | Jun 29, 06:59 UTC | Jun 29, 08:50 UTC | 1h 50m |
| 2026-06-29 | LPE2394 | - | Jun 29, 03:49 UTC | Jun 29, 05:09 UTC | 1h 20m |
| 2026-06-20 | LPE2405 | GIG → LIM | Jun 20, 10:29 UTC | Jun 21, 00:34 UTC | 14h 5m |
| 2026-06-20 | LPE2404 | - | Jun 20, 07:19 UTC | Jun 20, 08:59 UTC | 1h 40m |
| 2026-06-17 | LPE2368 | - | Jun 17, 23:05 UTC | Jun 17, 23:45 UTC | 40m |
| 2026-06-17 | LPE2369 | - | Jun 17, 21:15 UTC | Jun 17, 21:45 UTC | 30m |
| 2026-06-17 | LPE2369 | - | Jun 17, 00:25 UTC | Jun 17, 21:45 UTC | 21h 20m |
| 2026-06-16 | LPE2451 | - | Jun 16, 21:20 UTC | Jun 17, 21:15 UTC | 23h 55m |
| 2026-06-16 | LPE2450 | - | Jun 16, 21:10 UTC | Jun 17, 00:50 UTC | 3h 40m |
| 2026-06-16 | LPE2082 | - | Jun 16, 13:34 UTC | Jun 16, 16:05 UTC | 2h 30m |
| 2026-06-15 | LPE2395 | - | Jun 15, 07:00 UTC | Jun 15, 08:49 UTC | 1h 50m |
| 2026-06-15 | LPE2394 | - | Jun 15, 04:00 UTC | Jun 15, 05:20 UTC | 1h 20m |
| 2026-06-14 | LPE2142 | - | Jun 14, 11:55 UTC | Jun 14, 12:20 UTC | 25m |
| 2026-06-14 | LPE2141 | - | Jun 14, 10:20 UTC | Jun 14, 10:50 UTC | 30m |
| 2026-06-13 | LPE2296 | - | Jun 13, 22:30 UTC | Jun 13, 22:55 UTC | 25m |
| 2026-06-13 | LPE2297 | - | Jun 13, 20:35 UTC | Jun 13, 21:05 UTC | 30m |
| 2026-06-13 | LPE2073 | - | Jun 13, 00:05 UTC | Jun 13, 03:25 UTC | 3h 20m |
| 2026-06-12 | LPE2230 | IQT → LIM | Jun 12, 08:25 UTC | Jun 12, 12:05 UTC | 3h 40m |
| 2026-06-11 | LPE2395 | FLN → LIM | Jun 11, 07:20 UTC | Jun 12, 02:20 UTC | 19h 1m |
| 2026-06-11 | LPE2395 | FLN → LIM | Jun 11, 06:55 UTC | Jun 12, 02:20 UTC | 19h 25m |
| 2026-06-11 | LPE2394 | LIM → FLN | Jun 11, 03:50 UTC | Jun 11, 05:15 UTC | 1h 25m |
| 2026-06-10 | LPE2302 | LIM → PIU | Jun 10, 11:00 UTC | Jun 10, 13:50 UTC | 2h 50m |
| 2026-06-09 | LPE2453 | PUJ → LIM | Jun 9, 18:25 UTC | Jun 10, 01:55 UTC | 7h 30m |
| 2026-06-09 | LAN528 | SCL → LIM | Jun 9, 10:00 UTC | Jun 9, 10:10 UTC | 10m |
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-BFR page for operator, model, and routing details .