sensors Mode-S transponder
E48DF6
ICAO 24-bit transponder address · allocated to Brazil
Currently assigned to PT-MUI · BOEING 777-300ER
- Hex
- E48DF6
- Octal
- 71106766
- Decimal
- 14,978,550
- Country
- BR
- Tail
- PT-MUI
- Type
- B77W
- Flights observed
- 175
- Distinct callsigns
- 20
- Country
- BR
- Last broadcast
- Jul 26, 21:30 UTC
Last known position
Country allocation
The ICAO 24-bit address E48DF6 falls within the block assigned to Brazil (BR) by ICAO Annex 10, Volume III. Every aircraft registered in Brazil 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 |
|---|---|---|---|
| TAM8146 | TAM Brazilian Airlines | 19 | 2026-07-24 |
| TAM8147 | TAM Brazilian Airlines | 16 | 2026-07-25 |
| TAM8084 | TAM Brazilian Airlines | 15 | 2026-07-20 |
| TAM8085 | - | 14 | 2026-07-20 |
| TAM8071 | TAM Brazilian Airlines | 13 | 2026-07-26 |
| TAM8070 | TAM Brazilian Airlines | 13 | 2026-07-26 |
| TAM8191 | TAM Brazilian Airlines | 12 | 2026-07-24 |
| TAM8072 | - | 12 | 2026-07-18 |
| TAM8194 | TAM Brazilian Airlines | 11 | 2026-07-23 |
| TAM8121 | - | 10 | 2026-07-09 |
| TAM8120 | - | 10 | 2026-07-08 |
| TAM8073 | TAM Brazilian Airlines | 10 | 2026-07-19 |
| TAM8115 | - | 5 | 2026-07-12 |
| TAM8114 | - | 5 | 2026-07-11 |
| TAM8076 | - | 3 | 2026-07-13 |
| TAM8075 | - | 3 | 2026-07-13 |
| TAM8199 | - | 1 | 2026-07-08 |
| TAM8198 | - | 1 | 2026-07-07 |
| TAM8149 | TAM Brazilian Airlines | 1 | 2026-05-08 |
| TAM8148 | TAM Brazilian Airlines | 1 | 2026-05-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | TAM8071 | FRA → GRU | Jul 26, 19:55 UTC | Jul 26, 21:30 UTC | 1h 35m |
| 2026-07-26 | TAM8070 | GRU → FRA | Jul 26, 03:05 UTC | Jul 26, 14:35 UTC | 11h 31m |
| 2026-07-25 | TAM8147 | LIS → GRU | Jul 25, 08:35 UTC | Jul 25, 17:35 UTC | 9h 0m |
| 2026-07-24 | TAM8146 | GRU → LIS | Jul 24, 20:50 UTC | Jul 25, 05:50 UTC | 9h 0m |
| 2026-07-24 | TAM8191 | MIA → GRU | Jul 24, 00:20 UTC | Jul 24, 08:00 UTC | 7h 40m |
| 2026-07-23 | TAM8194 | GRU → MIA | Jul 23, 20:30 UTC | Jul 23, 20:55 UTC | 25m |
| 2026-07-23 | TAM8194 | GRU → MIA | Jul 23, 13:20 UTC | Jul 23, 18:50 UTC | 5h 30m |
| 2026-07-20 | TAM8085 | - | Jul 20, 20:50 UTC | Jul 21, 07:45 UTC | 10h 55m |
| 2026-07-20 | TAM8084 | GRU → LHR | Jul 20, 03:45 UTC | Jul 20, 14:10 UTC | 10h 25m |
| 2026-07-19 | TAM8073 | FRA → GIG | Jul 19, 12:15 UTC | Jul 19, 23:35 UTC | 11h 20m |
| 2026-07-18 | TAM8072 | - | Jul 18, 22:00 UTC | Jul 19, 09:15 UTC | 11h 15m |
| 2026-07-18 | TAM8147 | LIS → GRU | Jul 18, 08:55 UTC | Jul 18, 18:10 UTC | 9h 15m |
| 2026-07-17 | TAM8146 | - | Jul 17, 20:50 UTC | Jul 18, 05:45 UTC | 8h 56m |
| 2026-07-16 | TAM8071 | - | Jul 16, 20:09 UTC | Jul 17, 07:50 UTC | 11h 40m |
| 2026-07-16 | TAM8070 | - | Jul 16, 04:15 UTC | Jul 16, 15:00 UTC | 10h 45m |
| 2026-07-14 | TAM8071 | - | Jul 14, 19:50 UTC | Jul 15, 07:30 UTC | 11h 39m |
| 2026-07-14 | TAM8070 | - | Jul 14, 03:20 UTC | Jul 14, 14:00 UTC | 10h 40m |
| 2026-07-13 | TAM8075 | - | Jul 13, 13:30 UTC | Jul 13, 23:30 UTC | 10h 0m |
| 2026-07-13 | TAM8076 | - | Jul 13, 00:35 UTC | Jul 13, 10:00 UTC | 9h 25m |
| 2026-07-12 | TAM8115 | - | Jul 12, 11:40 UTC | Jul 12, 22:05 UTC | 10h 25m |
| 2026-07-11 | TAM8114 | - | Jul 11, 22:01 UTC | Jul 12, 07:31 UTC | 9h 30m |
| 2026-07-10 | TAM8071 | - | Jul 10, 19:45 UTC | Jul 11, 07:25 UTC | 11h 41m |
| 2026-07-10 | TAM8070 | - | Jul 10, 03:30 UTC | Jul 10, 14:15 UTC | 10h 45m |
| 2026-07-09 | TAM8121 | - | Jul 9, 11:50 UTC | Jul 9, 22:50 UTC | 11h 0m |
| 2026-07-08 | TAM8120 | - | Jul 8, 21:15 UTC | Jul 9, 07:55 UTC | 10h 40m |
| 2026-07-08 | TAM8199 | - | Jul 8, 03:15 UTC | Jul 8, 10:40 UTC | 7h 25m |
| 2026-07-07 | TAM8198 | - | Jul 7, 16:15 UTC | Jul 8, 00:20 UTC | 8h 5m |
| 2026-07-06 | TAM8071 | - | Jul 6, 19:50 UTC | Jul 7, 07:00 UTC | 11h 10m |
| 2026-07-06 | TAM8070 | GRU → FRA | Jul 6, 03:10 UTC | Jul 6, 14:15 UTC | 11h 5m |
| 2026-07-05 | TAM8147 | - | Jul 5, 08:45 UTC | Jul 5, 17:55 UTC | 9h 10m |
| 2026-07-04 | TAM8146 | GRU → LIS | Jul 4, 21:05 UTC | Jul 5, 05:55 UTC | 8h 50m |
| 2026-07-03 | TAM8071 | - | Jul 3, 19:55 UTC | Jul 4, 07:25 UTC | 11h 30m |
| 2026-07-03 | TAM8070 | GRU → FRA | Jul 3, 04:15 UTC | Jul 3, 15:05 UTC | 10h 50m |
| 2026-07-02 | TAM8121 | - | Jul 2, 12:05 UTC | Jul 2, 22:55 UTC | 10h 50m |
| 2026-07-01 | TAM8120 | - | Jul 1, 21:20 UTC | Jul 2, 08:15 UTC | 10h 55m |
| 2026-06-30 | TAM8075 | - | Jun 30, 13:35 UTC | Jun 30, 23:15 UTC | 9h 40m |
| 2026-06-30 | TAM8076 | - | Jun 30, 00:45 UTC | Jun 30, 10:15 UTC | 9h 30m |
| 2026-06-29 | TAM8115 | BCN → GRU | Jun 29, 11:45 UTC | Jun 29, 21:50 UTC | 10h 5m |
| 2026-06-28 | TAM8114 | - | Jun 28, 21:59 UTC | Jun 29, 07:40 UTC | 9h 40m |
| 2026-06-27 | TAM8085 | LHR → GRU | Jun 27, 20:55 UTC | Jun 28, 07:34 UTC | 10h 40m |
| 2026-06-27 | TAM8084 | - | Jun 27, 03:40 UTC | Jun 27, 14:25 UTC | 10h 45m |
| 2026-06-26 | TAM8121 | - | Jun 26, 11:49 UTC | Jun 26, 22:40 UTC | 10h 50m |
| 2026-06-25 | TAM8120 | - | Jun 25, 21:05 UTC | Jun 26, 07:50 UTC | 10h 45m |
| 2026-06-24 | TAM8073 | - | Jun 24, 12:44 UTC | Jun 24, 23:54 UTC | 11h 10m |
| 2026-06-23 | TAM8072 | GIG → FRA | Jun 23, 21:54 UTC | Jun 24, 09:29 UTC | 11h 35m |
| 2026-06-23 | TAM8147 | - | Jun 23, 08:50 UTC | Jun 23, 17:54 UTC | 9h 5m |
| 2026-06-22 | TAM8146 | GRU → LIS | Jun 22, 21:10 UTC | Jun 23, 06:09 UTC | 9h 0m |
| 2026-06-21 | TAM8073 | - | Jun 21, 11:30 UTC | Jun 21, 22:34 UTC | 11h 5m |
| 2026-06-20 | TAM8072 | GIG → FRA | Jun 20, 21:40 UTC | Jun 21, 08:40 UTC | 11h 0m |
| 2026-06-20 | TAM8147 | - | Jun 20, 09:19 UTC | Jun 20, 18:10 UTC | 8h 50m |
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 PT-MUI page for operator, model, and routing details .