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
- 191
- Distinct callsigns
- 20
- Country
- PT
- Last broadcast
- Jul 26, 19:00 UTC
Current 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 | - | 13 | 2026-07-11 |
| TAP104 | - | 12 | 2026-07-09 |
| TAP117 | TAP Portugal | 10 | 2026-07-21 |
| TAP298 | - | 9 | 2026-07-14 |
| TAP297 | - | 9 | 2026-07-13 |
| TAP028 | - | 9 | 2026-07-05 |
| TAP083 | - | 8 | 2026-07-03 |
| TAP075 | - | 8 | 2026-07-14 |
| TAP074 | - | 8 | 2026-07-15 |
| TAP084 | - | 7 | 2026-07-04 |
| TAP282 | TAP Portugal | 6 | 2026-06-10 |
| TAP248 | - | 6 | 2026-07-11 |
| TAP029 | TAP Portugal | 6 | 2026-07-26 |
| TAP247 | - | 5 | 2026-07-10 |
| TAP244 | TAP Portugal | 4 | 2026-07-24 |
| TAP243U | TAP Portugal | 4 | 2026-07-24 |
| TAP23SL | - | 4 | 2026-07-16 |
| TAP237M | - | 4 | 2026-07-16 |
| TAP22MI | TAP Portugal | 4 | 2026-07-25 |
| TAP224 | TAP Portugal | 4 | 2026-07-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | TAP029 | LIS → SSA | Jul 26, 17:20 UTC | Jul 26, 19:00 UTC | 1h 40m |
| 2026-07-25 | TAP224 | MIA → LIS | Jul 25, 20:35 UTC | Jul 26, 04:30 UTC | 7h 55m |
| 2026-07-25 | TAP22MI | LIS → MIA | Jul 25, 09:50 UTC | Jul 25, 17:55 UTC | 8h 5m |
| 2026-07-24 | TAP244 | LIS → RAK | Jul 24, 23:35 UTC | Jul 25, 07:20 UTC | 7h 45m |
| 2026-07-24 | TAP243U | LIS → ORD | Jul 24, 11:55 UTC | Jul 24, 20:05 UTC | 8h 10m |
| 2026-07-21 | TAP117 | LIS → POA | Jul 21, 20:35 UTC | Jul 22, 13:25 UTC | 16h 50m |
| 2026-07-21 | TAP117 | LIS → POA | Jul 21, 14:35 UTC | Jul 22, 13:25 UTC | 22h 50m |
| 2026-07-21 | TAP117 | LIS → POA | Jul 21, 14:05 UTC | Jul 22, 04:50 UTC | 14h 45m |
| 2026-07-20 | TAP072 | GIG → LIS | Jul 20, 23:30 UTC | Jul 21, 08:25 UTC | 8h 54m |
| 2026-07-20 | TAP073 | LIS → GIG | Jul 20, 11:05 UTC | Jul 20, 20:45 UTC | 9h 40m |
| 2026-07-19 | TAP072 | GIG → LIS | Jul 19, 23:15 UTC | Jul 20, 08:15 UTC | 9h 0m |
| 2026-07-19 | TAP073 | LIS → GIG | Jul 19, 08:40 UTC | Jul 19, 18:10 UTC | 9h 30m |
| 2026-07-18 | TAP058 | BSB → LIS | Jul 18, 10:35 UTC | Jul 19, 04:50 UTC | 18h 15m |
| 2026-07-18 | TAP057 | LIS → LIS | Jul 18, 09:05 UTC | Jul 19, 04:50 UTC | 19h 45m |
| 2026-07-17 | TAP296 | - | Jul 17, 22:49 UTC | Jul 18, 06:00 UTC | 7h 11m |
| 2026-07-17 | TAP295 | - | Jul 17, 13:05 UTC | Jul 17, 20:10 UTC | 7h 5m |
| 2026-07-16 | TAP23SL | SFO → LIS | Jul 16, 23:59 UTC | Jul 17, 10:40 UTC | 10h 40m |
| 2026-07-16 | TAP237M | LIS → SFO | Jul 16, 09:25 UTC | Jul 16, 20:49 UTC | 11h 25m |
| 2026-07-15 | TAP074 | - | Jul 15, 18:55 UTC | Jul 16, 04:00 UTC | 9h 5m |
| 2026-07-14 | TAP075 | - | Jul 14, 23:05 UTC | Jul 15, 08:30 UTC | 9h 25m |
| 2026-07-14 | TAP298 | - | Jul 14, 09:25 UTC | Jul 14, 16:40 UTC | 7h 15m |
| 2026-07-13 | TAP297 | - | Jul 13, 22:40 UTC | Jul 14, 05:45 UTC | 7h 5m |
| 2026-07-13 | TAP298 | - | Jul 13, 09:35 UTC | Jul 13, 16:50 UTC | 7h 15m |
| 2026-07-12 | TAP297 | - | Jul 12, 23:05 UTC | Jul 13, 06:10 UTC | 7h 5m |
| 2026-07-11 | TAP118 | - | Jul 11, 21:25 UTC | Jul 12, 15:01 UTC | 17h 35m |
| 2026-07-11 | TAP118 | - | Jul 11, 16:35 UTC | Jul 12, 15:01 UTC | 22h 25m |
| 2026-07-11 | TAP117 | - | Jul 11, 14:50 UTC | Jul 12, 14:30 UTC | 23h 40m |
| 2026-07-11 | TAP248 | LAX → LIS | Jul 11, 00:05 UTC | Jul 11, 10:20 UTC | 10h 15m |
| 2026-07-10 | TAP247 | LIS → LAX | Jul 10, 09:40 UTC | Jul 10, 21:00 UTC | 11h 20m |
| 2026-07-09 | TAP104 | - | Jul 9, 10:45 UTC | Jul 10, 05:10 UTC | 18h 25m |
| 2026-07-09 | TAP104 | LIS → LIS | Jul 9, 09:40 UTC | Jul 10, 05:10 UTC | 19h 30m |
| 2026-07-08 | TAP082 | - | Jul 8, 18:40 UTC | Jul 9, 03:55 UTC | 9h 15m |
| 2026-07-08 | TAP087 | LIS → GRU | Jul 8, 01:35 UTC | Jul 8, 11:25 UTC | 9h 50m |
| 2026-07-07 | TAP204A | EWR → LIS | Jul 7, 03:40 UTC | Jul 7, 10:05 UTC | 6h 25m |
| 2026-07-06 | TAP203 | LIS → EWR | Jul 6, 17:30 UTC | Jul 7, 00:50 UTC | 7h 20m |
| 2026-07-05 | TAP028 | LIS → LIS | Jul 5, 19:15 UTC | Jul 6, 12:30 UTC | 17h 15m |
| 2026-07-05 | TAP204A | - | Jul 5, 04:20 UTC | Jul 5, 10:30 UTC | 6h 10m |
| 2026-07-04 | TAP203 | LIS → EWR | Jul 4, 17:40 UTC | Jul 5, 01:15 UTC | 7h 35m |
| 2026-07-04 | TAP084 | - | Jul 4, 05:25 UTC | Jul 4, 14:55 UTC | 9h 30m |
| 2026-07-03 | TAP083 | - | Jul 3, 18:05 UTC | Jul 4, 02:40 UTC | 8h 35m |
| 2026-07-03 | TAP083 | - | Jul 3, 16:55 UTC | Jul 3, 17:35 UTC | 40m |
| 2026-07-03 | TAP084 | - | Jul 3, 04:35 UTC | Jul 3, 13:50 UTC | 9h 15m |
| 2026-07-02 | TAP083 | LIS → GRU | Jul 2, 17:00 UTC | Jul 3, 02:50 UTC | 9h 50m |
| 2026-07-01 | TAP029 | LIS → LIS | Jul 1, 17:25 UTC | Jul 2, 10:55 UTC | 17h 30m |
| 2026-07-01 | TAP084 | - | Jul 1, 04:00 UTC | Jul 1, 13:20 UTC | 9h 20m |
| 2026-06-30 | TAP083 | - | Jun 30, 16:35 UTC | Jul 1, 02:10 UTC | 9h 35m |
| 2026-06-30 | TAP084 | - | Jun 30, 04:20 UTC | Jun 30, 13:30 UTC | 9h 10m |
| 2026-06-29 | TAP083 | - | Jun 29, 16:35 UTC | Jun 30, 02:15 UTC | 9h 41m |
| 2026-06-29 | TAP248 | - | Jun 29, 00:10 UTC | Jun 29, 10:20 UTC | 10h 10m |
| 2026-06-28 | TAP247 | - | Jun 28, 09:20 UTC | Jun 28, 21:24 UTC | 12h 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-TUR page for operator, model, and routing details .