sensors Mode-S transponder
E48BA7
ICAO 24-bit transponder address · allocated to Brazil
Currently assigned to PT-MUF · BOEING 777-300ER
- Hex
- E48BA7
- Octal
- 71105647
- Decimal
- 14,977,959
- Country
- BR
- Tail
- PT-MUF
- Type
- B77W
- Flights observed
- 161
- Distinct callsigns
- 20
- Country
- BR
- Last broadcast
- Jul 26, 19:40 UTC
Last known position
Country allocation
The ICAO 24-bit address E48BA7 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 |
|---|---|---|---|
| TAM8072 | TAM Brazilian Airlines | 20 | 2026-07-22 |
| TAM8073 | TAM Brazilian Airlines | 18 | 2026-07-23 |
| TAM8071 | TAM Brazilian Airlines | 15 | 2026-07-24 |
| TAM8070 | TAM Brazilian Airlines | 14 | 2026-07-24 |
| TAM8085 | - | 12 | 2026-07-21 |
| TAM8146 | - | 11 | 2026-07-18 |
| TAM8084 | TAM Brazilian Airlines | 11 | 2026-07-21 |
| TAM8121 | TAM Brazilian Airlines | 10 | 2026-07-26 |
| TAM8120 | TAM Brazilian Airlines | 10 | 2026-07-25 |
| TAM8194 | TAM Brazilian Airlines | 9 | 2026-06-15 |
| TAM8147 | TAM Brazilian Airlines | 9 | 2026-07-19 |
| TAM8191 | - | 6 | 2026-06-16 |
| TAM8076 | - | 3 | 2026-06-29 |
| TAM8075 | - | 3 | 2026-06-29 |
| TAM9400 | TAM Brazilian Airlines | 2 | 2026-05-17 |
| TAM8202 | - | 2 | 2026-07-01 |
| TAM8115 | TAM Brazilian Airlines | 2 | 2026-07-02 |
| TAM8114 | - | 2 | 2026-07-02 |
| TAM8195 | - | 1 | 2026-07-11 |
| TAM8190 | - | 1 | 2026-07-11 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | TAM8121 | FCO → GRU | Jul 26, 11:35 UTC | Jul 26, 19:40 UTC | 8h 5m |
| 2026-07-25 | TAM8120 | GRU → FCO | Jul 25, 21:20 UTC | Jul 26, 08:00 UTC | 10h 41m |
| 2026-07-24 | TAM8071 | FRA → GRU | Jul 24, 19:40 UTC | Jul 25, 07:10 UTC | 11h 30m |
| 2026-07-24 | TAM8070 | GRU → FRA | Jul 24, 04:00 UTC | Jul 24, 14:55 UTC | 10h 55m |
| 2026-07-23 | TAM8073 | FRA → GIG | Jul 23, 11:55 UTC | Jul 23, 22:50 UTC | 10h 55m |
| 2026-07-22 | TAM8072 | GIG → FRA | Jul 22, 21:20 UTC | Jul 23, 08:45 UTC | 11h 25m |
| 2026-07-21 | TAM8085 | - | Jul 21, 20:40 UTC | Jul 22, 04:45 UTC | 8h 5m |
| 2026-07-21 | TAM8084 | GRU → LHR | Jul 21, 03:15 UTC | Jul 21, 13:45 UTC | 10h 30m |
| 2026-07-20 | TAM8073 | FRA → GIG | Jul 20, 11:50 UTC | Jul 20, 23:05 UTC | 11h 15m |
| 2026-07-19 | TAM8072 | - | Jul 19, 21:25 UTC | Jul 20, 07:50 UTC | 10h 25m |
| 2026-07-19 | TAM8147 | LIS → GRU | Jul 19, 09:10 UTC | Jul 19, 18:30 UTC | 9h 20m |
| 2026-07-18 | TAM8146 | - | Jul 18, 21:10 UTC | Jul 19, 05:50 UTC | 8h 40m |
| 2026-07-17 | TAM8121 | - | Jul 17, 11:30 UTC | Jul 17, 22:25 UTC | 10h 55m |
| 2026-07-16 | TAM8120 | - | Jul 16, 21:10 UTC | Jul 17, 07:44 UTC | 10h 35m |
| 2026-07-15 | TAM8085 | - | Jul 15, 20:40 UTC | Jul 16, 07:45 UTC | 11h 5m |
| 2026-07-15 | TAM8084 | - | Jul 15, 03:20 UTC | Jul 15, 13:55 UTC | 10h 35m |
| 2026-07-14 | TAM8073 | - | Jul 14, 11:50 UTC | Jul 14, 23:10 UTC | 11h 19m |
| 2026-07-13 | TAM8072 | - | Jul 13, 21:20 UTC | Jul 14, 08:40 UTC | 11h 20m |
| 2026-07-12 | TAM8071 | - | Jul 12, 19:50 UTC | Jul 13, 07:35 UTC | 11h 45m |
| 2026-07-12 | TAM8070 | GRU → FRA | Jul 12, 04:20 UTC | Jul 12, 15:01 UTC | 10h 40m |
| 2026-07-11 | TAM8195 | - | Jul 11, 17:30 UTC | Jul 12, 01:20 UTC | 7h 50m |
| 2026-07-11 | TAM8190 | - | Jul 11, 06:20 UTC | Jul 11, 14:25 UTC | 8h 5m |
| 2026-07-10 | TAM8073 | - | Jul 10, 16:35 UTC | Jul 11, 04:05 UTC | 11h 31m |
| 2026-07-10 | TAM8072 | - | Jul 10, 00:35 UTC | Jul 10, 11:30 UTC | 10h 55m |
| 2026-07-09 | TAM8147 | - | Jul 9, 09:05 UTC | Jul 9, 18:05 UTC | 9h 0m |
| 2026-07-08 | TAM8146 | - | Jul 8, 20:55 UTC | Jul 9, 06:00 UTC | 9h 5m |
| 2026-07-07 | TAM8071 | - | Jul 7, 19:45 UTC | Jul 8, 07:25 UTC | 11h 40m |
| 2026-07-07 | TAM8070 | GRU → FRA | Jul 7, 03:40 UTC | Jul 7, 14:45 UTC | 11h 5m |
| 2026-07-05 | TAM8121 | - | Jul 5, 11:25 UTC | Jul 5, 22:35 UTC | 11h 10m |
| 2026-07-04 | TAM8120 | - | Jul 4, 21:10 UTC | Jul 5, 07:50 UTC | 10h 40m |
| 2026-07-03 | TAM8085 | LHR → GRU | Jul 3, 20:40 UTC | Jul 4, 07:40 UTC | 11h 0m |
| 2026-07-03 | TAM8084 | - | Jul 3, 03:40 UTC | Jul 3, 14:25 UTC | 10h 45m |
| 2026-07-02 | TAM8115 | BCN → GRU | Jul 2, 13:55 UTC | Jul 3, 00:25 UTC | 10h 30m |
| 2026-07-02 | TAM8114 | - | Jul 2, 01:15 UTC | Jul 2, 11:05 UTC | 9h 50m |
| 2026-07-01 | TAM8202 | - | Jul 1, 10:50 UTC | Jul 1, 21:50 UTC | 11h 0m |
| 2026-06-29 | TAM8075 | - | Jun 29, 13:19 UTC | Jun 29, 23:19 UTC | 10h 0m |
| 2026-06-29 | TAM8076 | - | Jun 29, 01:10 UTC | Jun 29, 10:29 UTC | 9h 20m |
| 2026-06-28 | TAM8115 | BCN → GRU | Jun 28, 12:05 UTC | Jun 28, 22:04 UTC | 10h 0m |
| 2026-06-27 | TAM8114 | - | Jun 27, 21:40 UTC | Jun 28, 07:34 UTC | 9h 55m |
| 2026-06-26 | TAM8085 | LHR → GRU | Jun 26, 20:55 UTC | Jun 27, 07:24 UTC | 10h 30m |
| 2026-06-26 | TAM8084 | - | Jun 26, 03:54 UTC | Jun 26, 14:19 UTC | 10h 25m |
| 2026-06-25 | TAM8121 | - | Jun 25, 11:59 UTC | Jun 25, 23:09 UTC | 11h 10m |
| 2026-06-24 | TAM8120 | - | Jun 24, 21:29 UTC | Jun 25, 08:24 UTC | 10h 55m |
| 2026-06-23 | TAM8121 | - | Jun 23, 11:35 UTC | Jun 23, 22:05 UTC | 10h 30m |
| 2026-06-22 | TAM8120 | - | Jun 22, 21:14 UTC | Jun 23, 08:15 UTC | 11h 0m |
| 2026-06-21 | TAM8071 | - | Jun 21, 19:50 UTC | Jun 22, 07:25 UTC | 11h 35m |
| 2026-06-21 | TAM8070 | GRU → FRA | Jun 21, 03:25 UTC | Jun 21, 14:34 UTC | 11h 10m |
| 2026-06-19 | TAM8073 | - | Jun 19, 11:24 UTC | Jun 19, 22:19 UTC | 10h 55m |
| 2026-06-18 | TAM8072 | GIG → FRA | Jun 18, 21:25 UTC | Jun 19, 08:09 UTC | 10h 44m |
| 2026-06-18 | TAM8147 | - | Jun 18, 09:05 UTC | Jun 18, 18:20 UTC | 9h 15m |
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-MUF page for operator, model, and routing details .