Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

4951D3

ICAO 24-bit transponder address · allocated to Portugal

Currently assigned to CS-TNS · AIRBUS A-320

Hex
4951D3
Octal
22250723
Decimal
4,805,075
Country
PT
Tail
CS-TNS
Type
A320
Broadcasting now · callsign TAP564C · 33,975 ft
Flights observed
475
Distinct callsigns
20
Country
PT
Last broadcast
Jul 26, 22:45 UTC

Current position

4951D3 is currently broadcasting. Map zoomed to live position.

Country allocation

The ICAO 24-bit address 4951D3 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
TAP86VR - 12 2026-07-16
TAP863Y - 12 2026-07-16
TAP828 TAP Portugal 11 2026-07-26
TAP9ML - 9 2026-07-15
TAP94VA TAP Portugal 8 2026-07-26
TAP42LV TAP Portugal 8 2026-07-26
TAP1908 TAP Portugal 8 2026-07-17
TAP1907 - 8 2026-07-16
TAP9RH TAP Portugal 7 2026-06-09
TAP934 TAP Portugal 7 2026-06-08
TAP43PA TAP Portugal 7 2026-07-23
TAP43JD TAP Portugal 7 2026-07-23
TAP93MA TAP Portugal 6 2026-07-21
TAP30BC - 6 2026-07-13
TAP8RL TAP Portugal 5 2026-07-21
TAP89WT - 5 2026-07-08
TAP838Z - 5 2026-07-20
TAP57LK TAP Portugal 5 2026-07-25
TAP555 TAP Portugal 5 2026-07-23
TAP26TS TAP Portugal 5 2026-07-21

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-26 TAP828 LIS → MXP Jul 26, 21:35 UTCJul 26, 22:45 UTC1h 10m
2026-07-26 TAP94VA GVA → LIS Jul 26, 18:05 UTCJul 26, 20:10 UTC2h 5m
2026-07-26 TAP42LV LIS → GVA Jul 26, 14:40 UTCJul 26, 16:55 UTC2h 15m
2026-07-26 TAP575 FRA → LIS Jul 26, 06:00 UTCJul 26, 08:20 UTC2h 21m
2026-07-25 TAP57LK LIS → FRA Jul 25, 18:00 UTCJul 25, 20:50 UTC2h 50m
2026-07-25 TAP83RS FCO → LIS Jul 25, 12:20 UTCJul 25, 15:25 UTC3h 5m
2026-07-25 TAP832 LIS → FCO Jul 25, 07:55 UTCJul 25, 10:05 UTC2h 10m
2026-07-23 TAP555 MUC → LIS Jul 23, 18:15 UTCJul 23, 21:10 UTC2h 55m
2026-07-23 TAP554M LIS → MUC Jul 23, 14:30 UTCJul 23, 17:05 UTC2h 35m
2026-07-23 TAP43JD ORY → LIS Jul 23, 10:45 UTCJul 23, 12:50 UTC2h 5m
2026-07-23 TAP43PA LIS → ORY Jul 23, 07:40 UTCJul 23, 09:35 UTC1h 55m
2026-07-22 TAP645 BRU → LIS Jul 22, 19:25 UTCJul 22, 22:05 UTC2h 40m
2026-07-22 TAP44BR LIS → BRU Jul 22, 15:40 UTCJul 22, 17:55 UTC2h 15m
2026-07-22 TAP11EG MAN → LIS Jul 22, 11:10 UTCJul 22, 13:50 UTC2h 40m
2026-07-21 TAP94KM FNC → LIS Jul 21, 21:25 UTCJul 21, 22:50 UTC1h 25m
2026-07-21 TAP93MA LIS → FNC Jul 21, 19:50 UTCJul 21, 20:10 UTC20m
2026-07-21 TAP93MA LIS → FNC Jul 21, 18:30 UTCJul 21, 19:05 UTC35m
2026-07-21 TAP1127 - Jul 21, 12:30 UTCJul 21, 14:15 UTC1h 45m
2026-07-21 TAP26TS LIS → TFS Jul 21, 09:05 UTCJul 21, 11:05 UTC2h 0m
2026-07-21 TAP8RL FCO → LIS Jul 21, 04:15 UTCJul 21, 07:05 UTC2h 50m
2026-07-20 TAP838Z LIS → FCO Jul 20, 21:30 UTCJul 20, 23:50 UTC2h 20m
2026-07-20 TAP94VA - Jul 20, 17:20 UTCJul 20, 19:50 UTC2h 30m
2026-07-20 TAP42LV LIS → GVA Jul 20, 13:55 UTCJul 20, 15:55 UTC2h 0m
2026-07-20 TAP757P CPH → LIS Jul 20, 04:35 UTCJul 20, 08:10 UTC3h 35m
2026-07-19 TAP6CY LIS → CPH Jul 19, 19:50 UTCJul 19, 22:55 UTC3h 5m
2026-07-19 TAP1931 OPO → LIS Jul 19, 17:20 UTCJul 19, 18:00 UTC40m
2026-07-19 TAP1930 LIS → OPO Jul 19, 15:25 UTCJul 19, 16:05 UTC40m
2026-07-19 TAP11EG MAN → LIS Jul 19, 10:50 UTCJul 19, 13:25 UTC2h 35m
2026-07-19 TAP1310 LIS → MAN Jul 19, 06:50 UTCJul 19, 09:15 UTC2h 25m
2026-07-18 TAP1906 FAO → LIS Jul 18, 17:45 UTCJul 18, 18:15 UTC30m
2026-07-18 TAP1905 LIS → FAO Jul 18, 16:10 UTCJul 18, 16:45 UTC35m
2026-07-18 TAP1127 - Jul 18, 12:30 UTCJul 18, 14:10 UTC1h 40m
2026-07-18 TAP26TS - Jul 18, 09:10 UTCJul 18, 11:05 UTC1h 55m
2026-07-18 TAP575 FRA → LIS Jul 18, 04:25 UTCJul 18, 07:15 UTC2h 50m
2026-07-17 TAP57LK LIS → FRA Jul 17, 17:44 UTCJul 17, 20:10 UTC2h 25m
2026-07-17 TAP71VE VIE → LIS Jul 17, 11:45 UTCJul 17, 15:35 UTC3h 50m
2026-07-17 TAP70VE LIS → VIE Jul 17, 07:25 UTCJul 17, 10:25 UTC3h 0m
2026-07-17 TAP1908 FAO → LIS Jul 17, 05:20 UTCJul 17, 05:45 UTC25m
2026-07-16 TAP1907 LIS → FAO Jul 16, 22:19 UTCJul 16, 22:55 UTC35m
2026-07-16 TAP863Y - Jul 16, 18:00 UTCJul 16, 20:55 UTC2h 55m
2026-07-16 TAP86VR - Jul 16, 14:20 UTCJul 16, 16:40 UTC2h 20m
2026-07-16 TAP43JD ORY → LIS Jul 16, 10:10 UTCJul 16, 12:25 UTC2h 15m
2026-07-16 TAP43PA LIS → ORY Jul 16, 07:00 UTCJul 16, 08:50 UTC1h 50m
2026-07-16 TAP827V MXP → LIS Jul 16, 00:30 UTCJul 16, 02:55 UTC2h 25m
2026-07-15 TAP828 LIS → MXP Jul 15, 20:35 UTCJul 15, 22:55 UTC2h 20m
2026-07-15 TAP94VA - Jul 15, 16:40 UTCJul 15, 19:15 UTC2h 35m
2026-07-15 TAP42LV LIS → GVA Jul 15, 13:35 UTCJul 15, 15:30 UTC1h 55m
2026-07-15 TAP1902 FAO → LIS Jul 15, 10:45 UTCJul 15, 11:15 UTC30m
2026-07-15 TAP1901 LIS → FAO Jul 15, 09:05 UTCJul 15, 09:40 UTC35m
2026-07-15 TAP9ML MXP → LIS Jul 15, 04:20 UTCJul 15, 06:55 UTC2h 35m

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

Mode-S 4951D3 frequently asked

What is Mode-S code 4951D3?
4951D3 is an ICAO 24-bit transponder address. Allocated to Portugal. Assigned to CS-TNS.
Where is Mode-S 4951D3 registered?
Mode-S code 4951D3 is allocated to Portugal (PT). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 4951D3 broadcasting right now?
Yes. Mode-S 4951D3 is currently airborne.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 4951D3, octal 22250723, decimal 4,805,075.
What flights does 4951D3 operate?
Mode-S 4951D3 has broadcast 20 distinct callsigns, including TAP86VR, TAP863Y, TAP828, TAP9ML, TAP94VA.