sensors Mode-S transponder

E49830

ICAO 24-bit transponder address · allocated to Brazil

Currently assigned to PR-YJF · AIRBUS A-321neo

Hex
E49830
Octal
71114060
Decimal
14,981,168
Country
BR
Tail
PR-YJF
Type
A21N
No current signal · last broadcast 3h ago
Flights observed
139
Distinct callsigns
20
Country
BR
Last broadcast
3h ago

Last known position

Most recent position reported by Mode-S E49830.

Country allocation

The ICAO 24-bit address E49830 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

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-29 AZU4400 VCP → REC May 29, 21:30 UTCMay 29, 22:05 UTC35m
2026-05-29 AZU4669 FOR → VCP May 29, 16:05 UTCMay 29, 19:10 UTC3h 5m
2026-05-29 AZU4712 VCP → FOR May 29, 12:00 UTCMay 29, 14:55 UTC2h 55m
2026-05-29 AZU2648 REC → MAO May 29, 02:40 UTCMay 29, 09:50 UTC7h 10m
2026-05-28 AZU4400 VCP → REC May 28, 21:20 UTCMay 28, 21:50 UTC30m
2026-05-28 AZU2823 MCZ → SDU May 28, 11:25 UTCMay 28, 19:05 UTC7h 40m
2026-05-28 AZU4153 REC → GRU May 28, 02:35 UTCMay 28, 09:20 UTC6h 45m
2026-05-27 AZU4493 REC → VCP May 27, 18:15 UTCMay 28, 00:50 UTC6h 35m
2026-05-27 AZU2876 REC → VCP May 27, 09:20 UTCMay 27, 16:05 UTC6h 45m
2026-05-26 AZU2805 VCP → REC May 26, 16:45 UTCMay 26, 23:19 UTC6h 35m
2026-05-25 AZU2648 REC → MAO May 25, 21:19 UTCMay 26, 15:00 UTC17h 40m
2026-05-25 AZU2744 GRU → REC May 25, 11:20 UTCMay 25, 19:10 UTC7h 50m
2026-05-24 AZU4153 REC → GRU May 24, 17:35 UTCMay 25, 08:30 UTC14h 55m
2026-05-24 AZU2876 REC → VCP May 24, 09:10 UTCMay 24, 16:00 UTC6h 50m
2026-05-23 AZU4816 SLZ → VCP May 23, 17:30 UTCMay 24, 00:10 UTC6h 41m
2026-05-23 AZU4451 VCP → MAO May 23, 02:10 UTCMay 23, 16:10 UTC13h 59m
2026-05-22 AZU4345 REC → VCP May 22, 16:45 UTCMay 22, 23:20 UTC6h 35m
2026-05-22 AZU4451 VCP → MAO May 22, 02:20 UTCMay 22, 14:45 UTC12h 25m
2026-05-21 AZU2331 REC → VCP May 21, 17:00 UTCMay 21, 23:45 UTC6h 45m
2026-05-21 AZU4451 VCP → MAO May 21, 02:10 UTCMay 21, 15:00 UTC12h 50m
2026-05-20 AZU4493 REC → VCP May 20, 17:30 UTCMay 21, 00:10 UTC6h 40m
2026-05-20 AZU2608 POA → GRU May 20, 11:25 UTCMay 20, 15:05 UTC3h 40m
2026-05-19 AZU4493 REC → VCP May 19, 17:40 UTCMay 20, 00:15 UTC6h 35m
2026-05-19 AZU2713 VCP → CGR May 19, 11:20 UTCMay 19, 14:45 UTC3h 25m
2026-05-19 AZU9353 - May 19, 00:25 UTCMay 19, 02:30 UTC2h 5m
2026-05-18 AZU9353 - May 18, 04:05 UTCMay 19, 02:30 UTC22h 24m
2026-05-18 AZU4451 VCP → MAO May 18, 02:15 UTCMay 19, 02:00 UTC23h 44m
2026-05-17 AZU4865 IGU → VCP May 17, 23:30 UTCMay 17, 23:55 UTC25m
2026-05-17 AZU4864 VCP → IGU May 17, 20:40 UTCMay 17, 21:45 UTC1h 5m
2026-05-17 AZU4232 GRU → REC May 17, 08:15 UTCMay 17, 16:30 UTC8h 15m
2026-05-16 AZU5092 GRU → REC May 16, 19:50 UTCMay 17, 02:35 UTC6h 45m
2026-05-16 AZU2460 GYN → REC May 16, 10:11 UTCMay 16, 18:40 UTC8h 30m
2026-05-15 AZU2460 GYN → REC May 15, 21:20 UTCMay 16, 13:15 UTC15h 56m
2026-05-15 AZU2823 MCZ → SDU May 15, 12:50 UTCMay 15, 19:30 UTC6h 39m
2026-05-14 AZU2648 REC → MAO May 14, 21:40 UTCMay 15, 11:00 UTC13h 20m
2026-05-14 AZU4669 FOR → VCP May 14, 18:40 UTCMay 14, 20:15 UTC1h 35m
2026-05-14 AZU4669 FOR → VCP May 14, 17:10 UTCMay 14, 18:10 UTC1h 0m
2026-05-14 AZU4712 VCP → FOR May 14, 13:01 UTCMay 14, 16:10 UTC3h 10m
2026-05-13 AZU4383 MAO → VCP May 13, 21:15 UTCMay 14, 09:40 UTC12h 25m
2026-05-13 AZU2823 MCZ → SDU May 13, 12:10 UTCMay 13, 19:20 UTC7h 10m
2026-05-13 AZU4671 GRU → POA May 13, 00:10 UTCMay 13, 10:05 UTC9h 55m
2026-05-12 AZU2914 GRU → POA May 12, 17:50 UTCMay 12, 21:50 UTC4h 0m
2026-05-12 AZU2748 REC → GRU May 12, 10:20 UTCMay 12, 16:50 UTC6h 30m
2026-05-11 AZU4669 FOR → VCP May 11, 16:25 UTCMay 11, 19:30 UTC3h 5m
2026-05-11 AZU4712 VCP → FOR May 11, 12:15 UTCMay 11, 15:15 UTC3h 0m
2026-05-11 AZU4152 GRU → REC May 11, 03:10 UTCMay 11, 09:45 UTC6h 35m
2026-05-10 AZU4820 POA → CWB May 10, 17:40 UTCMay 11, 00:54 UTC7h 15m
2026-05-10 AZU2876 REC → VCP May 10, 09:20 UTCMay 10, 15:55 UTC6h 35m
2026-05-09 AZU2959 GRU → REC May 9, 17:00 UTCMay 10, 00:00 UTC7h 0m
2026-05-09 AZU4451 VCP → MAO May 9, 02:10 UTCMay 9, 15:10 UTC13h 0m

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-YJF page for operator, model, and routing details .

Mode-S E49830 frequently asked

What is Mode-S code E49830?
E49830 is an ICAO 24-bit transponder address. Allocated to Brazil. Assigned to PR-YJF.
Where is Mode-S E49830 registered?
Mode-S code E49830 is allocated to Brazil (BR). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is E49830 broadcasting right now?
No active broadcast right now. Last signal was 3h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex E49830, octal 71114060, decimal 14,981,168.
What flights does E49830 operate?
Mode-S E49830 has broadcast 20 distinct callsigns, including AZU4669, AZU4712, AZU4451, AZU2876, AZU4493.