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
- 137
- Distinct callsigns
- 10
- Country
- BG
- Last broadcast
- 1h 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 10 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| JAF3LC | Jetairfly | 24 | 2026-05-29 |
| JAF76T | Jetairfly | 21 | 2026-05-26 |
| JAF5GA | Jetairfly | 21 | 2026-05-26 |
| JAF2XB | Jetairfly | 15 | 2026-05-29 |
| JAF1VY | - | 14 | 2026-05-28 |
| JAF94H | Jetairfly | 13 | 2026-05-24 |
| JAF95J | - | 11 | 2026-05-28 |
| JAF56C | Jetairfly | 9 | 2026-05-28 |
| JAF5GJ | Jetairfly | 5 | 2026-05-14 |
| JAF49Y | Jetairfly | 4 | 2026-05-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | JAF2XB | BLQ → RAK | May 29, 19:35 UTC | May 29, 22:00 UTC | 2h 25m |
| 2026-05-29 | JAF3LC | RAK → BLQ | May 29, 15:05 UTC | May 29, 17:45 UTC | 2h 40m |
| 2026-05-28 | JAF1VY | - | May 28, 19:25 UTC | May 28, 22:20 UTC | 2h 55m |
| 2026-05-28 | JAF95J | - | May 28, 10:05 UTC | May 28, 18:05 UTC | 8h 0m |
| 2026-05-28 | JAF56C | BRU → ALC | May 28, 06:05 UTC | May 28, 08:55 UTC | 2h 50m |
| 2026-05-26 | JAF5GA | INN → ANR | May 26, 18:45 UTC | May 26, 21:09 UTC | 2h 25m |
| 2026-05-26 | JAF49Y | AGA → ORY | May 26, 09:29 UTC | May 26, 16:59 UTC | 7h 30m |
| 2026-05-26 | JAF76T | RAK → ORY | May 26, 05:40 UTC | May 26, 08:15 UTC | 2h 35m |
| 2026-05-25 | JAF2XB | BLQ → RAK | May 25, 19:44 UTC | May 25, 22:25 UTC | 2h 40m |
| 2026-05-25 | JAF3LC | RAK → BLQ | May 25, 15:55 UTC | May 25, 18:35 UTC | 2h 40m |
| 2026-05-24 | JAF3LC | RAK → BLQ | May 24, 20:35 UTC | May 25, 18:35 UTC | 22h 0m |
| 2026-05-24 | JAF5GA | INN → ANR | May 24, 19:00 UTC | May 25, 18:30 UTC | 23h 30m |
| 2026-05-24 | JAF94H | ORY → AGA | May 24, 10:05 UTC | May 24, 17:35 UTC | 7h 30m |
| 2026-05-24 | JAF76T | RAK → ORY | May 24, 06:25 UTC | May 24, 08:50 UTC | 2h 25m |
| 2026-05-23 | JAF1VY | - | May 23, 19:45 UTC | May 23, 22:30 UTC | 2h 45m |
| 2026-05-23 | JAF95J | - | May 23, 10:15 UTC | May 23, 18:15 UTC | 8h 1m |
| 2026-05-23 | JAF56C | BRU → ALC | May 23, 06:00 UTC | May 23, 08:50 UTC | 2h 50m |
| 2026-05-22 | JAF2XB | BLQ → RAK | May 22, 18:55 UTC | May 22, 21:30 UTC | 2h 35m |
| 2026-05-22 | JAF3LC | RAK → BLQ | May 22, 15:05 UTC | May 22, 17:40 UTC | 2h 35m |
| 2026-05-21 | JAF3LC | RAK → BLQ | May 21, 20:35 UTC | May 22, 17:40 UTC | 21h 5m |
| 2026-05-21 | JAF1VY | - | May 21, 19:40 UTC | May 22, 17:40 UTC | 22h 0m |
| 2026-05-21 | JAF95J | - | May 21, 10:20 UTC | May 21, 18:00 UTC | 7h 40m |
| 2026-05-20 | JAF5GA | INN → ANR | May 20, 19:25 UTC | May 21, 09:00 UTC | 13h 35m |
| 2026-05-20 | JAF76T | RAK → ORY | May 20, 15:25 UTC | May 20, 17:55 UTC | 2h 30m |
| 2026-05-19 | JAF76T | RAK → ORY | May 19, 20:35 UTC | May 20, 17:55 UTC | 21h 21m |
| 2026-05-19 | JAF5GA | INN → ANR | May 19, 18:50 UTC | May 20, 17:55 UTC | 23h 6m |
| 2026-05-19 | JAF94H | ORY → AGA | May 19, 09:45 UTC | May 19, 17:25 UTC | 7h 40m |
| 2026-05-19 | JAF76T | RAK → ORY | May 19, 05:50 UTC | May 19, 08:20 UTC | 2h 30m |
| 2026-05-18 | JAF2XB | BLQ → RAK | May 18, 19:25 UTC | May 18, 22:25 UTC | 3h 0m |
| 2026-05-18 | JAF3LC | RAK → BLQ | May 18, 15:20 UTC | May 18, 18:10 UTC | 2h 50m |
| 2026-05-17 | JAF3LC | RAK → BLQ | May 17, 20:35 UTC | May 18, 18:10 UTC | 21h 35m |
| 2026-05-17 | JAF3LC | RAK → BLQ | May 17, 19:01 UTC | May 18, 18:10 UTC | 23h 10m |
| 2026-05-17 | JAF94H | ORY → AGA | May 17, 10:05 UTC | May 17, 17:35 UTC | 7h 30m |
| 2026-05-17 | JAF76T | RAK → ORY | May 17, 06:15 UTC | May 17, 08:45 UTC | 2h 30m |
| 2026-05-16 | JAF1VY | - | May 16, 19:40 UTC | May 16, 22:40 UTC | 3h 0m |
| 2026-05-16 | JAF95J | - | May 16, 10:25 UTC | May 16, 18:15 UTC | 7h 50m |
| 2026-05-15 | JAF2XB | BLQ → RAK | May 15, 18:20 UTC | May 16, 09:01 UTC | 14h 41m |
| 2026-05-15 | JAF3LC | RAK → BLQ | May 15, 14:50 UTC | May 15, 17:00 UTC | 2h 10m |
| 2026-05-14 | JAF3LC | RAK → BLQ | May 14, 20:35 UTC | May 15, 17:00 UTC | 20h 24m |
| 2026-05-14 | JAF1VY | - | May 14, 19:30 UTC | May 15, 17:00 UTC | 21h 29m |
| 2026-05-14 | JAF5GJ | TFS → OST | May 14, 10:20 UTC | May 14, 18:05 UTC | 7h 45m |
| 2026-05-13 | JAF56C | BRU → ALC | May 13, 18:55 UTC | May 14, 08:40 UTC | 13h 45m |
| 2026-05-13 | JAF76T | RAK → ORY | May 13, 15:10 UTC | May 13, 17:35 UTC | 2h 25m |
| 2026-05-12 | JAF76T | RAK → ORY | May 12, 20:35 UTC | May 13, 17:35 UTC | 21h 0m |
| 2026-05-12 | JAF5GA | INN → ANR | May 12, 18:35 UTC | May 13, 17:35 UTC | 23h 0m |
| 2026-05-12 | JAF94H | ORY → AGA | May 12, 09:45 UTC | May 12, 17:15 UTC | 7h 30m |
| 2026-05-11 | JAF2XB | BLQ → RAK | May 11, 19:25 UTC | May 12, 08:15 UTC | 12h 50m |
| 2026-05-11 | JAF3LC | RAK → BLQ | May 11, 15:25 UTC | May 11, 17:35 UTC | 2h 11m |
| 2026-05-10 | JAF3LC | RAK → BLQ | May 10, 20:35 UTC | May 11, 17:35 UTC | 21h 1m |
| 2026-05-10 | JAF5GA | INN → ANR | May 10, 19:05 UTC | May 11, 17:35 UTC | 22h 31m |
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 .