sensors Mode-S transponder
4951EF
ICAO 24-bit transponder address · allocated to Portugal
Currently assigned to CS-TOO · AIRBUS A-330-200
- Hex
- 4951EF
- Octal
- 22250757
- Decimal
- 4,805,103
- Country
- PT
- Tail
- CS-TOO
- Type
- A332
- Flights observed
- 108
- Distinct callsigns
- 16
- Country
- PT
- Last broadcast
- 1h ago
Current position
Country allocation
The ICAO 24-bit address 4951EF 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 16 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| TAP110 | TAP Portugal | 20 | 2026-05-30 |
| TAP109 | TAP Portugal | 18 | 2026-05-29 |
| TAP036 | TAP Portugal | 13 | 2026-05-08 |
| TAP035 | TAP Portugal | 13 | 2026-05-07 |
| TAP89WT | TAP Portugal | 8 | 2026-05-24 |
| TAP011 | TAP Portugal | 8 | 2026-05-18 |
| TAP210 | TAP Portugal | 6 | 2026-05-29 |
| TAP209K | TAP Portugal | 6 | 2026-05-28 |
| TAP90EH | TAP Portugal | 5 | 2026-05-24 |
| TAP3178 | - | 4 | 2026-05-24 |
| TAP298 | - | 1 | 2026-05-25 |
| TAP297 | - | 1 | 2026-05-24 |
| TAP23PN | TAP Portugal | 1 | 2026-05-26 |
| TAP226 | TAP Portugal | 1 | 2026-05-18 |
| TAP225V | TAP Portugal | 1 | 2026-05-17 |
| TAP012 | TAP Portugal | 1 | 2026-04-15 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | TAP110 | FLN → LIS | May 30, 03:35 UTC | May 30, 11:45 UTC | 8h 10m |
| 2026-05-29 | TAP109 | LIS → FLN | May 29, 12:15 UTC | May 29, 22:30 UTC | 10h 15m |
| 2026-05-29 | TAP210 | JFK → LIS | May 29, 03:15 UTC | May 29, 09:25 UTC | 6h 10m |
| 2026-05-28 | TAP209K | LIS → JFK | May 28, 16:40 UTC | May 28, 23:50 UTC | 7h 10m |
| 2026-05-28 | TAP110 | FLN → LIS | May 28, 01:40 UTC | May 28, 11:30 UTC | 9h 50m |
| 2026-05-27 | TAP109 | LIS → FLN | May 27, 13:10 UTC | May 27, 23:45 UTC | 10h 35m |
| 2026-05-26 | TAP23PN | LIS → TER | May 26, 10:34 UTC | May 26, 16:20 UTC | 5h 45m |
| 2026-05-25 | TAP298 | - | May 25, 09:40 UTC | May 25, 17:10 UTC | 7h 30m |
| 2026-05-24 | TAP297 | - | May 24, 23:00 UTC | May 25, 05:45 UTC | 6h 45m |
| 2026-05-24 | TAP90EH | FNC → LIS | May 24, 13:50 UTC | May 24, 15:25 UTC | 1h 35m |
| 2026-05-24 | TAP89WT | LIS → FNC | May 24, 12:15 UTC | May 24, 12:30 UTC | 15m |
| 2026-05-24 | TAP89WT | LIS → FNC | May 24, 11:00 UTC | May 24, 11:35 UTC | 35m |
| 2026-05-24 | TAP3178 | - | May 24, 06:50 UTC | May 24, 08:20 UTC | 1h 30m |
| 2026-05-23 | TAP3178 | - | May 23, 11:50 UTC | May 24, 08:20 UTC | 20h 31m |
| 2026-05-18 | TAP011 | LIS → REC | May 18, 16:25 UTC | May 19, 08:20 UTC | 15h 54m |
| 2026-05-18 | TAP226 | MIA → LIS | May 18, 05:15 UTC | May 18, 12:40 UTC | 7h 25m |
| 2026-05-17 | TAP225V | LIS → MIA | May 17, 17:45 UTC | May 18, 02:45 UTC | 9h 0m |
| 2026-05-16 | TAP110 | FLN → LIS | May 16, 04:10 UTC | May 16, 13:31 UTC | 9h 21m |
| 2026-05-15 | TAP109 | LIS → FLN | May 15, 14:20 UTC | May 16, 00:35 UTC | 10h 14m |
| 2026-05-14 | TAP90EH | FNC → LIS | May 14, 14:25 UTC | May 14, 15:45 UTC | 1h 20m |
| 2026-05-14 | TAP89WT | LIS → FNC | May 14, 12:55 UTC | May 14, 13:10 UTC | 15m |
| 2026-05-14 | TAP89WT | LIS → FNC | May 14, 11:40 UTC | May 14, 12:15 UTC | 35m |
| 2026-05-13 | TAP011 | LIS → REC | May 13, 16:40 UTC | May 14, 09:05 UTC | 16h 25m |
| 2026-05-12 | TAP011 | LIS → REC | May 12, 16:50 UTC | May 13, 08:55 UTC | 16h 5m |
| 2026-05-11 | TAP110 | FLN → LIS | May 11, 22:35 UTC | May 12, 12:35 UTC | 14h 1m |
| 2026-05-11 | TAP110 | FLN → LIS | May 11, 14:10 UTC | May 12, 12:35 UTC | 22h 26m |
| 2026-05-11 | TAP110 | FLN → LIS | May 11, 12:50 UTC | May 12, 11:25 UTC | 22h 36m |
| 2026-05-10 | - | LIS → LIS | May 10, 11:05 UTC | May 10, 11:10 UTC | 5m |
| 2026-05-10 | TAP3178 | - | May 10, 07:25 UTC | May 10, 08:50 UTC | 1h 25m |
| 2026-05-09 | TAP3178 | LIS → LIS | May 9, 11:55 UTC | May 10, 08:50 UTC | 20h 55m |
| 2026-05-09 | TAP210 | JFK → LIS | May 9, 02:35 UTC | May 9, 08:50 UTC | 6h 15m |
| 2026-05-08 | TAP209K | LIS → JFK | May 8, 16:50 UTC | May 9, 00:05 UTC | 7h 15m |
| 2026-05-08 | TAP036 | FOR → LIS | May 8, 02:19 UTC | May 8, 09:04 UTC | 6h 45m |
| 2026-05-07 | TAP035 | LIS → FOR | May 7, 17:25 UTC | May 8, 00:40 UTC | 7h 15m |
| 2026-05-07 | TAP90EH | FNC → LIS | May 7, 14:00 UTC | May 7, 15:20 UTC | 1h 20m |
| 2026-05-07 | TAP89WT | LIS → FNC | May 7, 12:35 UTC | May 7, 12:50 UTC | 15m |
| 2026-05-07 | TAP89WT | LIS → FNC | May 7, 11:10 UTC | May 7, 11:45 UTC | 35m |
| 2026-05-06 | TAP011 | LIS → REC | May 6, 16:55 UTC | May 7, 08:55 UTC | 16h 0m |
| 2026-05-06 | TAP90EH | FNC → LIS | May 6, 13:55 UTC | May 6, 15:15 UTC | 1h 20m |
| 2026-05-06 | TAP89WT | LIS → FNC | May 6, 10:55 UTC | May 6, 12:25 UTC | 1h 30m |
| 2026-05-05 | TAP011 | LIS → REC | May 5, 17:00 UTC | May 6, 08:50 UTC | 15h 50m |
| 2026-05-05 | TAP110 | FLN → LIS | May 5, 03:00 UTC | May 5, 12:25 UTC | 9h 25m |
| 2026-05-04 | TAP109 | LIS → FLN | May 4, 12:35 UTC | May 4, 23:10 UTC | 10h 36m |
| 2026-05-04 | TAP036 | FOR → LIS | May 4, 02:04 UTC | May 4, 08:25 UTC | 6h 20m |
| 2026-05-03 | TAP035 | LIS → FOR | May 3, 17:10 UTC | May 4, 00:25 UTC | 7h 15m |
| 2026-05-03 | TAP90EH | FNC → LIS | May 3, 13:40 UTC | May 3, 15:05 UTC | 1h 25m |
| 2026-05-03 | TAP89WT | LIS → FNC | May 3, 11:00 UTC | May 3, 12:30 UTC | 1h 30m |
| 2026-05-02 | TAP011 | LIS → REC | May 2, 16:50 UTC | May 3, 08:45 UTC | 15h 54m |
| 2026-05-02 | TAP036 | FOR → LIS | May 2, 02:05 UTC | May 2, 08:55 UTC | 6h 50m |
| 2026-05-02 | TAP035 | LIS → FOR | May 2, 00:10 UTC | May 2, 00:30 UTC | 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-TOO page for operator, model, and routing details .