sensors Mode-S transponder

485993

ICAO 24-bit transponder address · allocated to Netherlands

Currently assigned to PH-KFY · DIAMOND DA-40 Club Star

Hex
485993
Octal
22054623
Decimal
4,741,523
Country
NL
Tail
PH-KFY
Type
DA40
No current signal · last broadcast 8d ago
Flights observed
89
Distinct callsigns
1
Country
NL
Last broadcast
8d ago

Last known position

Most recent position reported by Mode-S 485993.

Country allocation

The ICAO 24-bit address 485993 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 1 distinct

Callsign Airline Flights Last seen
PHKFY - 89 2026-05-21

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-21 PHKFY GRQ → GRQ May 21, 10:30 UTCMay 21, 11:45 UTC1h 15m
2026-05-21 PHKFY GRQ → GRQ May 21, 07:05 UTCMay 21, 09:00 UTC1h 55m
2026-05-19 PHKFY GRQ → GRQ May 19, 07:45 UTCMay 19, 09:50 UTC2h 5m
2026-05-13 PHKFY GRQ → GRQ May 13, 07:35 UTCMay 13, 08:50 UTC1h 15m
2026-05-12 PHKFY GRQ → GRQ May 12, 16:20 UTCMay 12, 18:15 UTC1h 55m
2026-05-12 PHKFY GRQ → GRQ May 12, 12:15 UTCMay 12, 14:10 UTC1h 55m
2026-05-12 PHKFY GRQ → GRQ May 12, 08:50 UTCMay 12, 10:55 UTC2h 5m
2026-05-09 PHKFY GRQ → GRQ May 9, 11:30 UTCMay 9, 12:50 UTC1h 20m
2026-05-09 PHKFY GRQ → GRQ May 9, 07:30 UTCMay 9, 09:00 UTC1h 30m
2026-05-08 PHKFY GRQ → GRQ May 8, 16:45 UTCMay 8, 18:45 UTC2h 0m
2026-05-08 PHKFY GRQ → GRQ May 8, 10:14 UTCMay 8, 12:20 UTC2h 5m
2026-05-08 PHKFY GRQ → GRQ May 8, 06:20 UTCMay 8, 07:34 UTC1h 15m
2026-05-07 PHKFY GRQ → GRQ May 7, 14:15 UTCMay 7, 15:00 UTC45m
2026-05-07 PHKFY GRQ → GRQ May 7, 11:10 UTCMay 7, 12:30 UTC1h 20m
2026-05-07 PHKFY - May 7, 09:00 UTCMay 7, 09:05 UTC5m
2026-05-07 PHKFY GRQ → GRQ May 7, 08:15 UTCMay 7, 08:35 UTC20m
2026-05-07 PHKFY GRQ → GRQ May 7, 06:20 UTCMay 7, 07:00 UTC40m
2026-05-06 PHKFY - May 6, 09:40 UTCMay 6, 11:45 UTC2h 5m
2026-05-06 PHKFY GRQ → GRQ May 6, 06:20 UTCMay 6, 08:25 UTC2h 5m
2026-05-05 PHKFY GRQ → GRQ May 5, 14:30 UTCMay 5, 14:40 UTC10m
2026-05-05 PHKFY GRQ → GRQ May 5, 13:10 UTCMay 5, 14:05 UTC55m
2026-05-05 PHKFY GRQ → GRQ May 5, 12:05 UTCMay 5, 12:10 UTC5m
2026-05-05 PHKFY GRQ → GRQ May 5, 10:50 UTCMay 5, 11:40 UTC50m
2026-05-05 PHKFY GRQ → GRQ May 5, 08:40 UTCMay 5, 09:30 UTC50m
2026-05-01 PHKFY - May 1, 06:20 UTCMay 1, 08:15 UTC1h 55m
2026-04-30 PHKFY - Apr 30, 15:10 UTCApr 30, 16:50 UTC1h 40m
2026-04-30 PHKFY - Apr 30, 12:20 UTCApr 30, 14:00 UTC1h 40m
2026-04-29 PHKFY GRQ → GRQ Apr 29, 19:20 UTCApr 29, 20:00 UTC40m
2026-04-29 PHKFY GRQ → GRQ Apr 29, 16:10 UTCApr 29, 17:35 UTC1h 25m
2026-04-29 PHKFY GRQ → GRQ Apr 29, 13:50 UTCApr 29, 15:15 UTC1h 25m
2026-04-29 PHKFY GRQ → GRQ Apr 29, 11:45 UTCApr 29, 13:05 UTC1h 20m
2026-04-29 PHKFY GRQ → GRQ Apr 29, 07:45 UTCApr 29, 09:45 UTC2h 1m
2026-04-28 PHKFY GRQ → GRQ Apr 28, 17:00 UTCApr 28, 18:20 UTC1h 20m
2026-04-28 PHKFY GRQ → GRQ Apr 28, 12:35 UTCApr 28, 14:05 UTC1h 30m
2026-04-28 PHKFY GRQ → GRQ Apr 28, 09:05 UTCApr 28, 11:05 UTC2h 0m
2026-04-26 PHKFY - Apr 26, 13:20 UTCApr 26, 14:10 UTC50m
2026-04-26 PHKFY - Apr 26, 09:25 UTCApr 26, 10:10 UTC45m
2026-04-25 PHKFY - Apr 25, 12:25 UTCApr 25, 14:25 UTC2h 0m
2026-04-25 PHKFY - Apr 25, 08:40 UTCApr 25, 10:40 UTC2h 0m
2026-04-24 PHKFY GRQ → GRQ Apr 24, 17:05 UTCApr 24, 18:20 UTC1h 15m
2026-04-24 PHKFY GRQ → GRQ Apr 24, 15:20 UTCApr 24, 16:35 UTC1h 15m
2026-04-24 PHKFY GRQ → GRQ Apr 24, 12:20 UTCApr 24, 13:00 UTC40m
2026-04-24 PHKFY GRQ → GRQ Apr 24, 10:10 UTCApr 24, 11:15 UTC1h 5m
2026-04-24 PHKFY GRQ → GRQ Apr 24, 07:20 UTCApr 24, 09:30 UTC2h 10m
2026-04-23 PHKFY GRQ → GRQ Apr 23, 14:45 UTCApr 23, 16:00 UTC1h 15m
2026-04-23 PHKFY - Apr 23, 11:50 UTCApr 23, 12:25 UTC35m
2026-04-23 PHKFY - Apr 23, 10:25 UTCApr 23, 11:45 UTC1h 20m
2026-04-23 PHKFY - Apr 23, 08:20 UTCApr 23, 09:30 UTC1h 10m
2026-04-22 PHKFY - Apr 22, 14:40 UTCApr 22, 15:50 UTC1h 10m
2026-04-22 PHKFY - Apr 22, 11:45 UTCApr 22, 13:10 UTC1h 25m

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-KFY page for operator, model, and routing details .

Mode-S 485993 frequently asked

What is Mode-S code 485993?
485993 is an ICAO 24-bit transponder address. Allocated to Netherlands. Assigned to PH-KFY.
Where is Mode-S 485993 registered?
Mode-S code 485993 is allocated to Netherlands (NL). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 485993 broadcasting right now?
No active broadcast right now. Last signal was 8d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 485993, octal 22054623, decimal 4,741,523.
What flights does 485993 operate?
Mode-S 485993 has broadcast 1 distinct callsign, including PHKFY.