sensors Mode-S transponder
E48F72
ICAO 24-bit transponder address · allocated to Brazil
Currently assigned to PR-NGM · EMBRAER EMB-505 Phenom 300
- Hex
- E48F72
- Octal
- 71107562
- Decimal
- 14,978,930
- Country
- BR
- Tail
- PR-NGM
- Type
- E55P
- Flights observed
- 89
- Distinct callsigns
- 3
- Country
- BR
- Last broadcast
- 16d ago
Last known position
Country allocation
The ICAO 24-bit address E48F72 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 3 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | AVANTTO | - | Jul 26, 18:10 UTC | Jul 26, 18:30 UTC | 20m |
| 2026-07-26 | AVANTTO | - | Jul 26, 14:20 UTC | Jul 26, 16:25 UTC | 2h 5m |
| 2026-07-24 | AVANTTO | - | Jul 24, 23:00 UTC | Jul 25, 01:40 UTC | 2h 40m |
| 2026-07-24 | AVANTTO | - | Jul 24, 21:40 UTC | Jul 24, 21:55 UTC | 15m |
| 2026-07-19 | AVANTTO | - | Jul 19, 17:10 UTC | Jul 19, 18:00 UTC | 50m |
| 2026-07-17 | AVANTTO | - | Jul 17, 17:20 UTC | Jul 17, 17:55 UTC | 35m |
| 2026-07-14 | AVANTTO | - | Jul 14, 14:05 UTC | Jul 14, 14:55 UTC | 50m |
| 2026-07-13 | AVANTTO | - | Jul 13, 11:50 UTC | Jul 13, 12:25 UTC | 35m |
| 2026-07-10 | AVANTTO | - | Jul 10, 19:05 UTC | Jul 10, 19:35 UTC | 30m |
| 2026-07-10 | AVANTTO | - | Jul 10, 17:55 UTC | Jul 10, 18:20 UTC | 25m |
| 2026-07-08 | AVANTTO | - | Jul 8, 20:45 UTC | Jul 8, 21:20 UTC | 35m |
| 2026-07-08 | AVANTTO | - | Jul 8, 19:35 UTC | Jul 8, 19:55 UTC | 20m |
| 2026-07-07 | AVANTTO | - | Jul 7, 12:35 UTC | Jul 7, 13:00 UTC | 25m |
| 2026-07-07 | AVANTTO | - | Jul 7, 11:20 UTC | Jul 7, 12:00 UTC | 40m |
| 2026-07-06 | AVANTTO | - | Jul 6, 14:50 UTC | Jul 6, 16:45 UTC | 1h 55m |
| 2026-07-06 | AVANTTO | - | Jul 6, 12:20 UTC | Jul 6, 13:35 UTC | 1h 15m |
| 2026-07-02 | AVANTTO | - | Jul 2, 00:20 UTC | Jul 2, 00:35 UTC | 15m |
| 2026-07-01 | AVANTTO | - | Jul 1, 17:45 UTC | Jul 1, 23:20 UTC | 5h 35m |
| 2026-07-01 | AVANTTO | CGH → RTE | Jul 1, 16:35 UTC | Jul 1, 16:50 UTC | 15m |
| 2026-06-30 | AVANTTO | - | Jun 30, 11:50 UTC | Jul 1, 00:20 UTC | 12h 30m |
| 2026-06-28 | AVANTTO | - | Jun 28, 15:29 UTC | Jun 28, 16:00 UTC | 30m |
| 2026-06-26 | AVANTTO | - | Jun 26, 13:59 UTC | Jun 26, 14:09 UTC | 10m |
| 2026-06-25 | N | CGH → CGH | Jun 25, 11:50 UTC | Jun 25, 17:05 UTC | 5h 15m |
| 2026-06-23 | N | - | Jun 23, 11:35 UTC | Jun 23, 11:59 UTC | 25m |
| 2026-06-22 | N | - | Jun 22, 17:00 UTC | Jun 22, 17:15 UTC | 15m |
| 2026-06-22 | N | - | Jun 22, 14:29 UTC | Jun 22, 15:14 UTC | 45m |
| 2026-06-22 | N | - | Jun 22, 10:44 UTC | Jun 22, 11:09 UTC | 25m |
| 2026-06-21 | N | - | Jun 21, 19:20 UTC | Jun 21, 19:50 UTC | 30m |
| 2026-06-19 | N | - | Jun 19, 16:09 UTC | Jun 19, 16:29 UTC | 20m |
| 2026-06-10 | N | - | Jun 10, 18:30 UTC | Jun 10, 19:35 UTC | 1h 5m |
| 2026-06-10 | N | - | Jun 10, 11:20 UTC | Jun 10, 12:25 UTC | 1h 5m |
| 2026-06-09 | N | CGH → RTE | Jun 9, 23:30 UTC | Jun 9, 23:40 UTC | 10m |
| 2026-06-07 | N | - | Jun 7, 19:10 UTC | Jun 7, 19:35 UTC | 25m |
| 2026-06-07 | N | - | Jun 7, 16:40 UTC | Jun 7, 17:05 UTC | 25m |
| 2026-06-07 | N | - | Jun 7, 15:15 UTC | Jun 7, 15:55 UTC | 40m |
| 2026-06-04 | N | - | Jun 4, 13:00 UTC | Jun 4, 13:20 UTC | 20m |
| 2026-06-03 | N | - | Jun 3, 22:20 UTC | Jun 3, 22:35 UTC | 15m |
| 2026-06-03 | N | - | Jun 3, 20:15 UTC | Jun 3, 20:50 UTC | 35m |
| 2026-06-03 | N | - | Jun 3, 17:10 UTC | Jun 3, 17:25 UTC | 15m |
| 2026-06-01 | N | - | Jun 1, 15:50 UTC | Jun 1, 16:25 UTC | 35m |
| 2026-06-01 | N | - | Jun 1, 14:40 UTC | Jun 1, 15:00 UTC | 20m |
| 2026-05-31 | N | - | May 31, 16:20 UTC | May 31, 16:55 UTC | 35m |
| 2026-05-31 | N | - | May 31, 14:30 UTC | May 31, 14:55 UTC | 25m |
| 2026-05-26 | PRNGM | CGH → CGH | May 26, 12:50 UTC | May 26, 13:00 UTC | 10m |
| 2026-05-24 | PRNGM | - | May 24, 23:30 UTC | May 24, 23:46 UTC | 16m |
| 2026-05-22 | PRNGM | - | May 22, 16:45 UTC | May 22, 18:05 UTC | 1h 20m |
| 2026-05-17 | PRNGM | - | May 17, 19:05 UTC | May 17, 19:55 UTC | 50m |
| 2026-05-17 | PRNGM | - | May 17, 15:15 UTC | May 17, 15:31 UTC | 15m |
| 2026-05-16 | PRNGM | CGH → CGH | May 16, 11:35 UTC | May 16, 23:10 UTC | 11h 35m |
| 2026-05-15 | PRNGM | - | May 15, 14:50 UTC | May 15, 15:30 UTC | 40m |
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 PR-NGM page for operator, model, and routing details .