sensors Mode-S transponder
AE4D3F
ICAO 24-bit transponder address
Currently assigned to 168553
- Hex
- AE4D3F
- Octal
- 53446477
- Decimal
- 11,423,039
- Tail
- 168553
- Type
- H60
- Flights observed
- 43
- Distinct callsigns
- 10
- Country
- -
- Last broadcast
- 3d ago
Last known position
Callsign history 10 distinct
Recent flights last 43
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-01 | BT11 | - | Jul 1, 17:15 UTC | Jul 1, 17:20 UTC | 5m |
| 2026-07-01 | BT22 | - | Jul 1, 14:55 UTC | Jul 1, 16:20 UTC | 1h 25m |
| 2026-06-27 | BT11 | - | Jun 27, 03:04 UTC | Jun 27, 03:25 UTC | 20m |
| 2026-06-25 | BT11 | - | Jun 25, 20:59 UTC | Jun 25, 22:10 UTC | 1h 10m |
| 2026-06-12 | BT21 | - | Jun 12, 00:30 UTC | Jun 12, 02:15 UTC | 1h 45m |
| 2026-06-11 | BT21 | NZY → NZY | Jun 11, 20:35 UTC | Jun 11, 23:05 UTC | 2h 30m |
| 2026-06-11 | FFAB123 | - | Jun 11, 20:05 UTC | Jun 11, 20:25 UTC | 20m |
| 2026-06-11 | FFAB123 | - | Jun 11, 19:05 UTC | Jun 11, 20:00 UTC | 55m |
| 2026-06-11 | FFAB123 | - | Jun 11, 18:15 UTC | Jun 11, 18:45 UTC | 30m |
| 2026-06-05 | NITE31 | - | Jun 5, 04:20 UTC | Jun 5, 04:55 UTC | 35m |
| 2026-06-05 | NITE31 | - | Jun 5, 02:25 UTC | Jun 5, 02:35 UTC | 10m |
| 2026-06-04 | NITE615 | - | Jun 4, 04:20 UTC | Jun 4, 05:05 UTC | 45m |
| 2026-06-04 | NITE615 | - | Jun 4, 00:50 UTC | Jun 4, 01:15 UTC | 25m |
| 2026-06-03 | BT11 | - | Jun 3, 23:10 UTC | Jun 3, 23:20 UTC | 10m |
| 2026-06-03 | NITE615 | - | Jun 3, 19:15 UTC | Jun 3, 19:40 UTC | 25m |
| 2026-06-03 | BT21 | - | Jun 3, 03:55 UTC | Jun 3, 04:10 UTC | 15m |
| 2026-06-03 | BT21 | - | Jun 3, 00:30 UTC | Jun 3, 00:50 UTC | 20m |
| 2026-06-02 | BT21 | - | Jun 2, 22:35 UTC | Jun 2, 23:45 UTC | 1h 10m |
| 2026-06-02 | BT21 | - | Jun 2, 21:35 UTC | Jun 2, 21:50 UTC | 15m |
| 2026-05-29 | BT22 | - | May 29, 05:40 UTC | May 29, 08:00 UTC | 2h 20m |
| 2026-05-28 | NITE12 | NZY → NZY | May 28, 22:25 UTC | May 29, 01:10 UTC | 2h 45m |
| 2026-05-28 | NITE21 | NZY → NZY | May 28, 02:40 UTC | May 28, 05:05 UTC | 2h 25m |
| 2026-05-27 | NITE21 | - | May 27, 23:35 UTC | May 28, 01:35 UTC | 2h 0m |
| 2026-05-08 | NITE31 | NZY → NZY | May 8, 01:59 UTC | May 8, 04:19 UTC | 2h 20m |
| 2026-05-07 | NITE21 | - | May 7, 23:24 UTC | May 8, 01:49 UTC | 2h 25m |
| 2026-05-07 | NITE11 | - | May 7, 21:50 UTC | May 7, 22:40 UTC | 50m |
| 2026-05-07 | NITE31 | - | May 7, 20:35 UTC | May 7, 21:10 UTC | 35m |
| 2026-05-06 | NITE11 | - | May 6, 23:05 UTC | May 7, 01:00 UTC | 1h 55m |
| 2026-05-06 | BT12 | - | May 6, 03:50 UTC | May 6, 05:25 UTC | 1h 35m |
| 2026-05-06 | BT12 | - | May 6, 02:45 UTC | May 6, 03:10 UTC | 25m |
| 2026-05-06 | BT12 | - | May 6, 01:40 UTC | May 6, 02:35 UTC | 55m |
| 2026-05-05 | BT12 | - | May 5, 23:20 UTC | May 5, 23:50 UTC | 30m |
| 2026-05-05 | BT12 | - | May 5, 21:20 UTC | May 5, 22:30 UTC | 1h 10m |
| 2026-04-30 | NITE11 | - | Apr 30, 20:30 UTC | Apr 30, 23:30 UTC | 3h 0m |
| 2026-04-30 | NITE11 | - | Apr 30, 17:00 UTC | Apr 30, 20:00 UTC | 3h 0m |
| 2026-04-29 | NITE21 | - | Apr 29, 22:35 UTC | Apr 29, 23:25 UTC | 49m |
| 2026-04-29 | NITE21 | - | Apr 29, 20:50 UTC | Apr 29, 21:15 UTC | 25m |
| 2026-04-29 | NITE11 | - | Apr 29, 19:30 UTC | Apr 29, 20:15 UTC | 45m |
| 2026-04-25 | NITE21 | - | Apr 25, 20:45 UTC | Apr 25, 21:05 UTC | 20m |
| 2026-04-17 | BT11 | - | Apr 17, 04:50 UTC | Apr 17, 05:15 UTC | 25m |
| 2026-04-17 | BT11 | - | Apr 17, 01:20 UTC | Apr 17, 03:10 UTC | 1h 50m |
| 2026-04-16 | BT11 | - | Apr 16, 23:55 UTC | Apr 17, 01:15 UTC | 1h 20m |
| 2026-04-16 | NITE11 | - | Apr 16, 18:20 UTC | Apr 16, 19:10 UTC | 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 168553 page for operator, model, and routing details .