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