sensors Mode-S transponder
E48D6E
ICAO 24-bit transponder address · allocated to Brazil
Currently assigned to PP-NMM · EMBRAER EMB-505 Phenom 300
- Hex
- E48D6E
- Octal
- 71106556
- Decimal
- 14,978,414
- Country
- BR
- Tail
- PP-NMM
- Type
- E55P
- Flights observed
- 71
- Distinct callsigns
- 1
- Country
- BR
- Last broadcast
- Jul 26, 14:35 UTC
Last known position
Country allocation
The ICAO 24-bit address E48D6E 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| PPNMM | - | 71 | 2026-07-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | PPNMM | - | Jul 26, 13:45 UTC | Jul 26, 14:35 UTC | 50m |
| 2026-07-26 | PPNMM | - | Jul 26, 12:10 UTC | Jul 26, 12:30 UTC | 20m |
| 2026-07-24 | PPNMM | CGH → CGH | Jul 24, 12:40 UTC | Jul 24, 19:05 UTC | 6h 25m |
| 2026-07-19 | PPNMM | - | Jul 19, 23:00 UTC | Jul 19, 23:50 UTC | 50m |
| 2026-07-18 | PPNMM | - | Jul 18, 15:30 UTC | Jul 18, 16:20 UTC | 50m |
| 2026-07-18 | PPNMM | - | Jul 18, 11:35 UTC | Jul 18, 12:05 UTC | 30m |
| 2026-07-17 | PPNMM | - | Jul 17, 16:24 UTC | Jul 17, 16:55 UTC | 30m |
| 2026-07-15 | PPNMM | - | Jul 15, 14:15 UTC | Jul 15, 14:40 UTC | 25m |
| 2026-07-14 | PPNMM | - | Jul 14, 10:25 UTC | Jul 14, 11:00 UTC | 35m |
| 2026-07-10 | PPNMM | CGH → CGH | Jul 10, 14:25 UTC | Jul 10, 15:40 UTC | 1h 15m |
| 2026-06-08 | PPNMM | - | Jun 8, 17:20 UTC | Jun 8, 18:15 UTC | 55m |
| 2026-06-08 | PPNMM | - | Jun 8, 11:30 UTC | Jun 8, 16:35 UTC | 5h 5m |
| 2026-06-08 | PPNMM | - | Jun 8, 10:15 UTC | Jun 8, 10:55 UTC | 40m |
| 2026-06-07 | PPNMM | - | Jun 7, 15:25 UTC | Jun 7, 16:40 UTC | 1h 15m |
| 2026-06-04 | PPNMM | - | Jun 4, 13:50 UTC | Jun 4, 15:00 UTC | 1h 10m |
| 2026-05-29 | PPNMM | CGH → CGH | May 29, 11:00 UTC | May 29, 17:20 UTC | 6h 20m |
| 2026-05-28 | PPNMM | - | May 28, 20:15 UTC | May 28, 20:50 UTC | 35m |
| 2026-05-28 | PPNMM | - | May 28, 17:05 UTC | May 28, 17:30 UTC | 25m |
| 2026-05-25 | PPNMM | CGH → CGH | May 25, 09:15 UTC | May 25, 15:20 UTC | 6h 5m |
| 2026-05-24 | PPNMM | - | May 24, 18:15 UTC | May 24, 19:20 UTC | 1h 5m |
| 2026-05-22 | PPNMM | - | May 22, 12:35 UTC | May 22, 13:30 UTC | 55m |
| 2026-05-21 | PPNMM | - | May 21, 20:00 UTC | May 21, 20:30 UTC | 30m |
| 2026-05-21 | PPNMM | - | May 21, 00:05 UTC | May 21, 00:40 UTC | 35m |
| 2026-05-17 | PPNMM | - | May 17, 23:15 UTC | May 17, 23:50 UTC | 35m |
| 2026-05-17 | PPNMM | - | May 17, 15:01 UTC | May 17, 15:31 UTC | 30m |
| 2026-05-12 | PPNMM | - | May 12, 20:15 UTC | May 12, 20:45 UTC | 30m |
| 2026-05-12 | PPNMM | CGH → JTC | May 12, 15:05 UTC | May 12, 15:35 UTC | 30m |
| 2026-05-10 | PPNMM | - | May 10, 19:40 UTC | May 10, 20:20 UTC | 40m |
| 2026-05-08 | PPNMM | - | May 8, 18:20 UTC | May 8, 19:05 UTC | 45m |
| 2026-05-04 | PPNMM | - | May 4, 13:25 UTC | May 4, 13:45 UTC | 20m |
| 2026-05-01 | PPNMM | - | May 1, 16:40 UTC | May 1, 17:00 UTC | 20m |
| 2026-05-01 | PPNMM | - | May 1, 15:40 UTC | May 1, 15:50 UTC | 10m |
| 2026-05-01 | PPNMM | - | May 1, 14:20 UTC | May 1, 14:40 UTC | 20m |
| 2026-05-01 | PPNMM | - | May 1, 12:45 UTC | May 1, 13:10 UTC | 25m |
| 2026-04-30 | PPNMM | - | Apr 30, 18:15 UTC | Apr 30, 18:45 UTC | 30m |
| 2026-04-30 | PPNMM | - | Apr 30, 17:10 UTC | Apr 30, 17:25 UTC | 15m |
| 2026-04-30 | PPNMM | - | Apr 30, 15:05 UTC | Apr 30, 15:50 UTC | 45m |
| 2026-04-30 | PPNMM | - | Apr 30, 13:30 UTC | Apr 30, 14:05 UTC | 35m |
| 2026-04-30 | PPNMM | - | Apr 30, 12:15 UTC | Apr 30, 12:30 UTC | 15m |
| 2026-04-26 | PPNMM | - | Apr 26, 01:10 UTC | Apr 26, 01:40 UTC | 30m |
| 2026-04-25 | PPNMM | - | Apr 25, 12:55 UTC | Apr 25, 13:20 UTC | 25m |
| 2026-04-24 | PPNMM | - | Apr 24, 19:55 UTC | Apr 24, 20:45 UTC | 50m |
| 2026-04-24 | PPNMM | - | Apr 24, 17:55 UTC | Apr 24, 18:40 UTC | 45m |
| 2026-04-24 | PPNMM | - | Apr 24, 13:50 UTC | Apr 24, 14:15 UTC | 25m |
| 2026-04-24 | PPNMM | - | Apr 24, 12:20 UTC | Apr 24, 12:35 UTC | 15m |
| 2026-04-22 | PPNMM | - | Apr 22, 13:45 UTC | Apr 22, 14:10 UTC | 25m |
| 2026-04-22 | PPNMM | - | Apr 22, 12:40 UTC | Apr 22, 13:00 UTC | 20m |
| 2026-04-21 | PPNMM | - | Apr 21, 22:00 UTC | Apr 21, 23:10 UTC | 1h 10m |
| 2026-04-21 | PPNMM | - | Apr 21, 15:45 UTC | Apr 21, 19:45 UTC | 4h 0m |
| 2026-04-21 | PPNMM | - | Apr 21, 13:35 UTC | Apr 21, 15:10 UTC | 1h 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.
Prefer a tail-number view? See the PP-NMM page for operator, model, and routing details .