sensors Mode-S transponder
8A0363
ICAO 24-bit transponder address · allocated to Indonesia
Currently assigned to PK-CLF · BOEING 737-500
- Hex
- 8A0363
- Octal
- 42401543
- Decimal
- 9,044,835
- Country
- ID
- Tail
- PK-CLF
- Type
- B735
- Flights observed
- 140
- Distinct callsigns
- 20
- Country
- ID
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 8A0363 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| SJY713 | - | 19 | 2026-07-12 |
| SJY712 | - | 15 | 2026-07-12 |
| SJY593 | - | 15 | 2026-07-13 |
| SJY594 | - | 12 | 2026-06-24 |
| SJY580 | - | 12 | 2026-07-08 |
| SJY581 | - | 8 | 2026-07-06 |
| SJY592 | Sriwijaya Air | 7 | 2026-06-07 |
| SJY077 | - | 6 | 2026-06-08 |
| SJY055 | - | 6 | 2026-07-14 |
| SJY273 | - | 5 | 2026-07-02 |
| SJY054 | Sriwijaya Air | 5 | 2026-05-30 |
| SJY9090 | - | 3 | 2026-05-20 |
| SJY272 | - | 3 | 2026-07-02 |
| SJY073 | - | 3 | 2026-07-02 |
| SJY061 | Sriwijaya Air | 3 | 2026-04-24 |
| SJY060 | Sriwijaya Air | 3 | 2026-04-24 |
| SJY9091 | - | 2 | 2026-05-20 |
| SJY185 | - | 2 | 2026-07-02 |
| SJY075 | - | 2 | 2026-07-03 |
| SJY9190 | - | 1 | 2026-05-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | SJY055 | - | Jul 14, 07:15 UTC | Jul 14, 07:35 UTC | 20m |
| 2026-07-13 | SJY593 | - | Jul 13, 18:40 UTC | Jul 13, 19:00 UTC | 20m |
| 2026-07-12 | SJY713 | - | Jul 12, 14:30 UTC | Jul 12, 14:45 UTC | 15m |
| 2026-07-12 | SJY712 | - | Jul 12, 13:05 UTC | Jul 12, 13:15 UTC | 10m |
| 2026-07-11 | SJY713 | - | Jul 11, 13:25 UTC | Jul 11, 13:35 UTC | 10m |
| 2026-07-11 | SJY712 | - | Jul 11, 12:05 UTC | Jul 11, 12:15 UTC | 10m |
| 2026-07-10 | SJY713 | - | Jul 10, 15:10 UTC | Jul 11, 12:15 UTC | 21h 5m |
| 2026-07-10 | SJY7130 | - | Jul 10, 04:45 UTC | Jul 10, 14:00 UTC | 9h 15m |
| 2026-07-09 | SJY712 | UPG → YIA | Jul 9, 11:55 UTC | Jul 9, 12:05 UTC | 10m |
| 2026-07-08 | SJY580 | - | Jul 8, 08:20 UTC | Jul 8, 08:45 UTC | 25m |
| 2026-07-07 | SJY713 | - | Jul 7, 12:50 UTC | Jul 8, 06:30 UTC | 17h 40m |
| 2026-07-07 | SJY712 | UPG → YIA | Jul 7, 11:35 UTC | Jul 7, 11:45 UTC | 10m |
| 2026-07-06 | SJY580 | - | Jul 6, 07:40 UTC | Jul 6, 08:05 UTC | 25m |
| 2026-07-06 | SJY581 | - | Jul 6, 06:05 UTC | Jul 6, 06:20 UTC | 15m |
| 2026-07-05 | SJY580 | - | Jul 5, 08:30 UTC | Jul 5, 08:55 UTC | 25m |
| 2026-07-05 | SJY581 | - | Jul 5, 06:25 UTC | Jul 5, 06:40 UTC | 15m |
| 2026-07-04 | SJY580 | - | Jul 4, 08:50 UTC | Jul 4, 09:15 UTC | 25m |
| 2026-07-04 | SJY581 | - | Jul 4, 06:30 UTC | Jul 4, 06:45 UTC | 15m |
| 2026-07-03 | SJY580 | - | Jul 3, 07:50 UTC | Jul 3, 08:25 UTC | 35m |
| 2026-07-03 | SJY5401 | - | Jul 3, 05:10 UTC | Jul 3, 05:25 UTC | 15m |
| 2026-07-03 | SJY5400 | - | Jul 3, 03:05 UTC | Jul 3, 03:15 UTC | 10m |
| 2026-07-03 | SJY075 | - | Jul 3, 01:35 UTC | Jul 3, 01:50 UTC | 15m |
| 2026-07-02 | SJY273 | - | Jul 2, 15:05 UTC | Jul 2, 15:20 UTC | 15m |
| 2026-07-02 | SJY272 | - | Jul 2, 11:25 UTC | Jul 2, 12:05 UTC | 40m |
| 2026-07-02 | SJY185 | - | Jul 2, 10:00 UTC | Jul 2, 10:15 UTC | 15m |
| 2026-07-02 | SJY073 | - | Jul 2, 05:35 UTC | Jul 2, 05:50 UTC | 15m |
| 2026-07-02 | SJY055 | - | Jul 2, 01:20 UTC | Jul 2, 01:40 UTC | 20m |
| 2026-07-01 | SJY273 | - | Jul 1, 11:15 UTC | Jul 1, 15:05 UTC | 3h 50m |
| 2026-07-01 | SJY185 | - | Jul 1, 09:35 UTC | Jul 1, 09:55 UTC | 20m |
| 2026-07-01 | SJY184 | - | Jul 1, 06:40 UTC | Jul 1, 06:50 UTC | 10m |
| 2026-06-29 | SJY593 | - | Jun 29, 22:05 UTC | Jun 30, 14:45 UTC | 16h 41m |
| 2026-06-29 | SJY593 | - | Jun 29, 11:45 UTC | Jun 29, 12:14 UTC | 30m |
| 2026-06-27 | SJY713 | - | Jun 27, 13:00 UTC | Jun 27, 13:09 UTC | 10m |
| 2026-06-27 | SJY712 | UPG → YIA | Jun 27, 11:30 UTC | Jun 27, 11:39 UTC | 10m |
| 2026-06-24 | SJY594 | - | Jun 24, 21:44 UTC | Jun 24, 22:19 UTC | 35m |
| 2026-06-24 | SJY593 | - | Jun 24, 16:34 UTC | Jun 24, 16:54 UTC | 20m |
| 2026-06-24 | SJY713 | - | Jun 24, 11:54 UTC | Jun 24, 12:04 UTC | 10m |
| 2026-06-24 | SJY712 | UPG → YIA | Jun 24, 10:35 UTC | Jun 24, 10:45 UTC | 10m |
| 2026-06-23 | SJY713 | - | Jun 23, 13:29 UTC | Jun 24, 10:45 UTC | 21h 15m |
| 2026-06-23 | SJY712 | UPG → YIA | Jun 23, 12:05 UTC | Jun 23, 12:15 UTC | 10m |
| 2026-06-22 | SJY713 | - | Jun 22, 13:10 UTC | Jun 22, 13:25 UTC | 15m |
| 2026-06-22 | SJY712 | UPG → YIA | Jun 22, 11:44 UTC | Jun 22, 11:54 UTC | 10m |
| 2026-06-21 | SJY580 | - | Jun 21, 13:59 UTC | Jun 21, 14:34 UTC | 35m |
| 2026-06-21 | SJY055 | - | Jun 21, 12:14 UTC | Jun 21, 12:24 UTC | 10m |
| 2026-06-21 | SJY581 | - | Jun 21, 07:49 UTC | Jun 21, 08:20 UTC | 30m |
| 2026-06-20 | SJY581 | - | Jun 20, 12:14 UTC | Jun 21, 08:20 UTC | 20h 5m |
| 2026-06-20 | SJY712 | UPG → YIA | Jun 20, 10:44 UTC | Jun 20, 10:55 UTC | 10m |
| 2026-06-19 | SJY594 | - | Jun 19, 22:24 UTC | Jun 19, 23:00 UTC | 35m |
| 2026-06-19 | SJY593 | - | Jun 19, 16:39 UTC | Jun 19, 16:49 UTC | 10m |
| 2026-06-19 | SJY713 | - | Jun 19, 12:19 UTC | Jun 19, 12:29 UTC | 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 PK-CLF page for operator, model, and routing details .