sensors Mode-S transponder
8A0536
ICAO 24-bit transponder address · allocated to Indonesia
Currently assigned to PK-GII · BOEING 777-300ER
- Hex
- 8A0536
- Octal
- 42402466
- Decimal
- 9,045,302
- Country
- ID
- Tail
- PK-GII
- Type
- B77W
- Flights observed
- 188
- Distinct callsigns
- 20
- Country
- ID
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 8A0536 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 |
|---|---|---|---|
| GIA961 | - | 10 | 2026-07-10 |
| GIA089 | Garuda Indonesia | 10 | 2026-05-02 |
| GIA5413 | - | 7 | 2026-06-17 |
| GIA960 | - | 6 | 2026-07-09 |
| GIA5415 | - | 6 | 2026-06-20 |
| GIA5403 | - | 6 | 2026-06-04 |
| GIA5414 | - | 5 | 2026-06-19 |
| GIA5410 | - | 5 | 2026-06-13 |
| GIA5402 | - | 5 | 2026-06-02 |
| GIA088 | Garuda Indonesia | 5 | 2026-04-30 |
| GIA993 | - | 4 | 2026-07-12 |
| GIA5411 | - | 4 | 2026-06-14 |
| GIA5409 | - | 4 | 2026-06-12 |
| GIA5408 | - | 4 | 2026-06-11 |
| GIA5405 | - | 4 | 2026-06-06 |
| GIA2410 | - | 4 | 2026-06-24 |
| GIA2408 | - | 4 | 2026-06-22 |
| GIA2205 | - | 4 | 2026-05-10 |
| GIA2203 | - | 4 | 2026-05-08 |
| GIA992 | - | 3 | 2026-07-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-12 | GIA993 | - | Jul 12, 08:35 UTC | Jul 13, 02:15 UTC | 17h 40m |
| 2026-07-12 | GIA992 | - | Jul 12, 04:50 UTC | Jul 12, 05:01 UTC | 10m |
| 2026-07-12 | GIA993 | - | Jul 12, 02:15 UTC | Jul 12, 02:25 UTC | 10m |
| 2026-07-11 | GIA993 | - | Jul 11, 08:40 UTC | Jul 12, 01:40 UTC | 17h 0m |
| 2026-07-11 | GIA992 | - | Jul 11, 04:55 UTC | Jul 11, 05:05 UTC | 10m |
| 2026-07-10 | GIA961 | - | Jul 10, 06:10 UTC | Jul 10, 06:30 UTC | 20m |
| 2026-07-09 | GIA961 | - | Jul 9, 12:35 UTC | Jul 10, 05:30 UTC | 16h 55m |
| 2026-07-09 | GIA960 | - | Jul 9, 09:00 UTC | Jul 9, 09:10 UTC | 10m |
| 2026-07-09 | GIA961 | MED → CGK | Jul 9, 06:10 UTC | Jul 9, 06:40 UTC | 30m |
| 2026-07-08 | GIA961 | MED → CGK | Jul 8, 12:40 UTC | Jul 9, 05:40 UTC | 17h 0m |
| 2026-07-08 | GIA960 | CGK → MED | Jul 8, 09:00 UTC | Jul 8, 09:10 UTC | 10m |
| 2026-07-07 | GIA961 | MED → CGK | Jul 7, 12:55 UTC | Jul 8, 06:35 UTC | 17h 40m |
| 2026-07-07 | GIA960 | CGK → MED | Jul 7, 09:20 UTC | Jul 7, 09:30 UTC | 10m |
| 2026-07-07 | GIA961 | MED → CGK | Jul 7, 06:40 UTC | Jul 7, 07:10 UTC | 30m |
| 2026-07-06 | GIA961 | MED → CGK | Jul 6, 13:05 UTC | Jul 7, 05:55 UTC | 16h 50m |
| 2026-07-06 | GIA960 | CGK → MED | Jul 6, 09:25 UTC | Jul 6, 09:35 UTC | 10m |
| 2026-07-05 | GIA961 | MED → CGK | Jul 5, 13:15 UTC | Jul 6, 06:40 UTC | 17h 25m |
| 2026-07-05 | GIA960 | CGK → MED | Jul 5, 09:05 UTC | Jul 5, 09:15 UTC | 10m |
| 2026-07-05 | GIA961 | MED → CGK | Jul 5, 06:30 UTC | Jul 5, 06:45 UTC | 15m |
| 2026-07-04 | GIA961 | MED → CGK | Jul 4, 12:25 UTC | Jul 5, 05:50 UTC | 17h 25m |
| 2026-07-04 | GIA960 | CGK → MED | Jul 4, 08:45 UTC | Jul 4, 08:55 UTC | 10m |
| 2026-07-04 | GIA981 | - | Jul 4, 02:25 UTC | Jul 4, 02:45 UTC | 20m |
| 2026-07-03 | GIA981 | - | Jul 3, 09:10 UTC | Jul 4, 01:55 UTC | 16h 45m |
| 2026-07-03 | GIA980 | - | Jul 3, 05:35 UTC | Jul 3, 05:45 UTC | 10m |
| 2026-07-02 | GIA993 | - | Jul 2, 08:30 UTC | Jul 3, 02:15 UTC | 17h 45m |
| 2026-07-02 | GIA992 | - | Jul 2, 04:55 UTC | Jul 2, 05:05 UTC | 10m |
| 2026-06-29 | GIA1471 | - | Jun 29, 13:34 UTC | Jun 30, 01:40 UTC | 12h 6m |
| 2026-06-29 | GIA1471 | - | Jun 29, 07:15 UTC | Jun 30, 01:40 UTC | 18h 26m |
| 2026-06-29 | GIA1471 | - | Jun 29, 03:44 UTC | Jun 30, 01:40 UTC | 21h 56m |
| 2026-06-28 | GIA2413 | - | Jun 28, 12:50 UTC | Jun 29, 07:15 UTC | 18h 25m |
| 2026-06-28 | GIA2413 | - | Jun 28, 10:24 UTC | Jun 29, 07:15 UTC | 20h 50m |
| 2026-06-28 | GIA2313 | - | Jun 28, 01:29 UTC | Jun 28, 14:14 UTC | 12h 45m |
| 2026-06-27 | GIA2313 | - | Jun 27, 07:49 UTC | Jun 28, 05:09 UTC | 21h 20m |
| 2026-06-27 | GIA2313 | - | Jun 27, 06:59 UTC | Jun 28, 05:09 UTC | 22h 10m |
| 2026-06-27 | GIA2412 | - | Jun 27, 04:34 UTC | Jun 28, 02:49 UTC | 22h 15m |
| 2026-06-26 | GIA2412 | - | Jun 26, 19:20 UTC | Jun 27, 08:20 UTC | 13h 0m |
| 2026-06-26 | GIA2411 | - | Jun 26, 02:14 UTC | Jun 26, 19:55 UTC | 17h 40m |
| 2026-06-25 | GIA2411 | - | Jun 25, 23:55 UTC | Jun 26, 19:55 UTC | 20h 0m |
| 2026-06-25 | GIA2411 | - | Jun 25, 13:59 UTC | Jun 26, 03:34 UTC | 13h 35m |
| 2026-06-24 | GIA2410 | - | Jun 24, 23:45 UTC | Jun 25, 18:04 UTC | 18h 20m |
| 2026-06-24 | GIA2410 | - | Jun 24, 23:04 UTC | Jun 25, 18:04 UTC | 19h 0m |
| 2026-06-24 | GIA2410 | - | Jun 24, 16:59 UTC | Jun 25, 14:29 UTC | 21h 30m |
| 2026-06-24 | GIA2410 | - | Jun 24, 13:40 UTC | Jun 25, 02:45 UTC | 13h 5m |
| 2026-06-24 | GIA2310 | - | Jun 24, 01:34 UTC | Jun 25, 01:30 UTC | 23h 55m |
| 2026-06-24 | GIA2310 | - | Jun 24, 01:19 UTC | Jun 24, 23:29 UTC | 22h 10m |
| 2026-06-23 | GIA2409 | - | Jun 23, 21:49 UTC | Jun 24, 17:20 UTC | 19h 30m |
| 2026-06-23 | GIA2409 | - | Jun 23, 16:35 UTC | Jun 24, 14:55 UTC | 22h 20m |
| 2026-06-23 | GIA2409 | - | Jun 23, 13:00 UTC | Jun 24, 01:49 UTC | 12h 50m |
| 2026-06-23 | GIA2309 | - | Jun 23, 00:09 UTC | Jun 23, 22:29 UTC | 22h 20m |
| 2026-06-22 | GIA2408 | - | Jun 22, 21:00 UTC | Jun 23, 16:50 UTC | 19h 50m |
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-GII page for operator, model, and routing details .