sensors Mode-S transponder
8A0928
ICAO 24-bit transponder address · allocated to Indonesia
Currently assigned to PK-MYD · BOEING 737-300
- Hex
- 8A0928
- Octal
- 42404450
- Decimal
- 9,046,312
- Country
- ID
- Tail
- PK-MYD
- Type
- B733
- Flights observed
- 59
- Distinct callsigns
- 17
- Country
- ID
- Last broadcast
- 17h ago
Last known position
Country allocation
The ICAO 24-bit address 8A0928 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 |
|---|---|---|---|
| MYU931 | My Indo Airlines | 9 | 2026-07-23 |
| MYU923 | - | 8 | 2026-06-24 |
| MYU912 | - | 7 | 2026-07-26 |
| PKMYD | - | 6 | 2026-07-09 |
| MYU804 | - | 6 | 2026-05-27 |
| MYU9901 | - | 5 | 2026-07-01 |
| MYU9902 | - | 4 | 2026-07-01 |
| MYU801 | - | 4 | 2026-05-27 |
| MYU9900 | My Indo Airlines | 2 | 2026-05-06 |
| MYU9914 | - | 1 | 2026-05-07 |
| MYU9913 | - | 1 | 2026-05-07 |
| MYU9912 | - | 1 | 2026-05-07 |
| MYU937 | - | 1 | 2026-05-27 |
| MYU924 | My Indo Airlines | 1 | 2026-04-26 |
| MYU910 | - | 1 | 2026-06-23 |
| MYU812 | - | 1 | 2026-05-27 |
| MYU2217 | - | 1 | 2026-05-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | MYU912 | - | Jul 26, 00:45 UTC | Jul 26, 01:00 UTC | 15m |
| 2026-07-23 | MYU931 | SIN → BPN | Jul 23, 20:40 UTC | Jul 23, 20:50 UTC | 10m |
| 2026-07-21 | MYU931 | SIN → BPN | Jul 21, 20:55 UTC | Jul 21, 21:05 UTC | 10m |
| 2026-07-16 | MYU931 | SIN → BPN | Jul 16, 20:45 UTC | Jul 16, 20:55 UTC | 10m |
| 2026-07-14 | MYU931 | - | Jul 14, 20:45 UTC | Jul 14, 20:55 UTC | 10m |
| 2026-07-09 | MYU912 | - | Jul 9, 15:30 UTC | Jul 9, 15:40 UTC | 10m |
| 2026-07-09 | PKMYD | - | Jul 9, 03:35 UTC | Jul 9, 03:50 UTC | 15m |
| 2026-07-06 | PKMYD | - | Jul 6, 09:30 UTC | Jul 6, 09:45 UTC | 15m |
| 2026-07-02 | MYU912 | - | Jul 2, 18:10 UTC | Jul 2, 18:20 UTC | 10m |
| 2026-07-02 | MYU912 | - | Jul 2, 14:45 UTC | Jul 2, 14:55 UTC | 10m |
| 2026-07-01 | MYU9901 | - | Jul 1, 22:05 UTC | Jul 1, 22:20 UTC | 15m |
| 2026-07-01 | MYU9901 | - | Jul 1, 21:00 UTC | Jul 1, 21:35 UTC | 35m |
| 2026-07-01 | MYU9902 | - | Jul 1, 17:25 UTC | Jul 1, 18:45 UTC | 1h 20m |
| 2026-06-30 | MYU912 | - | Jun 30, 14:35 UTC | Jun 30, 14:55 UTC | 20m |
| 2026-06-30 | PKMYD | - | Jun 30, 03:15 UTC | Jun 30, 03:45 UTC | 30m |
| 2026-06-27 | PKMYD | - | Jun 27, 03:25 UTC | Jun 27, 03:44 UTC | 20m |
| 2026-06-25 | MYU931 | - | Jun 25, 20:34 UTC | Jun 25, 20:45 UTC | 10m |
| 2026-06-24 | MYU9901 | - | Jun 24, 21:04 UTC | Jun 24, 22:29 UTC | 1h 25m |
| 2026-06-24 | MYU9902 | - | Jun 24, 17:34 UTC | Jun 24, 18:50 UTC | 1h 15m |
| 2026-06-24 | MYU923 | - | Jun 24, 04:50 UTC | Jun 24, 05:05 UTC | 15m |
| 2026-06-24 | MYU923 | - | Jun 24, 03:35 UTC | Jun 24, 04:05 UTC | 30m |
| 2026-06-23 | MYU912 | - | Jun 23, 08:00 UTC | Jun 23, 08:25 UTC | 25m |
| 2026-06-23 | MYU910 | - | Jun 23, 06:15 UTC | Jun 23, 06:59 UTC | 45m |
| 2026-06-18 | MYU931 | SIN → BPN | Jun 18, 20:35 UTC | Jun 18, 20:45 UTC | 10m |
| 2026-06-09 | MYU931 | SIN → BPN | Jun 9, 20:50 UTC | Jun 9, 21:00 UTC | 10m |
| 2026-06-04 | MYU931 | SIN → BPN | Jun 4, 20:35 UTC | Jun 4, 20:45 UTC | 10m |
| 2026-06-04 | MYU9902 | - | Jun 4, 15:20 UTC | Jun 4, 16:40 UTC | 1h 20m |
| 2026-06-03 | MYU9901 | - | Jun 3, 22:25 UTC | Jun 3, 22:35 UTC | 10m |
| 2026-06-03 | MYU9901 | - | Jun 3, 21:15 UTC | Jun 3, 21:45 UTC | 30m |
| 2026-06-03 | MYU9902 | - | Jun 3, 17:30 UTC | Jun 3, 19:05 UTC | 1h 35m |
| 2026-05-28 | MYU2217 | - | May 28, 05:50 UTC | May 28, 07:25 UTC | 1h 35m |
| 2026-05-27 | MYU804 | - | May 27, 21:55 UTC | May 27, 22:10 UTC | 15m |
| 2026-05-27 | MYU804 | - | May 27, 20:55 UTC | May 27, 21:25 UTC | 30m |
| 2026-05-27 | MYU801 | - | May 27, 17:20 UTC | May 27, 18:35 UTC | 1h 15m |
| 2026-05-27 | MYU812 | - | May 27, 08:30 UTC | May 27, 08:50 UTC | 20m |
| 2026-05-27 | MYU937 | - | May 27, 03:50 UTC | May 27, 03:59 UTC | 10m |
| 2026-05-20 | MYU804 | - | May 20, 21:10 UTC | May 20, 21:40 UTC | 30m |
| 2026-05-20 | MYU801 | - | May 20, 17:15 UTC | May 20, 18:30 UTC | 1h 15m |
| 2026-05-14 | MYU912 | - | May 14, 14:40 UTC | May 14, 14:55 UTC | 15m |
| 2026-05-13 | MYU804 | - | May 13, 20:55 UTC | May 13, 22:20 UTC | 1h 25m |
| 2026-05-13 | MYU801 | - | May 13, 17:05 UTC | May 13, 18:15 UTC | 1h 10m |
| 2026-05-07 | MYU9912 | - | May 7, 15:15 UTC | May 7, 15:35 UTC | 20m |
| 2026-05-07 | MYU9913 | - | May 7, 12:55 UTC | May 7, 13:05 UTC | 10m |
| 2026-05-07 | MYU9914 | - | May 7, 06:50 UTC | May 7, 07:55 UTC | 1h 5m |
| 2026-05-07 | MYU923 | SIN → CGK | May 7, 02:05 UTC | May 7, 02:20 UTC | 15m |
| 2026-05-07 | MYU923 | SIN → CGK | May 7, 01:15 UTC | May 7, 01:30 UTC | 15m |
| 2026-05-06 | MYU9900 | CGK → SIN | May 6, 21:55 UTC | May 6, 22:55 UTC | 1h 0m |
| 2026-05-06 | MYU923 | SIN → CGK | May 6, 01:30 UTC | May 6, 01:45 UTC | 15m |
| 2026-05-05 | MYU9900 | CGK → SIN | May 5, 21:35 UTC | May 5, 21:50 UTC | 15m |
| 2026-05-05 | PKMYD | - | May 5, 07:45 UTC | May 5, 08:15 UTC | 30m |
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-MYD page for operator, model, and routing details .