sensors Mode-S transponder
E80474
ICAO 24-bit transponder address · allocated to Chile
Currently assigned to CC-BGY · BOEING 787-9 Dreamliner
- Hex
- E80474
- Octal
- 72002164
- Decimal
- 15,205,492
- Country
- CL
- Tail
- CC-BGY
- Type
- B789
- Flights observed
- 167
- Distinct callsigns
- 20
- Country
- CL
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address E80474 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 |
|---|---|---|---|
| TAM8195 | TAM Brazilian Airlines | 11 | 2026-07-06 |
| TAM8187 | TAM Brazilian Airlines | 11 | 2026-06-11 |
| TAM8068 | TAM Brazilian Airlines | 10 | 2026-06-23 |
| TAM8186 | TAM Brazilian Airlines | 9 | 2026-06-10 |
| TAM8190 | - | 8 | 2026-07-06 |
| TAM8067 | TAM Brazilian Airlines | 7 | 2026-06-24 |
| TAM8181 | - | 6 | 2026-07-01 |
| TAM8180 | - | 6 | 2026-06-30 |
| TAM8126 | - | 6 | 2026-07-12 |
| TAM8058 | - | 6 | 2026-07-07 |
| TAM8150 | TAM Brazilian Airlines | 5 | 2026-05-25 |
| TAM8113 | - | 5 | 2026-06-27 |
| TAM8112 | TAM Brazilian Airlines | 5 | 2026-06-27 |
| TAM8079 | - | 5 | 2026-07-05 |
| TAM8078 | - | 5 | 2026-07-04 |
| LAN715 | LAN Airlines | 5 | 2026-05-23 |
| LAN714 | LAN Airlines | 5 | 2026-05-23 |
| TAM8151 | TAM Brazilian Airlines | 4 | 2026-05-25 |
| TAM8127 | - | 4 | 2026-07-12 |
| TAM8115 | TAM Brazilian Airlines | 4 | 2026-06-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | TAM8088 | - | Jul 13, 21:40 UTC | Jul 14, 00:25 UTC | 2h 45m |
| 2026-07-12 | TAM8127 | - | Jul 12, 23:45 UTC | Jul 13, 07:25 UTC | 7h 40m |
| 2026-07-12 | TAM8126 | - | Jul 12, 20:05 UTC | Jul 12, 20:50 UTC | 45m |
| 2026-07-12 | TAM8126 | - | Jul 12, 12:15 UTC | Jul 12, 18:30 UTC | 6h 15m |
| 2026-07-11 | TAM8087 | - | Jul 11, 21:35 UTC | Jul 12, 08:45 UTC | 11h 10m |
| 2026-07-11 | TAM8086 | - | Jul 11, 03:30 UTC | Jul 11, 15:20 UTC | 11h 50m |
| 2026-07-10 | TAM8165 | - | Jul 10, 16:25 UTC | Jul 11, 01:10 UTC | 8h 46m |
| 2026-07-10 | TAM8164 | - | Jul 10, 02:35 UTC | Jul 10, 11:50 UTC | 9h 15m |
| 2026-07-09 | TAM9541 | - | Jul 9, 08:50 UTC | Jul 9, 19:00 UTC | 10h 10m |
| 2026-07-07 | TAM8058 | - | Jul 7, 02:20 UTC | Jul 7, 10:00 UTC | 7h 40m |
| 2026-07-06 | TAM8195 | MIA → GRU | Jul 6, 17:00 UTC | Jul 6, 22:45 UTC | 5h 45m |
| 2026-07-06 | TAM8195 | MIA → GRU | Jul 6, 15:05 UTC | Jul 6, 15:20 UTC | 15m |
| 2026-07-06 | TAM8190 | - | Jul 6, 02:45 UTC | Jul 6, 10:30 UTC | 7h 45m |
| 2026-07-05 | TAM8079 | - | Jul 5, 11:40 UTC | Jul 5, 23:25 UTC | 11h 45m |
| 2026-07-04 | TAM8078 | - | Jul 4, 21:20 UTC | Jul 5, 08:10 UTC | 10h 50m |
| 2026-07-03 | TAM8065 | - | Jul 3, 22:00 UTC | Jul 4, 08:20 UTC | 10h 20m |
| 2026-07-03 | TAM8066 | GRU → MAD | Jul 3, 02:30 UTC | Jul 3, 12:05 UTC | 9h 35m |
| 2026-07-02 | TAM8089 | - | Jul 2, 11:55 UTC | Jul 2, 23:45 UTC | 11h 50m |
| 2026-07-01 | TAM8088 | - | Jul 1, 21:35 UTC | Jul 2, 08:40 UTC | 11h 5m |
| 2026-07-01 | TAM8181 | - | Jul 1, 01:00 UTC | Jul 1, 09:50 UTC | 8h 50m |
| 2026-06-30 | TAM8180 | - | Jun 30, 02:15 UTC | Jun 30, 11:30 UTC | 9h 15m |
| 2026-06-29 | TAM8121 | - | Jun 29, 11:35 UTC | Jun 29, 22:55 UTC | 11h 20m |
| 2026-06-28 | TAM8120 | - | Jun 28, 21:04 UTC | Jun 29, 07:40 UTC | 10h 35m |
| 2026-06-27 | TAM8113 | - | Jun 27, 23:50 UTC | Jun 28, 08:25 UTC | 8h 35m |
| 2026-06-27 | TAM8112 | GRU → MEX | Jun 27, 12:04 UTC | Jun 27, 20:55 UTC | 8h 50m |
| 2026-06-27 | TAM8127 | - | Jun 27, 00:10 UTC | Jun 27, 08:10 UTC | 8h 0m |
| 2026-06-26 | TAM8126 | GRU → MCO | Jun 26, 13:10 UTC | Jun 26, 21:45 UTC | 8h 35m |
| 2026-06-26 | TAM8181 | - | Jun 26, 01:24 UTC | Jun 26, 10:20 UTC | 8h 55m |
| 2026-06-25 | TAM8180 | - | Jun 25, 03:20 UTC | Jun 25, 12:30 UTC | 9h 10m |
| 2026-06-24 | TAM8067 | CDG → GRU | Jun 24, 11:54 UTC | Jun 24, 23:14 UTC | 11h 20m |
| 2026-06-23 | TAM8068 | GRU → CDG | Jun 23, 22:10 UTC | Jun 24, 08:45 UTC | 10h 35m |
| 2026-06-22 | TAM8113 | - | Jun 22, 23:45 UTC | Jun 23, 08:09 UTC | 8h 25m |
| 2026-06-22 | TAM8112 | GRU → MEX | Jun 22, 12:19 UTC | Jun 22, 21:10 UTC | 8h 50m |
| 2026-06-21 | TAM8202 | - | Jun 21, 11:15 UTC | Jun 21, 21:49 UTC | 10h 35m |
| 2026-06-20 | TAM8113 | - | Jun 20, 23:29 UTC | Jun 21, 07:55 UTC | 8h 25m |
| 2026-06-20 | TAM8112 | GRU → MEX | Jun 20, 12:24 UTC | Jun 20, 21:30 UTC | 9h 5m |
| 2026-06-19 | TAM8195 | MIA → GRU | Jun 19, 15:04 UTC | Jun 19, 22:34 UTC | 7h 30m |
| 2026-06-19 | TAM8190 | - | Jun 19, 02:45 UTC | Jun 19, 10:24 UTC | 7h 40m |
| 2026-06-18 | TAM8059 | JNB → GRU | Jun 18, 13:10 UTC | Jun 18, 23:35 UTC | 10h 25m |
| 2026-06-18 | TAM8058 | - | Jun 18, 02:10 UTC | Jun 18, 10:25 UTC | 8h 15m |
| 2026-06-17 | TAM8075 | - | Jun 17, 13:00 UTC | Jun 17, 22:55 UTC | 9h 55m |
| 2026-06-17 | TAM8076 | - | Jun 17, 00:40 UTC | Jun 17, 10:00 UTC | 9h 20m |
| 2026-06-16 | TAM8115 | BCN → GRU | Jun 16, 11:35 UTC | Jun 16, 22:05 UTC | 10h 31m |
| 2026-06-15 | TAM8114 | - | Jun 15, 22:05 UTC | Jun 16, 08:00 UTC | 9h 55m |
| 2026-06-14 | TAM8127 | - | Jun 14, 23:44 UTC | Jun 15, 07:45 UTC | 8h 0m |
| 2026-06-14 | TAM8126 | GRU → MCO | Jun 14, 12:50 UTC | Jun 14, 21:00 UTC | 8h 10m |
| 2026-06-14 | TAM8181 | - | Jun 14, 01:20 UTC | Jun 14, 10:15 UTC | 8h 55m |
| 2026-06-13 | TAM8180 | - | Jun 13, 02:35 UTC | Jun 13, 11:55 UTC | 9h 19m |
| 2026-06-12 | TAM8079 | AMS → GRU | Jun 12, 11:50 UTC | Jun 12, 23:40 UTC | 11h 50m |
| 2026-06-11 | TAM8078 | GRU → AMS | Jun 11, 21:35 UTC | Jun 12, 08:45 UTC | 11h 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-BGY page for operator, model, and routing details .