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
- 167
- Distinct callsigns
- 20
- Country
- PT
- Last broadcast
- 2h ago
Last known 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| TAP110 | - | 24 | 2026-07-14 |
| TAP109 | - | 22 | 2026-07-13 |
| TAP209K | - | 14 | 2026-07-14 |
| TAP210 | - | 13 | 2026-07-13 |
| TAP036 | TAP Portugal | 13 | 2026-05-08 |
| TAP035 | TAP Portugal | 13 | 2026-05-07 |
| TAP011 | - | 10 | 2026-07-10 |
| TAP89WT | TAP Portugal | 9 | 2026-06-13 |
| TAP3178 | - | 7 | 2026-06-16 |
| TAP90EH | TAP Portugal | 6 | 2026-06-13 |
| TAP203 | - | 6 | 2026-06-27 |
| TAP104 | - | 5 | 2026-06-11 |
| TAP204A | - | 4 | 2026-06-25 |
| TAP067 | - | 3 | 2026-07-12 |
| TAP226 | - | 2 | 2026-06-22 |
| TAP225V | - | 2 | 2026-06-21 |
| TAP028 | - | 2 | 2026-06-23 |
| TAP012 | - | 2 | 2026-07-11 |
| TAP9264 | TAP Portugal | 1 | 2026-06-05 |
| TAP9253 | - | 1 | 2026-07-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | TAP209K | - | Jul 14, 16:40 UTC | Jul 14, 17:30 UTC | 50m |
| 2026-07-14 | TAP110 | - | Jul 14, 03:00 UTC | Jul 14, 12:45 UTC | 9h 45m |
| 2026-07-13 | TAP109 | - | Jul 13, 13:00 UTC | Jul 13, 23:25 UTC | 10h 25m |
| 2026-07-13 | TAP210 | JFK → LIS | Jul 13, 03:05 UTC | Jul 13, 09:25 UTC | 6h 20m |
| 2026-07-12 | TAP209K | LIS → JFK | Jul 12, 16:40 UTC | Jul 12, 23:40 UTC | 7h 0m |
| 2026-07-12 | TAP067 | - | Jul 12, 02:30 UTC | Jul 12, 11:30 UTC | 9h 0m |
| 2026-07-11 | TAP067 | - | Jul 11, 23:50 UTC | Jul 12, 00:55 UTC | 1h 5m |
| 2026-07-11 | TAP067 | - | Jul 11, 11:15 UTC | Jul 11, 21:20 UTC | 10h 5m |
| 2026-07-11 | TAP012 | - | Jul 11, 01:45 UTC | Jul 11, 08:30 UTC | 6h 45m |
| 2026-07-10 | TAP011 | - | Jul 10, 23:35 UTC | Jul 10, 23:55 UTC | 20m |
| 2026-07-10 | TAP011 | - | Jul 10, 16:35 UTC | Jul 10, 18:25 UTC | 1h 50m |
| 2026-07-08 | TAP9253 | EWR → LIS | Jul 8, 16:40 UTC | Jul 8, 22:55 UTC | 6h 15m |
| 2026-06-27 | TAP203 | LIS → EWR | Jun 27, 17:14 UTC | Jun 28, 00:50 UTC | 7h 35m |
| 2026-06-27 | TAP110 | - | Jun 27, 03:44 UTC | Jun 27, 13:55 UTC | 10h 10m |
| 2026-06-26 | TAP109 | - | Jun 26, 12:39 UTC | Jun 26, 22:25 UTC | 9h 45m |
| 2026-06-26 | TAP210 | - | Jun 26, 03:15 UTC | Jun 26, 09:24 UTC | 6h 10m |
| 2026-06-25 | TAP209K | LIS → JFK | Jun 25, 16:39 UTC | Jun 25, 23:55 UTC | 7h 15m |
| 2026-06-25 | TAP204A | EWR → LIS | Jun 25, 03:44 UTC | Jun 25, 09:45 UTC | 6h 0m |
| 2026-06-24 | TAP203 | - | Jun 24, 17:25 UTC | Jun 25, 00:55 UTC | 7h 30m |
| 2026-06-23 | TAP028 | LIS → LIS | Jun 23, 16:59 UTC | Jun 24, 10:45 UTC | 17h 45m |
| 2026-06-22 | TAP226 | - | Jun 22, 04:44 UTC | Jun 22, 12:30 UTC | 7h 45m |
| 2026-06-21 | TAP225V | - | Jun 21, 17:50 UTC | Jun 22, 02:10 UTC | 8h 20m |
| 2026-06-21 | TAP210 | JFK → LIS | Jun 21, 02:40 UTC | Jun 21, 08:40 UTC | 6h 0m |
| 2026-06-20 | TAP209K | LIS → JFK | Jun 20, 16:34 UTC | Jun 20, 23:50 UTC | 7h 15m |
| 2026-06-19 | TAP110 | - | Jun 19, 13:59 UTC | Jun 20, 13:44 UTC | 23h 45m |
| 2026-06-19 | TAP109 | - | Jun 19, 12:49 UTC | Jun 20, 07:24 UTC | 18h 35m |
| 2026-06-19 | TAP210 | JFK → LIS | Jun 19, 02:59 UTC | Jun 19, 08:59 UTC | 6h 0m |
| 2026-06-18 | TAP209K | LIS → JFK | Jun 18, 16:40 UTC | Jun 19, 00:05 UTC | 7h 25m |
| 2026-06-18 | TAP204A | - | Jun 18, 03:35 UTC | Jun 18, 09:35 UTC | 6h 0m |
| 2026-06-17 | TAP203 | LIS → EWR | Jun 17, 17:35 UTC | Jun 18, 01:05 UTC | 7h 30m |
| 2026-06-16 | TAP028 | LIS → LIS | Jun 16, 16:55 UTC | Jun 17, 10:40 UTC | 17h 46m |
| 2026-06-16 | TAP3178 | - | Jun 16, 07:30 UTC | Jun 16, 08:10 UTC | 40m |
| 2026-06-15 | TAP3178 | - | Jun 15, 11:49 UTC | Jun 16, 08:10 UTC | 20h 20m |
| 2026-06-15 | TAP3178 | LIS → LIS | Jun 15, 11:30 UTC | Jun 16, 08:10 UTC | 20h 40m |
| 2026-06-15 | TAP210 | JFK → LIS | Jun 15, 03:05 UTC | Jun 15, 09:15 UTC | 6h 10m |
| 2026-06-14 | TAP209K | LIS → JFK | Jun 14, 16:30 UTC | Jun 14, 23:50 UTC | 7h 20m |
| 2026-06-14 | TAP204A | EWR → LIS | Jun 14, 05:40 UTC | Jun 14, 11:35 UTC | 5h 55m |
| 2026-06-13 | TAP203 | LIS → EWR | Jun 13, 19:00 UTC | Jun 14, 02:25 UTC | 7h 25m |
| 2026-06-13 | TAP90EH | FNC → LIS | Jun 13, 14:30 UTC | Jun 13, 16:15 UTC | 1h 45m |
| 2026-06-13 | TAP89WT | LIS → FNC | Jun 13, 10:45 UTC | Jun 13, 12:10 UTC | 1h 25m |
| 2026-06-12 | TAP058 | BSB → LIS | Jun 12, 11:50 UTC | Jun 13, 06:00 UTC | 18h 9m |
| 2026-06-12 | TAP057 | LIS → BSB | Jun 12, 10:15 UTC | Jun 13, 06:00 UTC | 19h 44m |
| 2026-06-11 | TAP104 | LIS → LIS | Jun 11, 09:55 UTC | Jun 12, 05:35 UTC | 19h 40m |
| 2026-06-10 | TAP104 | CNF → LIS | Jun 10, 09:55 UTC | Jun 11, 05:45 UTC | 19h 50m |
| 2026-06-09 | TAP104 | CNF → LIS | Jun 9, 09:50 UTC | Jun 10, 05:20 UTC | 19h 30m |
| 2026-06-09 | TAP104 | CNF → LIS | Jun 9, 09:00 UTC | Jun 10, 05:20 UTC | 20h 20m |
| 2026-06-08 | TAP104 | CNF → LIS | Jun 8, 09:55 UTC | Jun 9, 05:20 UTC | 19h 25m |
| 2026-06-07 | TAP224 | MIA → LIS | Jun 7, 20:50 UTC | Jun 8, 04:30 UTC | 7h 40m |
| 2026-06-07 | TAP22MI | LIS → MIA | Jun 7, 09:55 UTC | Jun 7, 18:30 UTC | 8h 35m |
| 2026-06-05 | TAP9264 | EWR → LIS | Jun 5, 23:55 UTC | Jun 6, 06:05 UTC | 6h 10m |
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 .