sensors Mode-S transponder
8A0447
ICAO 24-bit transponder address · allocated to Indonesia
Currently assigned to PK-TFS · EMBRAER EMB-135 Legacy
- Hex
- 8A0447
- Octal
- 42402107
- Decimal
- 9,045,063
- Country
- ID
- Tail
- PK-TFS
- Type
- E35L
- Flights observed
- 55
- Distinct callsigns
- 1
- Country
- ID
- Last broadcast
- 10h ago
Last known position
Country allocation
The ICAO 24-bit address 8A0447 falls within the block assigned to Indonesia (ID) by ICAO Annex 10, Volume III. Every aircraft registered in Indonesia receives a permanent address from this block at the time of registration; the address stays with the airframe even if the aircraft is re-registered to a different operator within the country.
Callsign history 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| PKTFS | - | 55 | 2026-07-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-23 | PKTFS | - | Jul 23, 00:35 UTC | Jul 23, 01:15 UTC | 40m |
| 2026-07-21 | PKTFS | - | Jul 21, 06:25 UTC | Jul 21, 07:00 UTC | 35m |
| 2026-07-21 | PKTFS | - | Jul 21, 04:10 UTC | Jul 21, 05:10 UTC | 1h 0m |
| 2026-07-20 | PKTFS | - | Jul 20, 08:35 UTC | Jul 20, 08:45 UTC | 10m |
| 2026-07-20 | PKTFS | - | Jul 20, 02:05 UTC | Jul 20, 02:55 UTC | 50m |
| 2026-07-17 | PKTFS | - | Jul 17, 01:20 UTC | Jul 17, 02:05 UTC | 45m |
| 2026-07-16 | PKTFS | - | Jul 16, 04:25 UTC | Jul 16, 04:45 UTC | 20m |
| 2026-07-13 | PKTFS | - | Jul 13, 13:50 UTC | Jul 13, 14:05 UTC | 15m |
| 2026-07-13 | PKTFS | - | Jul 13, 09:05 UTC | Jul 13, 10:55 UTC | 1h 50m |
| 2026-07-12 | PKTFS | - | Jul 12, 11:30 UTC | Jul 12, 12:01 UTC | 30m |
| 2026-07-11 | PKTFS | - | Jul 11, 08:55 UTC | Jul 11, 09:15 UTC | 20m |
| 2026-07-11 | PKTFS | - | Jul 11, 08:01 UTC | Jul 11, 08:15 UTC | 15m |
| 2026-07-11 | PKTFS | - | Jul 11, 01:15 UTC | Jul 11, 07:25 UTC | 6h 10m |
| 2026-07-10 | PKTFS | - | Jul 10, 09:25 UTC | Jul 10, 09:35 UTC | 10m |
| 2026-07-05 | PKTFS | - | Jul 5, 12:55 UTC | Jul 5, 13:05 UTC | 10m |
| 2026-07-04 | PKTFS | - | Jul 4, 22:05 UTC | Jul 4, 22:50 UTC | 45m |
| 2026-06-25 | PKTFS | - | Jun 25, 05:50 UTC | Jun 25, 06:25 UTC | 35m |
| 2026-06-25 | PKTFS | - | Jun 25, 03:34 UTC | Jun 25, 05:09 UTC | 1h 35m |
| 2026-06-21 | PKTFS | - | Jun 21, 09:49 UTC | Jun 21, 10:44 UTC | 55m |
| 2026-06-20 | PKTFS | - | Jun 20, 05:49 UTC | Jun 20, 06:35 UTC | 45m |
| 2026-06-18 | PKTFS | - | Jun 18, 09:50 UTC | Jun 18, 13:40 UTC | 3h 50m |
| 2026-06-12 | PKTFS | - | Jun 12, 02:45 UTC | Jun 12, 03:30 UTC | 45m |
| 2026-06-11 | PKTFS | - | Jun 11, 17:10 UTC | Jun 11, 17:20 UTC | 10m |
| 2026-06-11 | PKTFS | - | Jun 11, 15:35 UTC | Jun 11, 15:55 UTC | 20m |
| 2026-06-09 | PKTFS | - | Jun 9, 13:55 UTC | Jun 9, 18:15 UTC | 4h 20m |
| 2026-06-07 | PKTFS | - | Jun 7, 11:45 UTC | Jun 7, 13:10 UTC | 1h 25m |
| 2026-05-30 | PKTFS | - | May 30, 10:40 UTC | May 30, 11:10 UTC | 30m |
| 2026-05-28 | PKTFS | - | May 28, 06:45 UTC | May 28, 07:45 UTC | 1h 0m |
| 2026-05-27 | PKTFS | - | May 27, 01:05 UTC | May 27, 01:49 UTC | 45m |
| 2026-05-26 | PKTFS | - | May 26, 04:00 UTC | May 26, 09:04 UTC | 5h 5m |
| 2026-05-25 | PKTFS | - | May 25, 09:05 UTC | May 25, 09:30 UTC | 25m |
| 2026-05-25 | PKTFS | - | May 25, 03:15 UTC | May 25, 04:10 UTC | 55m |
| 2026-05-24 | PKTFS | - | May 24, 02:05 UTC | May 24, 02:50 UTC | 45m |
| 2026-05-23 | PKTFS | - | May 23, 10:10 UTC | May 23, 10:20 UTC | 10m |
| 2026-05-20 | PKTFS | - | May 20, 22:15 UTC | May 20, 22:25 UTC | 10m |
| 2026-05-18 | PKTFS | - | May 18, 23:10 UTC | May 18, 23:50 UTC | 40m |
| 2026-05-16 | PKTFS | - | May 16, 01:45 UTC | May 16, 02:15 UTC | 30m |
| 2026-05-15 | PKTFS | - | May 15, 17:20 UTC | May 15, 17:35 UTC | 15m |
| 2026-05-15 | PKTFS | - | May 15, 15:55 UTC | May 15, 16:20 UTC | 25m |
| 2026-05-13 | PKTFS | - | May 13, 12:10 UTC | May 13, 13:15 UTC | 1h 5m |
| 2026-05-09 | PKTFS | - | May 9, 07:05 UTC | May 9, 07:50 UTC | 45m |
| 2026-05-07 | PKTFS | - | May 7, 09:00 UTC | May 7, 09:15 UTC | 15m |
| 2026-05-07 | PKTFS | - | May 7, 05:10 UTC | May 7, 06:10 UTC | 1h 0m |
| 2026-05-07 | PKTFS | - | May 7, 04:25 UTC | May 7, 04:40 UTC | 15m |
| 2026-05-04 | PKTFS | - | May 4, 03:35 UTC | May 4, 04:00 UTC | 25m |
| 2026-04-29 | PKTFS | - | Apr 29, 09:15 UTC | Apr 29, 09:45 UTC | 30m |
| 2026-04-29 | PKTFS | - | Apr 29, 00:34 UTC | Apr 29, 00:59 UTC | 25m |
| 2026-04-26 | PKTFS | - | Apr 26, 02:15 UTC | Apr 26, 02:35 UTC | 20m |
| 2026-04-25 | PKTFS | - | Apr 25, 06:50 UTC | Apr 25, 07:10 UTC | 20m |
| 2026-04-24 | PKTFS | - | Apr 24, 11:15 UTC | Apr 24, 11:40 UTC | 25m |
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 PK-TFS page for operator, model, and routing details .