sensors Mode-S transponder

495145

ICAO 24-bit transponder address · allocated to Portugal

Currently assigned to CS-TJE · AIRBUS A-321

Hex
495145
Octal
22250505
Decimal
4,804,933
Country
PT
Tail
CS-TJE
Type
A321
No current signal · last broadcast 2h ago
Flights observed
404
Distinct callsigns
20
Country
PT
Last broadcast
2h ago

Last known position

Most recent position reported by Mode-S 495145.

Country allocation

The ICAO 24-bit address 495145 falls within the block assigned to Portugal (PT) by ICAO Annex 10, Volume III. Every aircraft registered in Portugal 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
TAP837 - 13 2026-07-11
TAP836A - 12 2026-07-11
TAP30BC - 12 2026-07-12
TAP1031 - 12 2026-07-12
TAP97LS - 11 2026-07-08
TAP83RS - 11 2026-07-14
TAP832 - 11 2026-07-14
TAP86PZ - 9 2026-07-08
TAP86GM - 9 2026-07-08
TAP1243 - 9 2026-07-13
TAP98CX - 8 2026-07-09
TAP1863 - 8 2026-07-14
TAP96AW - 7 2026-07-10
TAP93ZS - 7 2026-06-20
TAP932 - 7 2026-06-20
TAP43RY - 7 2026-07-10
TAP438T - 7 2026-07-10
TAP1242 - 7 2026-07-13
TAP64M - 6 2026-07-14
TAP1685 TAP Portugal 6 2026-06-05

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 TAP64M - Jul 14, 20:35 UTCJul 14, 20:45 UTC10m
2026-07-14 TAP1863 - Jul 14, 19:15 UTCJul 14, 19:25 UTC10m
2026-07-14 TAP1863 - Jul 14, 17:05 UTCJul 14, 18:00 UTC55m
2026-07-14 TAP83RS - Jul 14, 12:30 UTCJul 14, 15:30 UTC3h 0m
2026-07-14 TAP832 - Jul 14, 08:25 UTCJul 14, 10:55 UTC2h 30m
2026-07-13 TAP1243 PRG → LIS Jul 13, 18:40 UTCJul 13, 22:05 UTC3h 25m
2026-07-13 TAP1242 LIS → PRG Jul 13, 14:35 UTCJul 13, 17:25 UTC2h 50m
2026-07-13 TAP831 - Jul 13, 09:50 UTCJul 13, 12:30 UTC2h 40m
2026-07-13 TAP830 - Jul 13, 05:45 UTCJul 13, 08:10 UTC2h 25m
2026-07-12 TAP1243 PRG → LIS Jul 12, 18:05 UTCJul 12, 21:20 UTC3h 15m
2026-07-12 TAP1242 LIS → PRG Jul 12, 13:30 UTCJul 12, 16:45 UTC3h 15m
2026-07-12 TAP1031 BCN → LIS Jul 12, 10:20 UTCJul 12, 12:01 UTC1h 40m
2026-07-12 TAP30BC LIS → BCN Jul 12, 07:10 UTCJul 12, 08:35 UTC1h 25m
2026-07-11 TAP837 - Jul 11, 19:30 UTCJul 11, 22:15 UTC2h 45m
2026-07-11 TAP836A - Jul 11, 15:40 UTCJul 11, 18:00 UTC2h 20m
2026-07-11 TAP1013 - Jul 11, 12:30 UTCJul 11, 13:25 UTC55m
2026-07-11 TAP12LM LIS → MAD Jul 11, 09:50 UTCJul 11, 10:45 UTC55m
2026-07-10 TAP43RY ORY → LIS Jul 10, 19:30 UTCJul 10, 21:40 UTC2h 10m
2026-07-10 TAP438T LIS → ORY Jul 10, 16:20 UTCJul 10, 18:15 UTC1h 55m
2026-07-10 TAP83RS - Jul 10, 12:00 UTCJul 10, 14:40 UTC2h 40m
2026-07-10 TAP832 - Jul 10, 07:55 UTCJul 10, 10:35 UTC2h 40m
2026-07-10 TAP96AW FNC → LIS Jul 10, 03:45 UTCJul 10, 05:10 UTC1h 25m
2026-07-09 TAP16LN LIS → FNC Jul 9, 21:35 UTCJul 9, 23:05 UTC1h 30m
2026-07-09 TAP437X ORY → LIS Jul 9, 18:05 UTCJul 9, 20:15 UTC2h 10m
2026-07-09 TAP436 LIS → ORY Jul 9, 15:05 UTCJul 9, 17:05 UTC2h 0m
2026-07-09 TAP88TM FNC → LIS Jul 9, 12:05 UTCJul 9, 13:25 UTC1h 20m
2026-07-09 TAP1687 LIS → FNC Jul 9, 09:35 UTCJul 9, 11:05 UTC1h 30m
2026-07-09 TAP98CX FNC → LIS Jul 9, 04:55 UTCJul 9, 06:15 UTC1h 20m
2026-07-08 TAP97LS LIS → FNC Jul 8, 22:55 UTCJul 9, 00:20 UTC1h 25m
2026-07-08 TAP837 - Jul 8, 18:15 UTCJul 8, 21:00 UTC2h 45m
2026-07-08 TAP836A - Jul 8, 14:30 UTCJul 8, 17:00 UTC2h 30m
2026-07-08 TAP86GM - Jul 8, 10:05 UTCJul 8, 12:50 UTC2h 45m
2026-07-08 TAP86PZ - Jul 8, 06:00 UTCJul 8, 08:50 UTC2h 50m
2026-07-07 TAP127M VIE → LIS Jul 7, 19:10 UTCJul 7, 22:15 UTC3h 5m
2026-07-07 TAP1272 LIS → VIE Jul 7, 14:20 UTCJul 7, 17:25 UTC3h 5m
2026-07-07 TAP1335 - Jul 7, 09:45 UTCJul 7, 11:55 UTC2h 10m
2026-07-07 TAP34A LIS → LGW Jul 7, 06:20 UTCJul 7, 08:35 UTC2h 15m
2026-07-05 TAP21MM - Jul 5, 21:55 UTCJul 5, 22:55 UTC1h 0m
2026-07-05 TAP20L - Jul 5, 19:35 UTCJul 5, 20:30 UTC55m
2026-07-05 TAP15NC MAD → LIS Jul 5, 15:30 UTCJul 5, 16:25 UTC55m
2026-07-05 TAP14NC - Jul 5, 13:15 UTCJul 5, 14:10 UTC55m
2026-07-05 TAP66PD - Jul 5, 06:45 UTCJul 5, 08:40 UTC1h 55m
2026-07-04 TAP65PD - Jul 4, 22:55 UTCJul 4, 23:35 UTC40m
2026-07-04 TAP1692 - Jul 4, 20:50 UTCJul 4, 21:30 UTC40m
2026-07-04 TAP1692 - Jul 4, 20:05 UTCJul 4, 20:20 UTC15m
2026-07-04 TAP91SR - Jul 4, 18:55 UTCJul 4, 19:00 UTC5m
2026-07-04 TAP91SR - Jul 4, 17:30 UTCJul 4, 18:15 UTC45m
2026-07-04 TAP83RS - Jul 4, 12:55 UTCJul 4, 15:45 UTC2h 50m
2026-07-04 TAP832 - Jul 4, 08:30 UTCJul 4, 10:55 UTC2h 25m
2026-07-04 TAP98CX FNC → LIS Jul 4, 04:55 UTCJul 4, 06:15 UTC1h 20m

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

Mode-S 495145 frequently asked

What is Mode-S code 495145?
495145 is an ICAO 24-bit transponder address. Allocated to Portugal. Assigned to CS-TJE.
Where is Mode-S 495145 registered?
Mode-S code 495145 is allocated to Portugal (PT). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 495145 broadcasting right now?
No active broadcast right now. Last signal was 2h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 495145, octal 22250505, decimal 4,804,933.
What flights does 495145 operate?
Mode-S 495145 has broadcast 20 distinct callsigns, including TAP837, TAP836A, TAP30BC, TAP1031, TAP97LS.