Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

4863D0

ICAO 24-bit transponder address · allocated to Netherlands

Currently assigned to PH-1661 · SCHEMPP-HIRTH Duo Discus

Hex
4863D0
Octal
22061720
Decimal
4,744,144
Country
NL
Tail
PH-1661
Type
DUOD
No current signal · last broadcast 6h ago
Flights observed
71
Distinct callsigns
1
Country
NL
Last broadcast
6h ago

Last known position

Most recent position reported by Mode-S 4863D0.

Country allocation

The ICAO 24-bit address 4863D0 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
PH1661 - 71 2026-07-18

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-18 PH1661 - Jul 18, 10:10 UTCJul 18, 13:35 UTC3h 25m
2026-07-16 PH1661 - Jul 16, 11:20 UTCJul 16, 15:10 UTC3h 50m
2026-07-15 PH1661 - Jul 15, 11:20 UTCJul 15, 14:00 UTC2h 40m
2026-07-14 PH1661 - Jul 14, 11:55 UTCJul 14, 13:35 UTC1h 40m
2026-07-13 PH1661 - Jul 13, 11:00 UTCJul 13, 15:30 UTC4h 30m
2026-07-11 PH1661 WOE → WOE Jul 11, 11:20 UTCJul 11, 15:45 UTC4h 25m
2026-07-11 PH1661 - Jul 11, 10:30 UTCJul 11, 10:45 UTC15m
2026-07-05 PH1661 WOE → WOE Jul 5, 14:15 UTCJul 5, 16:10 UTC1h 55m
2026-07-05 PH1661 WOE → WOE Jul 5, 08:50 UTCJul 5, 13:45 UTC4h 55m
2026-07-04 PH1661 WOE → WOE Jul 4, 13:05 UTCJul 4, 16:35 UTC3h 30m
2026-07-04 PH1661 WOE → WOE Jul 4, 10:00 UTCJul 4, 12:35 UTC2h 35m
2026-07-04 PH1661 WOE → WOE Jul 4, 08:45 UTCJul 4, 09:05 UTC20m
2026-06-28 PH1661 WOE → WOE Jun 28, 13:59 UTCJun 28, 14:14 UTC15m
2026-06-28 PH1661 WOE → WOE Jun 28, 07:40 UTCJun 28, 12:35 UTC4h 55m
2026-06-27 PH1661 WOE → WOE Jun 27, 15:14 UTCJun 27, 15:24 UTC10m
2026-06-27 PH1661 WOE → WOE Jun 27, 13:00 UTCJun 27, 14:29 UTC1h 30m
2026-06-27 PH1661 WOE → WOE Jun 27, 11:04 UTCJun 27, 12:29 UTC1h 25m
2026-06-27 PH1661 WOE → WOE Jun 27, 09:34 UTCJun 27, 09:44 UTC10m
2026-06-27 PH1661 WOE → WOE Jun 27, 08:14 UTCJun 27, 08:55 UTC40m
2026-06-21 PH1661 WOE → WOE Jun 21, 11:00 UTCJun 21, 14:54 UTC3h 55m
2026-06-21 PH1661 WOE → WOE Jun 21, 10:09 UTCJun 21, 10:25 UTC15m
2026-06-21 PH1661 WOE → WOE Jun 21, 08:30 UTCJun 21, 09:10 UTC40m
2026-06-20 PH1661 WOE → WOE Jun 20, 14:09 UTCJun 20, 15:19 UTC1h 10m
2026-06-20 PH1661 WOE → WOE Jun 20, 13:24 UTCJun 20, 13:34 UTC10m
2026-06-20 PH1661 WOE → WOE Jun 20, 11:14 UTCJun 20, 12:50 UTC1h 35m
2026-06-14 PH1661 WOE → WOE Jun 14, 10:30 UTCJun 14, 16:20 UTC5h 50m
2026-06-14 PH1661 WOE → WOE Jun 14, 08:40 UTCJun 14, 09:55 UTC1h 15m
2026-06-13 PH1661 WOE → WOE Jun 13, 14:35 UTCJun 13, 14:50 UTC15m
2026-06-13 PH1661 WOE → WOE Jun 13, 10:35 UTCJun 13, 14:00 UTC3h 25m
2026-06-07 PH1661 WOE → WOE Jun 7, 12:30 UTCJun 7, 13:25 UTC55m
2026-06-07 PH1661 WOE → WOE Jun 7, 09:25 UTCJun 7, 11:15 UTC1h 50m
2026-06-01 PH1661 - Jun 1, 13:35 UTCJun 1, 14:45 UTC1h 10m
2026-06-01 PH1661 - Jun 1, 10:05 UTCJun 1, 12:40 UTC2h 35m
2026-05-31 PH1661 WOE → WOE May 31, 11:10 UTCMay 31, 16:15 UTC5h 5m
2026-05-31 PH1661 WOE → WOE May 31, 08:45 UTCMay 31, 10:00 UTC1h 15m
2026-05-30 PH1661 WOE → WOE May 30, 13:35 UTCMay 30, 15:00 UTC1h 25m
2026-05-30 PH1661 WOE → WOE May 30, 11:15 UTCMay 30, 12:55 UTC1h 40m
2026-05-30 PH1661 WOE → WOE May 30, 09:00 UTCMay 30, 10:30 UTC1h 30m
2026-05-25 PH1661 WOE → WOE May 25, 09:20 UTCMay 25, 15:40 UTC6h 20m
2026-05-24 PH1661 WOE → WOE May 24, 12:10 UTCMay 24, 17:00 UTC4h 50m
2026-05-24 PH1661 WOE → WOE May 24, 09:50 UTCMay 24, 11:35 UTC1h 45m
2026-05-24 PH1661 WOE → WOE May 24, 09:05 UTCMay 24, 09:15 UTC10m
2026-05-21 PH1661 WOE → WOE May 21, 11:55 UTCMay 21, 19:25 UTC7h 30m
2026-05-16 PH1661 WOE → WOE May 16, 08:46 UTCMay 16, 11:31 UTC2h 45m
2026-05-15 PH1661 WOE → WOE May 15, 12:25 UTCMay 15, 14:50 UTC2h 24m
2026-05-12 PH1661 WOE → WOE May 12, 18:35 UTCMay 12, 19:05 UTC30m
2026-05-12 PH1661 WOE → WOE May 12, 17:25 UTCMay 12, 18:00 UTC35m
2026-05-12 PH1661 WOE → WOE May 12, 16:00 UTCMay 12, 16:55 UTC55m
2026-05-10 PH1661 WOE → WOE May 10, 08:30 UTCMay 10, 14:25 UTC5h 55m
2026-05-06 PH1661 WOE → WOE May 6, 15:30 UTCMay 6, 19:20 UTC3h 49m

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

Mode-S 4863D0 frequently asked

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