sensors Mode-S transponder

495066

ICAO 24-bit transponder address · allocated to Portugal

Currently assigned to CS-TCF · AIRBUS A-330-900

Hex
495066
Octal
22250146
Decimal
4,804,710
Country
PT
Tail
CS-TCF
Type
A339
No current signal · last broadcast 6h ago
Flights observed
53
Distinct callsigns
13
Country
PT
Last broadcast
6h ago

Last known position

Most recent position reported by Mode-S 495066.

Country allocation

The ICAO 24-bit address 495066 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 13 distinct

Callsign Airline Flights Last seen
OBS864 Orbest 9 2026-05-25
OBS851 Orbest 9 2026-05-25
OBS863 Orbest 7 2026-05-24
OBS852 Orbest 6 2026-05-19
OBS162P - 6 2026-05-24
OBS153P Orbest 6 2026-05-26
EVE802 Air Evex 2 2026-05-03
EVE801 Air Evex 2 2026-05-02
ETR895 Aerolíneas Estelar 2 2026-05-01
OBS831 Orbest 1 2026-05-29
OBS130P - 1 2026-05-29
OBS125P - 1 2026-04-14
ETR894 - 1 2026-04-17

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-29 OBS831 LIS → AZS May 29, 19:00 UTCMay 29, 19:35 UTC35m
2026-05-29 OBS130P - May 29, 15:50 UTCMay 29, 17:00 UTC1h 10m
2026-05-26 OBS153P PUJ → MAD May 26, 12:40 UTCMay 26, 13:50 UTC1h 10m
2026-05-25 OBS851 LIS → PUJ May 25, 15:40 UTCMay 26, 08:30 UTC16h 49m
2026-05-25 OBS864 CUN → LIS May 25, 02:45 UTCMay 25, 11:35 UTC8h 50m
2026-05-24 OBS863 LIS → CUN May 24, 14:55 UTCMay 24, 23:46 UTC8h 51m
2026-05-24 OBS162P - May 24, 11:05 UTCMay 24, 12:00 UTC55m
2026-05-19 OBS153P PUJ → MAD May 19, 12:40 UTCMay 19, 13:35 UTC55m
2026-05-19 OBS852 PUJ → LIS May 19, 01:45 UTCMay 19, 08:20 UTC6h 35m
2026-05-18 OBS851 LIS → PUJ May 18, 14:55 UTCMay 18, 22:25 UTC7h 29m
2026-05-18 OBS864 CUN → LIS May 18, 02:50 UTCMay 18, 11:10 UTC8h 20m
2026-05-17 OBS863 LIS → CUN May 17, 15:05 UTCMay 18, 00:40 UTC9h 35m
2026-05-17 OBS162P MAD → LIS May 17, 10:50 UTCMay 17, 11:55 UTC1h 5m
2026-05-12 OBS153P PUJ → MAD May 12, 13:05 UTCMay 12, 14:00 UTC55m
2026-05-11 OBS851 LIS → PUJ May 11, 15:00 UTCMay 12, 08:20 UTC17h 21m
2026-05-11 OBS864 CUN → LIS May 11, 00:15 UTCMay 11, 12:25 UTC12h 10m
2026-05-10 OBS863 LIS → CUN May 10, 16:25 UTCMay 11, 12:25 UTC20h 0m
2026-05-10 OBS162P MAD → LIS May 10, 12:54 UTCMay 10, 14:04 UTC1h 10m
2026-05-05 OBS153P PUJ → MAD May 5, 12:35 UTCMay 5, 13:20 UTC45m
2026-05-05 OBS852 PUJ → LIS May 5, 01:40 UTCMay 5, 08:30 UTC6h 50m
2026-05-04 OBS851 LIS → PUJ May 4, 15:05 UTCMay 4, 22:25 UTC7h 21m
2026-05-04 OBS864 CUN → LIS May 4, 03:30 UTCMay 4, 11:45 UTC8h 15m
2026-05-03 OBS863 LIS → CUN May 3, 15:35 UTCMay 4, 01:20 UTC9h 45m
2026-05-03 OBS162P MAD → LIS May 3, 12:35 UTCMay 3, 13:45 UTC1h 10m
2026-05-03 EVE802 PUJ → MAD May 3, 08:40 UTCMay 3, 09:45 UTC1h 5m
2026-05-02 EVE801 MAD → PUJ May 2, 15:55 UTCMay 2, 23:55 UTC8h 0m
2026-05-01 ETR895 CCS → MAD May 1, 13:40 UTCMay 2, 09:00 UTC19h 20m
2026-04-28 OBS153P PUJ → MAD Apr 28, 12:00 UTCApr 28, 12:55 UTC55m
2026-04-28 OBS852 PUJ → LIS Apr 28, 02:35 UTCApr 28, 08:55 UTC6h 20m
2026-04-27 OBS851 LIS → PUJ Apr 27, 15:40 UTCApr 27, 23:25 UTC7h 45m
2026-04-27 OBS864 CUN → LIS Apr 27, 02:55 UTCApr 27, 11:20 UTC8h 25m
2026-04-26 OBS863 LIS → CUN Apr 26, 14:50 UTCApr 27, 00:30 UTC9h 41m
2026-04-26 OBS162P - Apr 26, 11:00 UTCApr 26, 11:50 UTC50m
2026-04-22 EVE802 PUJ → MAD Apr 22, 07:40 UTCApr 22, 08:55 UTC1h 15m
2026-04-21 EVE801 MAD → PUJ Apr 21, 14:20 UTCApr 21, 22:20 UTC8h 0m
2026-04-21 OBS153P PUJ → MAD Apr 21, 10:55 UTCApr 21, 11:45 UTC50m
2026-04-20 OBS852 PUJ → LIS Apr 20, 15:00 UTCApr 21, 08:15 UTC17h 15m
2026-04-20 OBS864 CUN → LIS Apr 20, 03:45 UTCApr 20, 12:25 UTC8h 40m
2026-04-19 OBS863 LIS → CUN Apr 19, 14:50 UTCApr 20, 00:20 UTC9h 30m
2026-04-19 OBS162P - Apr 19, 11:35 UTCApr 19, 12:30 UTC55m
2026-04-18 ETR895 CCS → MAD Apr 18, 09:00 UTCApr 18, 10:05 UTC1h 5m
2026-04-17 ETR894 MAD → MAD Apr 17, 13:50 UTCApr 18, 10:05 UTC20h 15m
2026-04-14 OBS125P - Apr 14, 10:50 UTCApr 14, 11:45 UTC55m
2026-04-14 OBS852 - Apr 14, 07:30 UTCApr 14, 08:10 UTC40m
2026-04-14 OBS852 - Apr 14, 06:15 UTCApr 14, 06:25 UTC10m
2026-04-13 OBS851 - Apr 13, 22:05 UTCApr 13, 22:45 UTC40m
2026-04-13 OBS851 - Apr 13, 16:15 UTCApr 13, 16:30 UTC15m
2026-04-13 OBS851 - Apr 13, 15:50 UTCApr 13, 16:30 UTC40m
2026-04-13 OBS851 - Apr 13, 15:00 UTCApr 13, 16:15 UTC1h 15m
2026-04-13 OBS864 CUN → LIS Apr 13, 10:35 UTCApr 13, 11:10 UTC35m

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

Mode-S 495066 frequently asked

What is Mode-S code 495066?
495066 is an ICAO 24-bit transponder address. Allocated to Portugal. Assigned to CS-TCF.
Where is Mode-S 495066 registered?
Mode-S code 495066 is allocated to Portugal (PT). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 495066 broadcasting right now?
No active broadcast right now. Last signal was 6h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 495066, octal 22250146, decimal 4,804,710.
What flights does 495066 operate?
Mode-S 495066 has broadcast 13 distinct callsigns, including OBS864, OBS851, OBS863, OBS852, OBS162P.