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
- 157
- Distinct callsigns
- 20
- Country
- PT
- Last broadcast
- Jul 26, 16:15 UTC
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 |
|---|---|---|---|
| TAP104 | TAP Portugal | 10 | 2026-07-24 |
| TAP209K | - | 7 | 2026-07-09 |
| TAP210 | - | 6 | 2026-07-10 |
| TAP028 | TAP Portugal | 6 | 2026-07-16 |
| TAP89WT | TAP Portugal | 5 | 2026-05-05 |
| TAP118 | - | 5 | 2026-07-02 |
| TAP093 | TAP Portugal | 5 | 2026-06-16 |
| TAP087 | - | 5 | 2026-07-11 |
| TAP082 | - | 5 | 2026-07-12 |
| TAP077 | TAP Portugal | 5 | 2026-06-15 |
| TAP029 | TAP Portugal | 5 | 2026-07-21 |
| TAP22MI | - | 4 | 2026-06-28 |
| TAP224 | - | 4 | 2026-06-28 |
| TAP094 | - | 4 | 2026-06-14 |
| TAP088 | TAP Portugal | 4 | 2026-07-21 |
| TAP078 | TAP Portugal | 4 | 2026-06-16 |
| TAP058 | TAP Portugal | 4 | 2026-07-25 |
| TAP057 | TAP Portugal | 4 | 2026-07-25 |
| TAP9022 | - | 3 | 2026-04-14 |
| TAP226 | - | 3 | 2026-07-06 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | TAP103 | LIS → CNF | Jul 26, 09:50 UTC | Jul 26, 16:15 UTC | 6h 25m |
| 2026-07-25 | TAP058 | BSB → LIS | Jul 25, 10:35 UTC | Jul 26, 05:10 UTC | 18h 35m |
| 2026-07-25 | TAP057 | LIS → BSB | Jul 25, 09:00 UTC | Jul 26, 05:10 UTC | 20h 10m |
| 2026-07-24 | TAP104 | CNF → LIS | Jul 24, 10:55 UTC | Jul 25, 05:20 UTC | 18h 25m |
| 2026-07-24 | TAP104 | CNF → LIS | Jul 24, 09:40 UTC | Jul 25, 05:20 UTC | 19h 40m |
| 2026-07-23 | TAP110 | FLN → LIS | Jul 23, 05:30 UTC | Jul 23, 15:30 UTC | 10h 0m |
| 2026-07-22 | TAP109 | LIS → FLN | Jul 22, 13:45 UTC | Jul 23, 00:00 UTC | 10h 15m |
| 2026-07-21 | TAP029 | LIS → SSA | Jul 21, 16:50 UTC | Jul 22, 04:25 UTC | 11h 35m |
| 2026-07-21 | TAP088 | GRU → LIS | Jul 21, 00:00 UTC | Jul 21, 09:00 UTC | 9h 0m |
| 2026-07-20 | TAP089 | LIS → GRU | Jul 20, 12:10 UTC | Jul 20, 21:55 UTC | 9h 45m |
| 2026-07-19 | TAP088 | GRU → LIS | Jul 19, 23:55 UTC | Jul 20, 09:05 UTC | 9h 10m |
| 2026-07-19 | TAP089 | LIS → GRU | Jul 19, 11:35 UTC | Jul 19, 21:20 UTC | 9h 45m |
| 2026-07-18 | TAP296 | - | Jul 18, 22:15 UTC | Jul 19, 05:35 UTC | 7h 20m |
| 2026-07-18 | TAP295 | - | Jul 18, 13:15 UTC | Jul 18, 20:05 UTC | 6h 50m |
| 2026-07-18 | TAP204A | - | Jul 18, 03:30 UTC | Jul 18, 09:45 UTC | 6h 15m |
| 2026-07-17 | TAP203 | LIS → EWR | Jul 17, 17:25 UTC | Jul 18, 00:45 UTC | 7h 20m |
| 2026-07-16 | TAP028 | FOR → LIS | Jul 16, 16:49 UTC | Jul 17, 10:25 UTC | 17h 35m |
| 2026-07-15 | TAP028 | LIS → LIS | Jul 15, 17:05 UTC | Jul 16, 10:35 UTC | 17h 30m |
| 2026-07-15 | TAP084 | - | Jul 15, 04:05 UTC | Jul 15, 13:30 UTC | 9h 25m |
| 2026-07-14 | TAP083 | - | Jul 14, 16:30 UTC | Jul 15, 02:20 UTC | 9h 49m |
| 2026-07-13 | TAP23SL | SFO → LIS | Jul 13, 23:55 UTC | Jul 14, 10:10 UTC | 10h 15m |
| 2026-07-13 | TAP237M | LIS → SFO | Jul 13, 08:50 UTC | Jul 13, 20:20 UTC | 11h 30m |
| 2026-07-12 | TAP082 | - | Jul 12, 18:35 UTC | Jul 13, 03:50 UTC | 9h 15m |
| 2026-07-11 | TAP087 | - | Jul 11, 23:15 UTC | Jul 12, 09:30 UTC | 10h 15m |
| 2026-07-10 | TAP244 | - | Jul 10, 23:20 UTC | Jul 11, 06:35 UTC | 7h 15m |
| 2026-07-10 | TAP243U | LIS → ORD | Jul 10, 11:55 UTC | Jul 10, 20:30 UTC | 8h 35m |
| 2026-07-10 | TAP210 | JFK → LIS | Jul 10, 03:25 UTC | Jul 10, 09:45 UTC | 6h 20m |
| 2026-07-09 | TAP209K | LIS → JFK | Jul 9, 16:50 UTC | Jul 10, 00:05 UTC | 7h 15m |
| 2026-07-08 | TAP029 | LIS → LIS | Jul 8, 17:15 UTC | Jul 9, 10:35 UTC | 17h 20m |
| 2026-07-08 | TAP084 | - | Jul 8, 05:20 UTC | Jul 8, 14:35 UTC | 9h 15m |
| 2026-07-07 | TAP083 | - | Jul 7, 16:30 UTC | Jul 8, 02:20 UTC | 9h 50m |
| 2026-07-06 | TAP029 | LIS → LIS | Jul 6, 17:55 UTC | Jul 7, 11:20 UTC | 17h 25m |
| 2026-07-06 | TAP226 | - | Jul 6, 04:45 UTC | Jul 6, 12:40 UTC | 7h 55m |
| 2026-07-05 | TAP225V | - | Jul 5, 18:25 UTC | Jul 6, 02:35 UTC | 8h 10m |
| 2026-07-04 | TAP226 | - | Jul 4, 04:45 UTC | Jul 4, 12:50 UTC | 8h 5m |
| 2026-07-03 | TAP225V | LIS → MIA | Jul 3, 17:50 UTC | Jul 4, 01:50 UTC | 8h 0m |
| 2026-07-02 | TAP118 | - | Jul 2, 21:30 UTC | Jul 3, 11:30 UTC | 14h 0m |
| 2026-07-02 | TAP118 | LIS → LIS | Jul 2, 12:35 UTC | Jul 3, 11:30 UTC | 22h 55m |
| 2026-07-02 | TAP210 | JFK → LIS | Jul 2, 03:15 UTC | Jul 2, 09:45 UTC | 6h 30m |
| 2026-07-01 | TAP209K | LIS → JFK | Jul 1, 16:40 UTC | Jul 1, 23:40 UTC | 7h 0m |
| 2026-07-01 | TAP248 | - | Jul 1, 00:10 UTC | Jul 1, 10:20 UTC | 10h 10m |
| 2026-06-30 | TAP247 | - | Jun 30, 10:00 UTC | Jun 30, 21:35 UTC | 11h 35m |
| 2026-06-29 | TAP104 | - | Jun 29, 10:34 UTC | Jun 30, 05:40 UTC | 19h 6m |
| 2026-06-29 | TAP104 | LIS → LIS | Jun 29, 09:54 UTC | Jun 30, 05:40 UTC | 19h 46m |
| 2026-06-28 | TAP224 | - | Jun 28, 20:59 UTC | Jun 29, 04:45 UTC | 7h 45m |
| 2026-06-28 | TAP22MI | - | Jun 28, 09:50 UTC | Jun 28, 18:10 UTC | 8h 20m |
| 2026-06-27 | TAP058 | - | Jun 27, 15:39 UTC | Jun 28, 05:24 UTC | 13h 45m |
| 2026-06-27 | TAP058 | LIS → LIS | Jun 27, 09:19 UTC | Jun 28, 05:24 UTC | 20h 5m |
| 2026-06-26 | TAP074 | - | Jun 26, 18:49 UTC | Jun 27, 03:44 UTC | 8h 55m |
| 2026-06-25 | TAP075 | LIS → GIG | Jun 25, 22:49 UTC | Jun 26, 08:10 UTC | 9h 20m |
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 .