sensors Mode-S transponder
4952AF
ICAO 24-bit transponder address · allocated to Portugal
Currently assigned to CS-TUO · AIRBUS A-330-900
- Hex
- 4952AF
- Octal
- 22251257
- Decimal
- 4,805,295
- Country
- PT
- Tail
- CS-TUO
- Type
- A339
- Flights observed
- 109
- Distinct callsigns
- 20
- Country
- PT
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 4952AF 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 |
|---|---|---|---|
| TAP073 | - | 8 | 2026-07-06 |
| TAP075 | TAP Portugal | 7 | 2026-07-19 |
| TAP072 | - | 7 | 2026-07-06 |
| TAP074 | TAP Portugal | 6 | 2026-07-20 |
| TAP087 | - | 5 | 2026-07-15 |
| TAP082 | - | 5 | 2026-07-16 |
| TAP057 | - | 5 | 2026-07-07 |
| TAP028 | TAP Portugal | 5 | 2026-07-23 |
| TAP248 | TAP Portugal | 4 | 2026-07-22 |
| TAP247 | TAP Portugal | 4 | 2026-07-21 |
| TAP104 | TAP Portugal | 4 | 2026-07-17 |
| TAP226 | - | 3 | 2026-06-18 |
| TAP118 | TAP Portugal | 3 | 2026-05-24 |
| TAP89WT | - | 2 | 2026-06-24 |
| TAP3927 | TAP Portugal | 2 | 2026-06-04 |
| TAP282 | - | 2 | 2026-06-27 |
| TAP243U | - | 2 | 2026-07-02 |
| TAP241 | - | 2 | 2026-07-14 |
| TAP23SL | - | 2 | 2026-07-10 |
| TAP237M | - | 2 | 2026-07-09 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | TAP083 | LIS → GRU | Jul 26, 16:55 UTC | Jul 26, 18:45 UTC | 1h 50m |
| 2026-07-26 | TAP204A | EWR → LIS | Jul 26, 03:25 UTC | Jul 26, 09:55 UTC | 6h 31m |
| 2026-07-25 | TAP203 | LIS → EWR | Jul 25, 17:30 UTC | Jul 26, 00:15 UTC | 6h 45m |
| 2026-07-25 | TAP084 | GRU → LIS | Jul 25, 05:30 UTC | Jul 25, 14:55 UTC | 9h 25m |
| 2026-07-24 | TAP083 | LIS → GRU | Jul 24, 16:40 UTC | Jul 25, 02:10 UTC | 9h 30m |
| 2026-07-23 | TAP028 | FOR → LIS | Jul 23, 16:50 UTC | Jul 24, 10:35 UTC | 17h 45m |
| 2026-07-22 | TAP028 | FOR → LIS | Jul 22, 17:10 UTC | Jul 23, 10:30 UTC | 17h 20m |
| 2026-07-22 | TAP248 | LIS → ALG | Jul 22, 00:05 UTC | Jul 22, 05:25 UTC | 5h 20m |
| 2026-07-21 | TAP247 | LIS → LAX | Jul 21, 09:35 UTC | Jul 21, 20:50 UTC | 11h 15m |
| 2026-07-20 | TAP074 | GIG → LIS | Jul 20, 18:40 UTC | Jul 21, 03:30 UTC | 8h 49m |
| 2026-07-19 | TAP075 | LIS → GIG | Jul 19, 22:40 UTC | Jul 20, 08:15 UTC | 9h 35m |
| 2026-07-19 | TAP248 | - | Jul 19, 00:25 UTC | Jul 19, 10:55 UTC | 10h 30m |
| 2026-07-18 | TAP247 | LIS → LAX | Jul 18, 09:45 UTC | Jul 18, 20:45 UTC | 11h 0m |
| 2026-07-17 | TAP104 | CNF → LIS | Jul 17, 12:04 UTC | Jul 18, 06:15 UTC | 18h 11m |
| 2026-07-17 | TAP104 | CNF → LIS | Jul 17, 10:55 UTC | Jul 18, 06:15 UTC | 19h 21m |
| 2026-07-16 | TAP082 | - | Jul 16, 18:44 UTC | Jul 17, 03:55 UTC | 9h 10m |
| 2026-07-15 | TAP087 | LIS → GRU | Jul 15, 22:45 UTC | Jul 16, 08:30 UTC | 9h 45m |
| 2026-07-15 | TAP240 | SFO → LIS | Jul 15, 02:40 UTC | Jul 15, 16:20 UTC | 13h 40m |
| 2026-07-14 | TAP241 | - | Jul 14, 17:35 UTC | Jul 14, 23:35 UTC | 5h 59m |
| 2026-07-14 | TAP241 | - | Jul 14, 08:50 UTC | Jul 14, 09:25 UTC | 35m |
| 2026-07-13 | TAP103 | LIS → LIS | Jul 13, 09:55 UTC | Jul 14, 05:40 UTC | 19h 45m |
| 2026-07-12 | TAP104 | - | Jul 12, 09:50 UTC | Jul 13, 05:35 UTC | 19h 45m |
| 2026-07-11 | TAP296 | - | Jul 11, 22:20 UTC | Jul 12, 05:45 UTC | 7h 25m |
| 2026-07-11 | TAP295 | - | Jul 11, 13:15 UTC | Jul 11, 20:10 UTC | 6h 55m |
| 2026-07-11 | TAP210 | JFK → LIS | Jul 11, 02:40 UTC | Jul 11, 09:00 UTC | 6h 20m |
| 2026-07-10 | TAP209K | LIS → JFK | Jul 10, 16:35 UTC | Jul 10, 23:40 UTC | 7h 6m |
| 2026-07-10 | TAP23SL | - | Jul 10, 00:25 UTC | Jul 10, 10:30 UTC | 10h 5m |
| 2026-07-09 | TAP237M | LIS → SFO | Jul 9, 09:30 UTC | Jul 9, 21:10 UTC | 11h 40m |
| 2026-07-08 | TAP104 | LIS → LIS | Jul 8, 10:25 UTC | Jul 9, 06:05 UTC | 19h 40m |
| 2026-07-07 | TAP057 | LIS → LIS | Jul 7, 10:30 UTC | Jul 8, 05:40 UTC | 19h 10m |
| 2026-07-06 | TAP072 | - | Jul 6, 23:20 UTC | Jul 7, 08:20 UTC | 9h 0m |
| 2026-07-06 | TAP073 | - | Jul 6, 11:20 UTC | Jul 6, 20:40 UTC | 9h 20m |
| 2026-07-05 | TAP072 | - | Jul 5, 23:30 UTC | Jul 6, 08:20 UTC | 8h 50m |
| 2026-07-05 | TAP073 | - | Jul 5, 09:15 UTC | Jul 5, 18:40 UTC | 9h 25m |
| 2026-07-04 | TAP082 | - | Jul 4, 18:35 UTC | Jul 5, 03:35 UTC | 9h 0m |
| 2026-07-03 | TAP087 | - | Jul 3, 23:20 UTC | Jul 4, 09:00 UTC | 9h 40m |
| 2026-07-03 | TAP242 | ORD → LIS | Jul 3, 04:25 UTC | Jul 3, 11:50 UTC | 7h 25m |
| 2026-07-02 | TAP243U | LIS → ORD | Jul 2, 08:40 UTC | Jul 2, 17:20 UTC | 8h 40m |
| 2026-07-01 | TAP074 | - | Jul 1, 19:10 UTC | Jul 2, 03:50 UTC | 8h 40m |
| 2026-06-30 | TAP075 | - | Jun 30, 23:30 UTC | Jul 1, 09:05 UTC | 9h 35m |
| 2026-06-28 | TAP082 | - | Jun 28, 18:55 UTC | Jun 29, 04:04 UTC | 9h 10m |
| 2026-06-27 | TAP087 | - | Jun 27, 23:00 UTC | Jun 28, 08:29 UTC | 9h 30m |
| 2026-06-27 | TAP282 | - | Jun 27, 16:10 UTC | Jun 27, 17:29 UTC | 1h 20m |
| 2026-06-26 | TAP282 | - | Jun 26, 19:50 UTC | Jun 27, 17:29 UTC | 21h 40m |
| 2026-06-26 | TAP281 | - | Jun 26, 18:54 UTC | Jun 26, 20:10 UTC | 1h 15m |
| 2026-06-26 | TAP250 | - | Jun 26, 05:35 UTC | Jun 26, 15:29 UTC | 9h 55m |
| 2026-06-25 | TAP249 | ALG → LIS | Jun 25, 15:20 UTC | Jun 26, 03:00 UTC | 11h 40m |
| 2026-06-24 | TAP028 | LIS → LIS | Jun 24, 17:10 UTC | Jun 25, 10:55 UTC | 17h 45m |
| 2026-06-24 | TAP90EH | FNC → LIS | Jun 24, 13:40 UTC | Jun 24, 15:00 UTC | 1h 20m |
| 2026-06-24 | TAP89WT | - | Jun 24, 12:09 UTC | Jun 24, 12:20 UTC | 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-TUO page for operator, model, and routing details .