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