sensors Mode-S transponder
AE273B
ICAO 24-bit transponder address
Currently assigned to 165742
- Hex
- AE273B
- Octal
- 53423473
- Decimal
- 11,413,307
- Tail
- 165742
- Type
- H60
- Flights observed
- 134
- Distinct callsigns
- 5
- Country
- -
- Last broadcast
- Jul 16, 17:00 UTC
Last known position
Callsign history 5 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-16 | RDHK707 | - | Jul 16, 16:15 UTC | Jul 16, 17:00 UTC | 45m |
| 2026-07-16 | RDHK707 | - | Jul 16, 15:19 UTC | Jul 16, 15:30 UTC | 10m |
| 2026-07-16 | RDHK707 | FAF → NGU | Jul 16, 13:49 UTC | Jul 16, 14:35 UTC | 45m |
| 2026-07-16 | RDHK707 | - | Jul 16, 12:44 UTC | Jul 16, 13:00 UTC | 15m |
| 2026-07-16 | RDHK707 | - | Jul 16, 01:20 UTC | Jul 16, 02:40 UTC | 1h 20m |
| 2026-07-16 | RDHK707 | - | Jul 16, 00:50 UTC | Jul 16, 01:15 UTC | 25m |
| 2026-07-16 | RDHK707 | - | Jul 16, 00:05 UTC | Jul 16, 00:35 UTC | 30m |
| 2026-07-15 | RDHK707 | - | Jul 15, 23:40 UTC | Jul 16, 00:00 UTC | 20m |
| 2026-07-15 | RDHK707 | - | Jul 15, 23:15 UTC | Jul 15, 23:35 UTC | 20m |
| 2026-07-15 | RDHK707 | - | Jul 15, 22:40 UTC | Jul 15, 23:10 UTC | 30m |
| 2026-07-15 | RDHK707 | - | Jul 15, 22:00 UTC | Jul 15, 22:35 UTC | 35m |
| 2026-07-15 | RDHK707 | - | Jul 15, 19:05 UTC | Jul 15, 20:55 UTC | 1h 50m |
| 2026-07-15 | RDHK707 | - | Jul 15, 18:15 UTC | Jul 15, 18:50 UTC | 35m |
| 2026-07-15 | RDHK707 | - | Jul 15, 15:55 UTC | Jul 15, 17:05 UTC | 1h 10m |
| 2026-07-15 | RDHK707 | - | Jul 15, 13:50 UTC | Jul 15, 14:35 UTC | 45m |
| 2026-07-14 | RDHK707 | - | Jul 14, 22:10 UTC | Jul 14, 23:50 UTC | 1h 39m |
| 2026-07-14 | RDHK707 | - | Jul 14, 17:30 UTC | Jul 14, 17:35 UTC | 5m |
| 2026-07-14 | RDHK707 | - | Jul 14, 14:50 UTC | Jul 14, 15:40 UTC | 50m |
| 2026-07-10 | RDHK707 | - | Jul 10, 20:10 UTC | Jul 10, 20:55 UTC | 45m |
| 2026-07-10 | RDHK707 | - | Jul 10, 18:45 UTC | Jul 10, 19:20 UTC | 35m |
| 2026-07-10 | RDHK707 | - | Jul 10, 16:45 UTC | Jul 10, 18:35 UTC | 1h 50m |
| 2026-07-10 | RDHK707 | - | Jul 10, 15:45 UTC | Jul 10, 15:55 UTC | 10m |
| 2026-07-10 | RDHK707 | - | Jul 10, 13:55 UTC | Jul 10, 15:00 UTC | 1h 5m |
| 2026-07-10 | RDHK707 | - | Jul 10, 13:10 UTC | Jul 10, 13:20 UTC | 10m |
| 2026-07-09 | RDHK707 | FAF → NGU | Jul 9, 03:55 UTC | Jul 9, 04:35 UTC | 40m |
| 2026-07-09 | RDHK707 | - | Jul 9, 02:45 UTC | Jul 9, 03:05 UTC | 20m |
| 2026-07-09 | RDHK707 | - | Jul 9, 01:55 UTC | Jul 9, 02:05 UTC | 10m |
| 2026-07-08 | RDHK707 | - | Jul 8, 22:55 UTC | Jul 9, 01:10 UTC | 2h 15m |
| 2026-07-08 | RDHK707 | NGU → FAF | Jul 8, 21:30 UTC | Jul 8, 22:25 UTC | 55m |
| 2026-07-08 | RDHK707 | - | Jul 8, 19:30 UTC | Jul 8, 21:20 UTC | 1h 50m |
| 2026-07-08 | RDHK707 | FAF → NGU | Jul 8, 16:30 UTC | Jul 8, 18:50 UTC | 2h 20m |
| 2026-07-08 | RDHK707 | - | Jul 8, 15:20 UTC | Jul 8, 15:30 UTC | 10m |
| 2026-07-08 | RDHK707 | - | Jul 8, 13:25 UTC | Jul 8, 14:20 UTC | 55m |
| 2026-07-03 | RDHK705 | - | Jul 3, 01:30 UTC | Jul 3, 02:15 UTC | 45m |
| 2026-07-03 | RDHK705 | - | Jul 3, 00:35 UTC | Jul 3, 00:45 UTC | 10m |
| 2026-07-02 | RDHK707 | - | Jul 2, 21:20 UTC | Jul 2, 21:30 UTC | 10m |
| 2026-07-02 | RDHK707 | - | Jul 2, 18:30 UTC | Jul 2, 20:40 UTC | 2h 10m |
| 2026-07-02 | RDHK707 | - | Jul 2, 17:20 UTC | Jul 2, 17:55 UTC | 35m |
| 2026-07-02 | RDHK707 | FAF → FAF | Jul 2, 16:30 UTC | Jul 2, 16:45 UTC | 15m |
| 2026-07-02 | RDHK707 | - | Jul 2, 15:45 UTC | Jul 2, 15:55 UTC | 10m |
| 2026-07-02 | RDHK705 | - | Jul 2, 01:45 UTC | Jul 2, 02:10 UTC | 25m |
| 2026-07-02 | RDHK705 | - | Jul 2, 00:30 UTC | Jul 2, 01:40 UTC | 1h 10m |
| 2026-07-01 | RDHK705 | - | Jul 1, 23:30 UTC | Jul 2, 00:00 UTC | 30m |
| 2026-07-01 | RDHK705 | - | Jul 1, 22:50 UTC | Jul 1, 23:15 UTC | 25m |
| 2026-07-01 | RDHK705 | - | Jul 1, 22:25 UTC | Jul 1, 22:45 UTC | 20m |
| 2026-07-01 | RDHK705 | - | Jul 1, 21:55 UTC | Jul 1, 22:20 UTC | 25m |
| 2026-07-01 | RDHK705 | - | Jul 1, 21:30 UTC | Jul 1, 21:50 UTC | 20m |
| 2026-07-01 | RDHK705 | - | Jul 1, 21:05 UTC | Jul 1, 21:25 UTC | 20m |
| 2026-07-01 | RDHK705 | - | Jul 1, 20:30 UTC | Jul 1, 20:50 UTC | 20m |
| 2026-07-01 | RDHK707 | NGU → NGU | Jul 1, 02:40 UTC | Jul 1, 04:30 UTC | 1h 50m |
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 165742 page for operator, model, and routing details .