sensors Mode-S transponder
AE62BD
ICAO 24-bit transponder address
Currently assigned to 165472
- Hex
- AE62BD
- Octal
- 53461275
- Decimal
- 11,428,541
- Tail
- 165472
- Type
- HAWK
- Flights observed
- 24
- Distinct callsigns
- 17
- Country
- -
- Last broadcast
- 20d ago
Last known position
Callsign history 17 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| CD100 | - | 4 | 2026-06-29 |
| TALON38 | - | 2 | 2026-06-04 |
| TALON26 | - | 2 | 2026-06-24 |
| BT13 | - | 2 | 2026-04-13 |
| B0BCT21 | - | 2 | 2026-05-17 |
| TALON66 | - | 1 | 2026-06-12 |
| TALON31 | - | 1 | 2026-04-28 |
| TALON27 | - | 1 | 2026-06-14 |
| CD1200 | - | 1 | 2026-06-25 |
| BT71 | - | 1 | 2026-04-13 |
| BOBCT99 | - | 1 | 2026-06-30 |
| BOBCT75 | - | 1 | 2026-06-09 |
| BOBCT71 | - | 1 | 2026-06-05 |
| BOBCT55 | - | 1 | 2026-06-12 |
| BOBCT45 | - | 1 | 2026-06-08 |
| BOBCT35 | - | 1 | 2026-06-09 |
| BOBCT25 | - | 1 | 2026-06-12 |
Recent flights last 24
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-30 | BOBCT99 | - | Jun 30, 16:35 UTC | Jun 30, 17:40 UTC | 1h 5m |
| 2026-06-29 | CD100 | - | Jun 29, 15:49 UTC | Jun 29, 16:10 UTC | 20m |
| 2026-06-29 | CD100 | - | Jun 29, 12:39 UTC | Jun 29, 12:55 UTC | 15m |
| 2026-06-28 | CD100 | - | Jun 28, 16:00 UTC | Jun 28, 16:14 UTC | 15m |
| 2026-06-26 | CD100 | - | Jun 26, 12:00 UTC | Jun 26, 12:29 UTC | 30m |
| 2026-06-25 | CD1200 | - | Jun 25, 14:09 UTC | Jun 25, 14:34 UTC | 25m |
| 2026-06-24 | TALON26 | - | Jun 24, 16:59 UTC | Jun 24, 17:59 UTC | 1h 0m |
| 2026-06-14 | TALON27 | - | Jun 14, 17:55 UTC | Jun 14, 18:25 UTC | 30m |
| 2026-06-12 | TALON66 | - | Jun 12, 20:50 UTC | Jun 12, 21:40 UTC | 50m |
| 2026-06-12 | BOBCT25 | - | Jun 12, 16:25 UTC | Jun 12, 16:45 UTC | 20m |
| 2026-06-12 | BOBCT55 | - | Jun 12, 14:01 UTC | Jun 12, 15:00 UTC | 1h 0m |
| 2026-06-09 | BOBCT35 | - | Jun 9, 21:15 UTC | Jun 9, 21:35 UTC | 20m |
| 2026-06-09 | BOBCT75 | - | Jun 9, 19:30 UTC | Jun 9, 19:50 UTC | 20m |
| 2026-06-08 | BOBCT45 | - | Jun 8, 20:45 UTC | Jun 8, 21:20 UTC | 35m |
| 2026-06-05 | BOBCT71 | - | Jun 5, 17:40 UTC | Jun 5, 18:30 UTC | 50m |
| 2026-06-04 | TALON38 | - | Jun 4, 17:00 UTC | Jun 4, 17:30 UTC | 30m |
| 2026-06-03 | TALON38 | - | Jun 3, 21:20 UTC | Jun 3, 21:40 UTC | 20m |
| 2026-06-03 | TALON26 | - | Jun 3, 18:10 UTC | Jun 3, 19:25 UTC | 1h 15m |
| 2026-05-17 | B0BCT21 | - | May 17, 17:40 UTC | May 17, 18:15 UTC | 35m |
| 2026-05-16 | B0BCT21 | - | May 16, 17:15 UTC | May 16, 17:55 UTC | 40m |
| 2026-04-28 | TALON31 | - | Apr 28, 17:05 UTC | Apr 28, 17:20 UTC | 15m |
| 2026-04-13 | BT13 | - | Apr 13, 15:50 UTC | Apr 13, 16:05 UTC | 15m |
| 2026-04-13 | BT13 | - | Apr 13, 15:35 UTC | Apr 13, 16:05 UTC | 30m |
| 2026-04-13 | BT71 | - | Apr 13, 13:30 UTC | Apr 13, 13:50 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 165472 page for operator, model, and routing details .