sensors Mode-S transponder
E483BB
ICAO 24-bit transponder address · allocated to Brazil
Currently assigned to 2591 · EMBRAER ERJ-190-100
- Hex
- E483BB
- Octal
- 71101673
- Decimal
- 14,975,931
- Country
- BR
- Tail
- 2591
- Type
- E190
- Flights observed
- 57
- Distinct callsigns
- 2
- Country
- BR
- Last broadcast
- 28d ago
Last known position
Country allocation
The ICAO 24-bit address E483BB 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-26 | FAB2591 | - | Jul 26, 20:15 UTC | Jul 26, 21:05 UTC | 50m |
| 2026-07-26 | FAB2591 | - | Jul 26, 12:50 UTC | Jul 26, 13:25 UTC | 35m |
| 2026-07-25 | FAB2591 | - | Jul 25, 19:55 UTC | Jul 26, 11:40 UTC | 15h 46m |
| 2026-07-25 | FAB2591 | - | Jul 25, 14:10 UTC | Jul 25, 14:30 UTC | 20m |
| 2026-07-24 | FAB2591 | - | Jul 24, 19:50 UTC | Jul 25, 11:00 UTC | 15h 10m |
| 2026-07-24 | FAB2591 | - | Jul 24, 14:20 UTC | Jul 24, 14:35 UTC | 15m |
| 2026-07-24 | FAB2591 | - | Jul 24, 12:20 UTC | Jul 24, 13:00 UTC | 40m |
| 2026-07-23 | FAB2591 | - | Jul 23, 15:05 UTC | Jul 24, 13:00 UTC | 21h 55m |
| 2026-07-23 | FAB2591 | - | Jul 23, 13:00 UTC | Jul 23, 13:55 UTC | 55m |
| 2026-07-22 | FAB2591 | - | Jul 22, 13:25 UTC | Jul 22, 14:15 UTC | 50m |
| 2026-07-22 | FAB2591 | - | Jul 22, 11:30 UTC | Jul 22, 12:05 UTC | 35m |
| 2026-07-18 | FAB2591 | - | Jul 18, 12:10 UTC | Jul 18, 12:50 UTC | 40m |
| 2026-07-17 | FAB2591 | - | Jul 17, 22:25 UTC | Jul 18, 11:10 UTC | 12h 46m |
| 2026-07-17 | FAB2591 | - | Jul 17, 17:15 UTC | Jul 17, 18:10 UTC | 55m |
| 2026-07-15 | FAB2591 | - | Jul 15, 17:30 UTC | Jul 15, 18:10 UTC | 40m |
| 2026-07-15 | FAB2591 | - | Jul 15, 12:45 UTC | Jul 15, 16:30 UTC | 3h 45m |
| 2026-07-15 | FAB2591 | - | Jul 15, 10:55 UTC | Jul 15, 11:40 UTC | 45m |
| 2026-07-14 | FAB2591 | - | Jul 14, 00:25 UTC | Jul 14, 01:15 UTC | 50m |
| 2026-07-13 | FAB2591 | - | Jul 13, 20:00 UTC | Jul 13, 23:35 UTC | 3h 35m |
| 2026-07-13 | FAB2591 | - | Jul 13, 17:40 UTC | Jul 13, 18:00 UTC | 20m |
| 2026-07-13 | FAB2591 | - | Jul 13, 09:45 UTC | Jul 13, 10:35 UTC | 50m |
| 2026-07-11 | FAB2591 | - | Jul 11, 17:15 UTC | Jul 11, 18:00 UTC | 45m |
| 2026-07-11 | FAB2591 | - | Jul 11, 12:45 UTC | Jul 11, 16:20 UTC | 3h 35m |
| 2026-07-11 | FAB2591 | - | Jul 11, 10:30 UTC | Jul 11, 11:25 UTC | 55m |
| 2026-07-10 | FAB2591 | - | Jul 10, 13:40 UTC | Jul 11, 11:25 UTC | 21h 45m |
| 2026-07-10 | FAB2591 | - | Jul 10, 11:35 UTC | Jul 10, 12:25 UTC | 50m |
| 2026-07-08 | FAB2591 | - | Jul 8, 14:00 UTC | Jul 8, 14:45 UTC | 45m |
| 2026-07-08 | FAB2591 | - | Jul 8, 11:50 UTC | Jul 8, 13:15 UTC | 1h 25m |
| 2026-07-08 | FAB2591 | - | Jul 8, 10:25 UTC | Jul 8, 11:10 UTC | 45m |
| 2026-07-03 | FAB2591 | - | Jul 3, 14:20 UTC | Jul 3, 16:20 UTC | 2h 0m |
| 2026-07-02 | FAB2591 | - | Jul 2, 23:25 UTC | Jul 3, 13:10 UTC | 13h 45m |
| 2026-07-02 | FAB2591 | - | Jul 2, 20:45 UTC | Jul 2, 21:55 UTC | 1h 10m |
| 2026-07-02 | FAB2591 | - | Jul 2, 02:05 UTC | Jul 2, 21:55 UTC | 19h 50m |
| 2026-06-30 | FAB2591 | - | Jun 30, 18:55 UTC | Jun 30, 20:15 UTC | 1h 20m |
| 2026-06-30 | FAB2591 | - | Jun 30, 12:15 UTC | Jun 30, 17:25 UTC | 5h 10m |
| 2026-06-30 | FAB2591 | - | Jun 30, 09:40 UTC | Jun 30, 11:25 UTC | 1h 45m |
| 2026-06-29 | FAB2591 | - | Jun 29, 14:50 UTC | Jun 30, 11:25 UTC | 20h 36m |
| 2026-06-29 | FAB2591 | - | Jun 29, 14:14 UTC | Jun 30, 11:25 UTC | 21h 11m |
| 2026-06-29 | FAB2591 | - | Jun 29, 11:55 UTC | Jun 29, 13:04 UTC | 1h 10m |
| 2026-06-28 | FAB2591 | - | Jun 28, 13:59 UTC | Jun 29, 12:45 UTC | 22h 45m |
| 2026-06-28 | BRS03 | - | Jun 28, 11:59 UTC | Jun 28, 12:44 UTC | 45m |
| 2026-06-26 | FAB2591 | - | Jun 26, 20:44 UTC | Jun 26, 21:35 UTC | 50m |
| 2026-06-25 | FAB2591 | - | Jun 25, 23:19 UTC | Jun 26, 14:55 UTC | 15h 35m |
| 2026-06-25 | FAB2591 | - | Jun 25, 21:05 UTC | Jun 25, 21:50 UTC | 45m |
| 2026-06-24 | FAB2591 | - | Jun 24, 18:05 UTC | Jun 24, 19:00 UTC | 55m |
| 2026-06-24 | FAB2591 | - | Jun 24, 04:24 UTC | Jun 24, 16:29 UTC | 12h 5m |
| 2026-06-23 | FAB2591 | - | Jun 23, 23:50 UTC | Jun 24, 03:29 UTC | 3h 40m |
| 2026-06-23 | FAB2591 | - | Jun 23, 21:45 UTC | Jun 23, 22:34 UTC | 50m |
| 2026-06-23 | FAB2591 | - | Jun 23, 16:44 UTC | Jun 23, 17:09 UTC | 25m |
| 2026-06-23 | FAB2591 | - | Jun 23, 00:15 UTC | Jun 23, 15:44 UTC | 15h 30m |
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 2591 page for operator, model, and routing details .