sensors Mode-S transponder

451DBD

ICAO 24-bit transponder address · allocated to Bulgaria

Currently assigned to LZ-CGU · BOEING 737-400

Hex
451DBD
Octal
21216675
Decimal
4,529,597
Country
BG
Tail
LZ-CGU
Type
B734
Transponder active on ground
Flights observed
252
Distinct callsigns
20
Country
BG
Last broadcast
1h ago

Last known position

Most recent position reported by Mode-S 451DBD.

Country allocation

The ICAO 24-bit address 451DBD falls within the block assigned to Bulgaria (BG) by ICAO Annex 10, Volume III. Every aircraft registered in Bulgaria 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

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 BCS942 - Jul 14, 03:05 UTCJul 14, 04:30 UTC1h 25m
2026-07-14 BCS2204 MXP → STN Jul 14, 00:40 UTCJul 14, 02:15 UTC1h 35m
2026-07-13 BCS943 BEG → BLQ Jul 13, 21:15 UTCJul 13, 21:50 UTC35m
2026-07-13 BCS943 BEG → BLQ Jul 13, 17:30 UTCJul 13, 18:40 UTC1h 10m
2026-07-13 BCS942 MXP → BEG Jul 13, 02:35 UTCJul 13, 03:55 UTC1h 20m
2026-07-10 BCS947 BEG → LEJ Jul 10, 21:10 UTCJul 10, 21:50 UTC40m
2026-07-10 BCS947 BEG → LEJ Jul 10, 18:10 UTCJul 10, 19:15 UTC1h 5m
2026-07-10 BCS942 MXP → BEG Jul 10, 06:10 UTCJul 10, 07:30 UTC1h 20m
2026-07-10 BCS942 - Jul 10, 03:20 UTCJul 10, 04:50 UTC1h 30m
2026-07-10 BCS2204 MXP → STN Jul 10, 00:35 UTCJul 10, 02:05 UTC1h 30m
2026-07-09 BCS943 BEG → BLQ Jul 9, 21:10 UTCJul 9, 21:45 UTC35m
2026-07-09 BCS943 BEG → BLQ Jul 9, 17:50 UTCJul 9, 18:50 UTC1h 0m
2026-07-09 BCS942 MXP → BEG Jul 9, 06:10 UTCJul 9, 07:30 UTC1h 20m
2026-07-09 BCS942 - Jul 9, 03:05 UTCJul 9, 04:30 UTC1h 25m
2026-07-09 BCS2204 MXP → STN Jul 9, 00:40 UTCJul 9, 02:10 UTC1h 30m
2026-07-08 BCS943 BEG → BLQ Jul 8, 21:10 UTCJul 8, 21:50 UTC40m
2026-07-08 BCS943 BEG → BLQ Jul 8, 17:35 UTCJul 8, 18:40 UTC1h 5m
2026-07-08 BCS942 MXP → BEG Jul 8, 06:15 UTCJul 8, 07:30 UTC1h 15m
2026-07-08 BCS942 - Jul 8, 03:20 UTCJul 8, 04:40 UTC1h 20m
2026-07-08 BCS2204 MXP → STN Jul 8, 00:45 UTCJul 8, 02:15 UTC1h 30m
2026-07-07 BCS943 BEG → BLQ Jul 7, 21:15 UTCJul 7, 21:50 UTC35m
2026-07-07 BCS943 BEG → BLQ Jul 7, 17:40 UTCJul 7, 18:40 UTC1h 0m
2026-07-07 BCS942 MXP → BEG Jul 7, 06:10 UTCJul 7, 07:30 UTC1h 20m
2026-07-07 BCS942 - Jul 7, 03:15 UTCJul 7, 04:30 UTC1h 15m
2026-07-07 BCS2204 MXP → STN Jul 7, 00:30 UTCJul 7, 02:05 UTC1h 35m
2026-07-06 BCS943 BEG → BLQ Jul 6, 21:10 UTCJul 6, 21:45 UTC35m
2026-07-06 BCS943 BEG → BLQ Jul 6, 17:25 UTCJul 6, 18:30 UTC1h 5m
2026-07-06 BCS942 MXP → BEG Jul 6, 02:30 UTCJul 6, 03:45 UTC1h 15m
2026-07-03 BCS947 BEG → LEJ Jul 3, 21:20 UTCJul 3, 22:00 UTC40m
2026-07-03 BCS947 BEG → LEJ Jul 3, 18:10 UTCJul 3, 19:15 UTC1h 5m
2026-07-03 BCS942 MXP → BEG Jul 3, 06:05 UTCJul 3, 07:30 UTC1h 25m
2026-07-03 BCS942 - Jul 3, 03:15 UTCJul 3, 04:30 UTC1h 15m
2026-07-03 BCS2204 MXP → STN Jul 3, 00:45 UTCJul 3, 02:20 UTC1h 35m
2026-07-02 BCS943 BEG → BLQ Jul 2, 21:15 UTCJul 2, 21:50 UTC35m
2026-07-02 BCS943 BEG → BLQ Jul 2, 17:15 UTCJul 2, 18:15 UTC1h 0m
2026-07-02 BCS942 - Jul 2, 06:15 UTCJul 2, 07:35 UTC1h 20m
2026-07-02 BCS942 - Jul 2, 03:45 UTCJul 2, 05:00 UTC1h 15m
2026-07-02 BCS2204 - Jul 2, 00:45 UTCJul 2, 02:20 UTC1h 35m
2026-07-01 BCS943 BEG → BLQ Jul 1, 17:35 UTCJul 1, 19:05 UTC1h 30m
2026-07-01 BCS942 MXP → BEG Jul 1, 06:20 UTCJul 1, 07:45 UTC1h 25m
2026-07-01 BCS942 STN → MXP Jul 1, 03:25 UTCJul 1, 04:50 UTC1h 25m
2026-07-01 BCS2204 MXP → STN Jul 1, 00:40 UTCJul 1, 02:20 UTC1h 40m
2026-06-30 BCS943 BEG → BLQ Jun 30, 21:15 UTCJun 30, 21:55 UTC40m
2026-06-30 BCS943 BEG → BLQ Jun 30, 17:45 UTCJun 30, 18:50 UTC1h 5m
2026-06-30 BCS942 MXP → BEG Jun 30, 06:15 UTCJun 30, 07:30 UTC1h 15m
2026-06-30 BCS942 STN → MXP Jun 30, 03:25 UTCJun 30, 04:55 UTC1h 30m
2026-06-30 BCS2204 MXP → STN Jun 30, 00:35 UTCJun 30, 02:05 UTC1h 31m
2026-06-29 BCS943 BEG → BLQ Jun 29, 21:09 UTCJun 29, 21:50 UTC40m
2026-06-29 BCS943 BEG → BLQ Jun 29, 17:40 UTCJun 29, 18:44 UTC1h 5m
2026-06-29 BCS942 MXP → BEG Jun 29, 02:35 UTCJun 29, 03:54 UTC1h 20m

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

Mode-S 451DBD frequently asked

What is Mode-S code 451DBD?
451DBD is an ICAO 24-bit transponder address. Allocated to Bulgaria. Assigned to LZ-CGU.
Where is Mode-S 451DBD registered?
Mode-S code 451DBD is allocated to Bulgaria (BG). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 451DBD broadcasting right now?
Mode-S 451DBD is currently broadcasting from the ground.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 451DBD, octal 21216675, decimal 4,529,597.
What flights does 451DBD operate?
Mode-S 451DBD has broadcast 20 distinct callsigns, including BCS942, BCS943, BCS2204, BCS947, BCS8VJ.