sensors Mode-S transponder
E48A8B
ICAO 24-bit transponder address · allocated to Brazil
Currently assigned to PR-GCR · EMBRAER EMB-505 Phenom 300
- Hex
- E48A8B
- Octal
- 71105213
- Decimal
- 14,977,675
- Country
- BR
- Tail
- PR-GCR
- Type
- E55P
- Flights observed
- 64
- Distinct callsigns
- 2
- Country
- BR
- Last broadcast
- 18d ago
Last known position
Country allocation
The ICAO 24-bit address E48A8B 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 2 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | AVANTTO | - | Jul 25, 12:30 UTC | Jul 25, 13:20 UTC | 50m |
| 2026-07-24 | AVANTTO | - | Jul 24, 19:10 UTC | Jul 24, 20:10 UTC | 1h 0m |
| 2026-07-19 | AVANTTO | - | Jul 19, 16:35 UTC | Jul 19, 17:25 UTC | 50m |
| 2026-07-17 | AVANTTO | - | Jul 17, 18:00 UTC | Jul 17, 18:40 UTC | 40m |
| 2026-07-12 | AVANTTO | - | Jul 12, 19:35 UTC | Jul 12, 21:25 UTC | 1h 50m |
| 2026-07-09 | AVANTTO | - | Jul 9, 13:15 UTC | Jul 9, 14:30 UTC | 1h 15m |
| 2026-07-08 | AVANTTO | - | Jul 8, 19:40 UTC | Jul 9, 00:25 UTC | 4h 45m |
| 2026-07-07 | AVANTTO | - | Jul 7, 18:15 UTC | Jul 7, 19:15 UTC | 1h 0m |
| 2026-07-07 | AVANTTO | - | Jul 7, 15:25 UTC | Jul 7, 16:30 UTC | 1h 5m |
| 2026-07-06 | AVANTTO | - | Jul 6, 08:20 UTC | Jul 6, 09:15 UTC | 55m |
| 2026-07-05 | AVANTTO | - | Jul 5, 17:05 UTC | Jul 5, 17:40 UTC | 35m |
| 2026-07-01 | AVANTTO | - | Jul 1, 19:15 UTC | Jul 1, 20:30 UTC | 1h 15m |
| 2026-07-01 | AVANTTO | - | Jul 1, 10:45 UTC | Jul 1, 12:25 UTC | 1h 40m |
| 2026-07-01 | PRGCR | - | Jul 1, 09:35 UTC | Jul 1, 09:50 UTC | 15m |
| 2026-06-30 | PRGCR | - | Jun 30, 12:05 UTC | Jun 30, 12:35 UTC | 30m |
| 2026-06-28 | PRGCR | - | Jun 28, 13:14 UTC | Jun 28, 13:29 UTC | 15m |
| 2026-06-26 | PRGCR | - | Jun 26, 19:35 UTC | Jun 26, 20:04 UTC | 30m |
| 2026-06-26 | PRGCR | - | Jun 26, 18:29 UTC | Jun 26, 18:44 UTC | 15m |
| 2026-06-25 | PRGCR | - | Jun 25, 12:35 UTC | Jun 25, 21:40 UTC | 9h 5m |
| 2026-06-23 | PRGCR | - | Jun 23, 19:04 UTC | Jun 23, 19:39 UTC | 35m |
| 2026-06-23 | PRGCR | - | Jun 23, 10:15 UTC | Jun 23, 11:14 UTC | 1h 0m |
| 2026-06-19 | PRGCR | - | Jun 19, 20:24 UTC | Jun 19, 21:14 UTC | 50m |
| 2026-06-11 | PRGCR | - | Jun 11, 23:35 UTC | Jun 12, 00:00 UTC | 25m |
| 2026-06-11 | PRGCR | - | Jun 11, 21:15 UTC | Jun 11, 22:05 UTC | 50m |
| 2026-06-11 | PRGCR | - | Jun 11, 20:00 UTC | Jun 11, 20:15 UTC | 15m |
| 2026-06-10 | PRGCR | - | Jun 10, 12:35 UTC | Jun 10, 12:50 UTC | 15m |
| 2026-06-10 | PRGCR | - | Jun 10, 10:05 UTC | Jun 10, 11:25 UTC | 1h 20m |
| 2026-06-06 | PRGCR | - | Jun 6, 18:04 UTC | Jun 6, 18:39 UTC | 35m |
| 2026-06-05 | PRGCR | - | Jun 5, 17:40 UTC | Jun 5, 18:15 UTC | 35m |
| 2026-06-03 | PRGCR | - | Jun 3, 12:25 UTC | Jun 3, 12:55 UTC | 30m |
| 2026-06-03 | PRGCR | - | Jun 3, 11:15 UTC | Jun 3, 11:35 UTC | 20m |
| 2026-05-31 | PRGCR | - | May 31, 19:40 UTC | May 31, 20:15 UTC | 35m |
| 2026-05-30 | PRGCR | - | May 30, 12:20 UTC | May 30, 12:40 UTC | 20m |
| 2026-05-28 | PRGCR | - | May 28, 15:50 UTC | May 28, 16:50 UTC | 1h 0m |
| 2026-05-28 | PRGCR | - | May 28, 10:15 UTC | May 28, 10:50 UTC | 35m |
| 2026-05-22 | PRGCR | - | May 22, 20:40 UTC | May 22, 21:15 UTC | 35m |
| 2026-05-22 | PRGCR | - | May 22, 12:15 UTC | May 22, 19:15 UTC | 7h 0m |
| 2026-05-21 | PRGCR | - | May 21, 10:15 UTC | May 21, 11:05 UTC | 50m |
| 2026-05-13 | PRGCR | - | May 13, 15:30 UTC | May 13, 16:20 UTC | 50m |
| 2026-05-13 | PRGCR | - | May 13, 00:25 UTC | May 13, 01:05 UTC | 40m |
| 2026-05-10 | PRGCR | - | May 10, 21:10 UTC | May 10, 22:05 UTC | 55m |
| 2026-05-08 | PRGCR | - | May 8, 21:55 UTC | May 8, 22:45 UTC | 50m |
| 2026-05-04 | PRGCR | - | May 4, 18:45 UTC | May 4, 19:10 UTC | 25m |
| 2026-05-04 | PRGCR | - | May 4, 17:15 UTC | May 4, 17:35 UTC | 20m |
| 2026-05-04 | PRGCR | - | May 4, 14:05 UTC | May 4, 15:05 UTC | 1h 0m |
| 2026-05-01 | PRGCR | - | May 1, 09:35 UTC | May 1, 11:05 UTC | 1h 30m |
| 2026-04-29 | PRGCR | - | Apr 29, 20:15 UTC | Apr 29, 21:00 UTC | 45m |
| 2026-04-28 | PRGCR | - | Apr 28, 11:20 UTC | Apr 28, 12:10 UTC | 50m |
| 2026-04-23 | PRGCR | - | Apr 23, 22:00 UTC | Apr 24, 00:35 UTC | 2h 35m |
| 2026-04-23 | PRGCR | - | Apr 23, 19:25 UTC | Apr 23, 20:00 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.
Prefer a tail-number view? See the PR-GCR page for operator, model, and routing details .