sensors Mode-S transponder
4952A2
ICAO 24-bit transponder address · allocated to Portugal
Currently assigned to CS-TUB · AIRBUS A-330-900
- Hex
- 4952A2
- Octal
- 22251242
- Decimal
- 4,805,282
- Country
- PT
- Tail
- CS-TUB
- Type
- A339
- Flights observed
- 72
- Distinct callsigns
- 20
- Country
- PT
- Last broadcast
- 8d ago
Last known position
Country allocation
The ICAO 24-bit address 4952A2 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 |
|---|---|---|---|
| TAP89WT | TAP Portugal | 5 | 2026-05-05 |
| TAP209K | TAP Portugal | 4 | 2026-04-16 |
| TAP087 | TAP Portugal | 4 | 2026-05-16 |
| TAP082 | TAP Portugal | 4 | 2026-05-17 |
| TAP028 | TAP Portugal | 4 | 2026-04-13 |
| TAP9022 | - | 3 | 2026-04-14 |
| TAP210 | TAP Portugal | 3 | 2026-04-17 |
| TAP118 | TAP Portugal | 3 | 2026-04-25 |
| TAP093 | TAP Portugal | 3 | 2026-05-12 |
| TAP036 | TAP Portugal | 3 | 2026-04-23 |
| TAP9023 | - | 2 | 2026-04-16 |
| TAP282 | TAP Portugal | 2 | 2026-04-20 |
| TAP22MI | TAP Portugal | 2 | 2026-05-20 |
| TAP224 | TAP Portugal | 2 | 2026-05-20 |
| TAP104 | TAP Portugal | 2 | 2026-05-02 |
| TAP094 | TAP Portugal | 2 | 2026-05-10 |
| TAP078 | TAP Portugal | 2 | 2026-05-12 |
| TAP077 | TAP Portugal | 2 | 2026-05-11 |
| TAP035 | TAP Portugal | 2 | 2026-04-22 |
| TAP029 | TAP Portugal | 2 | 2026-05-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-21 | TAP058 | BSB → LIS | May 21, 10:35 UTC | May 22, 04:55 UTC | 18h 20m |
| 2026-05-21 | TAP057 | LIS → BSB | May 21, 09:15 UTC | May 22, 04:55 UTC | 19h 40m |
| 2026-05-20 | TAP224 | MIA → LIS | May 20, 22:05 UTC | May 21, 05:50 UTC | 7h 45m |
| 2026-05-20 | TAP22MI | LIS → MIA | May 20, 09:55 UTC | May 20, 18:30 UTC | 8h 35m |
| 2026-05-19 | TAP074 | GIG → LIS | May 19, 18:45 UTC | May 20, 03:30 UTC | 8h 45m |
| 2026-05-18 | TAP075 | LIS → GIG | May 18, 22:45 UTC | May 19, 08:10 UTC | 9h 25m |
| 2026-05-17 | TAP082 | GRU → LIS | May 17, 18:40 UTC | May 18, 03:50 UTC | 9h 10m |
| 2026-05-16 | TAP087 | LIS → GRU | May 16, 23:05 UTC | May 17, 09:35 UTC | 10h 30m |
| 2026-05-15 | TAP224 | MIA → LIS | May 15, 21:00 UTC | May 16, 04:15 UTC | 7h 15m |
| 2026-05-15 | TAP22MI | LIS → MIA | May 15, 09:55 UTC | May 15, 18:30 UTC | 8h 34m |
| 2026-05-13 | TAP029 | LIS → SSA | May 13, 17:00 UTC | May 14, 10:25 UTC | 17h 25m |
| 2026-05-13 | TAP088 | GRU → LIS | May 13, 01:35 UTC | May 13, 10:20 UTC | 8h 45m |
| 2026-05-12 | TAP093 | OPO → GRU | May 12, 12:50 UTC | May 12, 23:40 UTC | 10h 50m |
| 2026-05-12 | TAP078 | GIG → OPO | May 12, 03:05 UTC | May 12, 09:35 UTC | 6h 30m |
| 2026-05-11 | TAP077 | OPO → GIG | May 11, 12:10 UTC | May 11, 22:35 UTC | 10h 25m |
| 2026-05-10 | TAP294 | - | May 10, 22:49 UTC | May 11, 06:35 UTC | 7h 45m |
| 2026-05-10 | TAP293 | - | May 10, 12:40 UTC | May 10, 19:50 UTC | 7h 10m |
| 2026-05-10 | TAP094 | GRU → OPO | May 10, 00:20 UTC | May 10, 09:40 UTC | 9h 20m |
| 2026-05-09 | TAP093 | OPO → GRU | May 9, 12:15 UTC | May 9, 22:30 UTC | 10h 15m |
| 2026-05-09 | TAP078 | GIG → OPO | May 9, 00:45 UTC | May 9, 09:55 UTC | 9h 10m |
| 2026-05-08 | TAP077 | OPO → GIG | May 8, 12:49 UTC | May 8, 22:50 UTC | 10h 0m |
| 2026-05-08 | TAP094 | GRU → OPO | May 8, 00:14 UTC | May 8, 09:44 UTC | 9h 30m |
| 2026-05-07 | TAP093 | OPO → GRU | May 7, 12:00 UTC | May 7, 22:15 UTC | 10h 15m |
| 2026-05-07 | TAP9243 | LIS → OPO | May 7, 08:20 UTC | May 7, 09:00 UTC | 40m |
| 2026-05-06 | TAP082 | GRU → LIS | May 6, 19:10 UTC | May 7, 04:05 UTC | 8h 55m |
| 2026-05-05 | TAP087 | LIS → GRU | May 5, 23:10 UTC | May 6, 09:10 UTC | 10h 0m |
| 2026-05-05 | TAP89WT | LIS → FNC | May 5, 14:00 UTC | May 5, 14:40 UTC | 40m |
| 2026-05-05 | TAP89WT | LIS → FNC | May 5, 12:35 UTC | May 5, 13:25 UTC | 50m |
| 2026-05-05 | TAP89WT | LIS → FNC | May 5, 11:15 UTC | May 5, 11:50 UTC | 35m |
| 2026-05-04 | TAP3178 | - | May 4, 18:50 UTC | May 5, 08:25 UTC | 13h 35m |
| 2026-05-04 | TAP3177 | LIS → LIS | May 4, 11:40 UTC | May 5, 08:25 UTC | 20h 46m |
| 2026-05-02 | TAP104 | CNF → LIS | May 2, 10:35 UTC | May 3, 05:20 UTC | 18h 44m |
| 2026-05-02 | TAP104 | CNF → LIS | May 2, 10:05 UTC | May 3, 05:20 UTC | 19h 14m |
| 2026-05-01 | TAP082 | GRU → LIS | May 1, 18:50 UTC | May 2, 03:45 UTC | 8h 55m |
| 2026-05-01 | TAP087 | LIS → GRU | May 1, 00:15 UTC | May 1, 10:05 UTC | 9h 50m |
| 2026-04-30 | TAP226 | MIA → LIS | Apr 30, 08:10 UTC | Apr 30, 15:40 UTC | 7h 30m |
| 2026-04-29 | TAP225V | LIS → MIA | Apr 29, 18:50 UTC | Apr 30, 03:20 UTC | 8h 29m |
| 2026-04-28 | TAP204A | EWR → LIS | Apr 28, 03:20 UTC | Apr 28, 10:10 UTC | 6h 50m |
| 2026-04-27 | TAP203 | LIS → EWR | Apr 27, 17:20 UTC | Apr 28, 00:15 UTC | 6h 55m |
| 2026-04-25 | TAP118 | POA → LIS | Apr 25, 23:55 UTC | Apr 26, 15:05 UTC | 15h 10m |
| 2026-04-25 | TAP118 | POA → LIS | Apr 25, 15:05 UTC | Apr 26, 14:30 UTC | 23h 25m |
| 2026-04-23 | TAP118 | POA → LIS | Apr 23, 19:40 UTC | Apr 24, 12:00 UTC | 16h 20m |
| 2026-04-23 | TAP117 | LIS → POA | Apr 23, 13:15 UTC | Apr 24, 12:00 UTC | 22h 45m |
| 2026-04-23 | TAP036 | FOR → LIS | Apr 23, 02:25 UTC | Apr 23, 08:45 UTC | 6h 21m |
| 2026-04-22 | TAP035 | LIS → FOR | Apr 22, 17:35 UTC | Apr 23, 00:45 UTC | 7h 10m |
| 2026-04-22 | TAP90EH | FNC → LIS | Apr 22, 13:50 UTC | Apr 22, 15:15 UTC | 1h 25m |
| 2026-04-22 | TAP89WT | LIS → FNC | Apr 22, 12:25 UTC | Apr 22, 12:30 UTC | 5m |
| 2026-04-22 | TAP89WT | LIS → FNC | Apr 22, 11:05 UTC | Apr 22, 11:40 UTC | 35m |
| 2026-04-21 | TAP082 | GRU → LIS | Apr 21, 18:50 UTC | Apr 22, 03:50 UTC | 9h 0m |
| 2026-04-20 | TAP087 | LIS → GRU | Apr 20, 21:35 UTC | Apr 21, 07:40 UTC | 10h 5m |
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-TUB page for operator, model, and routing details .