Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

4951D1

ICAO 24-bit transponder address · allocated to Portugal

Currently assigned to CS-TNQ · AIRBUS A-320

Hex
4951D1
Octal
22250721
Decimal
4,805,073
Country
PT
Tail
CS-TNQ
Type
A320
Broadcasting now · callsign TAP43PA · 22,775 ft
Flights observed
478
Distinct callsigns
20
Country
PT
Last broadcast
Jul 26, 22:15 UTC

Current position

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

Country allocation

The ICAO 24-bit address 4951D1 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
TAP93MA - 9 2026-07-15
TAP8RL - 8 2026-07-15
TAP83RS TAP Portugal 7 2026-05-31
TAP57LK TAP Portugal 7 2026-07-21
TAP575 TAP Portugal 7 2026-07-22
TAP53LB TAP Portugal 7 2026-07-24
TAP31DB TAP Portugal 7 2026-07-24
TAP9ML - 6 2026-07-03
TAP98CX - 6 2026-06-15
TAP94KM - 6 2026-07-15
TAP832 TAP Portugal 6 2026-05-31
TAP97LS - 5 2026-06-14
TAP93ZR - 5 2026-07-15
TAP931L - 5 2026-07-15
TAP838Z - 5 2026-07-14
TAP828 - 5 2026-07-02
TAP72LP - 5 2026-07-11
TAP64BR TAP Portugal 5 2026-07-26
TAP643 TAP Portugal 5 2026-07-26
TAP641 - 5 2026-07-02

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-26 TAP6CY LIS → CPH Jul 26, 19:40 UTCJul 26, 22:15 UTC2h 35m
2026-07-26 TAP643 BRU → LIS Jul 26, 15:45 UTCJul 26, 18:05 UTC2h 20m
2026-07-26 TAP64BR LIS → BRU Jul 26, 12:00 UTCJul 26, 14:30 UTC2h 30m
2026-07-26 TAP1921 OPO → LIS Jul 26, 08:50 UTCJul 26, 09:30 UTC40m
2026-07-26 TAP1920 LIS → OPO Jul 26, 07:05 UTCJul 26, 07:35 UTC30m
2026-07-25 TAP53ED BER → LIS Jul 25, 15:40 UTCJul 25, 18:50 UTC3h 10m
2026-07-25 TAP532B LIS → BER Jul 25, 11:30 UTCJul 25, 14:35 UTC3h 5m
2026-07-24 TAP31DB BER → BER Jul 24, 11:45 UTCJul 24, 15:10 UTC3h 25m
2026-07-24 TAP53LB LIS → BER Jul 24, 07:25 UTCJul 24, 10:30 UTC3h 5m
2026-07-23 TAP437X ORY → LIS Jul 23, 17:55 UTCJul 23, 20:10 UTC2h 15m
2026-07-23 TAP436 LIS → ORY Jul 23, 14:45 UTCJul 23, 16:40 UTC1h 55m
2026-07-23 TAP823 MXP → LIS Jul 23, 10:20 UTCJul 23, 12:55 UTC2h 35m
2026-07-23 TAP22MX LIS → MXP Jul 23, 06:40 UTCJul 23, 08:55 UTC2h 15m
2026-07-22 TAP825 MXP → LIS Jul 22, 20:45 UTCJul 22, 21:35 UTC50m
2026-07-22 TAP825 MXP → LIS Jul 22, 15:50 UTCJul 22, 19:10 UTC3h 20m
2026-07-22 TAP824 LIS → MXP Jul 22, 12:30 UTCJul 22, 14:35 UTC2h 5m
2026-07-22 TAP575 FRA → LIS Jul 22, 04:10 UTCJul 22, 05:25 UTC1h 15m
2026-07-21 TAP57LK LIS → FRA Jul 21, 17:45 UTCJul 21, 20:20 UTC2h 35m
2026-07-21 TAP571 FRA → LIS Jul 21, 11:55 UTCJul 21, 14:50 UTC2h 55m
2026-07-21 TAP7AB LIS → FRA Jul 21, 08:05 UTCJul 21, 10:40 UTC2h 35m
2026-07-20 TAP35MT OPO → LIS Jul 20, 21:45 UTCJul 20, 22:30 UTC45m
2026-07-20 TAP1827 OPO → OPO Jul 20, 14:45 UTCJul 20, 20:45 UTC6h 0m
2026-07-20 TAP453 ORY → OPO Jul 20, 08:10 UTCJul 20, 10:05 UTC1h 55m
2026-07-20 TAP452 OPO → ORY Jul 20, 05:20 UTCJul 20, 07:05 UTC1h 45m
2026-07-19 TAP31TY LGW → OPO Jul 19, 20:50 UTCJul 19, 22:40 UTC1h 50m
2026-07-19 TAP1330 OPO → LGW Jul 19, 17:45 UTCJul 19, 19:40 UTC1h 55m
2026-07-19 TAP939 GVA → OPO Jul 19, 14:20 UTCJul 19, 16:25 UTC2h 5m
2026-07-19 TAP938 OPO → GVA Jul 19, 11:30 UTCJul 19, 13:15 UTC1h 45m
2026-07-19 TAP9027 DSS → OPO Jul 19, 02:05 UTCJul 19, 06:00 UTC3h 55m
2026-07-18 TAP9026 OPO → DSS Jul 18, 19:40 UTCJul 18, 23:55 UTC4h 15m
2026-07-18 TAP9024 LIS → TRN Jul 18, 08:05 UTCJul 18, 17:10 UTC9h 5m
2026-07-18 TAP1920 LIS → OPO Jul 18, 06:20 UTCJul 18, 06:50 UTC30m
2026-07-17 TAP827V MXP → LIS Jul 17, 18:44 UTCJul 17, 21:30 UTC2h 45m
2026-07-17 TAP826 LIS → MXP Jul 17, 14:44 UTCJul 17, 16:49 UTC2h 5m
2026-07-17 TAP869 - Jul 17, 10:25 UTCJul 17, 13:20 UTC2h 55m
2026-07-17 TAP868 LIS → BLQ Jul 17, 06:40 UTCJul 17, 08:59 UTC2h 20m
2026-07-16 TAP35MT OPO → LIS Jul 16, 23:05 UTCJul 16, 23:44 UTC40m
2026-07-16 TAP939 GVA → OPO Jul 16, 19:55 UTCJul 16, 22:05 UTC2h 10m
2026-07-16 TAP938 OPO → GVA Jul 16, 16:05 UTCJul 16, 17:54 UTC1h 50m
2026-07-16 TAP1329 LGW → OPO Jul 16, 12:49 UTCJul 16, 14:55 UTC2h 5m
2026-07-16 TAP1328 OPO → LGW Jul 16, 09:45 UTCJul 16, 11:34 UTC1h 50m
2026-07-16 TAP1920 LIS → OPO Jul 16, 08:00 UTCJul 16, 08:30 UTC30m
2026-07-15 TAP94KM FNC → LIS Jul 15, 21:30 UTCJul 15, 22:50 UTC1h 20m
2026-07-15 TAP93MA LIS → FNC Jul 15, 18:40 UTCJul 15, 20:10 UTC1h 30m
2026-07-15 TAP931L ZRH → LIS Jul 15, 12:50 UTCJul 15, 15:30 UTC2h 40m
2026-07-15 TAP93ZR LIS → ZRH Jul 15, 08:45 UTCJul 15, 11:00 UTC2h 15m
2026-07-15 TAP8RL - Jul 15, 03:05 UTCJul 15, 05:55 UTC2h 50m
2026-07-14 TAP838Z LIS → FCO Jul 14, 19:40 UTCJul 14, 22:00 UTC2h 20m
2026-07-14 TAP2300 LIS → LIS Jul 14, 14:15 UTCJul 14, 17:40 UTC3h 25m
2026-07-14 TAP1335 LGW → LIS Jul 14, 09:55 UTCJul 14, 12:20 UTC2h 25m

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

Mode-S 4951D1 frequently asked

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