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