sensors Mode-S transponder
E4A465
ICAO 24-bit transponder address · allocated to Brazil
- Hex
- E4A465
- Octal
- 71122145
- Decimal
- 14,984,293
- Country
- BR
- Flights observed
- 40
- Distinct callsigns
- 20
- Country
- BR
- Last broadcast
- 13d ago
Last known position
Country allocation
The ICAO 24-bit address E4A465 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 |
|---|---|---|---|
| AP68 | - | 5 | 2026-05-15 |
| AP118 | - | 4 | 2026-05-15 |
| AP84 | - | 3 | 2026-05-01 |
| LEO2 | - | 2 | 2026-05-14 |
| APTRUNFO | - | 2 | 2026-04-13 |
| APCOPAS | - | 2 | 2026-04-14 |
| AP82 | - | 2 | 2026-05-14 |
| AP81 | - | 2 | 2026-05-01 |
| AP27 | - | 2 | 2026-05-03 |
| AP105 | Airbus Industrie | 2 | 2026-05-16 |
| EEXD43 | - | 1 | 2026-04-29 |
| CORING2 | - | 1 | 2026-05-06 |
| COPAS2 | - | 1 | 2026-04-13 |
| APCORING | - | 1 | 2026-05-03 |
| AP80 | - | 1 | 2026-05-08 |
| AP72 | - | 1 | 2026-04-30 |
| AP66 | - | 1 | 2026-05-07 |
| AP61 | - | 1 | 2026-04-23 |
| AP45 | - | 1 | 2026-05-05 |
| AP43 | - | 1 | 2026-05-07 |
Recent flights last 40
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-16 | AP105 | FRA → FRA | May 16, 16:00 UTC | May 16, 16:45 UTC | 45m |
| 2026-05-15 | AP118 | - | May 15, 14:35 UTC | May 15, 15:05 UTC | 29m |
| 2026-05-15 | AP25 | - | May 15, 12:20 UTC | May 15, 12:50 UTC | 30m |
| 2026-05-15 | AP68 | - | May 15, 10:25 UTC | May 15, 10:55 UTC | 30m |
| 2026-05-14 | AP82 | - | May 14, 17:20 UTC | May 14, 17:35 UTC | 15m |
| 2026-05-14 | AP118 | - | May 14, 12:25 UTC | May 14, 13:15 UTC | 50m |
| 2026-05-14 | LEO2 | - | May 14, 10:15 UTC | May 14, 11:05 UTC | 50m |
| 2026-05-12 | AP68 | - | May 12, 19:05 UTC | May 12, 19:35 UTC | 30m |
| 2026-05-12 | LEO2 | - | May 12, 16:50 UTC | May 12, 17:25 UTC | 35m |
| 2026-05-12 | AP82 | - | May 12, 14:30 UTC | May 12, 15:10 UTC | 40m |
| 2026-05-08 | AP126 | - | May 8, 15:40 UTC | May 8, 16:30 UTC | 50m |
| 2026-05-08 | AP80 | - | May 8, 12:39 UTC | May 8, 13:20 UTC | 40m |
| 2026-05-07 | AP66 | - | May 7, 14:35 UTC | May 7, 14:55 UTC | 20m |
| 2026-05-07 | AP43 | - | May 7, 10:10 UTC | May 7, 10:45 UTC | 35m |
| 2026-05-06 | CORING2 | - | May 6, 10:10 UTC | May 6, 11:05 UTC | 55m |
| 2026-05-05 | AP68 | - | May 5, 19:25 UTC | May 5, 19:40 UTC | 15m |
| 2026-05-05 | AP45 | - | May 5, 17:00 UTC | May 5, 17:10 UTC | 10m |
| 2026-05-05 | AP118 | - | May 5, 15:01 UTC | May 5, 15:30 UTC | 30m |
| 2026-05-05 | AP11 | - | May 5, 12:40 UTC | May 5, 13:30 UTC | 50m |
| 2026-05-03 | APCORING | - | May 3, 18:25 UTC | May 3, 18:50 UTC | 25m |
| 2026-05-03 | AP27 | - | May 3, 11:45 UTC | May 3, 12:10 UTC | 25m |
| 2026-05-01 | AP81 | - | May 1, 18:30 UTC | May 1, 18:55 UTC | 25m |
| 2026-05-01 | AP84 | - | May 1, 15:40 UTC | May 1, 16:20 UTC | 40m |
| 2026-05-01 | AP118 | - | May 1, 13:30 UTC | May 1, 14:05 UTC | 35m |
| 2026-04-30 | AP84 | - | Apr 30, 18:20 UTC | Apr 30, 19:00 UTC | 40m |
| 2026-04-30 | AP72 | - | Apr 30, 15:30 UTC | Apr 30, 16:25 UTC | 55m |
| 2026-04-29 | EEXD43 | - | Apr 29, 12:40 UTC | Apr 29, 12:50 UTC | 10m |
| 2026-04-23 | AP84 | - | Apr 23, 18:10 UTC | Apr 23, 18:40 UTC | 30m |
| 2026-04-23 | AP61 | - | Apr 23, 15:20 UTC | Apr 23, 15:35 UTC | 15m |
| 2026-04-23 | AP105 | FRA → FRA | Apr 23, 12:30 UTC | Apr 23, 13:20 UTC | 50m |
| 2026-04-22 | AP27 | - | Apr 22, 10:35 UTC | Apr 22, 11:35 UTC | 1h 0m |
| 2026-04-17 | AP68 | - | Apr 17, 15:20 UTC | Apr 17, 15:40 UTC | 20m |
| 2026-04-17 | AP68 | - | Apr 17, 15:00 UTC | Apr 17, 15:15 UTC | 15m |
| 2026-04-17 | - | - | Apr 17, 11:20 UTC | Apr 17, 11:30 UTC | 10m |
| 2026-04-14 | APCOPAS | - | Apr 14, 10:50 UTC | Apr 14, 11:15 UTC | 25m |
| 2026-04-14 | APCOPAS | - | Apr 14, 10:40 UTC | Apr 14, 11:05 UTC | 25m |
| 2026-04-13 | COPAS2 | - | Apr 13, 19:35 UTC | Apr 13, 20:05 UTC | 30m |
| 2026-04-13 | AP81 | - | Apr 13, 17:05 UTC | Apr 13, 17:45 UTC | 40m |
| 2026-04-13 | APTRUNFO | - | Apr 13, 11:55 UTC | Apr 13, 12:25 UTC | 30m |
| 2026-04-13 | APTRUNFO | - | Apr 13, 11:40 UTC | Apr 13, 12:15 UTC | 35m |
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.