sensors Mode-S transponder
898174
ICAO 24-bit transponder address · allocated to Papua New Guinea
Currently assigned to P2-PXB · BOEING 737-800
- Hex
- 898174
- Octal
- 42300564
- Decimal
- 9,011,572
- Country
- PG
- Tail
- P2-PXB
- Type
- B738
- Flights observed
- 61
- Distinct callsigns
- 4
- Country
- PG
- Last broadcast
- 4d ago
Last known position
Country allocation
The ICAO 24-bit address 898174 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 4 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-10 | ANG11 | - | Jul 10, 14:10 UTC | Jul 10, 14:35 UTC | 25m |
| 2026-07-10 | ANG10 | - | Jul 10, 11:00 UTC | Jul 10, 12:05 UTC | 1h 5m |
| 2026-07-03 | ANG11 | - | Jul 3, 13:45 UTC | Jul 3, 14:15 UTC | 30m |
| 2026-07-02 | ANG24 | - | Jul 2, 22:15 UTC | Jul 3, 11:40 UTC | 13h 25m |
| 2026-07-01 | ANG23 | - | Jul 1, 13:55 UTC | Jul 2, 07:05 UTC | 17h 10m |
| 2026-07-01 | ANG10 | - | Jul 1, 11:25 UTC | Jul 1, 12:00 UTC | 35m |
| 2026-06-29 | ANG11 | - | Jun 29, 13:59 UTC | Jun 29, 14:25 UTC | 25m |
| 2026-06-29 | ANG10 | - | Jun 29, 10:59 UTC | Jun 29, 11:35 UTC | 35m |
| 2026-06-28 | ANG11 | - | Jun 28, 13:40 UTC | Jun 29, 11:35 UTC | 21h 55m |
| 2026-06-28 | ANG10 | - | Jun 28, 10:55 UTC | Jun 28, 11:29 UTC | 35m |
| 2026-06-24 | ANG11 | - | Jun 24, 13:40 UTC | Jun 24, 14:04 UTC | 25m |
| 2026-06-24 | ANG10 | - | Jun 24, 10:59 UTC | Jun 24, 11:39 UTC | 40m |
| 2026-06-22 | ANG11 | - | Jun 22, 13:19 UTC | Jun 22, 13:49 UTC | 30m |
| 2026-06-22 | ANG10 | - | Jun 22, 10:55 UTC | Jun 22, 11:39 UTC | 45m |
| 2026-06-21 | ANG10 | - | Jun 21, 13:50 UTC | Jun 22, 11:39 UTC | 21h 50m |
| 2026-06-21 | ANG10 | - | Jun 21, 10:44 UTC | Jun 21, 11:49 UTC | 1h 5m |
| 2026-06-19 | ANG11 | - | Jun 19, 13:44 UTC | Jun 19, 14:09 UTC | 25m |
| 2026-06-19 | ANG10 | - | Jun 19, 11:14 UTC | Jun 19, 11:54 UTC | 40m |
| 2026-06-12 | ANG11 | MNL → POM | Jun 12, 13:25 UTC | Jun 12, 13:55 UTC | 30m |
| 2026-06-12 | ANG10 | - | Jun 12, 11:05 UTC | Jun 12, 11:45 UTC | 40m |
| 2026-06-08 | ANG11 | MNL → POM | Jun 8, 13:45 UTC | Jun 8, 14:20 UTC | 35m |
| 2026-06-08 | ANG10 | POM → MNL | Jun 8, 10:55 UTC | Jun 8, 11:30 UTC | 35m |
| 2026-06-07 | ANG10 | POM → MNL | Jun 7, 13:55 UTC | Jun 8, 11:30 UTC | 21h 35m |
| 2026-06-07 | ANG10 | POM → MNL | Jun 7, 11:00 UTC | Jun 7, 11:40 UTC | 40m |
| 2026-06-05 | ANG11 | MNL → POM | Jun 5, 13:50 UTC | Jun 5, 14:25 UTC | 35m |
| 2026-06-05 | ANG10 | POM → MNL | Jun 5, 11:00 UTC | Jun 5, 11:40 UTC | 40m |
| 2026-05-31 | ANG11 | MNL → POM | May 31, 13:50 UTC | May 31, 14:20 UTC | 30m |
| 2026-05-31 | ANG10 | POM → MNL | May 31, 10:40 UTC | May 31, 11:40 UTC | 1h 0m |
| 2026-05-29 | ANG11 | MNL → POM | May 29, 13:45 UTC | May 29, 14:15 UTC | 30m |
| 2026-05-29 | ANG10 | POM → MNL | May 29, 10:55 UTC | May 29, 11:45 UTC | 50m |
| 2026-05-24 | ANG11 | MNL → POM | May 24, 14:00 UTC | May 24, 14:20 UTC | 20m |
| 2026-05-24 | ANG10 | POM → MNL | May 24, 10:55 UTC | May 24, 11:35 UTC | 40m |
| 2026-05-22 | ANG11 | MNL → POM | May 22, 13:30 UTC | May 22, 13:55 UTC | 25m |
| 2026-05-22 | ANG10 | POM → MNL | May 22, 10:55 UTC | May 22, 11:35 UTC | 40m |
| 2026-05-20 | ANG11 | MNL → POM | May 20, 13:30 UTC | May 20, 14:00 UTC | 30m |
| 2026-05-20 | ANG10 | POM → MNL | May 20, 11:00 UTC | May 20, 11:30 UTC | 30m |
| 2026-05-18 | ANG11 | MNL → POM | May 18, 14:15 UTC | May 18, 14:40 UTC | 25m |
| 2026-05-18 | ANG10 | POM → MNL | May 18, 11:05 UTC | May 18, 11:50 UTC | 45m |
| 2026-05-17 | ANG10 | POM → MNL | May 17, 13:25 UTC | May 18, 11:50 UTC | 22h 25m |
| 2026-05-17 | ANG10 | POM → MNL | May 17, 10:55 UTC | May 17, 11:30 UTC | 35m |
| 2026-05-10 | ANG11 | MNL → POM | May 10, 13:40 UTC | May 10, 14:09 UTC | 30m |
| 2026-05-10 | ANG10 | POM → MNL | May 10, 10:40 UTC | May 10, 11:25 UTC | 45m |
| 2026-05-07 | ANG24 | BNE → POM | May 7, 22:30 UTC | May 7, 23:09 UTC | 40m |
| 2026-05-07 | ANG23 | POM → BNE | May 7, 06:15 UTC | May 7, 06:50 UTC | 35m |
| 2026-05-04 | ANG11 | MNL → POM | May 4, 14:00 UTC | May 4, 14:25 UTC | 25m |
| 2026-05-04 | ANG10 | POM → MNL | May 4, 11:10 UTC | May 4, 12:05 UTC | 55m |
| 2026-05-03 | ANG10 | POM → MNL | May 3, 13:35 UTC | May 4, 12:05 UTC | 22h 30m |
| 2026-05-03 | ANG10 | POM → MNL | May 3, 10:35 UTC | May 3, 11:30 UTC | 55m |
| 2026-05-01 | ANG11 | MNL → POM | May 1, 14:00 UTC | May 1, 14:25 UTC | 25m |
| 2026-05-01 | ANG10 | POM → MNL | May 1, 10:50 UTC | May 1, 11:40 UTC | 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 P2-PXB page for operator, model, and routing details .