sensors Mode-S transponder
70E048
ICAO 24-bit transponder address · allocated to Cambodia
Currently assigned to XU-353 · AIRBUS A-320
- Hex
- 70E048
- Octal
- 34160110
- Decimal
- 7,397,448
- Country
- KH
- Tail
- XU-353
- Type
- A320
- Flights observed
- 118
- Distinct callsigns
- 20
- Country
- KH
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address 70E048 falls within the block assigned to Cambodia (KH) by ICAO Annex 10, Volume III. Every aircraft registered in Cambodia 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 |
|---|---|---|---|
| KHV668 | Cambodia Angkor Air | 21 | 2026-06-01 |
| KHV593 | Cambodia Angkor Air | 17 | 2026-05-31 |
| KHV592 | Cambodia Angkor Air | 17 | 2026-05-29 |
| KHV669 | - | 15 | 2026-06-01 |
| KHV761 | - | 8 | 2026-05-12 |
| KHV760 | - | 7 | 2026-05-12 |
| KHV681 | Cambodia Angkor Air | 5 | 2026-05-06 |
| KHV680 | Cambodia Angkor Air | 5 | 2026-05-06 |
| KHV722 | - | 4 | 2026-05-08 |
| KHV725 | - | 3 | 2026-05-07 |
| KHV724 | - | 3 | 2026-05-07 |
| KHV723 | - | 3 | 2026-05-08 |
| KHV930 | Cambodia Angkor Air | 2 | 2026-05-07 |
| KHV897 | - | 2 | 2026-06-02 |
| KHV931 | Cambodia Angkor Air | 1 | 2026-05-07 |
| KHV927 | - | 1 | 2026-04-18 |
| KHV926 | - | 1 | 2026-04-18 |
| KHV896 | - | 1 | 2026-06-01 |
| KHV851 | - | 1 | 2026-05-28 |
| KHV850 | - | 1 | 2026-05-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | KHV897 | - | Jun 2, 13:30 UTC | Jun 2, 14:05 UTC | 35m |
| 2026-06-01 | KHV896 | - | Jun 1, 20:35 UTC | Jun 2, 11:45 UTC | 15h 10m |
| 2026-06-01 | KHV669 | - | Jun 1, 06:15 UTC | Jun 1, 19:00 UTC | 12h 45m |
| 2026-06-01 | KHV668 | PNH → CAN | Jun 1, 03:55 UTC | Jun 1, 04:25 UTC | 30m |
| 2026-05-31 | KHV593 | NRT → FOC | May 31, 10:10 UTC | Jun 1, 03:25 UTC | 17h 15m |
| 2026-05-30 | KHV897 | - | May 30, 13:20 UTC | May 30, 13:50 UTC | 30m |
| 2026-05-30 | KHV669 | - | May 30, 05:55 UTC | May 30, 11:30 UTC | 5h 35m |
| 2026-05-30 | KHV668 | PNH → CAN | May 30, 03:40 UTC | May 30, 04:00 UTC | 20m |
| 2026-05-29 | KHV593 | NRT → FOC | May 29, 15:15 UTC | May 30, 03:05 UTC | 11h 50m |
| 2026-05-29 | KHV593 | NRT → FOC | May 29, 10:00 UTC | May 29, 11:40 UTC | 1h 40m |
| 2026-05-29 | KHV592 | FOC → NRT | May 29, 06:55 UTC | May 29, 08:20 UTC | 1h 25m |
| 2026-05-28 | KHV851 | - | May 28, 13:05 UTC | May 29, 03:00 UTC | 13h 55m |
| 2026-05-28 | KHV850 | - | May 28, 11:00 UTC | May 28, 11:40 UTC | 40m |
| 2026-05-28 | KHV669 | - | May 28, 06:15 UTC | May 28, 07:00 UTC | 45m |
| 2026-05-28 | KHV668 | PNH → CAN | May 28, 03:50 UTC | May 28, 04:00 UTC | 10m |
| 2026-05-28 | KHV668 | PNH → CAN | May 28, 03:05 UTC | May 28, 03:15 UTC | 10m |
| 2026-05-27 | KHV669 | - | May 27, 06:15 UTC | May 28, 03:15 UTC | 21h 0m |
| 2026-05-27 | KHV668 | PNH → CAN | May 27, 03:45 UTC | May 27, 03:59 UTC | 15m |
| 2026-05-17 | KHV593 | NRT → FOC | May 17, 15:20 UTC | May 17, 16:01 UTC | 40m |
| 2026-05-17 | KHV593 | NRT → FOC | May 17, 10:20 UTC | May 17, 11:35 UTC | 1h 15m |
| 2026-05-17 | KHV592 | FOC → NRT | May 17, 02:35 UTC | May 17, 08:45 UTC | 6h 10m |
| 2026-05-16 | KHV592 | FOC → NRT | May 16, 08:05 UTC | May 17, 08:00 UTC | 23h 55m |
| 2026-05-16 | KHV668 | PNH → CAN | May 16, 05:46 UTC | May 16, 06:01 UTC | 15m |
| 2026-05-15 | KHV593 | NRT → FOC | May 15, 16:00 UTC | May 15, 16:25 UTC | 25m |
| 2026-05-15 | KHV593 | NRT → FOC | May 15, 10:45 UTC | May 15, 12:00 UTC | 1h 15m |
| 2026-05-15 | KHV592 | FOC → NRT | May 15, 02:45 UTC | May 15, 09:20 UTC | 6h 35m |
| 2026-05-14 | KHV668 | PNH → CAN | May 14, 03:50 UTC | May 14, 04:30 UTC | 40m |
| 2026-05-13 | KHV593 | NRT → FOC | May 13, 15:30 UTC | May 13, 16:35 UTC | 1h 5m |
| 2026-05-13 | KHV593 | NRT → FOC | May 13, 10:20 UTC | May 13, 11:45 UTC | 1h 25m |
| 2026-05-12 | KHV761 | - | May 12, 18:25 UTC | May 13, 08:55 UTC | 14h 30m |
| 2026-05-12 | KHV760 | - | May 12, 12:45 UTC | May 12, 17:10 UTC | 4h 25m |
| 2026-05-11 | KHV669 | - | May 11, 06:05 UTC | May 11, 06:15 UTC | 10m |
| 2026-05-11 | KHV668 | PNH → CAN | May 11, 03:40 UTC | May 11, 03:55 UTC | 15m |
| 2026-05-10 | KHV593 | NRT → FOC | May 10, 10:15 UTC | May 10, 16:30 UTC | 6h 15m |
| 2026-05-10 | KHV592 | FOC → NRT | May 10, 07:04 UTC | May 10, 08:35 UTC | 1h 30m |
| 2026-05-10 | KHV592 | FOC → NRT | May 10, 02:34 UTC | May 10, 03:25 UTC | 50m |
| 2026-05-09 | KHV592 | FOC → NRT | May 9, 06:05 UTC | May 10, 03:25 UTC | 21h 20m |
| 2026-05-09 | KHV668 | PNH → CAN | May 9, 03:35 UTC | May 9, 03:55 UTC | 20m |
| 2026-05-08 | KHV723 | - | May 8, 14:25 UTC | May 8, 15:00 UTC | 35m |
| 2026-05-08 | KHV722 | - | May 8, 08:34 UTC | May 8, 13:10 UTC | 4h 35m |
| 2026-05-08 | KHV668 | PNH → CAN | May 8, 06:04 UTC | May 8, 06:14 UTC | 10m |
| 2026-05-07 | KHV931 | SZX → KOS | May 7, 20:40 UTC | May 7, 20:55 UTC | 15m |
| 2026-05-07 | KHV930 | KOS → SZX | May 7, 18:35 UTC | May 7, 18:50 UTC | 15m |
| 2026-05-07 | KHV725 | - | May 7, 08:30 UTC | May 7, 09:00 UTC | 30m |
| 2026-05-07 | KHV724 | - | May 7, 06:00 UTC | May 7, 06:40 UTC | 40m |
| 2026-05-06 | KHV681 | HKG → PNH | May 6, 15:15 UTC | May 6, 15:30 UTC | 15m |
| 2026-05-06 | KHV680 | PNH → HKG | May 6, 13:40 UTC | May 6, 13:50 UTC | 10m |
| 2026-05-06 | KHV669 | - | May 6, 05:45 UTC | May 6, 05:55 UTC | 10m |
| 2026-05-06 | KHV668 | PNH → CAN | May 6, 03:30 UTC | May 6, 03:55 UTC | 25m |
| 2026-05-05 | KHV761 | - | May 5, 18:25 UTC | May 5, 22:10 UTC | 3h 45m |
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 XU-353 page for operator, model, and routing details .