sensors Mode-S transponder
4952A7
ICAO 24-bit transponder address · allocated to Portugal
Currently assigned to CS-TUG · AIRBUS A-330-900
- Hex
- 4952A7
- Octal
- 22251247
- Decimal
- 4,805,287
- Country
- PT
- Tail
- CS-TUG
- Type
- A339
- Flights observed
- 101
- Distinct callsigns
- 20
- Country
- PT
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 4952A7 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 |
|---|---|---|---|
| TAP237M | TAP Portugal | 7 | 2026-05-22 |
| TAP088 | TAP Portugal | 6 | 2026-05-01 |
| TAP89WT | TAP Portugal | 5 | 2026-05-17 |
| TAP236 | TAP Portugal | 5 | 2026-05-23 |
| TAP104 | TAP Portugal | 4 | 2026-05-18 |
| TAP075 | TAP Portugal | 4 | 2026-05-10 |
| TAP058 | TAP Portugal | 4 | 2026-05-07 |
| TAP036 | TAP Portugal | 4 | 2026-05-22 |
| TAP035 | TAP Portugal | 4 | 2026-05-21 |
| TAP90EH | TAP Portugal | 3 | 2026-05-17 |
| TAP294 | - | 3 | 2026-04-13 |
| TAP22MI | TAP Portugal | 3 | 2026-05-24 |
| TAP224 | TAP Portugal | 3 | 2026-05-24 |
| TAP093 | - | 3 | 2026-04-14 |
| TAP077 | - | 3 | 2026-04-13 |
| TAP073 | TAP Portugal | 3 | 2026-05-12 |
| TAP072 | TAP Portugal | 3 | 2026-05-12 |
| TAP23SL | TAP Portugal | 2 | 2026-05-20 |
| TAP210 | TAP Portugal | 2 | 2026-05-30 |
| TAP209K | TAP Portugal | 2 | 2026-05-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | TAP210 | JFK → LIS | May 30, 02:55 UTC | May 30, 03:45 UTC | 50m |
| 2026-05-29 | TAP209K | LIS → JFK | May 29, 16:35 UTC | May 29, 23:45 UTC | 7h 10m |
| 2026-05-28 | TAP029 | LIS → SSA | May 28, 16:55 UTC | May 29, 10:30 UTC | 17h 35m |
| 2026-05-27 | TAP029 | LIS → SSA | May 27, 17:55 UTC | May 28, 11:35 UTC | 17h 40m |
| 2026-05-26 | TAP082 | GRU → LIS | May 26, 18:50 UTC | May 27, 03:50 UTC | 9h 0m |
| 2026-05-25 | TAP087 | LIS → GRU | May 25, 23:14 UTC | May 26, 09:19 UTC | 10h 5m |
| 2026-05-24 | TAP224 | MIA → LIS | May 24, 21:00 UTC | May 25, 04:40 UTC | 7h 40m |
| 2026-05-24 | TAP22MI | LIS → MIA | May 24, 10:15 UTC | May 24, 18:45 UTC | 8h 30m |
| 2026-05-23 | TAP236 | SFO → LIS | May 23, 04:00 UTC | May 23, 14:50 UTC | 10h 50m |
| 2026-05-22 | TAP237M | LIS → SFO | May 22, 11:50 UTC | May 22, 23:25 UTC | 11h 35m |
| 2026-05-22 | TAP036 | FOR → LIS | May 22, 02:15 UTC | May 22, 08:45 UTC | 6h 30m |
| 2026-05-21 | TAP035 | LIS → FOR | May 21, 17:10 UTC | May 22, 00:15 UTC | 7h 5m |
| 2026-05-20 | TAP028 | FOR → LIS | May 20, 17:00 UTC | May 21, 10:25 UTC | 17h 25m |
| 2026-05-20 | TAP23SL | SFO → LIS | May 20, 00:25 UTC | May 20, 10:30 UTC | 10h 6m |
| 2026-05-19 | TAP237M | LIS → SFO | May 19, 09:40 UTC | May 19, 21:35 UTC | 11h 55m |
| 2026-05-18 | TAP104 | CNF → LIS | May 18, 10:10 UTC | May 19, 05:30 UTC | 19h 19m |
| 2026-05-17 | TAP90EH | FNC → LIS | May 17, 14:10 UTC | May 17, 15:40 UTC | 1h 30m |
| 2026-05-17 | TAP89WT | LIS → FNC | May 17, 12:15 UTC | May 17, 12:40 UTC | 25m |
| 2026-05-17 | TAP89WT | LIS → FNC | May 17, 11:01 UTC | May 17, 11:35 UTC | 35m |
| 2026-05-17 | TAP036 | FOR → LIS | May 17, 02:30 UTC | May 17, 08:45 UTC | 6h 15m |
| 2026-05-16 | TAP035 | LIS → FOR | May 16, 17:20 UTC | May 17, 00:40 UTC | 7h 20m |
| 2026-05-16 | TAP90EH | FNC → LIS | May 16, 13:35 UTC | May 16, 14:55 UTC | 1h 20m |
| 2026-05-16 | TAP89WT | LIS → FNC | May 16, 10:50 UTC | May 16, 12:21 UTC | 1h 30m |
| 2026-05-15 | TAP082 | GRU → LIS | May 15, 18:35 UTC | May 16, 03:50 UTC | 9h 15m |
| 2026-05-14 | TAP087 | LIS → GRU | May 14, 23:15 UTC | May 15, 09:05 UTC | 9h 50m |
| 2026-05-14 | TAP226 | MIA → LIS | May 14, 08:05 UTC | May 14, 15:35 UTC | 7h 30m |
| 2026-05-13 | TAP225V | LIS → MIA | May 13, 18:30 UTC | May 14, 03:25 UTC | 8h 55m |
| 2026-05-13 | TAP90EH | FNC → LIS | May 13, 13:45 UTC | May 13, 15:10 UTC | 1h 25m |
| 2026-05-13 | TAP89WT | LIS → FNC | May 13, 12:10 UTC | May 13, 12:20 UTC | 10m |
| 2026-05-13 | TAP89WT | LIS → FNC | May 13, 10:45 UTC | May 13, 11:25 UTC | 40m |
| 2026-05-12 | TAP072 | GIG → LIS | May 12, 23:15 UTC | May 13, 07:45 UTC | 8h 30m |
| 2026-05-12 | TAP073 | LIS → GIG | May 12, 10:50 UTC | May 12, 20:55 UTC | 10h 5m |
| 2026-05-11 | TAP074 | GIG → LIS | May 11, 18:50 UTC | May 12, 03:35 UTC | 8h 45m |
| 2026-05-10 | TAP075 | LIS → GIG | May 10, 23:19 UTC | May 11, 09:00 UTC | 9h 41m |
| 2026-05-08 | TAP224 | MIA → LIS | May 8, 21:00 UTC | May 9, 04:35 UTC | 7h 35m |
| 2026-05-08 | TAP22MI | LIS → MIA | May 8, 09:54 UTC | May 8, 18:30 UTC | 8h 35m |
| 2026-05-07 | TAP058 | BSB → LIS | May 7, 17:15 UTC | May 8, 05:00 UTC | 11h 45m |
| 2026-05-07 | TAP057 | LIS → BSB | May 7, 08:55 UTC | May 7, 17:10 UTC | 8h 15m |
| 2026-05-06 | TAP058 | BSB → LIS | May 6, 11:50 UTC | May 7, 06:00 UTC | 18h 9m |
| 2026-05-06 | TAP057 | LIS → BSB | May 6, 10:30 UTC | May 7, 06:00 UTC | 19h 29m |
| 2026-05-05 | TAP104 | CNF → LIS | May 5, 09:50 UTC | May 6, 05:05 UTC | 19h 15m |
| 2026-05-05 | TAP103 | LIS → CNF | May 5, 09:15 UTC | May 6, 05:05 UTC | 19h 50m |
| 2026-05-04 | TAP104 | CNF → LIS | May 4, 09:50 UTC | May 5, 05:20 UTC | 19h 31m |
| 2026-05-03 | TAP224 | MIA → LIS | May 3, 21:39 UTC | May 4, 04:55 UTC | 7h 15m |
| 2026-05-03 | TAP22MI | LIS → MIA | May 3, 10:10 UTC | May 3, 19:00 UTC | 8h 50m |
| 2026-05-02 | TAP296 | - | May 2, 22:40 UTC | May 3, 06:10 UTC | 7h 29m |
| 2026-05-02 | TAP295 | - | May 2, 12:55 UTC | May 2, 20:00 UTC | 7h 5m |
| 2026-05-01 | TAP088 | GRU → LIS | May 1, 23:55 UTC | May 2, 09:05 UTC | 9h 10m |
| 2026-05-01 | TAP089 | LIS → GRU | May 1, 12:40 UTC | May 1, 22:15 UTC | 9h 35m |
| 2026-05-01 | TAP072 | GIG → LIS | May 1, 00:15 UTC | May 1, 09:00 UTC | 8h 46m |
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-TUG page for operator, model, and routing details .