sensors Mode-S transponder
E80445
ICAO 24-bit transponder address · allocated to Chile
Currently assigned to CC-BGD · BOEING 787-9 Dreamliner
- Hex
- E80445
- Octal
- 72002105
- Decimal
- 15,205,445
- Country
- CL
- Tail
- CC-BGD
- Type
- B789
- Flights observed
- 167
- Distinct callsigns
- 20
- Country
- CL
- Last broadcast
- 18h ago
Last known position
Country allocation
The ICAO 24-bit address E80445 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 |
|---|---|---|---|
| TAM8087 | - | 17 | 2026-06-22 |
| LAN715 | LAN Airlines | 17 | 2026-07-05 |
| LAN714 | LAN Airlines | 15 | 2026-07-03 |
| LAN805 | - | 13 | 2026-06-30 |
| LAN706 | - | 12 | 2026-07-11 |
| TAM8086 | - | 11 | 2026-06-22 |
| LAN804 | - | 11 | 2026-07-01 |
| LAN809 | LAN Airlines | 8 | 2026-05-09 |
| LPE2485 | LAN Peru | 7 | 2026-06-11 |
| LAN810 | LAN Airlines | 6 | 2026-05-10 |
| TAM8067 | TAM Brazilian Airlines | 5 | 2026-04-14 |
| LAN705 | - | 4 | 2026-07-11 |
| TAM8068 | TAM Brazilian Airlines | 3 | 2026-04-14 |
| LAN843 | - | 3 | 2026-07-09 |
| LAN543 | LAN Airlines | 3 | 2026-05-01 |
| TAM9453 | - | 2 | 2026-04-16 |
| TAM8195 | TAM Brazilian Airlines | 2 | 2026-05-22 |
| TAM8066 | TAM Brazilian Airlines | 2 | 2026-07-08 |
| TAM8065 | - | 2 | 2026-07-06 |
| LAN841 | - | 2 | 2026-07-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | LAN841 | - | Jul 13, 13:20 UTC | Jul 13, 13:30 UTC | 10m |
| 2026-07-13 | LAN503 | - | Jul 13, 02:10 UTC | Jul 13, 07:05 UTC | 4h 55m |
| 2026-07-12 | LAN502 | - | Jul 12, 18:15 UTC | Jul 12, 22:35 UTC | 4h 20m |
| 2026-07-11 | LAN705 | - | Jul 11, 22:05 UTC | Jul 12, 08:55 UTC | 10h 50m |
| 2026-07-11 | LAN706 | - | Jul 11, 02:15 UTC | Jul 11, 11:55 UTC | 9h 40m |
| 2026-07-09 | LAN843 | - | Jul 9, 15:55 UTC | Jul 9, 16:05 UTC | 10m |
| 2026-07-08 | LAN705 | - | Jul 8, 22:05 UTC | Jul 9, 08:55 UTC | 10h 50m |
| 2026-07-08 | TAM8066 | GRU → MAD | Jul 8, 02:45 UTC | Jul 8, 12:15 UTC | 9h 30m |
| 2026-07-06 | TAM8065 | - | Jul 6, 22:05 UTC | Jul 7, 08:00 UTC | 9h 55m |
| 2026-07-06 | LAN706 | SCL → MAD | Jul 6, 02:15 UTC | Jul 6, 11:50 UTC | 9h 35m |
| 2026-07-05 | LAN715 | MAD → GRU | Jul 5, 12:05 UTC | Jul 5, 13:45 UTC | 1h 40m |
| 2026-07-05 | LAN715 | MAD → GRU | Jul 5, 10:30 UTC | Jul 5, 11:20 UTC | 50m |
| 2026-07-04 | TAM8065 | - | Jul 4, 22:30 UTC | Jul 5, 08:30 UTC | 10h 0m |
| 2026-07-04 | TAM8066 | GRU → MAD | Jul 4, 02:30 UTC | Jul 4, 11:50 UTC | 9h 20m |
| 2026-07-03 | LAN714 | GRU → MAD | Jul 3, 20:30 UTC | Jul 3, 22:45 UTC | 2h 15m |
| 2026-07-02 | LAN705 | - | Jul 2, 22:10 UTC | Jul 3, 08:05 UTC | 9h 55m |
| 2026-07-02 | LAN706 | SCL → MAD | Jul 2, 02:25 UTC | Jul 2, 12:05 UTC | 9h 40m |
| 2026-07-01 | LAN804 | - | Jul 1, 14:10 UTC | Jul 1, 14:25 UTC | 15m |
| 2026-07-01 | LAN804 | - | Jul 1, 02:20 UTC | Jul 1, 02:50 UTC | 30m |
| 2026-06-30 | LAN805 | - | Jun 30, 19:40 UTC | Jun 30, 20:25 UTC | 45m |
| 2026-06-30 | LAN805 | - | Jun 30, 05:25 UTC | Jun 30, 05:40 UTC | 15m |
| 2026-06-29 | LAN841 | SCL → IPC | Jun 29, 12:55 UTC | Jun 29, 13:04 UTC | 10m |
| 2026-06-28 | LAN804 | - | Jun 28, 14:25 UTC | Jun 28, 14:34 UTC | 10m |
| 2026-06-28 | LAN804 | - | Jun 28, 02:54 UTC | Jun 28, 03:29 UTC | 35m |
| 2026-06-27 | LAN805 | - | Jun 27, 07:04 UTC | Jun 27, 19:59 UTC | 12h 55m |
| 2026-06-26 | LAN843 | - | Jun 26, 15:20 UTC | Jun 26, 15:29 UTC | 10m |
| 2026-06-26 | LAN533 | - | Jun 26, 00:24 UTC | Jun 26, 04:00 UTC | 3h 35m |
| 2026-06-25 | LAN532 | SCL → JFK | Jun 25, 10:50 UTC | Jun 25, 13:14 UTC | 2h 25m |
| 2026-06-23 | LAN715 | MAD → GRU | Jun 23, 10:35 UTC | Jun 23, 12:45 UTC | 2h 10m |
| 2026-06-22 | TAM8087 | - | Jun 22, 21:05 UTC | Jun 23, 08:25 UTC | 11h 20m |
| 2026-06-22 | TAM8086 | - | Jun 22, 02:19 UTC | Jun 22, 13:59 UTC | 11h 40m |
| 2026-06-21 | LAN714 | GRU → MAD | Jun 21, 21:29 UTC | Jun 21, 23:24 UTC | 1h 55m |
| 2026-06-21 | LAN715 | MAD → GRU | Jun 21, 10:34 UTC | Jun 21, 12:49 UTC | 2h 15m |
| 2026-06-20 | LAN715 | MAD → GRU | Jun 20, 22:00 UTC | Jun 21, 07:40 UTC | 9h 40m |
| 2026-06-20 | LAN706 | SCL → MAD | Jun 20, 10:20 UTC | Jun 20, 11:49 UTC | 1h 30m |
| 2026-06-20 | LAN706 | SCL → MAD | Jun 20, 02:09 UTC | Jun 20, 04:34 UTC | 2h 25m |
| 2026-06-19 | LAN804 | - | Jun 19, 14:39 UTC | Jun 19, 14:49 UTC | 10m |
| 2026-06-19 | LAN804 | - | Jun 19, 02:54 UTC | Jun 19, 03:29 UTC | 35m |
| 2026-06-18 | LAN805 | - | Jun 18, 20:20 UTC | Jun 18, 21:05 UTC | 45m |
| 2026-06-18 | LAN805 | - | Jun 18, 05:40 UTC | Jun 18, 05:50 UTC | 10m |
| 2026-06-17 | LAN804 | - | Jun 17, 02:10 UTC | Jun 17, 14:25 UTC | 12h 15m |
| 2026-06-16 | LAN805 | - | Jun 16, 18:45 UTC | Jun 16, 19:25 UTC | 40m |
| 2026-06-16 | LAN805 | - | Jun 16, 05:30 UTC | Jun 16, 05:40 UTC | 10m |
| 2026-06-15 | LAN843 | SCL → IPC | Jun 15, 15:30 UTC | Jun 15, 15:40 UTC | 10m |
| 2026-06-14 | LAN705 | - | Jun 14, 22:30 UTC | Jun 15, 08:10 UTC | 9h 40m |
| 2026-06-14 | LAN706 | SCL → MAD | Jun 14, 02:00 UTC | Jun 14, 11:50 UTC | 9h 50m |
| 2026-06-13 | LAN715 | MAD → GRU | Jun 13, 11:15 UTC | Jun 13, 12:50 UTC | 1h 35m |
| 2026-06-12 | TAM8087 | LAX → GRU | Jun 12, 20:55 UTC | Jun 13, 08:10 UTC | 11h 14m |
| 2026-06-12 | TAM8086 | GRU → LAX | Jun 12, 02:40 UTC | Jun 12, 14:30 UTC | 11h 50m |
| 2026-06-11 | LAN714 | GRU → MAD | Jun 11, 22:00 UTC | Jun 11, 23:40 UTC | 1h 40m |
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-BGD page for operator, model, and routing details .