sensors Mode-S transponder
451E8E
ICAO 24-bit transponder address · allocated to Bulgaria
Currently assigned to LZ-FBD · AIRBUS A-320
- Hex
- 451E8E
- Octal
- 21217216
- Decimal
- 4,529,806
- Country
- BG
- Tail
- LZ-FBD
- Type
- A320
- Flights observed
- 65
- Distinct callsigns
- 20
- Country
- BG
- Last broadcast
- 4d ago
Last known position
Country allocation
The ICAO 24-bit address 451E8E 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
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| LZB472 | - | 5 | 2026-04-17 |
| LZB471 | Bulgaria Air | 4 | 2026-04-17 |
| LZB473 | Bulgaria Air | 3 | 2026-05-23 |
| LZB9991 | - | 2 | 2026-04-22 |
| LZB8534 | Bulgaria Air | 2 | 2026-05-01 |
| LZB8228 | - | 2 | 2026-05-25 |
| LZB8227 | - | 2 | 2026-05-25 |
| LZB6814 | Bulgaria Air | 2 | 2026-05-06 |
| LZB6813 | Bulgaria Air | 2 | 2026-05-06 |
| LZB474 | Bulgaria Air | 2 | 2026-05-23 |
| LZB438 | Bulgaria Air | 2 | 2026-04-17 |
| BVL8492 | - | 2 | 2026-04-30 |
| BVL8491 | - | 2 | 2026-04-29 |
| LZB9992 | - | 1 | 2026-04-15 |
| LZB972 | Bulgaria Air | 1 | 2026-05-26 |
| LZB971 | Bulgaria Air | 1 | 2026-05-26 |
| LZB8926 | - | 1 | 2026-05-20 |
| LZB8925 | - | 1 | 2026-05-13 |
| LZB8773 | Bulgaria Air | 1 | 2026-04-25 |
| LZB8533 | Bulgaria Air | 1 | 2026-05-01 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | LZB320 | BER → SOF | May 29, 15:10 UTC | May 29, 16:45 UTC | 1h 36m |
| 2026-05-29 | LZB319 | SOF → BER | May 29, 12:05 UTC | May 29, 14:00 UTC | 1h 55m |
| 2026-05-26 | LZB302 | PRG → SOF | May 26, 10:05 UTC | May 26, 11:30 UTC | 1h 25m |
| 2026-05-26 | LZB301 | SOF → PRG | May 26, 07:19 UTC | May 26, 08:54 UTC | 1h 35m |
| 2026-05-26 | LZB972 | VAR → SOF | May 26, 05:34 UTC | May 26, 05:49 UTC | 15m |
| 2026-05-26 | LZB971 | SOF → VAR | May 26, 04:04 UTC | May 26, 04:39 UTC | 35m |
| 2026-05-25 | LZB8228 | - | May 25, 15:40 UTC | May 25, 16:40 UTC | 1h 0m |
| 2026-05-25 | LZB8228 | - | May 25, 12:25 UTC | May 25, 14:05 UTC | 1h 40m |
| 2026-05-25 | LZB8227 | - | May 25, 09:45 UTC | May 25, 11:10 UTC | 1h 25m |
| 2026-05-25 | LZB8227 | - | May 25, 08:10 UTC | May 25, 08:20 UTC | 10m |
| 2026-05-24 | LZB808 | ATH → SOF | May 24, 15:50 UTC | May 24, 16:35 UTC | 45m |
| 2026-05-24 | LZB807 | SOF → ATH | May 24, 13:35 UTC | May 24, 14:30 UTC | 55m |
| 2026-05-23 | LZB474 | MAD → SOF | May 23, 12:20 UTC | May 23, 15:25 UTC | 3h 5m |
| 2026-05-23 | LZB473 | SOF → MAD | May 23, 06:05 UTC | May 23, 09:05 UTC | 3h 0m |
| 2026-05-21 | LZB7714 | NBE → SOF | May 21, 09:15 UTC | May 21, 10:40 UTC | 1h 25m |
| 2026-05-21 | LZB7713 | SOF → NBE | May 21, 06:10 UTC | May 21, 08:05 UTC | 1h 55m |
| 2026-05-20 | LZB8926 | - | May 20, 08:10 UTC | May 20, 11:55 UTC | 3h 45m |
| 2026-05-13 | LZB8925 | - | May 13, 05:15 UTC | May 13, 09:55 UTC | 4h 40m |
| 2026-05-11 | BVL5442 | - | May 11, 14:00 UTC | May 11, 15:25 UTC | 1h 25m |
| 2026-05-11 | BVL5441 | - | May 11, 10:45 UTC | May 11, 12:40 UTC | 1h 55m |
| 2026-05-10 | LZB5226 | OMO → VAR | May 10, 16:10 UTC | May 10, 17:15 UTC | 1h 5m |
| 2026-05-10 | LZB5225 | SOF → OMO | May 10, 14:04 UTC | May 10, 14:40 UTC | 35m |
| 2026-05-07 | BGH7702 | - | May 7, 11:20 UTC | May 7, 15:30 UTC | 4h 10m |
| 2026-05-06 | LZB6814 | CAI → SOF | May 6, 06:50 UTC | May 6, 08:35 UTC | 1h 45m |
| 2026-05-06 | LZB6813 | SOF → CAI | May 6, 03:15 UTC | May 6, 04:50 UTC | 1h 35m |
| 2026-05-03 | BGH7701 | - | May 3, 13:15 UTC | May 3, 17:35 UTC | 4h 20m |
| 2026-05-03 | BGH3007 | - | May 3, 05:25 UTC | May 3, 11:50 UTC | 6h 25m |
| 2026-05-02 | BGH3005 | - | May 2, 13:05 UTC | May 2, 19:35 UTC | 6h 30m |
| 2026-05-02 | BGH3003 | - | May 2, 04:25 UTC | May 2, 11:05 UTC | 6h 40m |
| 2026-05-01 | LZB8534 | SSH → SOF | May 1, 17:55 UTC | May 1, 18:15 UTC | 20m |
| 2026-05-01 | LZB8534 | SSH → SOF | May 1, 15:00 UTC | May 1, 17:15 UTC | 2h 15m |
| 2026-05-01 | LZB8533 | SOF → VAR | May 1, 11:25 UTC | May 1, 13:25 UTC | 2h 0m |
| 2026-04-30 | BVL8492 | - | Apr 30, 16:15 UTC | Apr 30, 16:35 UTC | 20m |
| 2026-04-30 | BVL8492 | - | Apr 30, 12:45 UTC | Apr 30, 15:20 UTC | 2h 35m |
| 2026-04-29 | BVL8491 | - | Apr 29, 04:39 UTC | Apr 29, 07:24 UTC | 2h 45m |
| 2026-04-29 | BVL8491 | - | Apr 29, 03:15 UTC | Apr 29, 03:40 UTC | 25m |
| 2026-04-26 | LZB8174 | SSH → SOF | Apr 26, 08:35 UTC | Apr 26, 16:40 UTC | 8h 5m |
| 2026-04-25 | LZB8773 | SOF → HRG | Apr 25, 05:20 UTC | Apr 25, 12:00 UTC | 6h 40m |
| 2026-04-24 | LZB7522 | - | Apr 24, 11:20 UTC | Apr 24, 17:35 UTC | 6h 15m |
| 2026-04-24 | LZB7521 | VAR → LIS | Apr 24, 05:40 UTC | Apr 24, 09:45 UTC | 4h 5m |
| 2026-04-22 | LZB9991 | - | Apr 22, 10:25 UTC | Apr 22, 10:50 UTC | 25m |
| 2026-04-22 | LZB6814 | CAI → SOF | Apr 22, 06:45 UTC | Apr 22, 08:40 UTC | 1h 55m |
| 2026-04-22 | LZB6813 | SOF → CAI | Apr 22, 03:30 UTC | Apr 22, 05:25 UTC | 1h 55m |
| 2026-04-19 | LZB492 | ZRH → SOF | Apr 19, 11:30 UTC | Apr 19, 13:00 UTC | 1h 30m |
| 2026-04-19 | LZB491 | SOF → ZRH | Apr 19, 08:35 UTC | Apr 19, 10:20 UTC | 1h 45m |
| 2026-04-18 | LZB474 | - | Apr 18, 10:50 UTC | Apr 18, 13:30 UTC | 2h 40m |
| 2026-04-18 | LZB473 | SOF → MAD | Apr 18, 07:25 UTC | Apr 18, 08:55 UTC | 1h 30m |
| 2026-04-18 | LZB473 | SOF → MAD | Apr 18, 06:00 UTC | Apr 18, 08:55 UTC | 2h 55m |
| 2026-04-17 | LZB438 | FRA → SOF | Apr 17, 17:25 UTC | Apr 17, 18:20 UTC | 55m |
| 2026-04-17 | LZB438 | FRA → SOF | Apr 17, 16:45 UTC | Apr 17, 17:15 UTC | 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 LZ-FBD page for operator, model, and routing details .