sensors Mode-S transponder
4952AC
ICAO 24-bit transponder address · allocated to Portugal
Currently assigned to CS-TUL · AIRBUS A-330-900
- Hex
- 4952AC
- Octal
- 22251254
- Decimal
- 4,805,292
- Country
- PT
- Tail
- CS-TUL
- Type
- A339
- Flights observed
- 219
- Distinct callsigns
- 20
- Country
- PT
- Last broadcast
- Jul 26, 21:05 UTC
Current position
Country allocation
The ICAO 24-bit address 4952AC 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 | 13 | 2026-07-25 |
| TAP89WT | - | 9 | 2026-07-18 |
| TAP22MI | - | 9 | 2026-06-26 |
| TAP224 | - | 9 | 2026-06-26 |
| TAP296 | - | 7 | 2026-07-24 |
| TAP248 | - | 7 | 2026-07-06 |
| TAP075 | - | 7 | 2026-07-15 |
| TAP074 | TAP Portugal | 7 | 2026-07-16 |
| TAP90EH | - | 6 | 2026-07-18 |
| TAP295 | - | 6 | 2026-07-24 |
| TAP282 | - | 6 | 2026-07-15 |
| TAP247 | - | 6 | 2026-07-05 |
| TAP226 | - | 6 | 2026-07-09 |
| TAP204A | - | 6 | 2026-07-19 |
| TAP203 | TAP Portugal | 6 | 2026-07-18 |
| TAP298 | - | 5 | 2026-07-21 |
| TAP297 | - | 5 | 2026-07-20 |
| TAP244 | TAP Portugal | 5 | 2026-05-16 |
| TAP089 | TAP Portugal | 5 | 2026-07-26 |
| TAP084 | TAP Portugal | 5 | 2026-06-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | TAP089 | LIS → GRU | Jul 26, 11:35 UTC | Jul 26, 21:05 UTC | 9h 30m |
| 2026-07-25 | TAP104 | CNF → LIS | Jul 25, 11:05 UTC | Jul 26, 05:25 UTC | 18h 20m |
| 2026-07-25 | TAP104 | CNF → LIS | Jul 25, 09:35 UTC | Jul 26, 05:25 UTC | 19h 50m |
| 2026-07-24 | TAP296 | - | Jul 24, 22:50 UTC | Jul 25, 06:05 UTC | 7h 15m |
| 2026-07-24 | TAP295 | - | Jul 24, 13:10 UTC | Jul 24, 20:20 UTC | 7h 10m |
| 2026-07-24 | TAP23SL | SFO → LIS | Jul 24, 00:30 UTC | Jul 24, 10:45 UTC | 10h 15m |
| 2026-07-23 | TAP237M | LIS → SFO | Jul 23, 09:40 UTC | Jul 23, 21:25 UTC | 11h 45m |
| 2026-07-22 | TAP082 | GRU → LIS | Jul 22, 18:50 UTC | Jul 23, 03:55 UTC | 9h 5m |
| 2026-07-21 | TAP087 | LIS → GRU | Jul 21, 23:10 UTC | Jul 22, 01:00 UTC | 1h 50m |
| 2026-07-21 | TAP298 | - | Jul 21, 09:55 UTC | Jul 21, 17:00 UTC | 7h 5m |
| 2026-07-20 | TAP297 | - | Jul 20, 22:50 UTC | Jul 21, 05:55 UTC | 7h 5m |
| 2026-07-20 | TAP298 | - | Jul 20, 09:20 UTC | Jul 20, 16:30 UTC | 7h 10m |
| 2026-07-19 | TAP297 | - | Jul 19, 22:50 UTC | Jul 20, 06:00 UTC | 7h 10m |
| 2026-07-19 | TAP1692 | FNC → LIS | Jul 19, 19:00 UTC | Jul 19, 20:15 UTC | 1h 15m |
| 2026-07-19 | TAP91SR | LIS → FNC | Jul 19, 16:15 UTC | Jul 19, 17:45 UTC | 1h 30m |
| 2026-07-19 | TAP204A | - | Jul 19, 05:20 UTC | Jul 19, 11:30 UTC | 6h 10m |
| 2026-07-18 | TAP203 | LIS → EWR | Jul 18, 17:50 UTC | Jul 19, 01:45 UTC | 7h 55m |
| 2026-07-18 | TAP90EH | FNC → LIS | Jul 18, 14:00 UTC | Jul 18, 15:25 UTC | 1h 25m |
| 2026-07-18 | TAP89WT | - | Jul 18, 12:25 UTC | Jul 18, 12:40 UTC | 15m |
| 2026-07-18 | TAP89WT | - | Jul 18, 11:05 UTC | Jul 18, 11:55 UTC | 50m |
| 2026-07-17 | TAP058 | - | Jul 17, 11:20 UTC | Jul 18, 06:05 UTC | 18h 46m |
| 2026-07-17 | TAP057 | LIS → LIS | Jul 17, 10:15 UTC | Jul 18, 06:05 UTC | 19h 51m |
| 2026-07-16 | TAP074 | GIG → LIS | Jul 16, 18:40 UTC | Jul 17, 03:34 UTC | 8h 55m |
| 2026-07-15 | TAP075 | - | Jul 15, 23:10 UTC | Jul 16, 08:30 UTC | 9h 20m |
| 2026-07-15 | TAP282 | - | Jul 15, 16:15 UTC | Jul 15, 17:50 UTC | 1h 35m |
| 2026-07-14 | TAP282 | LIS → LIS | Jul 14, 19:25 UTC | Jul 15, 17:50 UTC | 22h 24m |
| 2026-07-12 | TAP074 | - | Jul 12, 18:50 UTC | Jul 13, 03:50 UTC | 9h 0m |
| 2026-07-11 | TAP075 | - | Jul 11, 23:05 UTC | Jul 12, 08:50 UTC | 9h 45m |
| 2026-07-11 | TAP90EH | FNC → LIS | Jul 11, 13:30 UTC | Jul 11, 14:55 UTC | 1h 25m |
| 2026-07-11 | TAP89WT | LIS → FNC | Jul 11, 10:55 UTC | Jul 11, 12:20 UTC | 1h 25m |
| 2026-07-10 | TAP104 | - | Jul 10, 11:05 UTC | Jul 11, 05:05 UTC | 18h 0m |
| 2026-07-10 | TAP104 | LIS → LIS | Jul 10, 09:40 UTC | Jul 11, 05:05 UTC | 19h 25m |
| 2026-07-09 | TAP226 | - | Jul 9, 08:10 UTC | Jul 9, 16:15 UTC | 8h 5m |
| 2026-07-08 | TAP225V | - | Jul 8, 18:45 UTC | Jul 9, 03:05 UTC | 8h 20m |
| 2026-07-08 | TAP070 | GIG → LIS | Jul 8, 07:25 UTC | Jul 8, 16:25 UTC | 9h 0m |
| 2026-07-07 | TAP071 | LIS → GIG | Jul 7, 18:15 UTC | Jul 8, 03:35 UTC | 9h 20m |
| 2026-07-06 | TAP118 | - | Jul 6, 20:45 UTC | Jul 7, 14:25 UTC | 17h 40m |
| 2026-07-06 | TAP118 | - | Jul 6, 15:05 UTC | Jul 7, 14:25 UTC | 23h 20m |
| 2026-07-06 | TAP117 | - | Jul 6, 14:15 UTC | Jul 7, 13:00 UTC | 22h 45m |
| 2026-07-06 | TAP248 | - | Jul 6, 00:30 UTC | Jul 6, 10:55 UTC | 10h 25m |
| 2026-07-05 | TAP247 | LIS → LAX | Jul 5, 08:25 UTC | Jul 5, 19:40 UTC | 11h 15m |
| 2026-07-04 | TAP104 | - | Jul 4, 11:20 UTC | Jul 5, 05:30 UTC | 18h 10m |
| 2026-07-04 | TAP104 | LIS → LIS | Jul 4, 10:10 UTC | Jul 5, 05:30 UTC | 19h 20m |
| 2026-07-03 | TAP082 | - | Jul 3, 19:00 UTC | Jul 4, 04:00 UTC | 9h 0m |
| 2026-07-02 | TAP087 | - | Jul 2, 23:40 UTC | Jul 3, 09:15 UTC | 9h 35m |
| 2026-07-02 | TAP204A | EWR → LIS | Jul 2, 03:35 UTC | Jul 2, 10:05 UTC | 6h 30m |
| 2026-07-01 | TAP203 | LIS → EWR | Jul 1, 17:40 UTC | Jul 2, 00:55 UTC | 7h 15m |
| 2026-07-01 | TAP204A | - | Jul 1, 03:50 UTC | Jul 1, 10:25 UTC | 6h 35m |
| 2026-06-30 | TAP203 | - | Jun 30, 18:20 UTC | Jul 1, 01:25 UTC | 7h 5m |
| 2026-06-30 | TAP90EH | FNC → LIS | Jun 30, 14:30 UTC | Jun 30, 15:55 UTC | 1h 25m |
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-TUL page for operator, model, and routing details .