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
- 137
- Distinct callsigns
- 20
- Country
- PT
- Last broadcast
- 5h 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 |
|---|---|---|---|
| TAP104 | - | 8 | 2026-06-29 |
| TAP209K | - | 7 | 2026-07-09 |
| TAP210 | - | 6 | 2026-07-10 |
| 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 |
| TAP22MI | - | 4 | 2026-06-28 |
| TAP224 | - | 4 | 2026-06-28 |
| TAP094 | - | 4 | 2026-06-14 |
| TAP078 | TAP Portugal | 4 | 2026-06-16 |
| TAP029 | - | 4 | 2026-07-08 |
| TAP028 | TAP Portugal | 4 | 2026-04-13 |
| TAP9022 | - | 3 | 2026-04-14 |
| TAP226 | - | 3 | 2026-07-06 |
| TAP225V | - | 3 | 2026-07-05 |
| TAP074 | - | 3 | 2026-06-26 |
| TAP058 | - | 3 | 2026-06-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 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 |
| 2026-06-18 | TAP104 | - | Jun 18, 10:35 UTC | Jun 19, 05:59 UTC | 19h 24m |
| 2026-06-18 | TAP104 | LIS → LIS | Jun 18, 09:40 UTC | Jun 19, 05:59 UTC | 20h 19m |
| 2026-06-17 | TAP244 | - | Jun 17, 23:55 UTC | Jun 18, 07:00 UTC | 7h 5m |
| 2026-06-17 | TAP243U | LIS → ORD | Jun 17, 12:10 UTC | Jun 17, 20:25 UTC | 8h 15m |
| 2026-06-17 | TAP088 | - | Jun 17, 00:30 UTC | Jun 17, 09:30 UTC | 9h 0m |
| 2026-06-16 | TAP093 | OPO → GRU | Jun 16, 12:30 UTC | Jun 16, 22:30 UTC | 10h 1m |
| 2026-06-16 | TAP078 | GIG → OPO | Jun 16, 00:35 UTC | Jun 16, 10:00 UTC | 9h 25m |
| 2026-06-15 | TAP077 | OPO → GIG | Jun 15, 12:30 UTC | Jun 15, 22:20 UTC | 9h 50m |
| 2026-06-14 | TAP294 | - | Jun 14, 22:30 UTC | Jun 15, 06:04 UTC | 7h 34m |
| 2026-06-14 | TAP293 | - | Jun 14, 12:45 UTC | Jun 14, 19:50 UTC | 7h 5m |
| 2026-06-14 | TAP094 | - | Jun 14, 01:00 UTC | Jun 14, 10:30 UTC | 9h 31m |
| 2026-06-13 | TAP093 | OPO → GRU | Jun 13, 13:00 UTC | Jun 13, 23:05 UTC | 10h 5m |
| 2026-06-13 | TAP078 | GIG → OPO | Jun 13, 01:00 UTC | Jun 13, 10:30 UTC | 9h 29m |
| 2026-06-12 | TAP077 | OPO → GIG | Jun 12, 22:30 UTC | Jun 12, 22:45 UTC | 15m |
| 2026-06-12 | TAP077 | OPO → GIG | Jun 12, 13:05 UTC | Jun 12, 21:50 UTC | 8h 45m |
| 2026-06-12 | TAP094 | GRU → OPO | Jun 12, 00:50 UTC | Jun 12, 10:20 UTC | 9h 30m |
| 2026-06-11 | TAP089 | LIS → GRU | Jun 11, 12:45 UTC | Jun 11, 22:30 UTC | 9h 45m |
| 2026-06-11 | TAP210 | JFK → LIS | Jun 11, 02:40 UTC | Jun 11, 09:25 UTC | 6h 45m |
| 2026-06-10 | TAP209K | LIS → JFK | Jun 10, 16:35 UTC | Jun 10, 23:35 UTC | 7h 0m |
| 2026-06-10 | TAP248 | LIS → ALG | Jun 10, 00:10 UTC | Jun 10, 10:40 UTC | 10h 30m |
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 .