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