sensors Mode-S transponder
8A094A
ICAO 24-bit transponder address · allocated to Indonesia
Currently assigned to PK-SJL · AIRBUS A-320
- Hex
- 8A094A
- Octal
- 42404512
- Decimal
- 9,046,346
- Country
- ID
- Tail
- PK-SJL
- Type
- A320
- Flights observed
- 38
- Distinct callsigns
- 20
- Country
- ID
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 8A094A 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 |
|---|---|---|---|
| SJV687 | - | 5 | 2026-05-31 |
| SJV957 | Super Air Jet | 3 | 2026-05-28 |
| SJV904 | Super Air Jet | 2 | 2026-05-27 |
| SJV874 | Super Air Jet | 2 | 2026-05-28 |
| SJV865 | Super Air Jet | 2 | 2026-04-22 |
| SJV676 | Super Air Jet | 2 | 2026-05-01 |
| SJV356 | - | 2 | 2026-05-29 |
| SJV965 | Super Air Jet | 1 | 2026-04-25 |
| SJV964 | Super Air Jet | 1 | 2026-04-25 |
| SJV956 | Super Air Jet | 1 | 2026-05-27 |
| SJV926 | Super Air Jet | 1 | 2026-04-22 |
| SJV914 | Super Air Jet | 1 | 2026-04-22 |
| SJV908 | Super Air Jet | 1 | 2026-04-23 |
| SJV903 | Super Air Jet | 1 | 2026-05-27 |
| SJV847 | - | 1 | 2026-04-13 |
| SJV819 | - | 1 | 2026-05-29 |
| SJV817 | Super Air Jet | 1 | 2026-04-24 |
| SJV777 | Super Air Jet | 1 | 2026-04-29 |
| SJV764 | Super Air Jet | 1 | 2026-04-24 |
| SJV665 | Super Air Jet | 1 | 2026-04-30 |
Recent flights last 38
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-31 | SJV687 | - | May 31, 09:55 UTC | May 31, 10:10 UTC | 15m |
| 2026-05-30 | SJV687 | - | May 30, 09:35 UTC | May 30, 09:50 UTC | 15m |
| 2026-05-29 | SJV628 | CGK → BDJ | May 29, 23:10 UTC | May 29, 23:20 UTC | 10m |
| 2026-05-29 | SJV819 | - | May 29, 10:55 UTC | May 29, 11:05 UTC | 10m |
| 2026-05-29 | SJV356 | - | May 29, 03:25 UTC | May 29, 04:10 UTC | 45m |
| 2026-05-28 | SJV874 | CGK → PLM | May 28, 12:10 UTC | May 28, 12:25 UTC | 15m |
| 2026-05-28 | SJV687 | - | May 28, 09:50 UTC | May 28, 10:05 UTC | 15m |
| 2026-05-28 | SJV957 | DTB → CGK | May 28, 03:10 UTC | May 28, 04:05 UTC | 55m |
| 2026-05-27 | SJV956 | CGK → DTB | May 27, 23:55 UTC | May 28, 01:10 UTC | 1h 15m |
| 2026-05-27 | SJV903 | PDG → CGK | May 27, 11:05 UTC | May 27, 12:25 UTC | 1h 20m |
| 2026-05-27 | SJV904 | CGK → PDG | May 27, 09:30 UTC | May 27, 09:45 UTC | 15m |
| 2026-05-27 | SJV904 | CGK → PDG | May 27, 08:45 UTC | May 27, 08:55 UTC | 10m |
| 2026-05-27 | SJV357 | - | May 27, 06:20 UTC | May 27, 06:34 UTC | 15m |
| 2026-05-27 | SJV356 | - | May 27, 03:34 UTC | May 27, 04:14 UTC | 40m |
| 2026-05-12 | SJV687 | - | May 12, 09:25 UTC | May 12, 09:40 UTC | 15m |
| 2026-05-11 | SJV513 | BPN → CGK | May 11, 05:50 UTC | May 11, 06:10 UTC | 20m |
| 2026-05-11 | SJV512 | CGK → BPN | May 11, 01:10 UTC | May 11, 01:20 UTC | 10m |
| 2026-05-01 | SJV676 | YIA → BPN | May 1, 07:05 UTC | May 1, 07:20 UTC | 15m |
| 2026-04-30 | SJV665 | BDJ → YIA | Apr 30, 12:05 UTC | May 1, 00:00 UTC | 11h 55m |
| 2026-04-30 | SJV676 | YIA → BPN | Apr 30, 07:00 UTC | Apr 30, 07:10 UTC | 10m |
| 2026-04-29 | SJV777 | LOP → YIA | Apr 29, 23:05 UTC | Apr 29, 23:15 UTC | 10m |
| 2026-04-28 | SJV121 | YIA → DPS | Apr 28, 09:20 UTC | Apr 28, 09:30 UTC | 10m |
| 2026-04-28 | SJV120 | DPS → YIA | Apr 28, 07:45 UTC | Apr 28, 07:55 UTC | 10m |
| 2026-04-26 | SJV658 | YIA → AAP | Apr 26, 04:25 UTC | Apr 26, 04:40 UTC | 15m |
| 2026-04-25 | SJV965 | KNO → PLM | Apr 25, 23:50 UTC | Apr 26, 02:55 UTC | 3h 5m |
| 2026-04-25 | SJV964 | PLM → KNO | Apr 25, 12:30 UTC | Apr 25, 12:55 UTC | 25m |
| 2026-04-24 | SJV874 | CGK → PLM | Apr 24, 12:45 UTC | Apr 24, 12:55 UTC | 10m |
| 2026-04-24 | SJV764 | CGK → LOP | Apr 24, 06:40 UTC | Apr 24, 11:05 UTC | 4h 25m |
| 2026-04-24 | SJV817 | PDG → CGK | Apr 24, 03:20 UTC | Apr 24, 03:30 UTC | 10m |
| 2026-04-23 | SJV908 | CGK → PDG | Apr 23, 23:50 UTC | Apr 24, 00:10 UTC | 20m |
| 2026-04-23 | SJV687 | - | Apr 23, 09:45 UTC | Apr 23, 09:55 UTC | 10m |
| 2026-04-23 | SJV957 | DTB → CGK | Apr 23, 04:15 UTC | Apr 23, 04:30 UTC | 15m |
| 2026-04-23 | SJV957 | DTB → CGK | Apr 23, 00:00 UTC | Apr 23, 03:30 UTC | 3h 30m |
| 2026-04-22 | SJV865 | PKU → CGK | Apr 22, 15:55 UTC | Apr 22, 16:05 UTC | 10m |
| 2026-04-22 | SJV865 | PKU → CGK | Apr 22, 14:55 UTC | Apr 22, 15:10 UTC | 15m |
| 2026-04-22 | SJV914 | CGK → PKU | Apr 22, 12:15 UTC | Apr 22, 13:15 UTC | 1h 0m |
| 2026-04-22 | SJV926 | CGK → PLM | Apr 22, 07:30 UTC | Apr 22, 07:40 UTC | 10m |
| 2026-04-13 | SJV847 | - | Apr 13, 07:20 UTC | Apr 13, 07:40 UTC | 20m |
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-SJL page for operator, model, and routing details .