sensors Mode-S transponder
898055
ICAO 24-bit transponder address · allocated to Papua New Guinea
Currently assigned to P2-PXV · BOEING 767-300
- Hex
- 898055
- Octal
- 42300125
- Decimal
- 9,011,285
- Country
- PG
- Tail
- P2-PXV
- Type
- B763
- Flights observed
- 172
- Distinct callsigns
- 5
- Country
- PG
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 898055 falls within the block assigned to Papua New Guinea (PG) by ICAO Annex 10, Volume III. Every aircraft registered in Papua New Guinea 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 5 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | ANG4 | - | Jul 13, 01:40 UTC | Jul 13, 02:55 UTC | 1h 15m |
| 2026-07-12 | ANG19 | HKG → BNE | Jul 12, 13:01 UTC | Jul 12, 23:30 UTC | 10h 30m |
| 2026-07-12 | ANG8 | - | Jul 12, 11:01 UTC | Jul 12, 11:15 UTC | 15m |
| 2026-07-12 | ANG8 | - | Jul 12, 09:30 UTC | Jul 12, 10:05 UTC | 35m |
| 2026-07-11 | ANG4 | - | Jul 11, 01:30 UTC | Jul 11, 02:50 UTC | 1h 20m |
| 2026-07-10 | ANG3 | - | Jul 10, 14:20 UTC | Jul 10, 23:45 UTC | 9h 26m |
| 2026-07-10 | ANG19 | - | Jul 10, 13:15 UTC | Jul 10, 13:25 UTC | 10m |
| 2026-07-10 | ANG8 | - | Jul 10, 11:10 UTC | Jul 10, 11:30 UTC | 20m |
| 2026-07-10 | ANG8 | - | Jul 10, 09:40 UTC | Jul 10, 10:20 UTC | 40m |
| 2026-07-09 | ANG4 | - | Jul 9, 02:35 UTC | Jul 9, 03:55 UTC | 1h 20m |
| 2026-07-08 | ANG19 | - | Jul 8, 14:45 UTC | Jul 9, 00:55 UTC | 10h 10m |
| 2026-07-08 | ANG8 | - | Jul 8, 11:05 UTC | Jul 8, 11:20 UTC | 15m |
| 2026-07-08 | ANG8 | - | Jul 8, 09:20 UTC | Jul 8, 10:10 UTC | 50m |
| 2026-07-07 | ANG4 | - | Jul 7, 05:45 UTC | Jul 7, 07:15 UTC | 1h 30m |
| 2026-07-06 | ANG3 | HKG → BNE | Jul 6, 14:55 UTC | Jul 7, 04:20 UTC | 13h 25m |
| 2026-07-06 | ANG8 | - | Jul 6, 12:45 UTC | Jul 6, 13:05 UTC | 20m |
| 2026-07-06 | ANG4 | - | Jul 6, 02:20 UTC | Jul 6, 12:05 UTC | 9h 45m |
| 2026-07-05 | ANG3 | - | Jul 5, 14:20 UTC | Jul 5, 23:25 UTC | 9h 5m |
| 2026-07-05 | ANG19 | - | Jul 5, 13:15 UTC | Jul 5, 13:35 UTC | 20m |
| 2026-07-05 | ANG8 | - | Jul 5, 11:05 UTC | Jul 5, 11:20 UTC | 15m |
| 2026-07-05 | ANG8 | - | Jul 5, 09:25 UTC | Jul 5, 10:10 UTC | 45m |
| 2026-07-04 | ANG4 | - | Jul 4, 01:15 UTC | Jul 4, 02:45 UTC | 1h 30m |
| 2026-07-03 | ANG3 | - | Jul 3, 14:40 UTC | Jul 3, 23:35 UTC | 8h 55m |
| 2026-07-03 | ANG19 | - | Jul 3, 13:30 UTC | Jul 3, 13:45 UTC | 15m |
| 2026-07-03 | ANG8 | - | Jul 3, 11:10 UTC | Jul 3, 11:20 UTC | 10m |
| 2026-07-03 | ANG8 | - | Jul 3, 09:25 UTC | Jul 3, 10:40 UTC | 1h 15m |
| 2026-07-02 | ANG4 | - | Jul 2, 01:20 UTC | Jul 2, 02:50 UTC | 1h 30m |
| 2026-07-01 | ANG19 | HKG → BNE | Jul 1, 13:35 UTC | Jul 1, 23:45 UTC | 10h 10m |
| 2026-07-01 | ANG8 | - | Jul 1, 11:25 UTC | Jul 1, 11:40 UTC | 15m |
| 2026-07-01 | ANG8 | - | Jul 1, 09:55 UTC | Jul 1, 10:55 UTC | 1h 0m |
| 2026-06-30 | ANG4 | - | Jun 30, 05:05 UTC | Jun 30, 06:30 UTC | 1h 25m |
| 2026-06-30 | ANG3 | - | Jun 30, 01:50 UTC | Jun 30, 03:20 UTC | 1h 30m |
| 2026-06-29 | ANG392 | - | Jun 29, 11:35 UTC | Jun 29, 12:05 UTC | 30m |
| 2026-06-29 | ANG4 | - | Jun 29, 01:14 UTC | Jun 29, 02:45 UTC | 1h 30m |
| 2026-06-28 | ANG19 | HKG → BNE | Jun 28, 13:00 UTC | Jun 28, 23:39 UTC | 10h 40m |
| 2026-06-28 | ANG8 | - | Jun 28, 09:34 UTC | Jun 28, 11:25 UTC | 1h 50m |
| 2026-06-27 | ANG4 | - | Jun 27, 01:24 UTC | Jun 27, 02:39 UTC | 1h 15m |
| 2026-06-26 | ANG3 | HKG → BNE | Jun 26, 13:34 UTC | Jun 26, 23:44 UTC | 10h 10m |
| 2026-06-26 | ANG8 | - | Jun 26, 09:50 UTC | Jun 26, 11:40 UTC | 1h 50m |
| 2026-06-25 | ANG4 | - | Jun 25, 01:35 UTC | Jun 25, 03:10 UTC | 1h 35m |
| 2026-06-24 | ANG3 | - | Jun 24, 22:25 UTC | Jun 24, 23:45 UTC | 1h 20m |
| 2026-06-22 | ANG4 | - | Jun 22, 01:19 UTC | Jun 22, 02:40 UTC | 1h 20m |
| 2026-06-21 | ANG19 | HKG → BNE | Jun 21, 13:15 UTC | Jun 21, 23:14 UTC | 10h 0m |
| 2026-06-21 | ANG8 | - | Jun 21, 09:24 UTC | Jun 21, 11:24 UTC | 2h 0m |
| 2026-06-20 | ANG4 | - | Jun 20, 01:39 UTC | Jun 20, 03:19 UTC | 1h 40m |
| 2026-06-19 | ANG19 | HKG → BNE | Jun 19, 12:44 UTC | Jun 19, 23:14 UTC | 10h 30m |
| 2026-06-19 | ANG8 | - | Jun 19, 09:14 UTC | Jun 19, 10:59 UTC | 1h 45m |
| 2026-06-18 | ANG4 | - | Jun 18, 01:45 UTC | Jun 18, 03:00 UTC | 1h 15m |
| 2026-06-17 | ANG3 | - | Jun 17, 14:15 UTC | Jun 17, 23:15 UTC | 9h 0m |
| 2026-06-17 | ANG19 | HKG → POM | Jun 17, 13:15 UTC | Jun 17, 13:20 UTC | 5m |
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 P2-PXV page for operator, model, and routing details .