sensors Mode-S transponder

4951F0

ICAO 24-bit transponder address · allocated to Portugal

Currently assigned to CS-TOP · AIRBUS A-330-200

Hex
4951F0
Octal
22250760
Decimal
4,805,104
Country
PT
Tail
CS-TOP
Type
A332
No current signal · last broadcast Jul 26, 22:00 UTC
Flights observed
114
Distinct callsigns
20
Country
PT
Last broadcast
Jul 26, 22:00 UTC

Last known position

Most recent position reported by Mode-S 4951F0.

Country allocation

The ICAO 24-bit address 4951F0 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
TAP067 TAP Portugal 21 2026-07-26
TAP209K TAP Portugal 10 2026-07-26
TAP210 TAP Portugal 9 2026-07-20
TAP203 TAP Portugal 9 2026-07-22
TAP109 - 9 2026-07-12
TAP204A TAP Portugal 8 2026-07-23
TAP110 - 8 2026-06-30
TAP011 TAP Portugal 7 2026-07-24
TAP89WT - 5 2026-06-28
TAP90EH - 4 2026-06-28
TAP012 TAP Portugal 4 2026-07-25
TAP2249 - 3 2026-07-08
TAP103 TAP Portugal 3 2026-06-04
TAP3178 - 2 2026-06-20
TAP028 - 2 2026-06-18
TAP9646 - 1 2026-05-30
TAP9254 - 1 2026-07-07
TAP3177 - 1 2026-06-20
TAP296 - 1 2026-06-26
TAP295 - 1 2026-06-26

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-26 TAP209K LIS → JFK Jul 26, 16:40 UTCJul 26, 22:00 UTC5h 20m
2026-07-26 TAP067 OPO → GIG Jul 26, 02:15 UTCJul 26, 11:30 UTC9h 16m
2026-07-25 TAP067 OPO → GIG Jul 25, 23:30 UTCJul 26, 00:35 UTC1h 5m
2026-07-25 TAP067 OPO → GIG Jul 25, 11:35 UTCJul 25, 21:30 UTC9h 55m
2026-07-25 TAP012 REC → LIS Jul 25, 02:30 UTCJul 25, 09:35 UTC7h 5m
2026-07-24 TAP011 LIS → REC Jul 24, 17:10 UTCJul 25, 00:20 UTC7h 10m
2026-07-24 TAP067 OPO → GIG Jul 24, 05:30 UTCJul 24, 14:40 UTC9h 10m
2026-07-24 TAP067 OPO → GIG Jul 24, 02:45 UTCJul 24, 03:35 UTC50m
2026-07-23 TAP067 OPO → GIG Jul 23, 14:50 UTCJul 24, 00:55 UTC10h 5m
2026-07-23 TAP204A EWR → LIS Jul 23, 04:40 UTCJul 23, 11:10 UTC6h 30m
2026-07-22 TAP203 LIS → EWR Jul 22, 18:45 UTCJul 23, 02:00 UTC7h 15m
2026-07-20 TAP029 LIS → SSA Jul 20, 17:40 UTCJul 21, 11:15 UTC17h 35m
2026-07-20 TAP210 JFK → LIS Jul 20, 04:30 UTCJul 20, 10:50 UTC6h 20m
2026-07-19 TAP209K LIS → JFK Jul 19, 16:40 UTCJul 19, 23:55 UTC7h 15m
2026-07-19 TAP210 JFK → LIS Jul 19, 05:45 UTCJul 19, 11:55 UTC6h 10m
2026-07-18 TAP209K LIS → JFK Jul 18, 16:35 UTCJul 19, 00:40 UTC8h 5m
2026-07-18 TAP012 REC → LIS Jul 18, 04:00 UTCJul 18, 11:00 UTC7h 0m
2026-07-17 TAP011 LIS → REC Jul 17, 23:55 UTCJul 18, 00:15 UTC20m
2026-07-17 TAP011 LIS → REC Jul 17, 17:05 UTCJul 17, 18:55 UTC1h 50m
2026-07-17 TAP067 OPO → GIG Jul 17, 05:25 UTCJul 17, 14:20 UTC8h 55m
2026-07-17 TAP067 OPO → GIG Jul 17, 02:59 UTCJul 17, 03:55 UTC55m
2026-07-16 TAP067 OPO → GIG Jul 16, 14:55 UTCJul 17, 00:50 UTC9h 55m
2026-07-16 TAP210 JFK → LIS Jul 16, 02:40 UTCJul 16, 08:45 UTC6h 5m
2026-07-15 TAP209K LIS → JFK Jul 15, 16:25 UTCJul 15, 23:55 UTC7h 30m
2026-07-15 TAP067 GIG → LIS Jul 15, 04:00 UTCJul 15, 13:25 UTC9h 25m
2026-07-15 TAP067 - Jul 15, 01:15 UTCJul 15, 02:05 UTC50m
2026-07-14 TAP067 - Jul 14, 12:55 UTCJul 14, 23:20 UTC10h 24m
2026-07-14 TAP210 JFK → LIS Jul 14, 03:15 UTCJul 14, 09:45 UTC6h 30m
2026-07-13 TAP209K LIS → JFK Jul 13, 17:10 UTCJul 14, 00:05 UTC6h 55m
2026-07-13 TAP112 - Jul 13, 03:25 UTCJul 13, 13:20 UTC9h 55m
2026-07-12 TAP109 - Jul 12, 11:45 UTCJul 12, 22:10 UTC10h 25m
2026-07-12 TAP210 JFK → LIS Jul 12, 03:35 UTCJul 12, 09:50 UTC6h 15m
2026-07-11 TAP209K LIS → JFK Jul 11, 16:35 UTCJul 12, 00:05 UTC7h 30m
2026-07-11 TAP204A - Jul 11, 03:30 UTCJul 11, 09:40 UTC6h 10m
2026-07-10 TAP203 LIS → EWR Jul 10, 17:35 UTCJul 11, 00:55 UTC7h 20m
2026-07-10 TAP067 - Jul 10, 05:50 UTCJul 10, 14:50 UTC9h 0m
2026-07-10 TAP067 - Jul 10, 02:55 UTCJul 10, 03:45 UTC50m
2026-07-09 TAP067 - Jul 9, 14:35 UTCJul 10, 00:30 UTC9h 55m
2026-07-08 TAP2249 - Jul 8, 20:10 UTCJul 9, 05:15 UTC9h 5m
2026-07-08 TAP2249 - Jul 8, 17:40 UTCJul 8, 18:40 UTC1h 0m
2026-07-08 TAP2249 - Jul 8, 05:35 UTCJul 8, 15:45 UTC10h 10m
2026-07-07 TAP9254 BOS → LIS Jul 7, 22:05 UTCJul 8, 03:50 UTC5h 45m
2026-07-05 TAP203 LIS → BOS Jul 5, 17:50 UTCJul 6, 02:05 UTC8h 15m
2026-07-05 TAP067 - Jul 5, 02:45 UTCJul 5, 11:50 UTC9h 5m
2026-07-05 TAP067 - Jul 5, 00:05 UTCJul 5, 00:55 UTC50m
2026-07-04 TAP067 - Jul 4, 11:50 UTCJul 4, 22:05 UTC10h 15m
2026-07-03 TAP011 LIS → LIS Jul 3, 17:10 UTCJul 4, 09:30 UTC16h 20m
2026-07-03 TAP067 - Jul 3, 06:15 UTCJul 3, 15:10 UTC8h 55m
2026-07-03 TAP067 - Jul 3, 03:15 UTCJul 3, 03:55 UTC40m
2026-07-02 TAP067 - Jul 2, 14:35 UTCJul 3, 00:45 UTC10h 10m

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

Mode-S 4951F0 frequently asked

What is Mode-S code 4951F0?
4951F0 is an ICAO 24-bit transponder address. Allocated to Portugal. Assigned to CS-TOP.
Where is Mode-S 4951F0 registered?
Mode-S code 4951F0 is allocated to Portugal (PT). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 4951F0 broadcasting right now?
No active broadcast right now. Last signal was Jul 26, 22:00 UTC.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 4951F0, octal 22250760, decimal 4,805,104.
What flights does 4951F0 operate?
Mode-S 4951F0 has broadcast 20 distinct callsigns, including TAP067, TAP209K, TAP210, TAP203, TAP109.