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