sensors Mode-S transponder

E495D0

ICAO 24-bit transponder address · allocated to Brazil

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

Hex
E495D0
Octal
71112720
Decimal
14,980,560
Country
BR
Tail
PR-YJC
Type
A21N
No current signal · last broadcast 4h ago
Flights observed
140
Distinct callsigns
20
Country
BR
Last broadcast
4h ago

Last known position

Most recent position reported by Mode-S E495D0.

Country allocation

The ICAO 24-bit address E495D0 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-30 AZU2922 VCP → REC May 30, 11:50 UTCMay 30, 12:25 UTC35m
2026-05-30 AZU4335 REC → VCP May 30, 02:30 UTCMay 30, 09:30 UTC7h 0m
2026-05-29 AZU2959 GRU → REC May 29, 16:45 UTCMay 30, 00:45 UTC8h 0m
2026-05-29 AZU4232 GRU → REC May 29, 08:15 UTCMay 29, 15:00 UTC6h 45m
2026-05-28 AZU5092 GRU → REC May 28, 19:55 UTCMay 29, 02:35 UTC6h 40m
2026-05-28 AZU2768 REC → GRU May 28, 11:45 UTCMay 28, 18:35 UTC6h 50m
2026-05-27 AZU2648 REC → MAO May 27, 21:20 UTCMay 28, 10:05 UTC12h 45m
2026-05-27 AZU2823 MCZ → SDU May 27, 11:55 UTCMay 27, 19:10 UTC7h 15m
2026-05-27 AZU4152 GRU → REC May 27, 02:44 UTCMay 27, 09:20 UTC6h 35m
2026-05-26 AZU2764 GRU → REC May 26, 17:25 UTCMay 27, 00:19 UTC6h 55m
2026-05-26 AZU4232 GRU → REC May 26, 08:19 UTCMay 26, 15:09 UTC6h 50m
2026-05-25 AZU5092 GRU → REC May 25, 19:50 UTCMay 26, 02:35 UTC6h 45m
2026-05-25 AZU2768 REC → GRU May 25, 11:55 UTCMay 25, 18:45 UTC6h 50m
2026-05-25 AZU4152 GRU → REC May 25, 02:55 UTCMay 25, 09:15 UTC6h 20m
2026-05-24 AZU2959 GRU → REC May 24, 16:50 UTCMay 24, 23:46 UTC6h 56m
2026-05-23 AZU4674 REC → GRU May 23, 21:15 UTCMay 24, 15:05 UTC17h 50m
2026-05-23 AZU2744 GRU → REC May 23, 11:50 UTCMay 23, 19:00 UTC7h 11m
2026-05-23 AZU4153 REC → GRU May 23, 03:00 UTCMay 23, 10:15 UTC7h 15m
2026-05-22 AZU4493 REC → VCP May 22, 18:10 UTCMay 23, 00:35 UTC6h 25m
2026-05-22 AZU2876 REC → VCP May 22, 09:20 UTCMay 22, 15:55 UTC6h 35m
2026-05-21 AZU2660 VCP → POA May 21, 21:00 UTCMay 22, 00:50 UTC3h 50m
2026-05-21 AZU4669 FOR → VCP May 21, 16:30 UTCMay 21, 19:35 UTC3h 5m
2026-05-21 AZU4712 VCP → FOR May 21, 12:00 UTCMay 21, 14:55 UTC2h 55m
2026-05-21 AZU4152 GRU → REC May 21, 02:50 UTCMay 21, 09:25 UTC6h 35m
2026-05-20 AZU2959 GRU → REC May 20, 16:55 UTCMay 21, 00:20 UTC7h 25m
2026-05-20 AZU4451 VCP → MAO May 20, 02:10 UTCMay 20, 15:20 UTC13h 11m
2026-05-19 AZU2660 VCP → POA May 19, 20:20 UTCMay 20, 00:15 UTC3h 55m
2026-05-19 AZU4669 FOR → VCP May 19, 16:00 UTCMay 19, 19:05 UTC3h 5m
2026-05-19 AZU4712 VCP → FOR May 19, 12:00 UTCMay 19, 14:55 UTC2h 55m
2026-05-19 AZU2618 BEL → SLZ May 19, 01:35 UTCMay 19, 10:05 UTC8h 30m
2026-05-18 AZU4056 VCP → MAO May 18, 16:35 UTCMay 19, 00:15 UTC7h 39m
2026-05-18 AZU2904 SSA → VCP May 18, 09:25 UTCMay 18, 14:30 UTC5h 5m
2026-05-17 AZU2660 VCP → POA May 17, 20:30 UTCMay 18, 00:25 UTC3h 55m
2026-05-17 AZU4669 FOR → VCP May 17, 15:55 UTCMay 17, 19:05 UTC3h 10m
2026-05-17 AZU4712 VCP → FOR May 17, 11:55 UTCMay 17, 14:45 UTC2h 50m
2026-05-17 AZU4451 VCP → MAO May 17, 02:40 UTCMay 17, 10:20 UTC7h 40m
2026-05-16 AZU2744 GRU → REC May 16, 12:05 UTCMay 16, 19:15 UTC7h 10m
2026-05-16 AZU2871 FOR → REC May 16, 03:30 UTCMay 16, 10:01 UTC6h 31m
2026-05-15 AZU4036 FOR → REC May 15, 22:55 UTCMay 16, 02:35 UTC3h 40m
2026-05-15 AZU2959 GRU → REC May 15, 16:45 UTCMay 15, 21:55 UTC5h 10m
2026-05-15 AZU4232 GRU → REC May 15, 08:05 UTCMay 15, 15:00 UTC6h 54m
2026-05-14 AZU5092 GRU → REC May 14, 20:05 UTCMay 15, 02:30 UTC6h 25m
2026-05-14 AZU2744 GRU → REC May 14, 11:40 UTCMay 14, 18:30 UTC6h 50m
2026-05-14 AZU4153 REC → GRU May 14, 02:40 UTCMay 14, 09:35 UTC6h 55m
2026-05-13 AZU2660 VCP → POA May 13, 20:25 UTCMay 14, 00:00 UTC3h 35m
2026-05-13 AZU4669 FOR → VCP May 13, 16:00 UTCMay 13, 19:05 UTC3h 5m
2026-05-13 AZU4712 VCP → FOR May 13, 12:00 UTCMay 13, 15:00 UTC3h 0m
2026-05-13 AZU4451 VCP → MAO May 13, 02:05 UTCMay 13, 09:40 UTC7h 35m
2026-05-12 AZU2660 VCP → POA May 12, 20:40 UTCMay 13, 00:25 UTC3h 45m
2026-05-12 AZU4669 FOR → VCP May 12, 16:10 UTCMay 12, 19:25 UTC3h 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 PR-YJC page for operator, model, and routing details .

Mode-S E495D0 frequently asked

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