Apparatus

Try JFK, AAL1290, BAW, or N225AN.

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
Broadcasting now · callsign PHKFY · 1,300 ft
Flights observed
147
Distinct callsigns
1
Country
NL
Last broadcast
4h ago

Current position

485993 is currently broadcasting. Map zoomed to live position.

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 - 147 2026-07-14

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 PHKFY GRQ → GRQ Jul 14, 10:35 UTCJul 14, 11:35 UTC1h 0m
2026-07-14 PHKFY GRQ → GRQ Jul 14, 09:00 UTCJul 14, 09:50 UTC50m
2026-07-13 PHKFY GRQ → GRQ Jul 13, 08:55 UTCJul 13, 11:00 UTC2h 5m
2026-07-10 PHKFY GRQ → GRQ Jul 10, 10:55 UTCJul 10, 12:55 UTC2h 0m
2026-07-09 PHKFY - Jul 9, 13:30 UTCJul 9, 14:45 UTC1h 15m
2026-07-08 PHKFY GRQ → GRQ Jul 8, 11:05 UTCJul 8, 13:05 UTC2h 0m
2026-07-07 PHKFY - Jul 7, 12:40 UTCJul 7, 14:40 UTC2h 0m
2026-07-07 PHKFY GRQ → NRN Jul 7, 09:00 UTCJul 7, 11:00 UTC2h 0m
2026-07-06 PHKFY - Jul 6, 15:45 UTCJul 6, 17:40 UTC1h 55m
2026-07-06 PHKFY GRQ → GRQ Jul 6, 08:35 UTCJul 6, 10:35 UTC2h 0m
2026-07-03 PHKFY GRQ → GRQ Jul 3, 12:40 UTCJul 3, 14:35 UTC1h 55m
2026-07-03 PHKFY GRQ → GRQ Jul 3, 07:45 UTCJul 3, 09:45 UTC2h 0m
2026-06-30 PHKFY GRQ → GRQ Jun 30, 15:25 UTCJun 30, 16:45 UTC1h 20m
2026-06-30 PHKFY MST → GRQ Jun 30, 10:50 UTCJun 30, 12:55 UTC2h 5m
2026-06-30 PHKFY GRQ → MST Jun 30, 07:10 UTCJun 30, 09:00 UTC1h 50m
2026-06-29 PHKFY GRQ → GRQ Jun 29, 14:54 UTCJun 29, 16:59 UTC2h 5m
2026-06-26 PHKFY GRQ → GRQ Jun 26, 08:45 UTCJun 26, 10:05 UTC1h 20m
2026-06-26 PHKFY - Jun 26, 08:05 UTCJun 26, 08:15 UTC10m
2026-06-26 PHKFY GRQ → GRQ Jun 26, 07:20 UTCJun 26, 07:39 UTC20m
2026-06-25 PHKFY - Jun 25, 18:04 UTCJun 25, 18:45 UTC40m
2026-06-25 PHKFY - Jun 25, 16:14 UTCJun 25, 17:39 UTC1h 25m
2026-06-25 PHKFY - Jun 25, 14:29 UTCJun 25, 15:24 UTC55m
2026-06-25 PHKFY - Jun 25, 13:00 UTCJun 25, 13:40 UTC40m
2026-06-25 PHKFY - Jun 25, 09:59 UTCJun 25, 10:04 UTC5m
2026-06-25 PHKFY GRQ → GRQ Jun 25, 08:24 UTCJun 25, 09:20 UTC55m
2026-06-24 PHKFY - Jun 24, 10:49 UTCJun 24, 12:04 UTC1h 15m
2026-06-24 PHKFY - Jun 24, 08:14 UTCJun 24, 09:34 UTC1h 20m
2026-06-23 PHKFY GRQ → GRQ Jun 23, 17:44 UTCJun 23, 19:00 UTC1h 15m
2026-06-23 PHKFY - Jun 23, 14:35 UTCJun 23, 14:49 UTC15m
2026-06-23 PHKFY - Jun 23, 11:59 UTCJun 23, 13:09 UTC1h 10m
2026-06-23 PHKFY GRQ → GRQ Jun 23, 10:04 UTCJun 23, 11:19 UTC1h 15m
2026-06-23 PHKFY - Jun 23, 07:45 UTCJun 23, 07:55 UTC10m
2026-06-23 PHKFY GRQ → GRQ Jun 23, 06:19 UTCJun 23, 07:09 UTC50m
2026-06-22 PHKFY GRQ → GRQ Jun 22, 11:04 UTCJun 22, 12:25 UTC1h 20m
2026-06-22 PHKFY - Jun 22, 06:25 UTCJun 22, 08:25 UTC2h 0m
2026-06-19 PHKFY GRQ → GRQ Jun 19, 16:29 UTCJun 19, 18:25 UTC1h 55m
2026-06-19 PHKFY GRQ → GRQ Jun 19, 13:54 UTCJun 19, 15:09 UTC1h 15m
2026-06-19 PHKFY GRQ → GRQ Jun 19, 11:49 UTCJun 19, 13:04 UTC1h 15m
2026-06-19 PHKFY - Jun 19, 07:34 UTCJun 19, 09:44 UTC2h 10m
2026-06-17 PHKFY - Jun 17, 12:20 UTCJun 17, 13:35 UTC1h 15m
2026-06-17 PHKFY GRQ → GRQ Jun 17, 10:15 UTCJun 17, 11:25 UTC1h 10m
2026-06-17 PHKFY - Jun 17, 06:35 UTCJun 17, 08:35 UTC2h 0m
2026-06-16 PHKFY GRQ → GRQ Jun 16, 10:04 UTCJun 16, 12:14 UTC2h 10m
2026-06-16 PHKFY GRQ → GRQ Jun 16, 06:20 UTCJun 16, 07:34 UTC1h 15m
2026-06-15 PHKFY GRQ → GRQ Jun 15, 13:40 UTCJun 15, 15:04 UTC1h 25m
2026-06-15 PHKFY EME → GRQ Jun 15, 11:05 UTCJun 15, 12:49 UTC1h 45m
2026-06-15 PHKFY GRQ → EME Jun 15, 09:05 UTCJun 15, 10:20 UTC1h 15m
2026-06-12 PHKFY GRQ → GRQ Jun 12, 13:45 UTCJun 12, 15:10 UTC1h 25m
2026-06-12 PHKFY GRQ → GRQ Jun 12, 10:05 UTCJun 12, 11:25 UTC1h 20m
2026-06-11 PHKFY - Jun 11, 17:20 UTCJun 11, 19:05 UTC1h 45m

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?
Yes. Mode-S 485993 is currently airborne.
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.