Not currently tracked · last seen 2d ago
- Flights observed
- 85 showing last 50
- Avg flight time
- 37m
- Typical route
- BTH → CGK
- Last seen
- 2d ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-27 | - | May 27, 05:55 UTC | May 27, 06:09 UTC | 15m |
| 2026-05-27 | - | May 27, 03:24 UTC | May 27, 03:34 UTC | 10m |
| 2026-05-26 | PDG → CGK | May 26, 11:39 UTC | May 26, 12:30 UTC | 50m |
| 2026-05-26 | CGK → PDG | May 26, 08:15 UTC | May 26, 11:09 UTC | 2h 55m |
| 2026-05-26 | YIA → PLM | May 26, 00:00 UTC | May 26, 00:24 UTC | 25m |
| 2026-05-25 | BPN → YIA | May 25, 07:10 UTC | May 25, 10:50 UTC | 3h 40m |
| 2026-05-24 | YIA → BDJ | May 24, 12:00 UTC | May 24, 12:10 UTC | 10m |
| 2026-05-24 | BPN → YIA | May 24, 10:35 UTC | May 24, 10:45 UTC | 10m |
| 2026-05-24 | YIA → BPN | May 24, 07:00 UTC | May 24, 07:15 UTC | 15m |
| 2026-05-24 | - | May 24, 01:45 UTC | May 24, 05:30 UTC | 3h 45m |
| 2026-05-23 | LOP → YIA | May 23, 23:10 UTC | May 23, 23:20 UTC | 10m |
| 2026-05-23 | CGK → LOP | May 23, 10:20 UTC | May 23, 11:05 UTC | 45m |
| 2026-05-23 | BTH → CGK | May 23, 08:55 UTC | May 23, 09:10 UTC | 15m |
| 2026-05-23 | BTH → CGK | May 23, 08:10 UTC | May 23, 08:20 UTC | 10m |
| 2026-05-23 | CGK → BTH | May 23, 05:35 UTC | May 23, 06:30 UTC | 55m |
| 2026-05-23 | BDJ → CGK | May 23, 02:50 UTC | May 23, 03:10 UTC | 20m |
| 2026-05-22 | CGK → BDJ | May 22, 23:10 UTC | May 22, 23:25 UTC | 15m |
| 2026-05-22 | DJB → CGK | May 22, 09:20 UTC | May 22, 09:35 UTC | 15m |
| 2026-05-22 | CGK → DJB | May 22, 07:15 UTC | May 22, 08:05 UTC | 50m |
| 2026-05-21 | CGK → BDJ | May 21, 23:05 UTC | May 21, 23:15 UTC | 10m |
| 2026-05-20 | PLM → CGK | May 20, 23:35 UTC | May 20, 23:50 UTC | 15m |
| 2026-05-20 | CGK → PLM | May 20, 12:15 UTC | May 20, 12:25 UTC | 10m |
| 2026-05-20 | BTH → CGK | May 20, 09:05 UTC | May 20, 09:15 UTC | 10m |
| 2026-05-20 | BTH → CGK | May 20, 08:20 UTC | May 20, 08:30 UTC | 10m |
| 2026-05-08 | PDG → BTH | May 8, 10:29 UTC | May 8, 10:59 UTC | 30m |
| 2026-05-08 | - | May 8, 04:34 UTC | May 8, 04:44 UTC | 10m |
| 2026-05-08 | CGK → PDG | May 8, 00:05 UTC | May 8, 01:04 UTC | 1h 0m |
| 2026-05-06 | PLM → CGK | May 6, 04:10 UTC | May 6, 04:25 UTC | 15m |
| 2026-05-06 | CGK → PLM | May 6, 02:05 UTC | May 6, 02:20 UTC | 15m |
| 2026-05-05 | BPN → CGK | May 5, 11:50 UTC | May 5, 12:10 UTC | 20m |
| 2026-05-03 | - | May 3, 03:10 UTC | May 3, 03:25 UTC | 15m |
| 2026-05-02 | - | May 2, 19:40 UTC | May 2, 19:55 UTC | 15m |
| 2026-05-02 | - | May 2, 06:20 UTC | May 2, 06:30 UTC | 10m |
| 2026-05-01 | PLM → CGK | May 1, 11:20 UTC | May 1, 11:35 UTC | 15m |
| 2026-05-01 | CGK → PLM | May 1, 08:55 UTC | May 1, 09:10 UTC | 15m |
| 2026-05-01 | - | May 1, 07:25 UTC | May 1, 07:40 UTC | 15m |
| 2026-05-01 | - | May 1, 04:00 UTC | May 1, 04:10 UTC | 10m |
| 2026-05-01 | PLM → CGK | May 1, 02:25 UTC | May 1, 02:35 UTC | 10m |
| 2026-05-01 | CGK → PLM | May 1, 00:20 UTC | May 1, 00:35 UTC | 15m |
| 2026-04-30 | BPN → CGK | Apr 30, 13:25 UTC | Apr 30, 13:35 UTC | 10m |
| 2026-04-30 | CGK → BPN | Apr 30, 09:00 UTC | Apr 30, 09:10 UTC | 10m |
| 2026-04-30 | DJB → CGK | Apr 30, 06:50 UTC | Apr 30, 07:05 UTC | 15m |
| 2026-04-30 | BTH → DJB | Apr 30, 05:05 UTC | Apr 30, 05:25 UTC | 20m |
| 2026-04-30 | DJB → BTH | Apr 30, 02:30 UTC | Apr 30, 02:40 UTC | 10m |
| 2026-04-30 | CGK → DJB | Apr 30, 00:05 UTC | Apr 30, 01:00 UTC | 55m |
| 2026-04-29 | CGK → KDI | Apr 29, 06:00 UTC | Apr 29, 11:40 UTC | 5h 41m |
| 2026-04-29 | TJQ → CGK | Apr 29, 02:30 UTC | Apr 29, 02:45 UTC | 15m |
| 2026-04-28 | - | Apr 28, 05:55 UTC | Apr 28, 06:10 UTC | 15m |
| 2026-04-27 | PKU → CGK | Apr 27, 23:25 UTC | Apr 27, 23:35 UTC | 10m |
| 2026-04-26 | CGK → PKU | Apr 26, 12:45 UTC | Apr 26, 13:05 UTC | 20m |
Specifications
| Registration | PK-SAG |
| Aircraft type | AIRBUS A-320 (A320) |
| Mode-S code | 8A08DE · 42404336 (octal) |
Looking for transponder-level data? View the Mode-S 8A08DE page for country allocation, callsign history, and ADS-B signal details.
PK-SAG frequently asked
What type of aircraft is PK-SAG?
PK-SAG is a AIRBUS A-320 (ICAO type code A320).
What is the Mode-S transponder code for PK-SAG?
PK-SAG broadcasts on Mode-S (ICAO 24-bit) address 8A08DE (octal 42404336). View the transponder page.
What route does PK-SAG typically fly?
PK-SAG most frequently flies between BTH and CGK based on observed flights.
Where is PK-SAG right now?
PK-SAG is not currently being tracked; last seen 2d ago.