sensors Mode-S transponder

3DAFB2

ICAO 24-bit transponder address · allocated to Germany

Currently assigned to D-GMUC · DIAMOND DA-42 Guardian

Hex
3DAFB2
Octal
17327662
Decimal
4,042,674
Country
DE
Tail
D-GMUC
Type
DA42
No current signal · last broadcast 2d ago
Flights observed
64
Distinct callsigns
20
Country
DE
Last broadcast
2d ago

Last known position

Most recent position reported by Mode-S 3DAFB2.

Country allocation

The ICAO 24-bit address 3DAFB2 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 20 distinct

Callsign Airline Flights Last seen
GAF515 - 18 2026-05-08
PTO4436 - 4 2026-04-27
PTO4435 - 4 2026-04-18
PTO4432 - 3 2026-04-17
PTO4486 - 2 2026-04-15
PTO4485 - 2 2026-04-15
PTO4475 - 2 2026-05-26
PTO4463 - 2 2026-04-21
PTO4431 - 2 2026-04-17
PTO4429 - 2 2026-04-28
PTO4418 - 2 2026-05-21
PTO4417 - 2 2026-05-21
PTO4416 - 2 2026-05-21
PTO7725 - 1 2026-05-06
PTO7724 - 1 2026-05-06
PTO4476 - 1 2026-05-26
PTO4467 - 1 2026-05-16
PTO4464 - 1 2026-04-20
PTO4462 - 1 2026-04-21
PTO4451 - 1 2026-05-13

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-28 PTO4413 - May 28, 09:30 UTCMay 28, 11:10 UTC1h 40m
2026-05-28 PTO4412 - May 28, 06:30 UTCMay 28, 08:10 UTC1h 40m
2026-05-26 PTO4476 RLG → RLG May 26, 11:34 UTCMay 26, 14:00 UTC2h 25m
2026-05-26 PTO4475 - May 26, 07:45 UTCMay 26, 09:49 UTC2h 5m
2026-05-26 PTO4475 - May 26, 06:49 UTCMay 26, 06:59 UTC10m
2026-05-22 GAF525 - May 22, 06:40 UTCMay 22, 10:30 UTC3h 50m
2026-05-21 PTO4418 - May 21, 16:01 UTCMay 21, 18:15 UTC2h 15m
2026-05-21 PTO4417 - May 21, 12:10 UTCMay 21, 13:50 UTC1h 40m
2026-05-21 PTO4416 RLG → RLG May 21, 07:30 UTCMay 21, 09:20 UTC1h 50m
2026-05-20 PTO4418 - May 20, 14:45 UTCMay 20, 17:05 UTC2h 20m
2026-05-20 PTO4417 - May 20, 11:30 UTCMay 20, 13:30 UTC2h 0m
2026-05-20 PTO4416 RLG → RLG May 20, 08:15 UTCMay 20, 10:40 UTC2h 25m
2026-05-16 PTO4467 RLG → RLG May 16, 11:11 UTCMay 16, 13:31 UTC2h 20m
2026-05-13 PTO4451 - May 13, 06:35 UTCMay 13, 08:50 UTC2h 15m
2026-05-08 GAF515 - May 8, 07:55 UTCMay 8, 09:19 UTC1h 25m
2026-05-07 GAF515 - May 7, 11:00 UTCMay 7, 13:30 UTC2h 30m
2026-05-07 GAF515 - May 7, 07:40 UTCMay 7, 09:55 UTC2h 15m
2026-05-06 PTO7725 ODE → RLG May 6, 15:45 UTCMay 6, 18:05 UTC2h 20m
2026-05-06 PTO7724 - May 6, 12:40 UTCMay 6, 14:55 UTC2h 15m
2026-05-04 PTO1532 RLG → RLG May 4, 12:15 UTCMay 4, 13:00 UTC45m
2026-04-30 GAF515 - Apr 30, 12:50 UTCApr 30, 14:40 UTC1h 50m
2026-04-30 GAF515 - Apr 30, 09:35 UTCApr 30, 11:45 UTC2h 10m
2026-04-29 GAF515 - Apr 29, 16:30 UTCApr 29, 18:35 UTC2h 5m
2026-04-29 GAF515 - Apr 29, 13:45 UTCApr 29, 15:50 UTC2h 5m
2026-04-29 PTO4428 - Apr 29, 09:30 UTCApr 29, 11:45 UTC2h 15m
2026-04-29 PTO4427 - Apr 29, 06:15 UTCApr 29, 08:34 UTC2h 20m
2026-04-28 PTO4423 - Apr 28, 11:00 UTCApr 28, 11:40 UTC40m
2026-04-28 PTO4421 - Apr 28, 10:00 UTCApr 28, 10:20 UTC20m
2026-04-28 PTO4429 - Apr 28, 08:35 UTCApr 28, 09:15 UTC40m
2026-04-28 PTO4429 - Apr 28, 07:35 UTCApr 28, 07:55 UTC20m
2026-04-27 PTO4436 - Apr 27, 10:45 UTCApr 27, 12:30 UTC1h 45m
2026-04-27 PTO4438 - Apr 27, 07:55 UTCApr 27, 09:40 UTC1h 45m
2026-04-24 GAF515 - Apr 24, 10:55 UTCApr 24, 12:25 UTC1h 30m
2026-04-24 GAF515 - Apr 24, 08:50 UTCApr 24, 10:20 UTC1h 30m
2026-04-23 GAF515 SGE → RLG Apr 23, 16:50 UTCApr 23, 19:00 UTC2h 10m
2026-04-23 GAF515 RLG → SGE Apr 23, 12:50 UTCApr 23, 14:55 UTC2h 5m
2026-04-22 GAF515 - Apr 22, 16:30 UTCApr 22, 17:20 UTC50m
2026-04-22 GAF515 RLG → RLG Apr 22, 13:35 UTCApr 22, 15:25 UTC1h 50m
2026-04-21 PTO4463 - Apr 21, 16:20 UTCApr 21, 18:40 UTC2h 20m
2026-04-21 PTO4462 - Apr 21, 13:10 UTCApr 21, 15:10 UTC2h 0m
2026-04-20 PTO4464 - Apr 20, 16:55 UTCApr 20, 19:10 UTC2h 15m
2026-04-20 PTO4463 - Apr 20, 13:30 UTCApr 20, 15:50 UTC2h 20m
2026-04-18 PTO4436 - Apr 18, 11:30 UTCApr 18, 13:50 UTC2h 20m
2026-04-18 PTO4435 - Apr 18, 08:20 UTCApr 18, 10:30 UTC2h 10m
2026-04-17 PTO4436 - Apr 17, 15:40 UTCApr 17, 17:15 UTC1h 35m
2026-04-17 PTO4435 - Apr 17, 13:20 UTCApr 17, 14:55 UTC1h 35m
2026-04-17 PTO4432 - Apr 17, 11:20 UTCApr 17, 12:10 UTC50m
2026-04-17 PTO4432 - Apr 17, 10:50 UTCApr 17, 11:15 UTC25m
2026-04-17 PTO4432 - Apr 17, 09:40 UTCApr 17, 10:20 UTC40m
2026-04-17 PTO4431 - Apr 17, 07:20 UTCApr 17, 08:50 UTC1h 30m

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

Mode-S 3DAFB2 frequently asked

What is Mode-S code 3DAFB2?
3DAFB2 is an ICAO 24-bit transponder address. Allocated to Germany. Assigned to D-GMUC.
Where is Mode-S 3DAFB2 registered?
Mode-S code 3DAFB2 is allocated to Germany (DE). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 3DAFB2 broadcasting right now?
No active broadcast right now. Last signal was 2d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 3DAFB2, octal 17327662, decimal 4,042,674.
What flights does 3DAFB2 operate?
Mode-S 3DAFB2 has broadcast 20 distinct callsigns, including GAF515, PTO4436, PTO4435, PTO4432, PTO4486.