sensors Mode-S transponder
E8046F
ICAO 24-bit transponder address · allocated to Chile
Currently assigned to CC-BGT · BOEING 787-9 Dreamliner
- Hex
- E8046F
- Octal
- 72002157
- Decimal
- 15,205,487
- Country
- CL
- Tail
- CC-BGT
- Type
- B789
- Flights observed
- 210
- Distinct callsigns
- 20
- Country
- CL
- Last broadcast
- Jul 26, 21:45 UTC
Last known position
Country allocation
The ICAO 24-bit address E8046F 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 |
|---|---|---|---|
| TAM8059 | TAM Brazilian Airlines | 14 | 2026-07-26 |
| TAM8058 | TAM Brazilian Airlines | 14 | 2026-07-26 |
| TAM8078 | TAM Brazilian Airlines | 13 | 2026-07-24 |
| TAM8150 | TAM Brazilian Airlines | 11 | 2026-07-21 |
| TAM8195 | TAM Brazilian Airlines | 10 | 2026-06-26 |
| TAM8079 | TAM Brazilian Airlines | 9 | 2026-07-25 |
| TAM4777 | TAM Brazilian Airlines | 9 | 2026-07-22 |
| TAM8190 | - | 8 | 2026-06-26 |
| TAM8181 | TAM Brazilian Airlines | 8 | 2026-07-18 |
| TAM8180 | - | 8 | 2026-07-17 |
| TAM8127 | TAM Brazilian Airlines | 8 | 2026-07-18 |
| TAM8126 | - | 8 | 2026-07-18 |
| TAM4776 | TAM Brazilian Airlines | 8 | 2026-07-21 |
| TAM8151 | TAM Brazilian Airlines | 7 | 2026-07-21 |
| TAM8068 | - | 7 | 2026-07-15 |
| TAM8067 | - | 7 | 2026-07-16 |
| TAM8148 | TAM Brazilian Airlines | 6 | 2026-04-22 |
| TAM8149 | TAM Brazilian Airlines | 5 | 2026-04-22 |
| TAM8076 | - | 5 | 2026-07-05 |
| TAM8075 | - | 5 | 2026-07-05 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | TAM8059 | JNB → GRU | Jul 26, 13:20 UTC | Jul 26, 21:45 UTC | 8h 25m |
| 2026-07-26 | TAM8058 | GRU → JNB | Jul 26, 02:20 UTC | Jul 26, 10:15 UTC | 7h 56m |
| 2026-07-25 | TAM8079 | AMS → GRU | Jul 25, 11:50 UTC | Jul 25, 22:50 UTC | 11h 0m |
| 2026-07-24 | TAM8078 | GRU → AMS | Jul 24, 21:10 UTC | Jul 25, 08:15 UTC | 11h 5m |
| 2026-07-23 | TAM8113 | MEX → GRU | Jul 23, 23:50 UTC | Jul 24, 08:25 UTC | 8h 35m |
| 2026-07-23 | TAM8112 | GRU → MEX | Jul 23, 12:10 UTC | Jul 23, 21:05 UTC | 8h 55m |
| 2026-07-22 | TAM8113 | MEX → GRU | Jul 22, 23:35 UTC | Jul 23, 08:05 UTC | 8h 30m |
| 2026-07-22 | TAM8112 | - | Jul 22, 12:05 UTC | Jul 22, 20:50 UTC | 8h 45m |
| 2026-07-22 | TAM4777 | FOR → GRU | Jul 22, 05:15 UTC | Jul 22, 05:25 UTC | 10m |
| 2026-07-21 | TAM8151 | LIS → FOR | Jul 21, 18:35 UTC | Jul 22, 01:25 UTC | 6h 50m |
| 2026-07-21 | TAM8150 | FOR → LIS | Jul 21, 09:35 UTC | Jul 21, 16:05 UTC | 6h 30m |
| 2026-07-21 | TAM4776 | GRU → FOR | Jul 21, 03:25 UTC | Jul 21, 06:10 UTC | 2h 45m |
| 2026-07-20 | TAM8121 | FCO → GRU | Jul 20, 11:40 UTC | Jul 20, 22:40 UTC | 11h 0m |
| 2026-07-19 | TAM8120 | GRU → FCO | Jul 19, 21:05 UTC | Jul 20, 07:25 UTC | 10h 20m |
| 2026-07-18 | TAM8127 | MCO → GRU | Jul 18, 23:50 UTC | Jul 19, 07:45 UTC | 7h 55m |
| 2026-07-18 | TAM8126 | - | Jul 18, 12:45 UTC | Jul 18, 20:55 UTC | 8h 10m |
| 2026-07-18 | TAM8181 | JFK → GRU | Jul 18, 01:00 UTC | Jul 18, 10:05 UTC | 9h 6m |
| 2026-07-17 | TAM8180 | - | Jul 17, 02:30 UTC | Jul 17, 11:20 UTC | 8h 50m |
| 2026-07-16 | TAM8067 | - | Jul 16, 11:25 UTC | Jul 16, 22:35 UTC | 11h 10m |
| 2026-07-15 | TAM8068 | - | Jul 15, 21:45 UTC | Jul 16, 08:10 UTC | 10h 25m |
| 2026-07-15 | TAM8127 | - | Jul 15, 01:45 UTC | Jul 15, 09:55 UTC | 8h 10m |
| 2026-07-14 | TAM8126 | - | Jul 14, 12:35 UTC | Jul 14, 20:45 UTC | 8h 10m |
| 2026-07-14 | TAM4777 | - | Jul 14, 05:15 UTC | Jul 14, 08:15 UTC | 3h 0m |
| 2026-07-13 | TAM8151 | LIS → FOR | Jul 13, 18:40 UTC | Jul 14, 01:25 UTC | 6h 45m |
| 2026-07-13 | TAM8150 | - | Jul 13, 14:05 UTC | Jul 13, 15:55 UTC | 1h 50m |
| 2026-07-13 | TAM8150 | - | Jul 13, 09:20 UTC | Jul 13, 09:40 UTC | 20m |
| 2026-07-13 | TAM4776 | - | Jul 13, 03:45 UTC | Jul 13, 06:40 UTC | 2h 55m |
| 2026-07-12 | TAM8059 | - | Jul 12, 13:30 UTC | Jul 13, 00:05 UTC | 10h 35m |
| 2026-07-12 | TAM8058 | - | Jul 12, 03:25 UTC | Jul 12, 10:20 UTC | 6h 55m |
| 2026-07-12 | TAM8058 | - | Jul 12, 02:30 UTC | Jul 12, 02:45 UTC | 15m |
| 2026-07-11 | TAM8067 | - | Jul 11, 11:15 UTC | Jul 11, 22:40 UTC | 11h 25m |
| 2026-07-10 | TAM8068 | - | Jul 10, 22:10 UTC | Jul 11, 08:20 UTC | 10h 10m |
| 2026-07-10 | TAM8113 | - | Jul 10, 05:05 UTC | Jul 10, 13:15 UTC | 8h 10m |
| 2026-07-09 | TAM8112 | - | Jul 9, 12:20 UTC | Jul 9, 21:55 UTC | 9h 35m |
| 2026-07-08 | TAM8065 | - | Jul 8, 22:30 UTC | Jul 9, 08:20 UTC | 9h 50m |
| 2026-07-08 | LAN706 | SCL → MAD | Jul 8, 02:10 UTC | Jul 8, 11:40 UTC | 9h 30m |
| 2026-07-06 | LAN705 | - | Jul 6, 22:25 UTC | Jul 7, 08:55 UTC | 10h 30m |
| 2026-07-06 | TAM8066 | GRU → MAD | Jul 6, 02:40 UTC | Jul 6, 12:05 UTC | 9h 25m |
| 2026-07-05 | TAM8075 | - | Jul 5, 13:05 UTC | Jul 5, 23:15 UTC | 10h 10m |
| 2026-07-05 | TAM8076 | - | Jul 5, 00:40 UTC | Jul 5, 10:00 UTC | 9h 20m |
| 2026-07-04 | TAM8115 | BCN → GRU | Jul 4, 11:30 UTC | Jul 4, 21:55 UTC | 10h 25m |
| 2026-07-03 | TAM8114 | - | Jul 3, 21:30 UTC | Jul 4, 07:15 UTC | 9h 45m |
| 2026-07-03 | TAM8181 | - | Jul 3, 01:20 UTC | Jul 3, 10:10 UTC | 8h 50m |
| 2026-07-02 | TAM8180 | - | Jul 2, 02:45 UTC | Jul 2, 11:50 UTC | 9h 5m |
| 2026-07-01 | TAM8075 | - | Jul 1, 13:10 UTC | Jul 1, 22:55 UTC | 9h 45m |
| 2026-07-01 | TAM8076 | - | Jul 1, 01:10 UTC | Jul 1, 10:40 UTC | 9h 30m |
| 2026-06-30 | TAM8067 | CDG → GRU | Jun 30, 11:35 UTC | Jun 30, 22:35 UTC | 11h 0m |
| 2026-06-29 | TAM8068 | GRU → CDG | Jun 29, 21:44 UTC | Jun 30, 08:20 UTC | 10h 36m |
| 2026-06-29 | TAM8127 | - | Jun 29, 00:34 UTC | Jun 29, 08:29 UTC | 7h 55m |
| 2026-06-28 | TAM8126 | GRU → MCO | Jun 28, 13:14 UTC | Jun 28, 21:40 UTC | 8h 25m |
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-BGT page for operator, model, and routing details .