sensors Mode-S transponder
4952B2
ICAO 24-bit transponder address · allocated to Portugal
Currently assigned to CS-TUR · AIRBUS A-330-900
- Hex
- 4952B2
- Octal
- 22251262
- Decimal
- 4,805,298
- Country
- PT
- Tail
- CS-TUR
- Type
- A339
- Flights observed
- 96
- Distinct callsigns
- 20
- Country
- PT
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 4952B2 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 |
|---|---|---|---|
| TAP118 | TAP Portugal | 9 | 2026-05-16 |
| TAP104 | TAP Portugal | 8 | 2026-05-26 |
| TAP028 | TAP Portugal | 7 | 2026-05-12 |
| TAP117 | TAP Portugal | 5 | 2026-04-15 |
| TAP298 | - | 4 | 2026-04-17 |
| TAP297 | - | 4 | 2026-04-17 |
| TAP075 | TAP Portugal | 4 | 2026-05-29 |
| TAP244 | TAP Portugal | 3 | 2026-05-08 |
| TAP243U | TAP Portugal | 3 | 2026-05-08 |
| TAP210 | TAP Portugal | 3 | 2026-05-24 |
| TAP209K | TAP Portugal | 3 | 2026-05-23 |
| TAP103 | TAP Portugal | 3 | 2026-04-27 |
| TAP074 | TAP Portugal | 3 | 2026-05-25 |
| TAP029 | TAP Portugal | 3 | 2026-05-06 |
| TAP282 | TAP Portugal | 2 | 2026-04-18 |
| TAP248 | TAP Portugal | 2 | 2026-05-20 |
| TAP23SL | TAP Portugal | 2 | 2026-05-06 |
| TAP237M | TAP Portugal | 2 | 2026-05-05 |
| TAP22MI | TAP Portugal | 2 | 2026-05-27 |
| TAP226 | TAP Portugal | 2 | 2026-05-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | TAP075 | LIS → GIG | May 29, 22:45 UTC | May 30, 00:30 UTC | 1h 45m |
| 2026-05-29 | TAP250 | LAX → LIS | May 29, 05:15 UTC | May 29, 15:35 UTC | 10h 20m |
| 2026-05-28 | TAP249 | - | May 28, 15:15 UTC | May 29, 02:20 UTC | 11h 5m |
| 2026-05-27 | TAP224 | MIA → LIS | May 27, 20:45 UTC | May 28, 04:15 UTC | 7h 30m |
| 2026-05-27 | TAP22MI | LIS → MIA | May 27, 09:50 UTC | May 27, 18:20 UTC | 8h 30m |
| 2026-05-26 | TAP104 | CNF → LIS | May 26, 21:49 UTC | May 27, 05:45 UTC | 7h 55m |
| 2026-05-26 | TAP104 | CNF → LIS | May 26, 08:34 UTC | May 27, 05:45 UTC | 21h 10m |
| 2026-05-25 | TAP074 | GIG → LIS | May 25, 18:45 UTC | May 26, 03:25 UTC | 8h 39m |
| 2026-05-24 | TAP075 | LIS → GIG | May 24, 23:15 UTC | May 25, 08:55 UTC | 9h 40m |
| 2026-05-24 | TAP210 | JFK → LIS | May 24, 03:20 UTC | May 24, 09:30 UTC | 6h 10m |
| 2026-05-23 | TAP209K | LIS → JFK | May 23, 16:40 UTC | May 24, 00:00 UTC | 7h 21m |
| 2026-05-23 | TAP226 | MIA → LIS | May 23, 04:40 UTC | May 23, 12:15 UTC | 7h 35m |
| 2026-05-22 | TAP225V | LIS → MIA | May 22, 17:20 UTC | May 23, 01:45 UTC | 8h 25m |
| 2026-05-22 | TAP210 | JFK → LIS | May 22, 04:55 UTC | May 22, 10:45 UTC | 5h 50m |
| 2026-05-22 | TAP9253 | LIS → OPO | May 22, 01:45 UTC | May 22, 02:35 UTC | 50m |
| 2026-05-20 | TAP209K | LIS → JFK | May 20, 16:35 UTC | May 21, 00:15 UTC | 7h 40m |
| 2026-05-20 | TAP248 | LIS → ALG | May 20, 10:00 UTC | May 20, 10:35 UTC | 35m |
| 2026-05-20 | TAP248 | LIS → ALG | May 20, 00:40 UTC | May 20, 05:45 UTC | 5h 6m |
| 2026-05-19 | TAP247 | LIS → LAX | May 19, 09:50 UTC | May 19, 22:15 UTC | 12h 25m |
| 2026-05-18 | TAP082 | GRU → LIS | May 18, 18:55 UTC | May 19, 04:05 UTC | 9h 10m |
| 2026-05-17 | TAP087 | LIS → GRU | May 17, 23:35 UTC | May 18, 09:20 UTC | 9h 45m |
| 2026-05-16 | TAP118 | POA → LIS | May 16, 22:25 UTC | May 17, 14:50 UTC | 16h 25m |
| 2026-05-16 | TAP118 | POA → LIS | May 16, 15:45 UTC | May 17, 14:30 UTC | 22h 45m |
| 2026-05-16 | TAP226 | MIA → LIS | May 16, 04:25 UTC | May 16, 11:46 UTC | 7h 21m |
| 2026-05-15 | TAP225V | LIS → MIA | May 15, 16:50 UTC | May 16, 01:20 UTC | 8h 30m |
| 2026-05-14 | TAP118 | POA → LIS | May 14, 19:45 UTC | May 15, 11:55 UTC | 16h 10m |
| 2026-05-14 | TAP118 | POA → LIS | May 14, 13:05 UTC | May 15, 11:55 UTC | 22h 50m |
| 2026-05-14 | TAP210 | JFK → LIS | May 14, 03:00 UTC | May 14, 09:10 UTC | 6h 10m |
| 2026-05-13 | TAP209K | LIS → JFK | May 13, 16:25 UTC | May 13, 23:30 UTC | 7h 5m |
| 2026-05-12 | TAP028 | FOR → LIS | May 12, 17:00 UTC | May 13, 10:45 UTC | 17h 45m |
| 2026-05-11 | TAP028 | FOR → LIS | May 11, 17:05 UTC | May 12, 10:40 UTC | 17h 35m |
| 2026-05-11 | TAP084 | GRU → LIS | May 11, 04:50 UTC | May 11, 13:55 UTC | 9h 5m |
| 2026-05-10 | TAP083 | LIS → GRU | May 10, 16:59 UTC | May 11, 03:05 UTC | 10h 5m |
| 2026-05-09 | TAP057 | LIS → BSB | May 9, 10:35 UTC | May 10, 04:39 UTC | 18h 5m |
| 2026-05-09 | TAP057 | LIS → BSB | May 9, 09:15 UTC | May 10, 04:39 UTC | 19h 25m |
| 2026-05-08 | TAP244 | LIS → RAK | May 8, 23:40 UTC | May 9, 07:05 UTC | 7h 25m |
| 2026-05-08 | TAP243U | LIS → ORD | May 8, 12:00 UTC | May 8, 20:25 UTC | 8h 25m |
| 2026-05-07 | TAP011 | LIS → REC | May 7, 16:45 UTC | May 8, 08:59 UTC | 16h 14m |
| 2026-05-06 | TAP029 | LIS → SSA | May 6, 17:00 UTC | May 7, 10:35 UTC | 17h 35m |
| 2026-05-06 | TAP23SL | SFO → LIS | May 6, 00:15 UTC | May 6, 10:40 UTC | 10h 25m |
| 2026-05-05 | TAP237M | LIS → SFO | May 5, 09:40 UTC | May 5, 20:45 UTC | 11h 5m |
| 2026-05-04 | TAP058 | BSB → LIS | May 4, 11:05 UTC | May 5, 05:15 UTC | 18h 11m |
| 2026-05-04 | TAP058 | BSB → LIS | May 4, 09:40 UTC | May 5, 05:15 UTC | 19h 36m |
| 2026-05-03 | TAP244 | LIS → RAK | May 3, 23:20 UTC | May 4, 06:40 UTC | 7h 20m |
| 2026-05-03 | TAP243U | LIS → ORD | May 3, 12:15 UTC | May 3, 20:40 UTC | 8h 25m |
| 2026-05-02 | TAP244 | LIS → RAK | May 2, 23:55 UTC | May 3, 07:25 UTC | 7h 29m |
| 2026-05-02 | TAP243U | LIS → ORD | May 2, 12:25 UTC | May 2, 20:25 UTC | 8h 0m |
| 2026-05-01 | TAP012 | REC → LIS | May 1, 16:50 UTC | May 2, 08:45 UTC | 15h 55m |
| 2026-04-30 | TAP028 | FOR → LIS | Apr 30, 17:05 UTC | May 1, 10:30 UTC | 17h 25m |
| 2026-04-30 | TAP088 | GRU → LIS | Apr 30, 06:05 UTC | Apr 30, 14:05 UTC | 8h 0m |
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-TUR page for operator, model, and routing details .