sensors Mode-S transponder
484561
ICAO 24-bit transponder address · allocated to Netherlands
Currently assigned to PH-BVD · BOEING 777-300ER
- Hex
- 484561
- Octal
- 22042541
- Decimal
- 4,736,353
- Country
- NL
- Tail
- PH-BVD
- Type
- B77W
- Flights observed
- 183
- Distinct callsigns
- 20
- Country
- NL
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 484561 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 |
|---|---|---|---|
| KLM744 | - | 15 | 2026-06-18 |
| KLM743 | - | 13 | 2026-06-18 |
| KLM791 | KLM Royal Dutch Airlines | 10 | 2026-07-01 |
| KLM792 | - | 8 | 2026-07-02 |
| KLM758 | KLM Royal Dutch Airlines | 8 | 2026-06-02 |
| KLM589 | - | 8 | 2026-07-10 |
| KLM219 | - | 8 | 2026-07-07 |
| KLM844 | KLM Royal Dutch Airlines | 7 | 2026-05-11 |
| KLM843 | KLM Royal Dutch Airlines | 7 | 2026-05-10 |
| KLM592 | - | 7 | 2026-06-30 |
| KLM226 | - | 7 | 2026-07-08 |
| KLM757 | KLM Royal Dutch Airlines | 6 | 2026-06-02 |
| KLM591 | KLM Royal Dutch Airlines | 6 | 2026-06-30 |
| KLM590 | - | 6 | 2026-06-24 |
| KLM248 | - | 6 | 2026-07-09 |
| KLM133 | - | 6 | 2026-07-08 |
| KLM105 | KLM Royal Dutch Airlines | 6 | 2026-06-16 |
| KLM836 | KLM Royal Dutch Airlines | 5 | 2026-04-25 |
| KLM188 | - | 3 | 2026-05-01 |
| KLM163 | KLM Royal Dutch Airlines | 3 | 2026-05-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-12 | KLM174 | - | Jul 12, 01:30 UTC | Jul 12, 05:40 UTC | 4h 10m |
| 2026-07-11 | KLM565 | - | Jul 11, 19:15 UTC | Jul 11, 19:25 UTC | 10m |
| 2026-07-11 | KLM565 | - | Jul 11, 11:30 UTC | Jul 11, 15:20 UTC | 3h 50m |
| 2026-07-10 | KLM589 | - | Jul 10, 14:00 UTC | Jul 11, 04:25 UTC | 14h 25m |
| 2026-07-09 | KLM589 | AMS → AMS | Jul 9, 13:30 UTC | Jul 10, 04:35 UTC | 15h 5m |
| 2026-07-09 | KLM248 | ATL → AMS | Jul 9, 02:55 UTC | Jul 9, 10:50 UTC | 7h 55m |
| 2026-07-08 | KLM133 | AMS → ATL | Jul 8, 15:45 UTC | Jul 9, 00:20 UTC | 8h 35m |
| 2026-07-08 | KLM226 | - | Jul 8, 01:25 UTC | Jul 8, 10:00 UTC | 8h 35m |
| 2026-07-07 | KLM219 | - | Jul 7, 14:00 UTC | Jul 7, 23:05 UTC | 9h 5m |
| 2026-07-06 | KLM48 | - | Jul 6, 22:50 UTC | Jul 7, 05:50 UTC | 7h 0m |
| 2026-07-06 | KLM611 | AMS → ORD | Jul 6, 12:15 UTC | Jul 6, 20:25 UTC | 8h 10m |
| 2026-07-06 | KLM226 | YVR → AMS | Jul 6, 01:15 UTC | Jul 6, 09:40 UTC | 8h 25m |
| 2026-07-05 | KLM219 | - | Jul 5, 14:05 UTC | Jul 5, 23:15 UTC | 9h 10m |
| 2026-07-05 | KLM248 | ATL → AMS | Jul 5, 03:30 UTC | Jul 5, 11:00 UTC | 7h 30m |
| 2026-07-04 | KLM133 | AMS → ATL | Jul 4, 15:25 UTC | Jul 5, 00:35 UTC | 9h 10m |
| 2026-07-04 | KLM226 | - | Jul 4, 01:10 UTC | Jul 4, 09:45 UTC | 8h 35m |
| 2026-07-03 | KLM219 | - | Jul 3, 14:00 UTC | Jul 3, 23:05 UTC | 9h 5m |
| 2026-07-03 | KLM248 | ATL → AMS | Jul 3, 03:25 UTC | Jul 3, 11:00 UTC | 7h 35m |
| 2026-07-02 | KLM133 | AMS → ATL | Jul 2, 16:05 UTC | Jul 3, 00:55 UTC | 8h 50m |
| 2026-07-02 | KLM792 | - | Jul 2, 01:05 UTC | Jul 2, 12:10 UTC | 11h 5m |
| 2026-07-01 | KLM791 | AMS → GRU | Jul 1, 14:30 UTC | Jul 1, 22:40 UTC | 8h 10m |
| 2026-07-01 | KLM791 | AMS → GRU | Jul 1, 11:30 UTC | Jul 1, 14:05 UTC | 2h 35m |
| 2026-06-30 | KLM592 | - | Jun 30, 21:35 UTC | Jul 1, 08:05 UTC | 10h 30m |
| 2026-06-30 | KLM591 | AMS → JNB | Jun 30, 09:00 UTC | Jun 30, 19:15 UTC | 10h 15m |
| 2026-06-28 | KLM896 | - | Jun 28, 02:25 UTC | Jun 28, 21:04 UTC | 18h 40m |
| 2026-06-27 | KLM896 | - | Jun 27, 20:39 UTC | Jun 28, 20:14 UTC | 23h 35m |
| 2026-06-27 | KLM895 | - | Jun 27, 18:20 UTC | Jun 28, 17:55 UTC | 23h 35m |
| 2026-06-27 | KLM895 | - | Jun 27, 16:55 UTC | Jun 28, 10:10 UTC | 17h 15m |
| 2026-06-26 | KLM856 | - | Jun 26, 14:55 UTC | Jun 27, 02:50 UTC | 11h 55m |
| 2026-06-26 | KLM856 | - | Jun 26, 13:45 UTC | Jun 26, 14:05 UTC | 20m |
| 2026-06-26 | KLM855 | - | Jun 26, 06:50 UTC | Jun 26, 07:14 UTC | 25m |
| 2026-06-25 | KLM855 | - | Jun 25, 19:59 UTC | Jun 26, 05:55 UTC | 9h 55m |
| 2026-06-24 | KLM590 | AMS → AMS | Jun 24, 13:50 UTC | Jun 25, 04:54 UTC | 15h 5m |
| 2026-06-24 | KLM226 | - | Jun 24, 00:55 UTC | Jun 24, 09:49 UTC | 8h 55m |
| 2026-06-23 | KLM219 | - | Jun 23, 13:45 UTC | Jun 23, 22:55 UTC | 9h 10m |
| 2026-06-23 | KLM226 | - | Jun 23, 01:15 UTC | Jun 23, 09:54 UTC | 8h 40m |
| 2026-06-22 | KLM219 | - | Jun 22, 13:59 UTC | Jun 22, 22:49 UTC | 8h 50m |
| 2026-06-22 | KLM226 | - | Jun 22, 01:05 UTC | Jun 22, 09:49 UTC | 8h 45m |
| 2026-06-21 | KLM219 | - | Jun 21, 13:54 UTC | Jun 21, 22:49 UTC | 8h 55m |
| 2026-06-21 | KLM248 | ATL → AMS | Jun 21, 03:44 UTC | Jun 21, 11:10 UTC | 7h 25m |
| 2026-06-20 | KLM133 | - | Jun 20, 16:44 UTC | Jun 21, 01:25 UTC | 8h 40m |
| 2026-06-20 | KLM248 | - | Jun 20, 03:59 UTC | Jun 20, 11:14 UTC | 7h 15m |
| 2026-06-19 | KLM133 | AMS → ATL | Jun 19, 17:04 UTC | Jun 20, 01:24 UTC | 8h 20m |
| 2026-06-18 | KLM744 | - | Jun 18, 16:55 UTC | Jun 19, 10:24 UTC | 17h 29m |
| 2026-06-18 | KLM743 | - | Jun 18, 08:30 UTC | Jun 19, 02:29 UTC | 17h 59m |
| 2026-06-16 | KLM104 | CPT → AMS | Jun 16, 21:15 UTC | Jun 17, 08:30 UTC | 11h 15m |
| 2026-06-16 | KLM105 | - | Jun 16, 19:05 UTC | Jun 16, 19:25 UTC | 20m |
| 2026-06-16 | KLM105 | - | Jun 16, 08:44 UTC | Jun 16, 16:45 UTC | 8h 0m |
| 2026-06-15 | KLM590 | - | Jun 15, 13:34 UTC | Jun 16, 04:35 UTC | 15h 0m |
| 2026-06-15 | KLM226 | - | Jun 15, 01:10 UTC | Jun 15, 10:05 UTC | 8h 55m |
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-BVD page for operator, model, and routing details .