sensors Mode-S transponder
E490C2
ICAO 24-bit transponder address · allocated to Brazil
Currently assigned to PT-XPB · AIRBUS A-321
- Hex
- E490C2
- Octal
- 71110302
- Decimal
- 14,979,266
- Country
- BR
- Tail
- PT-XPB
- Type
- A321
- Flights observed
- 291
- Distinct callsigns
- 20
- Country
- BR
- Last broadcast
- 16d ago
Last known position
Country allocation
The ICAO 24-bit address E490C2 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| LAN613 | LAN Airlines | 8 | 2026-06-22 |
| TAM3340 | - | 6 | 2026-06-26 |
| TAM3285 | - | 5 | 2026-06-22 |
| TAM3284 | - | 5 | 2026-06-22 |
| TAM3240 | - | 5 | 2026-06-25 |
| LAN612 | LAN Airlines | 5 | 2026-06-22 |
| TAM3979 | TAM Brazilian Airlines | 4 | 2026-04-30 |
| TAM3547 | TAM Brazilian Airlines | 4 | 2026-06-10 |
| TAM3131 | - | 4 | 2026-06-26 |
| TAM4524 | TAM Brazilian Airlines | 3 | 2026-05-20 |
| TAM3879 | - | 3 | 2026-04-15 |
| TAM3732 | - | 3 | 2026-06-18 |
| TAM3602 | TAM Brazilian Airlines | 3 | 2026-06-11 |
| TAM3510 | TAM Brazilian Airlines | 3 | 2026-05-06 |
| TAM3374 | - | 3 | 2026-06-21 |
| TAM3241 | - | 3 | 2026-06-25 |
| TAM3232 | - | 3 | 2026-06-14 |
| TAM3227 | - | 3 | 2026-06-15 |
| TAM3219 | TAM Brazilian Airlines | 3 | 2026-05-27 |
| TAM3200 | TAM Brazilian Airlines | 3 | 2026-06-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-28 | TAM9420 | - | Jun 28, 12:29 UTC | Jun 28, 12:55 UTC | 25m |
| 2026-06-27 | TAM3450 | - | Jun 27, 13:35 UTC | Jun 28, 02:20 UTC | 12h 45m |
| 2026-06-27 | TAM3073 | - | Jun 27, 03:25 UTC | Jun 27, 09:19 UTC | 5h 55m |
| 2026-06-26 | TAM3131 | - | Jun 26, 20:44 UTC | Jun 27, 00:29 UTC | 3h 45m |
| 2026-06-26 | TAM3528 | - | Jun 26, 13:59 UTC | Jun 26, 18:54 UTC | 4h 55m |
| 2026-06-26 | TAM3340 | - | Jun 26, 11:34 UTC | Jun 26, 12:05 UTC | 30m |
| 2026-06-26 | TAM4537 | - | Jun 26, 08:05 UTC | Jun 26, 09:20 UTC | 1h 15m |
| 2026-06-26 | TAM3336 | - | Jun 26, 04:45 UTC | Jun 26, 05:24 UTC | 40m |
| 2026-06-26 | TAM3336 | - | Jun 26, 03:50 UTC | Jun 26, 04:04 UTC | 15m |
| 2026-06-25 | TAM3131 | - | Jun 25, 21:40 UTC | Jun 26, 01:29 UTC | 3h 50m |
| 2026-06-25 | TAM3287 | - | Jun 25, 18:24 UTC | Jun 25, 19:15 UTC | 50m |
| 2026-06-25 | TAM3288 | - | Jun 25, 16:20 UTC | Jun 25, 16:45 UTC | 25m |
| 2026-06-25 | TAM3241 | - | Jun 25, 13:05 UTC | Jun 25, 14:24 UTC | 1h 20m |
| 2026-06-25 | TAM3240 | - | Jun 25, 10:15 UTC | Jun 25, 11:25 UTC | 1h 10m |
| 2026-06-25 | TAM3359 | - | Jun 25, 03:24 UTC | Jun 25, 08:20 UTC | 4h 55m |
| 2026-06-24 | TAM3613 | - | Jun 24, 18:15 UTC | Jun 25, 01:14 UTC | 7h 0m |
| 2026-06-24 | TAM3223 | - | Jun 24, 10:30 UTC | Jun 24, 16:24 UTC | 5h 55m |
| 2026-06-23 | TAM3834 | - | Jun 23, 23:05 UTC | Jun 24, 08:49 UTC | 9h 45m |
| 2026-06-23 | TAM3349 | - | Jun 23, 20:24 UTC | Jun 23, 20:54 UTC | 30m |
| 2026-06-23 | TAM4548 | - | Jun 23, 18:39 UTC | Jun 23, 19:19 UTC | 40m |
| 2026-06-23 | TAM4607 | - | Jun 23, 13:19 UTC | Jun 23, 16:59 UTC | 3h 40m |
| 2026-06-23 | TAM3691 | - | Jun 23, 03:00 UTC | Jun 23, 09:20 UTC | 6h 20m |
| 2026-06-22 | LAN613 | SCL → GRU | Jun 22, 23:05 UTC | Jun 23, 00:45 UTC | 1h 40m |
| 2026-06-22 | LAN613 | SCL → GRU | Jun 22, 21:25 UTC | Jun 22, 21:35 UTC | 10m |
| 2026-06-22 | LAN612 | GRU → SCL | Jun 22, 15:54 UTC | Jun 22, 17:55 UTC | 2h 0m |
| 2026-06-22 | TAM3285 | - | Jun 22, 13:35 UTC | Jun 22, 14:10 UTC | 35m |
| 2026-06-22 | TAM3284 | - | Jun 22, 11:44 UTC | Jun 22, 12:10 UTC | 25m |
| 2026-06-21 | TAM3354 | - | Jun 21, 19:14 UTC | Jun 22, 00:20 UTC | 5h 5m |
| 2026-06-21 | TAM3383 | - | Jun 21, 16:54 UTC | Jun 21, 17:24 UTC | 30m |
| 2026-06-21 | TAM3374 | - | Jun 21, 11:05 UTC | Jun 21, 12:04 UTC | 1h 0m |
| 2026-06-20 | TAM3014 | - | Jun 20, 20:55 UTC | Jun 21, 09:15 UTC | 12h 20m |
| 2026-06-20 | TAM3795 | - | Jun 20, 15:19 UTC | Jun 20, 19:40 UTC | 4h 20m |
| 2026-06-19 | TAM3819 | - | Jun 19, 23:59 UTC | Jun 20, 13:34 UTC | 13h 35m |
| 2026-06-19 | TAM3818 | - | Jun 19, 18:20 UTC | Jun 19, 22:49 UTC | 4h 30m |
| 2026-06-19 | TAM3027 | - | Jun 19, 12:59 UTC | Jun 19, 16:55 UTC | 3h 55m |
| 2026-06-19 | TAM3340 | - | Jun 19, 11:24 UTC | Jun 19, 11:59 UTC | 35m |
| 2026-06-18 | TAM3743 | - | Jun 18, 20:30 UTC | Jun 19, 08:29 UTC | 11h 59m |
| 2026-06-18 | TAM3732 | - | Jun 18, 00:35 UTC | Jun 18, 19:15 UTC | 18h 40m |
| 2026-06-18 | TAM3732 | - | Jun 18, 00:15 UTC | Jun 18, 19:15 UTC | 19h 0m |
| 2026-06-17 | TAM3732 | - | Jun 17, 20:35 UTC | Jun 18, 19:15 UTC | 22h 40m |
| 2026-06-17 | TAM3805 | SLZ → BSB | Jun 17, 17:40 UTC | Jun 18, 00:45 UTC | 7h 5m |
| 2026-06-17 | TAM3804 | BSB → SLZ | Jun 17, 13:05 UTC | Jun 17, 15:55 UTC | 2h 50m |
| 2026-06-16 | TAM3804 | BSB → SLZ | Jun 16, 18:35 UTC | Jun 17, 15:55 UTC | 21h 21m |
| 2026-06-16 | TAM4509 | - | Jun 16, 17:30 UTC | Jun 17, 15:55 UTC | 22h 26m |
| 2026-06-16 | TAM3730 | BSB → FOR | Jun 16, 11:00 UTC | Jun 16, 15:40 UTC | 4h 40m |
| 2026-06-16 | TAM8119 | MVD → GRU | Jun 16, 06:15 UTC | Jun 16, 08:10 UTC | 1h 55m |
| 2026-06-16 | TAM8016 | GRU → BOG | Jun 16, 03:00 UTC | Jun 16, 05:10 UTC | 2h 10m |
| 2026-06-15 | LAN613 | SCL → GRU | Jun 15, 22:35 UTC | Jun 16, 00:29 UTC | 1h 55m |
| 2026-06-15 | LAN612 | GRU → SCL | Jun 15, 15:30 UTC | Jun 15, 17:10 UTC | 1h 40m |
| 2026-06-15 | TAM3227 | - | Jun 15, 06:04 UTC | Jun 15, 09:20 UTC | 3h 15m |
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 PT-XPB page for operator, model, and routing details .