sensors Mode-S transponder
485ECD
ICAO 24-bit transponder address · allocated to Netherlands
Currently assigned to PH-BVV · BOEING 777-300ER
- Hex
- 485ECD
- Octal
- 22057315
- Decimal
- 4,742,861
- Country
- NL
- Tail
- PH-BVV
- Type
- B77W
- Flights observed
- 148
- Distinct callsigns
- 20
- Country
- NL
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 485ECD 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 |
|---|---|---|---|
| KLM743 | - | 11 | 2026-06-25 |
| KLM836 | - | 9 | 2026-07-13 |
| KLM744 | - | 9 | 2026-06-25 |
| KLM835 | - | 8 | 2026-07-12 |
| KLM591 | - | 8 | 2026-07-14 |
| KLM791 | KLM Royal Dutch Airlines | 7 | 2026-06-11 |
| KLM758 | - | 7 | 2026-06-23 |
| KLM592 | - | 7 | 2026-06-22 |
| KLM248 | - | 7 | 2026-07-08 |
| KLM133 | - | 7 | 2026-07-07 |
| KLM877 | - | 6 | 2026-07-05 |
| KLM792 | KLM Royal Dutch Airlines | 6 | 2026-06-12 |
| KLM878 | - | 5 | 2026-07-05 |
| KLM105 | KLM Royal Dutch Airlines | 4 | 2026-05-15 |
| KLM896 | - | 3 | 2026-06-16 |
| KLM757 | - | 3 | 2026-06-23 |
| KLM646 | - | 3 | 2026-06-21 |
| KLM589 | KLM Royal Dutch Airlines | 3 | 2026-05-30 |
| KLM207 | - | 3 | 2026-06-21 |
| KLM188 | - | 3 | 2026-05-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | KLM591 | - | Jul 14, 09:00 UTC | Jul 14, 11:30 UTC | 2h 30m |
| 2026-07-13 | KLM836 | - | Jul 13, 17:15 UTC | Jul 14, 05:50 UTC | 12h 35m |
| 2026-07-13 | KLM836 | - | Jul 13, 15:10 UTC | Jul 13, 15:20 UTC | 10m |
| 2026-07-12 | KLM835 | - | Jul 12, 19:30 UTC | Jul 13, 07:20 UTC | 11h 50m |
| 2026-07-10 | KLM296 | IAD → AMS | Jul 10, 22:20 UTC | Jul 11, 05:05 UTC | 6h 45m |
| 2026-07-10 | KLM225 | - | Jul 10, 11:50 UTC | Jul 10, 19:45 UTC | 7h 55m |
| 2026-07-08 | KLM248 | ATL → AMS | Jul 8, 03:00 UTC | Jul 8, 11:05 UTC | 8h 5m |
| 2026-07-07 | KLM133 | - | Jul 7, 15:40 UTC | Jul 8, 00:20 UTC | 8h 40m |
| 2026-07-07 | KLM248 | ATL → AMS | Jul 7, 03:45 UTC | Jul 7, 11:55 UTC | 8h 10m |
| 2026-07-06 | KLM133 | - | Jul 6, 16:35 UTC | Jul 7, 01:05 UTC | 8h 30m |
| 2026-07-05 | KLM878 | - | Jul 5, 21:40 UTC | Jul 6, 06:25 UTC | 8h 45m |
| 2026-07-05 | KLM877 | - | Jul 5, 11:15 UTC | Jul 5, 19:25 UTC | 8h 10m |
| 2026-07-04 | KLM590 | AMS → AMS | Jul 4, 14:00 UTC | Jul 5, 04:30 UTC | 14h 30m |
| 2026-07-03 | KLM874 | - | Jul 3, 15:20 UTC | Jul 4, 09:30 UTC | 18h 10m |
| 2026-07-03 | KLM873 | - | Jul 3, 13:20 UTC | Jul 4, 09:30 UTC | 20h 10m |
| 2026-07-03 | KLM873 | AMS → AMS | Jul 3, 12:50 UTC | Jul 4, 09:30 UTC | 20h 40m |
| 2026-06-30 | KLM878 | - | Jun 30, 21:05 UTC | Jul 1, 05:40 UTC | 8h 35m |
| 2026-06-30 | KLM877 | - | Jun 30, 10:20 UTC | Jun 30, 18:30 UTC | 8h 10m |
| 2026-06-29 | KLM836 | SIN → AMS | Jun 29, 17:24 UTC | Jun 30, 06:00 UTC | 12h 36m |
| 2026-06-29 | KLM836 | SIN → AMS | Jun 29, 14:54 UTC | Jun 29, 15:04 UTC | 10m |
| 2026-06-28 | KLM835 | - | Jun 28, 19:25 UTC | Jun 29, 07:40 UTC | 12h 15m |
| 2026-06-28 | KLM174 | - | Jun 28, 02:05 UTC | Jun 28, 06:10 UTC | 4h 5m |
| 2026-06-27 | KLM565 | - | Jun 27, 11:50 UTC | Jun 27, 15:24 UTC | 3h 35m |
| 2026-06-25 | KLM744 | - | Jun 25, 18:15 UTC | Jun 26, 10:35 UTC | 16h 20m |
| 2026-06-25 | KLM743 | - | Jun 25, 09:20 UTC | Jun 26, 09:14 UTC | 23h 55m |
| 2026-06-25 | KLM743 | - | Jun 25, 08:20 UTC | Jun 26, 03:00 UTC | 18h 40m |
| 2026-06-23 | KLM758 | - | Jun 23, 19:19 UTC | Jun 24, 09:59 UTC | 14h 40m |
| 2026-06-23 | KLM757 | - | Jun 23, 11:24 UTC | Jun 24, 09:59 UTC | 22h 35m |
| 2026-06-22 | KLM592 | - | Jun 22, 21:30 UTC | Jun 23, 07:49 UTC | 10h 20m |
| 2026-06-22 | KLM591 | AMS → JNB | Jun 22, 08:54 UTC | Jun 22, 19:09 UTC | 10h 15m |
| 2026-06-21 | KLM646 | JFK → AMS | Jun 21, 23:44 UTC | Jun 22, 06:05 UTC | 6h 20m |
| 2026-06-21 | KLM207 | - | Jun 21, 13:34 UTC | Jun 21, 20:50 UTC | 7h 15m |
| 2026-06-21 | KLM226 | - | Jun 21, 00:59 UTC | Jun 21, 09:40 UTC | 8h 40m |
| 2026-06-20 | KLM219 | AMS → YVR | Jun 20, 13:44 UTC | Jun 20, 22:35 UTC | 8h 50m |
| 2026-06-19 | KLM758 | - | Jun 19, 19:19 UTC | Jun 20, 10:04 UTC | 14h 45m |
| 2026-06-19 | KLM757 | - | Jun 19, 11:20 UTC | Jun 20, 10:04 UTC | 22h 45m |
| 2026-06-18 | KLM592 | - | Jun 18, 21:35 UTC | Jun 19, 07:59 UTC | 10h 24m |
| 2026-06-18 | KLM591 | AMS → JNB | Jun 18, 09:05 UTC | Jun 18, 19:10 UTC | 10h 5m |
| 2026-06-17 | KLM836 | SIN → AMS | Jun 17, 17:30 UTC | Jun 18, 06:10 UTC | 12h 40m |
| 2026-06-16 | KLM835 | - | Jun 16, 19:35 UTC | Jun 17, 07:15 UTC | 11h 41m |
| 2026-06-16 | KLM896 | - | Jun 16, 12:25 UTC | Jun 16, 17:10 UTC | 4h 45m |
| 2026-06-15 | KLM896 | - | Jun 15, 17:30 UTC | Jun 16, 17:10 UTC | 23h 40m |
| 2026-06-15 | KLM896 | - | Jun 15, 15:19 UTC | Jun 16, 15:15 UTC | 23h 55m |
| 2026-06-15 | KLM895 | AMS → PVG | Jun 15, 14:00 UTC | Jun 16, 13:15 UTC | 23h 15m |
| 2026-06-14 | KLM744 | - | Jun 14, 18:45 UTC | Jun 15, 10:30 UTC | 15h 44m |
| 2026-06-14 | KLM743 | - | Jun 14, 09:20 UTC | Jun 15, 09:15 UTC | 23h 55m |
| 2026-06-14 | KLM743 | AMS → LIM | Jun 14, 08:45 UTC | Jun 15, 02:24 UTC | 17h 39m |
| 2026-06-13 | KLM248 | ATL → AMS | Jun 13, 02:55 UTC | Jun 13, 10:45 UTC | 7h 49m |
| 2026-06-12 | KLM133 | AMS → ATL | Jun 12, 15:25 UTC | Jun 13, 00:05 UTC | 8h 40m |
| 2026-06-12 | KLM792 | GRU → AMS | Jun 12, 01:20 UTC | Jun 12, 12:10 UTC | 10h 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 PH-BVV page for operator, model, and routing details .