sensors Mode-S transponder
484560
ICAO 24-bit transponder address · allocated to Netherlands
Currently assigned to PH-BVC · BOEING 777-300ER
- Hex
- 484560
- Octal
- 22042540
- Decimal
- 4,736,352
- Country
- NL
- Tail
- PH-BVC
- Type
- B77W
- Flights observed
- 167
- Distinct callsigns
- 20
- Country
- NL
- Last broadcast
- 6h ago
Current position
Country allocation
The ICAO 24-bit address 484560 falls within the block assigned to Netherlands (NL) by ICAO Annex 10, Volume III. Every aircraft registered in Netherlands 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 |
|---|---|---|---|
| KLM758 | - | 17 | 2026-07-07 |
| KLM592 | - | 9 | 2026-07-06 |
| KLM163 | KLM Royal Dutch Airlines | 9 | 2026-05-18 |
| KLM591 | KLM Royal Dutch Airlines | 8 | 2026-07-06 |
| KLM844 | - | 7 | 2026-07-04 |
| KLM843 | - | 7 | 2026-07-03 |
| KLM835 | KLM Royal Dutch Airlines | 7 | 2026-06-10 |
| KLM744 | - | 7 | 2026-07-13 |
| KLM743 | - | 7 | 2026-07-13 |
| KLM248 | - | 7 | 2026-07-10 |
| KLM188 | - | 7 | 2026-05-18 |
| KLM105 | KLM Royal Dutch Airlines | 7 | 2026-06-11 |
| KLM836 | KLM Royal Dutch Airlines | 6 | 2026-06-10 |
| KLM219 | - | 6 | 2026-07-10 |
| KLM133 | - | 6 | 2026-07-09 |
| KLM861 | KLM Royal Dutch Airlines | 5 | 2026-04-17 |
| KLM792 | - | 5 | 2026-06-14 |
| KLM791 | KLM Royal Dutch Airlines | 5 | 2026-06-13 |
| KLM226 | - | 5 | 2026-07-11 |
| KLM268 | - | 4 | 2026-06-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | KLM744 | - | Jul 13, 22:55 UTC | Jul 14, 02:40 UTC | 3h 45m |
| 2026-07-13 | KLM743 | - | Jul 13, 08:30 UTC | Jul 13, 20:05 UTC | 11h 35m |
| 2026-07-12 | KLM898 | - | Jul 12, 10:15 UTC | Jul 12, 15:01 UTC | 4h 45m |
| 2026-07-12 | KLM897 | - | Jul 12, 00:20 UTC | Jul 12, 00:35 UTC | 15m |
| 2026-07-11 | KLM897 | - | Jul 11, 15:00 UTC | Jul 11, 18:45 UTC | 3h 45m |
| 2026-07-11 | KLM226 | YVR → AMS | Jul 11, 01:10 UTC | Jul 11, 09:35 UTC | 8h 25m |
| 2026-07-10 | KLM219 | - | Jul 10, 14:00 UTC | Jul 10, 23:00 UTC | 9h 0m |
| 2026-07-10 | KLM248 | ATL → AMS | Jul 10, 02:55 UTC | Jul 10, 10:40 UTC | 7h 45m |
| 2026-07-09 | KLM133 | - | Jul 9, 15:40 UTC | Jul 10, 00:20 UTC | 8h 40m |
| 2026-07-09 | KLM226 | YVR → AMS | Jul 9, 01:15 UTC | Jul 9, 10:00 UTC | 8h 45m |
| 2026-07-08 | KLM219 | AMS → YVR | Jul 8, 13:55 UTC | Jul 8, 23:00 UTC | 9h 5m |
| 2026-07-07 | KLM758 | - | Jul 7, 19:55 UTC | Jul 8, 09:55 UTC | 14h 0m |
| 2026-07-07 | KLM758 | - | Jul 7, 12:05 UTC | Jul 8, 09:55 UTC | 21h 50m |
| 2026-07-07 | KLM757 | - | Jul 7, 11:30 UTC | Jul 8, 09:55 UTC | 22h 25m |
| 2026-07-06 | KLM592 | - | Jul 6, 21:25 UTC | Jul 7, 07:50 UTC | 10h 25m |
| 2026-07-06 | KLM591 | AMS → JNB | Jul 6, 09:00 UTC | Jul 6, 19:10 UTC | 10h 10m |
| 2026-07-04 | KLM844 | BKK → AMS | Jul 4, 05:25 UTC | Jul 4, 17:05 UTC | 11h 40m |
| 2026-07-03 | KLM843 | AMS → BKK | Jul 3, 15:45 UTC | Jul 4, 02:05 UTC | 10h 20m |
| 2026-07-03 | KLM226 | YVR → AMS | Jul 3, 01:00 UTC | Jul 3, 09:40 UTC | 8h 40m |
| 2026-07-02 | KLM219 | - | Jul 2, 13:55 UTC | Jul 2, 23:05 UTC | 9h 10m |
| 2026-07-02 | KLM226 | YVR → AMS | Jul 2, 01:10 UTC | Jul 2, 09:45 UTC | 8h 35m |
| 2026-07-01 | KLM219 | - | Jul 1, 14:00 UTC | Jul 1, 22:55 UTC | 8h 55m |
| 2026-06-30 | KLM758 | - | Jun 30, 21:05 UTC | Jul 1, 10:55 UTC | 13h 50m |
| 2026-06-30 | KLM758 | - | Jun 30, 14:05 UTC | Jul 1, 10:55 UTC | 20h 50m |
| 2026-06-30 | KLM758 | AMS → AMS | Jun 30, 13:10 UTC | Jul 1, 10:55 UTC | 21h 45m |
| 2026-06-29 | KLM758 | - | Jun 29, 20:04 UTC | Jun 30, 09:55 UTC | 13h 51m |
| 2026-06-29 | KLM758 | - | Jun 29, 12:05 UTC | Jun 30, 09:55 UTC | 21h 51m |
| 2026-06-29 | KLM758 | - | Jun 29, 11:29 UTC | Jun 30, 09:55 UTC | 22h 26m |
| 2026-06-28 | KLM268 | - | Jun 28, 08:05 UTC | Jun 29, 03:39 UTC | 19h 35m |
| 2026-06-27 | KLM268 | - | Jun 27, 08:05 UTC | Jun 28, 03:45 UTC | 19h 40m |
| 2026-06-27 | KLM195 | - | Jun 27, 07:55 UTC | Jun 28, 03:45 UTC | 19h 50m |
| 2026-06-26 | KLM268 | - | Jun 26, 08:05 UTC | Jun 27, 03:49 UTC | 19h 45m |
| 2026-06-26 | KLM268 | AMS → AMS | Jun 26, 07:39 UTC | Jun 27, 03:49 UTC | 20h 10m |
| 2026-06-22 | KLM844 | - | Jun 22, 06:19 UTC | Jun 22, 17:29 UTC | 11h 10m |
| 2026-06-21 | KLM843 | - | Jun 21, 17:35 UTC | Jun 22, 03:50 UTC | 10h 15m |
| 2026-06-20 | KLM744 | - | Jun 20, 16:44 UTC | Jun 21, 10:40 UTC | 17h 55m |
| 2026-06-20 | KLM744 | - | Jun 20, 10:04 UTC | Jun 21, 09:59 UTC | 23h 55m |
| 2026-06-20 | KLM743 | - | Jun 20, 08:59 UTC | Jun 21, 00:40 UTC | 15h 40m |
| 2026-06-18 | KLM758 | - | Jun 18, 19:15 UTC | Jun 19, 09:55 UTC | 14h 39m |
| 2026-06-18 | KLM758 | - | Jun 18, 12:05 UTC | Jun 19, 09:55 UTC | 21h 49m |
| 2026-06-18 | KLM757 | AMS → AMS | Jun 18, 11:25 UTC | Jun 19, 09:55 UTC | 22h 29m |
| 2026-06-17 | KLM592 | - | Jun 17, 21:30 UTC | Jun 18, 08:05 UTC | 10h 35m |
| 2026-06-17 | KLM591 | AMS → JNB | Jun 17, 09:00 UTC | Jun 17, 19:00 UTC | 10h 0m |
| 2026-06-16 | KLM878 | - | Jun 16, 20:50 UTC | Jun 17, 05:45 UTC | 8h 55m |
| 2026-06-16 | KLM877 | - | Jun 16, 10:25 UTC | Jun 16, 18:20 UTC | 7h 55m |
| 2026-06-14 | KLM792 | - | Jun 14, 01:45 UTC | Jun 14, 12:30 UTC | 10h 45m |
| 2026-06-13 | KLM791 | AMS → GRU | Jun 13, 12:25 UTC | Jun 13, 23:30 UTC | 11h 5m |
| 2026-06-13 | KLM758 | PTY → AMS | Jun 13, 01:50 UTC | Jun 13, 09:40 UTC | 7h 49m |
| 2026-06-12 | KLM758 | PTY → AMS | Jun 12, 11:15 UTC | Jun 13, 09:40 UTC | 22h 24m |
| 2026-06-11 | KLM104 | CPT → AMS | Jun 11, 21:15 UTC | Jun 12, 08:35 UTC | 11h 21m |
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 PH-BVC page for operator, model, and routing details .