sensors Mode-S transponder
8A034E
ICAO 24-bit transponder address · allocated to Indonesia
Currently assigned to PK-CLE · BOEING 737-500
- Hex
- 8A034E
- Octal
- 42401516
- Decimal
- 9,044,814
- Country
- ID
- Tail
- PK-CLE
- Type
- B735
- Flights observed
- 56
- Distinct callsigns
- 17
- Country
- ID
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 8A034E 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 17 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| SJY713 | Sriwijaya Air | 10 | 2026-05-15 |
| SJY712 | Sriwijaya Air | 10 | 2026-05-15 |
| SJY593 | Sriwijaya Air | 8 | 2026-06-01 |
| SJY594 | Sriwijaya Air | 5 | 2026-06-01 |
| SJY592 | Sriwijaya Air | 4 | 2026-05-31 |
| SJY077 | - | 4 | 2026-05-31 |
| SJY184 | Sriwijaya Air | 3 | 2026-05-22 |
| SJY073 | - | 2 | 2026-05-22 |
| SJY055 | Sriwijaya Air | 2 | 2026-05-22 |
| SJY598 | Sriwijaya Air | 1 | 2026-05-17 |
| SJY580 | Sriwijaya Air | 1 | 2026-05-18 |
| SJY272 | Sriwijaya Air | 1 | 2026-05-01 |
| SJY185 | Sriwijaya Air | 1 | 2026-04-19 |
| SJY072 | - | 1 | 2026-05-22 |
| SJY061 | Sriwijaya Air | 1 | 2026-04-19 |
| SJY060 | Sriwijaya Air | 1 | 2026-04-19 |
| SJY054 | Sriwijaya Air | 1 | 2026-05-21 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-01 | SJY594 | CGK → UPG | Jun 1, 21:45 UTC | Jun 1, 22:10 UTC | 25m |
| 2026-06-01 | SJY593 | UPG → CGK | Jun 1, 11:45 UTC | Jun 1, 12:20 UTC | 35m |
| 2026-05-31 | SJY592 | CGK → UPG | May 31, 14:55 UTC | Jun 1, 12:20 UTC | 21h 25m |
| 2026-05-31 | SJY077 | - | May 31, 11:15 UTC | May 31, 11:35 UTC | 20m |
| 2026-05-29 | SJY594 | CGK → UPG | May 29, 21:40 UTC | May 29, 22:05 UTC | 25m |
| 2026-05-29 | SJY077 | - | May 29, 11:10 UTC | May 29, 11:35 UTC | 25m |
| 2026-05-29 | SJY593 | UPG → CGK | May 29, 07:15 UTC | May 29, 07:40 UTC | 25m |
| 2026-05-27 | SJY077 | - | May 27, 12:50 UTC | May 27, 13:05 UTC | 15m |
| 2026-05-24 | SJY592 | CGK → UPG | May 24, 15:30 UTC | May 24, 16:15 UTC | 45m |
| 2026-05-24 | SJY593 | UPG → CGK | May 24, 11:10 UTC | May 24, 11:35 UTC | 25m |
| 2026-05-22 | SJY594 | CGK → UPG | May 22, 21:55 UTC | May 22, 22:30 UTC | 35m |
| 2026-05-22 | SJY184 | CGK → PNK | May 22, 06:50 UTC | May 22, 07:00 UTC | 10m |
| 2026-05-22 | SJY073 | - | May 22, 05:40 UTC | May 22, 05:50 UTC | 10m |
| 2026-05-22 | SJY072 | - | May 22, 03:10 UTC | May 22, 03:20 UTC | 10m |
| 2026-05-22 | SJY055 | TJQ → CGK | May 22, 01:40 UTC | May 22, 01:50 UTC | 10m |
| 2026-05-21 | SJY054 | CGK → TJQ | May 21, 23:25 UTC | May 21, 23:35 UTC | 10m |
| 2026-05-21 | SJY073 | - | May 21, 05:10 UTC | May 21, 05:25 UTC | 15m |
| 2026-05-20 | SJY184 | CGK → PNK | May 20, 10:30 UTC | May 20, 10:40 UTC | 10m |
| 2026-05-18 | SJY580 | CGK → UPG | May 18, 15:10 UTC | May 18, 15:35 UTC | 25m |
| 2026-05-18 | SJY055 | TJQ → CGK | May 18, 13:05 UTC | May 18, 13:20 UTC | 15m |
| 2026-05-17 | SJY598 | CGK → UPG | May 17, 18:40 UTC | May 18, 09:25 UTC | 14h 45m |
| 2026-05-17 | SJY184 | CGK → PNK | May 17, 12:40 UTC | May 17, 12:50 UTC | 10m |
| 2026-05-15 | SJY713 | YIA → UPG | May 15, 16:45 UTC | May 15, 17:00 UTC | 15m |
| 2026-05-15 | SJY712 | UPG → YIA | May 15, 15:30 UTC | May 15, 15:40 UTC | 10m |
| 2026-05-13 | SJY592 | CGK → UPG | May 13, 15:20 UTC | May 13, 15:55 UTC | 35m |
| 2026-05-13 | SJY593 | UPG → CGK | May 13, 11:10 UTC | May 13, 11:50 UTC | 40m |
| 2026-05-12 | SJY712 | UPG → YIA | May 12, 12:40 UTC | May 12, 12:50 UTC | 10m |
| 2026-05-11 | SJY713 | YIA → UPG | May 11, 13:40 UTC | May 11, 13:55 UTC | 15m |
| 2026-05-11 | SJY712 | UPG → YIA | May 11, 12:20 UTC | May 11, 12:30 UTC | 10m |
| 2026-05-09 | SJY713 | YIA → UPG | May 9, 13:20 UTC | May 9, 13:30 UTC | 10m |
| 2026-05-09 | SJY712 | UPG → YIA | May 9, 12:00 UTC | May 9, 12:15 UTC | 15m |
| 2026-05-08 | SJY594 | CGK → UPG | May 8, 21:45 UTC | May 8, 22:20 UTC | 35m |
| 2026-05-08 | SJY593 | UPG → CGK | May 8, 17:35 UTC | May 8, 18:00 UTC | 25m |
| 2026-05-07 | SJY713 | YIA → UPG | May 7, 13:25 UTC | May 7, 13:35 UTC | 10m |
| 2026-05-07 | SJY712 | UPG → YIA | May 7, 12:00 UTC | May 7, 12:15 UTC | 15m |
| 2026-05-05 | SJY713 | YIA → UPG | May 5, 14:05 UTC | May 5, 14:15 UTC | 10m |
| 2026-05-05 | SJY712 | UPG → YIA | May 5, 12:40 UTC | May 5, 12:50 UTC | 10m |
| 2026-05-03 | SJY713 | YIA → UPG | May 3, 13:35 UTC | May 3, 13:45 UTC | 10m |
| 2026-05-03 | SJY712 | UPG → YIA | May 3, 12:15 UTC | May 3, 12:25 UTC | 10m |
| 2026-05-02 | SJY713 | YIA → UPG | May 2, 12:55 UTC | May 2, 13:10 UTC | 15m |
| 2026-05-01 | SJY594 | CGK → UPG | May 1, 21:50 UTC | May 2, 11:40 UTC | 13h 51m |
| 2026-05-01 | SJY272 | CGK → DPS | May 1, 11:30 UTC | May 1, 15:30 UTC | 4h 0m |
| 2026-05-01 | SJY593 | UPG → CGK | May 1, 09:40 UTC | May 1, 10:10 UTC | 30m |
| 2026-04-25 | SJY713 | YIA → UPG | Apr 25, 12:20 UTC | Apr 25, 12:35 UTC | 15m |
| 2026-04-25 | SJY712 | UPG → YIA | Apr 25, 11:00 UTC | Apr 25, 11:10 UTC | 10m |
| 2026-04-24 | SJY713 | YIA → UPG | Apr 24, 12:35 UTC | Apr 25, 11:10 UTC | 22h 35m |
| 2026-04-24 | SJY712 | UPG → YIA | Apr 24, 11:10 UTC | Apr 24, 11:25 UTC | 15m |
| 2026-04-20 | SJY592 | CGK → UPG | Apr 20, 14:40 UTC | Apr 20, 15:00 UTC | 20m |
| 2026-04-20 | SJY077 | - | Apr 20, 13:05 UTC | Apr 20, 13:20 UTC | 15m |
| 2026-04-20 | SJY593 | UPG → CGK | Apr 20, 08:05 UTC | Apr 20, 08:20 UTC | 15m |
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-CLE page for operator, model, and routing details .