sensors Mode-S transponder
495275
ICAO 24-bit transponder address · allocated to Portugal
Currently assigned to CS-TSU · BOEING 767-300
- Hex
- 495275
- Octal
- 22251165
- Decimal
- 4,805,237
- Country
- PT
- Tail
- CS-TSU
- Type
- B763
- Flights observed
- 80
- Distinct callsigns
- 6
- Country
- PT
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address 495275 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 6 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| AZU8000 | Azul Brazilian Airlines | 24 | 2026-05-28 |
| AZU8002 | Azul Brazilian Airlines | 23 | 2026-05-29 |
| AZU8001 | Azul Brazilian Airlines | 19 | 2026-05-27 |
| AZU8003 | Azul Brazilian Airlines | 10 | 2026-05-24 |
| AZU8731 | - | 2 | 2026-04-13 |
| AZU8730 | Azul Brazilian Airlines | 2 | 2026-04-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | AZU8002 | REC → OPO | May 29, 11:25 UTC | May 30, 07:20 UTC | 19h 55m |
| 2026-05-29 | AZU8002 | REC → OPO | May 29, 09:55 UTC | May 30, 07:20 UTC | 21h 25m |
| 2026-05-28 | AZU8000 | REC → MAD | May 28, 11:20 UTC | May 29, 06:45 UTC | 19h 25m |
| 2026-05-28 | AZU8000 | REC → MAD | May 28, 10:30 UTC | May 29, 06:45 UTC | 20h 15m |
| 2026-05-28 | AZU8002 | REC → OPO | May 28, 06:00 UTC | May 28, 08:10 UTC | 2h 10m |
| 2026-05-27 | AZU8002 | REC → OPO | May 27, 11:20 UTC | May 28, 08:10 UTC | 20h 50m |
| 2026-05-27 | AZU8001 | MAD → REC | May 27, 09:25 UTC | May 28, 08:10 UTC | 22h 45m |
| 2026-05-27 | AZU8000 | REC → MAD | May 27, 04:04 UTC | May 27, 06:15 UTC | 2h 10m |
| 2026-05-25 | AZU8001 | MAD → REC | May 25, 09:35 UTC | May 25, 11:50 UTC | 2h 15m |
| 2026-05-24 | AZU8000 | REC → MAD | May 24, 11:45 UTC | May 25, 06:20 UTC | 18h 35m |
| 2026-05-24 | AZU8003 | OPO → REC | May 24, 10:25 UTC | May 25, 06:20 UTC | 19h 55m |
| 2026-05-22 | AZU8002 | REC → OPO | May 22, 11:20 UTC | May 23, 07:15 UTC | 19h 55m |
| 2026-05-22 | AZU8001 | MAD → REC | May 22, 10:45 UTC | May 23, 07:15 UTC | 20h 29m |
| 2026-05-21 | AZU8000 | REC → MAD | May 21, 11:20 UTC | May 22, 06:55 UTC | 19h 35m |
| 2026-05-20 | AZU8002 | REC → OPO | May 20, 11:35 UTC | May 21, 06:55 UTC | 19h 20m |
| 2026-05-20 | AZU8001 | MAD → REC | May 20, 09:55 UTC | May 21, 06:55 UTC | 21h 0m |
| 2026-05-20 | AZU8000 | REC → MAD | May 20, 04:10 UTC | May 20, 06:20 UTC | 2h 11m |
| 2026-05-18 | AZU8001 | MAD → REC | May 18, 10:50 UTC | May 18, 12:50 UTC | 2h 0m |
| 2026-05-17 | AZU8000 | REC → MAD | May 17, 11:25 UTC | May 18, 06:25 UTC | 19h 0m |
| 2026-05-17 | AZU8000 | REC → MAD | May 17, 10:00 UTC | May 18, 06:25 UTC | 20h 25m |
| 2026-05-16 | AZU8002 | REC → OPO | May 16, 05:15 UTC | May 16, 07:16 UTC | 2h 1m |
| 2026-05-14 | AZU8003 | OPO → REC | May 14, 10:20 UTC | May 14, 12:25 UTC | 2h 5m |
| 2026-05-14 | AZU8002 | REC → OPO | May 14, 05:50 UTC | May 14, 07:35 UTC | 1h 45m |
| 2026-05-13 | AZU8002 | REC → OPO | May 13, 11:20 UTC | May 14, 07:35 UTC | 20h 15m |
| 2026-05-13 | AZU8001 | MAD → REC | May 13, 09:20 UTC | May 14, 07:35 UTC | 22h 15m |
| 2026-05-13 | AZU8000 | REC → MAD | May 13, 03:50 UTC | May 13, 05:45 UTC | 1h 55m |
| 2026-05-11 | AZU8001 | MAD → REC | May 11, 09:25 UTC | May 11, 12:05 UTC | 2h 40m |
| 2026-05-10 | AZU8000 | REC → MAD | May 10, 11:30 UTC | May 11, 06:15 UTC | 18h 45m |
| 2026-05-10 | AZU8003 | OPO → REC | May 10, 10:24 UTC | May 11, 06:15 UTC | 19h 50m |
| 2026-05-09 | AZU8002 | REC → OPO | May 9, 05:20 UTC | May 9, 07:20 UTC | 2h 0m |
| 2026-05-08 | AZU8002 | REC → OPO | May 8, 12:00 UTC | May 9, 07:20 UTC | 19h 20m |
| 2026-05-08 | AZU8001 | MAD → REC | May 8, 09:59 UTC | May 9, 07:20 UTC | 21h 20m |
| 2026-05-07 | AZU8000 | REC → MAD | May 7, 11:45 UTC | May 8, 06:30 UTC | 18h 45m |
| 2026-05-07 | AZU8003 | OPO → REC | May 7, 10:15 UTC | May 8, 06:30 UTC | 20h 15m |
| 2026-05-06 | AZU8001 | MAD → REC | May 6, 12:10 UTC | May 7, 07:10 UTC | 18h 59m |
| 2026-05-06 | AZU8000 | REC → MAD | May 6, 04:05 UTC | May 6, 06:15 UTC | 2h 10m |
| 2026-05-04 | AZU8001 | MAD → REC | May 4, 10:35 UTC | May 4, 12:55 UTC | 2h 20m |
| 2026-05-03 | AZU8000 | REC → MAD | May 3, 11:25 UTC | May 4, 06:15 UTC | 18h 50m |
| 2026-05-03 | AZU8003 | OPO → REC | May 3, 10:20 UTC | May 4, 06:15 UTC | 19h 55m |
| 2026-05-01 | AZU8002 | REC → OPO | May 1, 13:20 UTC | May 2, 08:00 UTC | 18h 40m |
| 2026-05-01 | AZU8002 | REC → OPO | May 1, 11:20 UTC | May 2, 08:00 UTC | 20h 40m |
| 2026-05-01 | AZU8001 | MAD → REC | May 1, 11:10 UTC | May 2, 08:00 UTC | 20h 50m |
| 2026-04-30 | AZU8000 | REC → MAD | Apr 30, 11:55 UTC | May 1, 07:15 UTC | 19h 20m |
| 2026-04-30 | AZU8003 | OPO → REC | Apr 30, 10:30 UTC | May 1, 07:15 UTC | 20h 45m |
| 2026-04-30 | AZU8002 | REC → OPO | Apr 30, 05:30 UTC | Apr 30, 07:45 UTC | 2h 15m |
| 2026-04-29 | AZU8002 | REC → OPO | Apr 29, 11:55 UTC | Apr 30, 07:45 UTC | 19h 49m |
| 2026-04-29 | AZU8002 | REC → OPO | Apr 29, 10:00 UTC | Apr 30, 07:45 UTC | 21h 44m |
| 2026-04-29 | AZU8000 | REC → MAD | Apr 29, 04:49 UTC | Apr 29, 07:05 UTC | 2h 15m |
| 2026-04-27 | AZU8001 | MAD → REC | Apr 27, 09:55 UTC | Apr 27, 12:10 UTC | 2h 15m |
| 2026-04-26 | AZU8000 | REC → MAD | Apr 26, 11:20 UTC | Apr 27, 06:55 UTC | 19h 35m |
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-TSU page for operator, model, and routing details .