sensors Mode-S transponder
4520AA
ICAO 24-bit transponder address · allocated to Bulgaria
Currently assigned to LZ-FBG · AIRBUS A-320
- Hex
- 4520AA
- Octal
- 21220252
- Decimal
- 4,530,346
- Country
- BG
- Tail
- LZ-FBG
- Type
- A320
- Flights observed
- 254
- Distinct callsigns
- 11
- Country
- BG
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address 4520AA 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 11 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JAF2XB | - | Jul 13, 19:15 UTC | Jul 13, 22:00 UTC | 2h 45m |
| 2026-07-13 | JAF1VY | - | Jul 13, 10:20 UTC | Jul 13, 17:45 UTC | 7h 25m |
| 2026-07-13 | JAF56C | - | Jul 13, 06:05 UTC | Jul 13, 08:35 UTC | 2h 30m |
| 2026-07-12 | JAF5GA | - | Jul 12, 18:55 UTC | Jul 12, 21:40 UTC | 2h 45m |
| 2026-07-12 | JAF94H | ORY → ORY | Jul 12, 10:05 UTC | Jul 12, 17:20 UTC | 7h 15m |
| 2026-07-11 | JAF1VY | - | Jul 11, 19:20 UTC | Jul 12, 08:30 UTC | 13h 10m |
| 2026-07-11 | JAF95J | - | Jul 11, 10:10 UTC | Jul 11, 17:55 UTC | 7h 45m |
| 2026-07-10 | JAF2XB | - | Jul 10, 19:00 UTC | Jul 11, 08:45 UTC | 13h 46m |
| 2026-07-10 | JAF5GA | ORY → BLQ | Jul 10, 09:50 UTC | Jul 10, 17:10 UTC | 7h 20m |
| 2026-07-10 | JAF76T | - | Jul 10, 06:00 UTC | Jul 10, 08:25 UTC | 2h 25m |
| 2026-07-09 | JAF1VY | - | Jul 9, 19:25 UTC | Jul 9, 22:20 UTC | 2h 55m |
| 2026-07-09 | JAF95J | - | Jul 9, 10:20 UTC | Jul 9, 18:05 UTC | 7h 45m |
| 2026-07-08 | JAF5GA | - | Jul 8, 19:00 UTC | Jul 9, 08:55 UTC | 13h 55m |
| 2026-07-08 | JAF2XB | - | Jul 8, 10:25 UTC | Jul 8, 17:55 UTC | 7h 30m |
| 2026-07-07 | JAF3LC | ORY → BLQ | Jul 7, 18:45 UTC | Jul 8, 09:05 UTC | 14h 20m |
| 2026-07-07 | JAF94H | ORY → ORY | Jul 7, 09:35 UTC | Jul 7, 17:05 UTC | 7h 30m |
| 2026-07-07 | JAF76T | - | Jul 7, 05:45 UTC | Jul 7, 08:25 UTC | 2h 40m |
| 2026-07-06 | JAF2XB | - | Jul 6, 19:10 UTC | Jul 6, 21:55 UTC | 2h 45m |
| 2026-07-06 | JAF1VY | - | Jul 6, 10:15 UTC | Jul 6, 17:45 UTC | 7h 30m |
| 2026-07-05 | JAF5GA | - | Jul 5, 18:50 UTC | Jul 6, 09:00 UTC | 14h 10m |
| 2026-07-05 | JAF49Y | ORY → ORY | Jul 5, 10:05 UTC | Jul 5, 17:35 UTC | 7h 30m |
| 2026-07-05 | JAF76T | - | Jul 5, 06:10 UTC | Jul 5, 08:50 UTC | 2h 40m |
| 2026-07-04 | JAF1VY | - | Jul 4, 19:05 UTC | Jul 4, 21:45 UTC | 2h 40m |
| 2026-07-04 | JAF95J | - | Jul 4, 10:00 UTC | Jul 4, 17:50 UTC | 7h 50m |
| 2026-07-04 | JAF56C | - | Jul 4, 06:10 UTC | Jul 4, 08:50 UTC | 2h 40m |
| 2026-07-03 | JAF2XB | - | Jul 3, 18:50 UTC | Jul 3, 21:30 UTC | 2h 40m |
| 2026-07-03 | JAF3LC | - | Jul 3, 14:50 UTC | Jul 3, 17:30 UTC | 2h 40m |
| 2026-07-03 | JAF5GA | - | Jul 3, 10:20 UTC | Jul 3, 12:40 UTC | 2h 20m |
| 2026-07-02 | JAF76T | - | Jul 2, 19:20 UTC | Jul 3, 08:30 UTC | 13h 10m |
| 2026-07-02 | JAF5GJ | - | Jul 2, 10:25 UTC | Jul 2, 18:00 UTC | 7h 35m |
| 2026-07-01 | JAF5GA | - | Jul 1, 19:10 UTC | Jul 2, 09:20 UTC | 14h 10m |
| 2026-07-01 | JAF76T | - | Jul 1, 14:50 UTC | Jul 1, 17:35 UTC | 2h 45m |
| 2026-07-01 | JAF2XB | - | Jul 1, 10:15 UTC | Jul 1, 12:50 UTC | 2h 35m |
| 2026-06-30 | JAF3LC | ORY → BLQ | Jun 30, 18:25 UTC | Jul 1, 09:00 UTC | 14h 35m |
| 2026-06-30 | JAF49Y | ORY → ORY | Jun 30, 09:55 UTC | Jun 30, 17:05 UTC | 7h 10m |
| 2026-06-30 | JAF76T | - | Jun 30, 05:45 UTC | Jun 30, 08:30 UTC | 2h 45m |
| 2026-06-29 | JAF2XB | - | Jun 29, 19:24 UTC | Jun 29, 22:15 UTC | 2h 50m |
| 2026-06-29 | JAF1VY | - | Jun 29, 10:15 UTC | Jun 29, 17:55 UTC | 7h 40m |
| 2026-06-29 | JAF56C | - | Jun 29, 06:09 UTC | Jun 29, 09:00 UTC | 2h 50m |
| 2026-06-28 | JAF5GA | - | Jun 28, 18:59 UTC | Jun 28, 21:40 UTC | 2h 40m |
| 2026-06-28 | JAF94H | ORY → ORY | Jun 28, 10:39 UTC | Jun 28, 17:50 UTC | 7h 10m |
| 2026-06-28 | JAF76T | - | Jun 28, 06:00 UTC | Jun 28, 08:39 UTC | 2h 40m |
| 2026-06-27 | JAF1VY | - | Jun 27, 19:15 UTC | Jun 27, 22:09 UTC | 2h 55m |
| 2026-06-27 | JAF95J | - | Jun 27, 10:00 UTC | Jun 27, 17:44 UTC | 7h 45m |
| 2026-06-26 | JAF2XB | - | Jun 26, 19:00 UTC | Jun 27, 08:29 UTC | 13h 30m |
| 2026-06-26 | JAF3LC | - | Jun 26, 14:55 UTC | Jun 26, 17:25 UTC | 2h 30m |
| 2026-06-25 | JAF3LC | - | Jun 25, 20:34 UTC | Jun 26, 17:25 UTC | 20h 50m |
| 2026-06-25 | JAF1VY | - | Jun 25, 19:34 UTC | Jun 26, 17:25 UTC | 21h 50m |
| 2026-06-25 | JAF95J | - | Jun 25, 10:25 UTC | Jun 25, 18:04 UTC | 7h 40m |
| 2026-06-25 | JAF56C | - | Jun 25, 06:09 UTC | Jun 25, 08:40 UTC | 2h 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-FBG page for operator, model, and routing details .