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
- 147
- Distinct callsigns
- 9
- Country
- PT
- Last broadcast
- 1d 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 9 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | AZU8731 | - | Jul 13, 03:01 UTC | Jul 13, 06:50 UTC | 3h 50m |
| 2026-07-12 | AZU8730 | - | Jul 12, 05:20 UTC | Jul 13, 00:15 UTC | 18h 55m |
| 2026-07-12 | AZU8730 | - | Jul 12, 03:20 UTC | Jul 13, 00:15 UTC | 20h 55m |
| 2026-07-12 | AZU8730 | MCO → MCO | Jul 12, 03:10 UTC | Jul 13, 00:15 UTC | 21h 5m |
| 2026-07-11 | AZU8730 | - | Jul 11, 20:05 UTC | Jul 12, 00:01 UTC | 3h 55m |
| 2026-07-08 | AZU8731 | - | Jul 8, 03:00 UTC | Jul 8, 09:30 UTC | 6h 30m |
| 2026-07-07 | AZU8730 | - | Jul 7, 20:05 UTC | Jul 8, 00:05 UTC | 4h 0m |
| 2026-07-06 | AZU8731 | - | Jul 6, 03:25 UTC | Jul 6, 09:40 UTC | 6h 15m |
| 2026-07-05 | AZU8730 | - | Jul 5, 05:20 UTC | Jul 6, 00:05 UTC | 18h 45m |
| 2026-07-05 | AZU8731 | - | Jul 5, 03:20 UTC | Jul 6, 00:05 UTC | 20h 45m |
| 2026-07-05 | AZU8731 | MCO → MCO | Jul 5, 03:00 UTC | Jul 6, 00:05 UTC | 21h 5m |
| 2026-07-04 | AZU8730 | - | Jul 4, 20:25 UTC | Jul 5, 00:25 UTC | 4h 0m |
| 2026-07-03 | MMZ601P | - | Jul 3, 17:55 UTC | Jul 3, 21:30 UTC | 3h 35m |
| 2026-06-29 | MMZ600P | - | Jun 29, 13:44 UTC | Jun 29, 14:25 UTC | 40m |
| 2026-06-29 | MMZ600P | - | Jun 29, 05:54 UTC | Jun 29, 06:29 UTC | 35m |
| 2026-06-27 | AZU8002 | - | Jun 27, 00:34 UTC | Jun 27, 07:39 UTC | 7h 5m |
| 2026-06-26 | AZU8001 | - | Jun 26, 09:59 UTC | Jun 26, 12:24 UTC | 2h 25m |
| 2026-06-25 | AZU8000 | - | Jun 25, 22:59 UTC | Jun 26, 06:19 UTC | 7h 20m |
| 2026-06-25 | AZU8003 | - | Jun 25, 17:30 UTC | Jun 25, 17:44 UTC | 15m |
| 2026-06-25 | AZU8003 | - | Jun 25, 10:30 UTC | Jun 25, 12:30 UTC | 2h 0m |
| 2026-06-24 | AZU8002 | - | Jun 24, 23:50 UTC | Jun 25, 07:15 UTC | 7h 25m |
| 2026-06-24 | AZU8001 | - | Jun 24, 10:04 UTC | Jun 24, 12:20 UTC | 2h 15m |
| 2026-06-24 | AZU8000 | - | Jun 24, 04:15 UTC | Jun 24, 06:20 UTC | 2h 5m |
| 2026-06-22 | AZU8001 | - | Jun 22, 09:24 UTC | Jun 22, 11:39 UTC | 2h 15m |
| 2026-06-22 | AZU8000 | - | Jun 22, 02:40 UTC | Jun 22, 06:25 UTC | 3h 45m |
| 2026-06-21 | AZU8000 | - | Jun 21, 22:54 UTC | Jun 21, 23:10 UTC | 15m |
| 2026-06-21 | AZU8003 | - | Jun 21, 17:50 UTC | Jun 21, 18:00 UTC | 10m |
| 2026-06-21 | AZU8003 | - | Jun 21, 10:34 UTC | Jun 21, 12:40 UTC | 2h 5m |
| 2026-06-20 | AZU8002 | - | Jun 20, 00:14 UTC | Jun 20, 07:44 UTC | 7h 30m |
| 2026-06-19 | AZU8001 | - | Jun 19, 16:55 UTC | Jun 19, 17:09 UTC | 15m |
| 2026-06-19 | AZU8001 | - | Jun 19, 09:40 UTC | Jun 19, 11:54 UTC | 2h 15m |
| 2026-06-18 | AZU8000 | - | Jun 18, 22:55 UTC | Jun 19, 06:24 UTC | 7h 29m |
| 2026-06-18 | AZU8003 | OPO → REC | Jun 18, 17:25 UTC | Jun 18, 17:40 UTC | 15m |
| 2026-06-18 | AZU8003 | OPO → REC | Jun 18, 10:15 UTC | Jun 18, 12:15 UTC | 2h 0m |
| 2026-06-18 | AZU8002 | - | Jun 18, 00:10 UTC | Jun 18, 07:30 UTC | 7h 20m |
| 2026-06-17 | AZU8001 | - | Jun 17, 09:30 UTC | Jun 17, 11:40 UTC | 2h 10m |
| 2026-06-17 | AZU8000 | - | Jun 17, 02:00 UTC | Jun 17, 06:20 UTC | 4h 20m |
| 2026-06-16 | AZU8000 | - | Jun 16, 22:50 UTC | Jun 16, 23:05 UTC | 15m |
| 2026-06-15 | AZU8001 | MAD → REC | Jun 15, 16:35 UTC | Jun 15, 16:49 UTC | 15m |
| 2026-06-15 | AZU8001 | MAD → REC | Jun 15, 09:20 UTC | Jun 15, 11:30 UTC | 2h 10m |
| 2026-06-14 | AZU8000 | - | Jun 14, 23:05 UTC | Jun 15, 06:35 UTC | 7h 29m |
| 2026-06-14 | AZU8003 | OPO → REC | Jun 14, 10:05 UTC | Jun 14, 12:05 UTC | 2h 0m |
| 2026-06-13 | AZU8002 | REC → OPO | Jun 13, 05:30 UTC | Jun 13, 07:35 UTC | 2h 5m |
| 2026-06-12 | AZU8002 | REC → OPO | Jun 12, 11:20 UTC | Jun 13, 07:35 UTC | 20h 14m |
| 2026-06-12 | AZU8002 | REC → OPO | Jun 12, 10:25 UTC | Jun 13, 07:35 UTC | 21h 9m |
| 2026-06-12 | AZU8000 | - | Jun 12, 05:10 UTC | Jun 12, 07:25 UTC | 2h 15m |
| 2026-06-11 | AZU8000 | - | Jun 11, 11:30 UTC | Jun 12, 07:25 UTC | 19h 55m |
| 2026-06-11 | AZU8000 | - | Jun 11, 10:05 UTC | Jun 12, 07:25 UTC | 21h 20m |
| 2026-06-11 | AZU8002 | REC → OPO | Jun 11, 05:30 UTC | Jun 11, 07:30 UTC | 2h 0m |
| 2026-06-10 | AZU8002 | REC → OPO | Jun 10, 11:20 UTC | Jun 11, 07:30 UTC | 20h 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-TSU page for operator, model, and routing details .