sensors Mode-S transponder
ADFE9A
ICAO 24-bit transponder address
Currently assigned to 95-00101 · Beech C-12V Huron
- Hex
- ADFE9A
- Octal
- 53377232
- Decimal
- 11,402,906
- Tail
- 95-00101
- Type
- BE20
- Flights observed
- 43
- Distinct callsigns
- 2
- Country
- -
- Last broadcast
- 22h ago
Last known position
Callsign history 2 distinct
Recent flights last 43
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | MFO692 | - | Jun 2, 10:55 UTC | Jun 2, 11:35 UTC | 40m |
| 2026-06-02 | MFO692 | - | Jun 2, 09:35 UTC | Jun 2, 09:45 UTC | 10m |
| 2026-06-01 | MFO692 | - | Jun 1, 09:15 UTC | Jun 1, 09:40 UTC | 25m |
| 2026-06-01 | MFO692 | - | Jun 1, 07:05 UTC | Jun 1, 07:45 UTC | 40m |
| 2026-05-30 | MFO692 | - | May 30, 08:05 UTC | May 30, 08:25 UTC | 20m |
| 2026-05-30 | MFO692 | - | May 30, 06:40 UTC | May 30, 07:05 UTC | 25m |
| 2026-05-29 | MFO692 | - | May 29, 09:30 UTC | May 29, 09:55 UTC | 25m |
| 2026-05-29 | MFO692 | - | May 29, 07:05 UTC | May 29, 07:40 UTC | 35m |
| 2026-05-27 | MFO692 | - | May 27, 09:15 UTC | May 27, 09:35 UTC | 20m |
| 2026-05-27 | MFO692 | - | May 27, 06:55 UTC | May 27, 07:50 UTC | 55m |
| 2026-05-26 | MFO692 | - | May 26, 10:25 UTC | May 26, 10:50 UTC | 25m |
| 2026-05-26 | MFO692 | - | May 26, 08:24 UTC | May 26, 09:04 UTC | 40m |
| 2026-05-25 | MFO692 | - | May 25, 08:05 UTC | May 25, 09:20 UTC | 1h 15m |
| 2026-05-24 | MFO692 | - | May 24, 09:15 UTC | May 24, 10:15 UTC | 1h 0m |
| 2026-05-24 | MFO692 | - | May 24, 07:10 UTC | May 24, 08:10 UTC | 1h 0m |
| 2026-05-22 | MFO692 | - | May 22, 10:15 UTC | May 22, 10:45 UTC | 30m |
| 2026-05-22 | MFO692 | - | May 22, 07:55 UTC | May 22, 08:25 UTC | 30m |
| 2026-05-20 | MFO692 | - | May 20, 07:15 UTC | May 20, 07:40 UTC | 25m |
| 2026-05-20 | MFO692 | - | May 20, 05:50 UTC | May 20, 06:10 UTC | 20m |
| 2026-05-19 | MFO692 | - | May 19, 10:15 UTC | May 19, 10:35 UTC | 20m |
| 2026-05-19 | MFO692 | - | May 19, 07:15 UTC | May 19, 07:35 UTC | 20m |
| 2026-05-15 | MFO692 | - | May 15, 07:00 UTC | May 15, 08:55 UTC | 1h 55m |
| 2026-05-14 | - | - | May 14, 08:40 UTC | May 14, 08:50 UTC | 10m |
| 2026-05-12 | MFO692 | - | May 12, 07:15 UTC | May 12, 08:55 UTC | 1h 40m |
| 2026-05-11 | MFO692 | - | May 11, 08:20 UTC | May 11, 09:15 UTC | 55m |
| 2026-05-11 | MFO692 | - | May 11, 07:10 UTC | May 11, 07:45 UTC | 35m |
| 2026-05-08 | MFO692 | - | May 8, 09:09 UTC | May 8, 09:30 UTC | 20m |
| 2026-05-08 | MFO692 | - | May 8, 06:39 UTC | May 8, 07:29 UTC | 50m |
| 2026-05-07 | MFO692 | - | May 7, 10:30 UTC | May 7, 10:55 UTC | 25m |
| 2026-05-06 | MFO692 | - | May 6, 05:55 UTC | May 6, 06:35 UTC | 40m |
| 2026-05-04 | MFO692 | - | May 4, 07:10 UTC | May 4, 09:10 UTC | 2h 0m |
| 2026-04-30 | MFO692 | - | Apr 30, 08:15 UTC | Apr 30, 08:50 UTC | 35m |
| 2026-04-27 | MFO692 | - | Apr 27, 07:20 UTC | Apr 27, 08:50 UTC | 1h 30m |
| 2026-04-26 | MFO692 | - | Apr 26, 07:20 UTC | Apr 26, 07:40 UTC | 20m |
| 2026-04-24 | MFO692 | - | Apr 24, 09:05 UTC | Apr 24, 09:35 UTC | 30m |
| 2026-04-24 | MFO692 | - | Apr 24, 07:05 UTC | Apr 24, 07:50 UTC | 45m |
| 2026-04-22 | UNITY18 | - | Apr 22, 12:50 UTC | Apr 22, 15:35 UTC | 2h 45m |
| 2026-04-22 | UNITY18 | - | Apr 22, 07:25 UTC | Apr 22, 11:10 UTC | 3h 45m |
| 2026-04-20 | UNITY18 | - | Apr 20, 07:10 UTC | Apr 20, 09:05 UTC | 1h 55m |
| 2026-04-19 | UNITY18 | ATH → VCE | Apr 19, 14:00 UTC | Apr 19, 17:20 UTC | 3h 20m |
| 2026-04-19 | UNITY18 | - | Apr 19, 11:00 UTC | Apr 19, 11:45 UTC | 45m |
| 2026-04-19 | UNITY18 | - | Apr 19, 08:30 UTC | Apr 19, 09:20 UTC | 50m |
| 2026-04-13 | MFO692 | - | Apr 13, 08:20 UTC | Apr 13, 09:30 UTC | 1h 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 95-00101 page for operator, model, and routing details .