sensors Mode-S transponder

3D6EF2

ICAO 24-bit transponder address · allocated to Germany

Currently assigned to D-FOGO · PILATUS PC-6 Turbo-Porter

Hex
3D6EF2
Octal
17267362
Decimal
4,026,098
Country
DE
Tail
D-FOGO
Type
PC6T
Broadcasting now · callsign RVP631 · 200 ft
Flights observed
308
Distinct callsigns
8
Country
DE
Last broadcast
2h ago

Current position

3D6EF2 is currently broadcasting. Map zoomed to live position.

Country allocation

The ICAO 24-bit address 3D6EF2 falls within the block assigned to Germany (DE) by ICAO Annex 10, Volume III. Every aircraft registered in Germany 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 8 distinct

Callsign Airline Flights Last seen
RVP631 - 268 2026-07-14
RVP631A - 15 2026-07-08
RVP631B - 11 2026-07-08
RVP631C - 7 2026-07-08
RVP631D - 4 2026-07-08
RVP691 - 1 2026-04-26
RVP690 - 1 2026-04-30
RVP631E - 1 2026-07-07

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 RVP631 - Jul 14, 10:00 UTCJul 14, 10:20 UTC20m
2026-07-14 RVP631 - Jul 14, 08:10 UTCJul 14, 08:35 UTC25m
2026-07-13 RVP631 - Jul 13, 10:25 UTCJul 13, 10:50 UTC25m
2026-07-12 RVP631 - Jul 12, 11:45 UTCJul 12, 12:10 UTC25m
2026-07-12 RVP631 - Jul 12, 10:35 UTCJul 12, 10:55 UTC20m
2026-07-12 RVP631 - Jul 12, 10:01 UTCJul 12, 10:25 UTC25m
2026-07-12 RVP631 - Jul 12, 09:10 UTCJul 12, 09:35 UTC25m
2026-07-12 RVP631 - Jul 12, 08:35 UTCJul 12, 09:00 UTC25m
2026-07-11 RVP631 - Jul 11, 11:15 UTCJul 11, 11:40 UTC25m
2026-07-11 RVP631 - Jul 11, 10:20 UTCJul 11, 10:45 UTC25m
2026-07-11 RVP631 - Jul 11, 09:30 UTCJul 11, 09:55 UTC25m
2026-07-11 RVP631 - Jul 11, 07:50 UTCJul 11, 08:15 UTC25m
2026-07-10 RVP631 - Jul 10, 11:55 UTCJul 10, 12:15 UTC20m
2026-07-10 RVP631 - Jul 10, 11:20 UTCJul 10, 11:45 UTC25m
2026-07-10 RVP631 - Jul 10, 10:10 UTCJul 10, 10:40 UTC30m
2026-07-10 RVP631 - Jul 10, 07:45 UTCJul 10, 08:10 UTC25m
2026-07-09 RVP631 - Jul 9, 12:15 UTCJul 9, 12:40 UTC25m
2026-07-09 RVP631 - Jul 9, 10:55 UTCJul 9, 11:20 UTC25m
2026-07-09 RVP631 PRM → PRM Jul 9, 09:50 UTCJul 9, 10:20 UTC30m
2026-07-09 RVP631 - Jul 9, 07:45 UTCJul 9, 08:05 UTC20m
2026-07-08 RVP631D - Jul 8, 12:10 UTCJul 8, 12:35 UTC25m
2026-07-08 RVP631C - Jul 8, 11:05 UTCJul 8, 11:30 UTC25m
2026-07-08 RVP631B PRM → PRM Jul 8, 10:00 UTCJul 8, 10:30 UTC30m
2026-07-08 RVP631A - Jul 8, 08:15 UTCJul 8, 08:40 UTC25m
2026-07-07 RVP631E - Jul 7, 13:00 UTCJul 7, 13:15 UTC15m
2026-07-07 RVP631D - Jul 7, 11:45 UTCJul 7, 12:15 UTC30m
2026-07-07 RVP631C - Jul 7, 10:45 UTCJul 7, 11:10 UTC25m
2026-07-07 RVP631B - Jul 7, 09:35 UTCJul 7, 10:05 UTC30m
2026-07-07 RVP631A - Jul 7, 08:35 UTCJul 7, 09:00 UTC25m
2026-07-06 RVP631B - Jul 6, 09:50 UTCJul 6, 10:15 UTC25m
2026-07-06 RVP631A - Jul 6, 07:55 UTCJul 6, 08:20 UTC25m
2026-07-05 RVP631 - Jul 5, 12:40 UTCJul 5, 13:00 UTC20m
2026-07-05 RVP631 PRM → PRM Jul 5, 12:10 UTCJul 5, 12:30 UTC20m
2026-07-05 RVP631 - Jul 5, 11:10 UTCJul 5, 11:35 UTC25m
2026-07-05 RVP631 PRM → PRM Jul 5, 10:10 UTCJul 5, 10:40 UTC30m
2026-07-05 RVP631 - Jul 5, 09:40 UTCJul 5, 10:05 UTC25m
2026-07-05 RVP631 - Jul 5, 08:40 UTCJul 5, 09:05 UTC25m
2026-07-05 RVP631 - Jul 5, 07:45 UTCJul 5, 08:05 UTC20m
2026-07-04 RVP631 - Jul 4, 12:30 UTCJul 4, 13:00 UTC30m
2026-07-04 RVP631 PRM → PRM Jul 4, 11:25 UTCJul 4, 11:55 UTC30m
2026-07-04 RVP631 - Jul 4, 10:25 UTCJul 4, 10:50 UTC25m
2026-07-04 RVP631 - Jul 4, 07:55 UTCJul 4, 08:15 UTC20m
2026-07-03 RVP631 PRM → PRM Jul 3, 10:10 UTCJul 3, 10:40 UTC30m
2026-07-03 RVP631 PRM → PRM Jul 3, 09:30 UTCJul 3, 10:00 UTC30m
2026-07-03 RVP631 PRM → PRM Jul 3, 08:15 UTCJul 3, 08:40 UTC25m
2026-07-03 RVP631 PRM → PRM Jul 3, 07:35 UTCJul 3, 08:05 UTC30m
2026-07-02 RVP631 - Jul 2, 13:10 UTCJul 2, 13:35 UTC25m
2026-07-02 RVP631 PRM → PRM Jul 2, 12:35 UTCJul 2, 13:05 UTC30m
2026-07-02 RVP631 PRM → PRM Jul 2, 11:20 UTCJul 2, 11:50 UTC30m
2026-07-02 RVP631 - Jul 2, 10:15 UTCJul 2, 10:40 UTC25m

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

Mode-S 3D6EF2 frequently asked

What is Mode-S code 3D6EF2?
3D6EF2 is an ICAO 24-bit transponder address. Allocated to Germany. Assigned to D-FOGO.
Where is Mode-S 3D6EF2 registered?
Mode-S code 3D6EF2 is allocated to Germany (DE). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 3D6EF2 broadcasting right now?
Yes. Mode-S 3D6EF2 is currently airborne.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 3D6EF2, octal 17267362, decimal 4,026,098.
What flights does 3D6EF2 operate?
Mode-S 3D6EF2 has broadcast 8 distinct callsigns, including RVP631, RVP631A, RVP631B, RVP631C, RVP631D.