sensors Mode-S transponder
4952B1
ICAO 24-bit transponder address · allocated to Portugal
Currently assigned to CS-TUQ · AIRBUS A-330-900
- Hex
- 4952B1
- Octal
- 22251261
- Decimal
- 4,805,297
- Country
- PT
- Tail
- CS-TUQ
- Type
- A339
- Flights observed
- 83
- Distinct callsigns
- 20
- Country
- PT
- Last broadcast
- 21h ago
Last known position
Country allocation
The ICAO 24-bit address 4952B1 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 |
|---|---|---|---|
| TAP075 | TAP Portugal | 13 | 2026-05-27 |
| TAP082 | TAP Portugal | 12 | 2026-05-19 |
| TAP087 | TAP Portugal | 9 | 2026-05-18 |
| TAP074 | TAP Portugal | 9 | 2026-05-28 |
| TAP104 | TAP Portugal | 4 | 2026-05-16 |
| TAP22MI | TAP Portugal | 3 | 2026-05-17 |
| TAP083 | TAP Portugal | 3 | 2026-05-25 |
| TAP057 | TAP Portugal | 3 | 2026-05-20 |
| TAP91SR | TAP Portugal | 2 | 2026-04-23 |
| TAP224 | TAP Portugal | 2 | 2026-05-17 |
| TAP084 | TAP Portugal | 2 | 2026-05-25 |
| TAP058 | TAP Portugal | 2 | 2026-05-02 |
| TAP029 | TAP Portugal | 2 | 2026-05-10 |
| TAP298 | - | 1 | 2026-05-27 |
| TAP297 | - | 1 | 2026-05-26 |
| TAP296 | - | 1 | 2026-05-15 |
| TAP295 | - | 1 | 2026-05-15 |
| TAP248 | TAP Portugal | 1 | 2026-04-22 |
| TAP247 | TAP Portugal | 1 | 2026-04-21 |
| TAP237M | TAP Portugal | 1 | 2026-05-21 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-28 | TAP074 | GIG → LIS | May 28, 18:50 UTC | May 29, 03:45 UTC | 8h 55m |
| 2026-05-27 | TAP075 | LIS → GIG | May 27, 23:05 UTC | May 28, 08:15 UTC | 9h 10m |
| 2026-05-27 | TAP298 | - | May 27, 08:30 UTC | May 27, 16:35 UTC | 8h 5m |
| 2026-05-26 | TAP297 | - | May 26, 22:50 UTC | May 27, 05:45 UTC | 6h 55m |
| 2026-05-25 | TAP028 | FOR → LIS | May 25, 17:30 UTC | May 26, 11:00 UTC | 17h 29m |
| 2026-05-25 | TAP084 | GRU → LIS | May 25, 04:15 UTC | May 25, 13:20 UTC | 9h 5m |
| 2026-05-25 | TAP083 | LIS → GRU | May 25, 01:55 UTC | May 25, 02:10 UTC | 15m |
| 2026-05-24 | TAP083 | LIS → GRU | May 24, 16:25 UTC | May 24, 18:15 UTC | 1h 50m |
| 2026-05-23 | TAP074 | GIG → LIS | May 23, 18:55 UTC | May 24, 03:45 UTC | 8h 50m |
| 2026-05-22 | TAP075 | LIS → GIG | May 22, 23:55 UTC | May 23, 09:30 UTC | 9h 34m |
| 2026-05-22 | TAP236 | SFO → LIS | May 22, 03:15 UTC | May 22, 13:20 UTC | 10h 5m |
| 2026-05-21 | TAP237M | LIS → SFO | May 21, 11:45 UTC | May 21, 22:50 UTC | 11h 5m |
| 2026-05-20 | TAP057 | LIS → BSB | May 20, 10:20 UTC | May 21, 06:00 UTC | 19h 40m |
| 2026-05-19 | TAP082 | GRU → LIS | May 19, 18:50 UTC | May 20, 04:00 UTC | 9h 10m |
| 2026-05-18 | TAP087 | LIS → GRU | May 18, 22:50 UTC | May 19, 08:45 UTC | 9h 55m |
| 2026-05-17 | TAP224 | MIA → LIS | May 17, 21:45 UTC | May 18, 05:00 UTC | 7h 15m |
| 2026-05-17 | TAP22MI | LIS → MIA | May 17, 18:50 UTC | May 17, 19:15 UTC | 25m |
| 2026-05-17 | TAP22MI | LIS → MIA | May 17, 10:35 UTC | May 17, 17:05 UTC | 6h 30m |
| 2026-05-16 | TAP104 | CNF → LIS | May 16, 10:20 UTC | May 17, 05:45 UTC | 19h 25m |
| 2026-05-16 | TAP104 | CNF → LIS | May 16, 10:11 UTC | May 17, 05:45 UTC | 19h 35m |
| 2026-05-15 | TAP296 | - | May 15, 22:25 UTC | May 16, 05:35 UTC | 7h 10m |
| 2026-05-15 | TAP295 | - | May 15, 12:55 UTC | May 15, 20:05 UTC | 7h 9m |
| 2026-05-14 | TAP011 | LIS → REC | May 14, 16:45 UTC | May 15, 09:00 UTC | 16h 15m |
| 2026-05-13 | TAP082 | GRU → LIS | May 13, 18:50 UTC | May 14, 03:45 UTC | 8h 55m |
| 2026-05-12 | TAP087 | LIS → GRU | May 12, 23:15 UTC | May 13, 09:20 UTC | 10h 5m |
| 2026-05-10 | TAP029 | LIS → SSA | May 10, 17:10 UTC | May 11, 10:45 UTC | 17h 35m |
| 2026-05-09 | TAP072 | GIG → LIS | May 9, 23:35 UTC | May 10, 08:25 UTC | 8h 50m |
| 2026-05-09 | TAP073 | LIS → GIG | May 9, 11:10 UTC | May 9, 20:55 UTC | 9h 45m |
| 2026-05-08 | TAP074 | GIG → LIS | May 8, 18:55 UTC | May 9, 03:45 UTC | 8h 50m |
| 2026-05-07 | TAP075 | LIS → GIG | May 7, 23:14 UTC | May 8, 08:49 UTC | 9h 35m |
| 2026-05-06 | TAP074 | GIG → LIS | May 6, 19:00 UTC | May 7, 03:50 UTC | 8h 50m |
| 2026-05-06 | TAP075 | LIS → GIG | May 6, 08:30 UTC | May 6, 08:45 UTC | 15m |
| 2026-05-05 | TAP075 | LIS → GIG | May 5, 23:00 UTC | May 6, 07:40 UTC | 8h 40m |
| 2026-05-04 | TAP074 | GIG → LIS | May 4, 18:50 UTC | May 5, 03:20 UTC | 8h 30m |
| 2026-05-03 | TAP075 | LIS → GIG | May 3, 23:15 UTC | May 4, 08:45 UTC | 9h 30m |
| 2026-05-02 | TAP058 | BSB → LIS | May 2, 22:25 UTC | May 3, 05:15 UTC | 6h 49m |
| 2026-05-02 | TAP057 | LIS → BSB | May 2, 09:45 UTC | May 2, 22:20 UTC | 12h 35m |
| 2026-05-01 | TAP074 | GIG → LIS | May 1, 18:45 UTC | May 2, 03:30 UTC | 8h 45m |
| 2026-04-30 | TAP075 | LIS → GIG | Apr 30, 23:40 UTC | May 1, 09:20 UTC | 9h 40m |
| 2026-04-29 | TAP082 | GRU → LIS | Apr 29, 19:15 UTC | Apr 30, 04:20 UTC | 9h 4m |
| 2026-04-28 | TAP087 | LIS → GRU | Apr 28, 22:49 UTC | Apr 29, 08:34 UTC | 9h 45m |
| 2026-04-28 | TAP036 | FOR → LIS | Apr 28, 02:35 UTC | Apr 28, 09:10 UTC | 6h 35m |
| 2026-04-27 | TAP035 | LIS → FOR | Apr 27, 17:45 UTC | Apr 28, 00:35 UTC | 6h 50m |
| 2026-04-27 | TAP084 | GRU → LIS | Apr 27, 04:15 UTC | Apr 27, 13:40 UTC | 9h 25m |
| 2026-04-26 | TAP083 | LIS → GRU | Apr 26, 16:30 UTC | Apr 27, 01:55 UTC | 9h 25m |
| 2026-04-26 | TAP088 | GRU → LIS | Apr 26, 00:05 UTC | Apr 26, 09:15 UTC | 9h 10m |
| 2026-04-25 | TAP089 | LIS → GRU | Apr 25, 12:10 UTC | Apr 25, 21:30 UTC | 9h 20m |
| 2026-04-24 | TAP074 | GIG → LIS | Apr 24, 18:55 UTC | Apr 25, 03:55 UTC | 9h 0m |
| 2026-04-23 | TAP075 | LIS → GIG | Apr 23, 23:10 UTC | Apr 24, 08:35 UTC | 9h 25m |
| 2026-04-23 | TAP1692 | FNC → LIS | Apr 23, 18:55 UTC | Apr 23, 20:15 UTC | 1h 20m |
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-TUQ page for operator, model, and routing details .