sensors Mode-S transponder
4CC571
ICAO 24-bit transponder address
Currently assigned to TF-HNH · BELL 407
- Hex
- 4CC571
- Octal
- 23142561
- Decimal
- 5,031,281
- Tail
- TF-HNH
- Type
- B407
- Flights observed
- 44
- Distinct callsigns
- 1
- Country
- -
- Last broadcast
- 12h ago
Last known position
Callsign history 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| TFHNH | - | 44 | 2026-06-03 |
Recent flights last 44
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-03 | TFHNH | - | Jun 3, 12:45 UTC | Jun 3, 13:45 UTC | 1h 0m |
| 2026-06-03 | TFHNH | - | Jun 3, 11:20 UTC | Jun 3, 11:30 UTC | 10m |
| 2026-06-02 | TFHNH | - | Jun 2, 16:55 UTC | Jun 2, 17:05 UTC | 10m |
| 2026-05-30 | TFHNH | - | May 30, 15:10 UTC | May 30, 15:15 UTC | 5m |
| 2026-05-30 | TFHNH | - | May 30, 11:20 UTC | May 30, 12:25 UTC | 1h 5m |
| 2026-05-30 | TFHNH | - | May 30, 10:25 UTC | May 30, 11:00 UTC | 35m |
| 2026-05-30 | TFHNH | - | May 30, 09:00 UTC | May 30, 09:10 UTC | 10m |
| 2026-05-30 | TFHNH | - | May 30, 08:10 UTC | May 30, 08:20 UTC | 10m |
| 2026-05-27 | TFHNH | - | May 27, 11:25 UTC | May 27, 12:10 UTC | 45m |
| 2026-05-27 | TFHNH | RKV → RKV | May 27, 10:15 UTC | May 27, 11:10 UTC | 55m |
| 2026-05-21 | TFHNH | - | May 21, 13:45 UTC | May 21, 13:55 UTC | 10m |
| 2026-05-21 | TFHNH | - | May 21, 12:25 UTC | May 21, 12:35 UTC | 10m |
| 2026-05-20 | TFHNH | - | May 20, 18:10 UTC | May 20, 18:20 UTC | 10m |
| 2026-05-20 | TFHNH | - | May 20, 15:55 UTC | May 20, 16:05 UTC | 10m |
| 2026-05-20 | TFHNH | - | May 20, 13:30 UTC | May 20, 13:40 UTC | 10m |
| 2026-05-20 | TFHNH | - | May 20, 10:25 UTC | May 20, 10:35 UTC | 10m |
| 2026-05-18 | TFHNH | - | May 18, 11:05 UTC | May 18, 12:00 UTC | 55m |
| 2026-05-18 | TFHNH | - | May 18, 10:05 UTC | May 18, 10:15 UTC | 10m |
| 2026-05-17 | TFHNH | - | May 17, 17:10 UTC | May 17, 17:20 UTC | 10m |
| 2026-05-17 | TFHNH | - | May 17, 16:20 UTC | May 17, 16:40 UTC | 20m |
| 2026-05-17 | TFHNH | - | May 17, 13:01 UTC | May 17, 13:10 UTC | 10m |
| 2026-05-17 | TFHNH | - | May 17, 10:15 UTC | May 17, 10:25 UTC | 10m |
| 2026-05-13 | TFHNH | - | May 13, 19:05 UTC | May 13, 19:20 UTC | 15m |
| 2026-05-13 | TFHNH | - | May 13, 10:55 UTC | May 13, 11:05 UTC | 10m |
| 2026-05-13 | TFHNH | - | May 13, 08:20 UTC | May 13, 09:00 UTC | 40m |
| 2026-05-08 | TFHNH | - | May 8, 18:00 UTC | May 8, 19:25 UTC | 1h 25m |
| 2026-05-08 | TFHNH | - | May 8, 17:05 UTC | May 8, 17:15 UTC | 10m |
| 2026-05-03 | TFHNH | - | May 3, 21:20 UTC | May 3, 21:35 UTC | 15m |
| 2026-05-03 | TFHNH | - | May 3, 10:05 UTC | May 3, 10:20 UTC | 15m |
| 2026-05-02 | TFHNH | RKV → RKV | May 2, 14:10 UTC | May 2, 15:10 UTC | 1h 0m |
| 2026-05-01 | TFHNH | - | May 1, 13:45 UTC | May 1, 13:55 UTC | 10m |
| 2026-05-01 | TFHNH | - | May 1, 11:00 UTC | May 1, 11:10 UTC | 10m |
| 2026-04-30 | TFHNH | RKV → RKV | Apr 30, 16:00 UTC | Apr 30, 16:20 UTC | 20m |
| 2026-04-26 | TFHNH | RKV → RKV | Apr 26, 10:15 UTC | Apr 26, 11:15 UTC | 1h 0m |
| 2026-04-25 | TFHNH | - | Apr 25, 15:55 UTC | Apr 25, 16:05 UTC | 10m |
| 2026-04-25 | TFHNH | - | Apr 25, 13:30 UTC | Apr 25, 13:40 UTC | 10m |
| 2026-04-25 | TFHNH | - | Apr 25, 12:50 UTC | Apr 25, 13:00 UTC | 10m |
| 2026-04-25 | TFHNH | - | Apr 25, 09:50 UTC | Apr 25, 10:35 UTC | 45m |
| 2026-04-23 | TFHNH | RKV → RKV | Apr 23, 13:55 UTC | Apr 23, 15:10 UTC | 1h 15m |
| 2026-04-19 | TFHNH | - | Apr 19, 16:20 UTC | Apr 19, 16:30 UTC | 10m |
| 2026-04-19 | TFHNH | - | Apr 19, 13:25 UTC | Apr 19, 13:35 UTC | 10m |
| 2026-04-19 | TFHNH | RKV → RKV | Apr 19, 11:25 UTC | Apr 19, 12:55 UTC | 1h 30m |
| 2026-04-18 | TFHNH | - | Apr 18, 11:20 UTC | Apr 18, 12:20 UTC | 1h 0m |
| 2026-04-18 | TFHNH | - | Apr 18, 08:55 UTC | Apr 18, 10:40 UTC | 1h 45m |
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 TF-HNH page for operator, model, and routing details .