sensors Mode-S transponder
45217E
ICAO 24-bit transponder address · allocated to Bulgaria
Currently assigned to LZ-TWO · AIRBUS A-330-200
- Hex
- 45217E
- Octal
- 21220576
- Decimal
- 4,530,558
- Country
- BG
- Tail
- LZ-TWO
- Type
- A332
- Flights observed
- 119
- Distinct callsigns
- 20
- Country
- BG
- Last broadcast
- 16h ago
Last known position
Country allocation
The ICAO 24-bit address 45217E 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 |
|---|---|---|---|
| AIZ592 | - | 36 | 2026-07-13 |
| AIZ591 | - | 36 | 2026-07-13 |
| AIZ596 | Arkia Israel Airlines | 10 | 2026-07-01 |
| AIZ595 | Arkia Israel Airlines | 10 | 2026-07-01 |
| AIZ636 | - | 4 | 2026-05-06 |
| AIZ635 | - | 3 | 2026-05-05 |
| AIZ418 | Arkia Israel Airlines | 2 | 2026-06-14 |
| AIZ417 | Arkia Israel Airlines | 2 | 2026-06-14 |
| AIZ104 | - | 2 | 2026-05-15 |
| AIZ103 | Arkia Israel Airlines | 2 | 2026-05-14 |
| GBG303P | - | 1 | 2026-05-31 |
| GBG303F | - | 1 | 2026-05-26 |
| AIZ598 | - | 1 | 2026-07-08 |
| AIZ597 | - | 1 | 2026-07-07 |
| AIZ302 | Arkia Israel Airlines | 1 | 2026-06-07 |
| AIZ301 | Arkia Israel Airlines | 1 | 2026-04-19 |
| AIZ1596 | - | 1 | 2026-06-05 |
| AIZ1163 | Arkia Israel Airlines | 1 | 2026-04-26 |
| AIZ1160 | - | 1 | 2026-04-14 |
| AIZ108 | - | 1 | 2026-04-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | AIZ592 | - | Jul 13, 14:50 UTC | Jul 13, 22:20 UTC | 7h 30m |
| 2026-07-13 | AIZ592 | - | Jul 13, 12:15 UTC | Jul 13, 13:35 UTC | 1h 20m |
| 2026-07-13 | AIZ591 | - | Jul 13, 09:40 UTC | Jul 13, 10:05 UTC | 25m |
| 2026-07-12 | AIZ591 | - | Jul 12, 22:50 UTC | Jul 13, 06:55 UTC | 8h 5m |
| 2026-07-12 | AIZ592 | - | Jul 12, 13:25 UTC | Jul 12, 20:55 UTC | 7h 30m |
| 2026-07-12 | AIZ592 | - | Jul 12, 10:45 UTC | Jul 12, 12:10 UTC | 1h 25m |
| 2026-07-10 | AIZ591 | - | Jul 10, 17:00 UTC | Jul 10, 17:20 UTC | 20m |
| 2026-07-10 | AIZ591 | - | Jul 10, 05:50 UTC | Jul 10, 14:15 UTC | 8h 25m |
| 2026-07-08 | AIZ598 | - | Jul 8, 06:00 UTC | Jul 8, 22:00 UTC | 16h 0m |
| 2026-07-07 | AIZ597 | - | Jul 7, 22:00 UTC | Jul 8, 21:30 UTC | 23h 30m |
| 2026-07-06 | AIZ592 | - | Jul 6, 11:35 UTC | Jul 6, 21:55 UTC | 10h 20m |
| 2026-07-05 | AIZ591 | - | Jul 5, 21:50 UTC | Jul 6, 09:45 UTC | 11h 55m |
| 2026-07-05 | AIZ592 | - | Jul 5, 01:35 UTC | Jul 5, 02:05 UTC | 30m |
| 2026-07-04 | AIZ592 | - | Jul 4, 15:45 UTC | Jul 4, 19:00 UTC | 3h 15m |
| 2026-07-03 | AIZ591 | TLV → BKK | Jul 3, 05:35 UTC | Jul 3, 17:05 UTC | 11h 30m |
| 2026-07-01 | AIZ596 | HAN → TLV | Jul 1, 21:25 UTC | Jul 2, 00:00 UTC | 2h 35m |
| 2026-07-01 | AIZ596 | HAN → TLV | Jul 1, 12:35 UTC | Jul 1, 12:55 UTC | 20m |
| 2026-07-01 | AIZ595 | LCA → HAN | Jul 1, 07:50 UTC | Jul 1, 08:15 UTC | 25m |
| 2026-06-30 | AIZ595 | LCA → HAN | Jun 30, 22:05 UTC | Jul 1, 00:15 UTC | 2h 10m |
| 2026-06-29 | AIZ592 | - | Jun 29, 11:10 UTC | Jun 29, 21:14 UTC | 10h 5m |
| 2026-06-29 | AIZ591 | - | Jun 29, 05:15 UTC | Jun 29, 09:05 UTC | 3h 50m |
| 2026-06-28 | AIZ591 | - | Jun 28, 21:14 UTC | Jun 28, 21:40 UTC | 25m |
| 2026-06-28 | AIZ592 | - | Jun 28, 01:25 UTC | Jun 28, 01:50 UTC | 25m |
| 2026-06-27 | AIZ592 | - | Jun 27, 18:20 UTC | Jun 27, 18:45 UTC | 25m |
| 2026-06-27 | AIZ592 | - | Jun 27, 15:39 UTC | Jun 27, 15:55 UTC | 15m |
| 2026-06-26 | AIZ591 | - | Jun 26, 13:10 UTC | Jun 26, 16:44 UTC | 3h 35m |
| 2026-06-26 | AIZ591 | - | Jun 26, 05:19 UTC | Jun 26, 05:39 UTC | 20m |
| 2026-06-24 | AIZ596 | HAN → TLV | Jun 24, 12:30 UTC | Jun 25, 00:05 UTC | 11h 35m |
| 2026-06-24 | AIZ595 | LCA → HAN | Jun 24, 07:54 UTC | Jun 24, 08:14 UTC | 20m |
| 2026-06-23 | AIZ595 | LCA → HAN | Jun 23, 22:15 UTC | Jun 24, 00:30 UTC | 2h 15m |
| 2026-06-22 | AIZ592 | - | Jun 22, 11:19 UTC | Jun 22, 21:40 UTC | 10h 20m |
| 2026-06-22 | AIZ591 | - | Jun 22, 05:44 UTC | Jun 22, 09:24 UTC | 3h 40m |
| 2026-06-21 | AIZ591 | - | Jun 21, 21:39 UTC | Jun 21, 22:15 UTC | 35m |
| 2026-06-20 | AIZ592 | - | Jun 20, 18:34 UTC | Jun 21, 02:20 UTC | 7h 45m |
| 2026-06-20 | AIZ592 | - | Jun 20, 15:54 UTC | Jun 20, 16:14 UTC | 20m |
| 2026-06-19 | AIZ591 | - | Jun 19, 05:14 UTC | Jun 19, 17:04 UTC | 11h 50m |
| 2026-06-17 | AIZ596 | HAN → TLV | Jun 17, 21:30 UTC | Jun 18, 00:20 UTC | 2h 50m |
| 2026-06-17 | AIZ596 | HAN → TLV | Jun 17, 12:50 UTC | Jun 17, 13:10 UTC | 20m |
| 2026-06-16 | AIZ595 | LCA → HAN | Jun 16, 22:15 UTC | Jun 17, 08:40 UTC | 10h 25m |
| 2026-06-15 | AIZ592 | - | Jun 15, 11:19 UTC | Jun 15, 21:30 UTC | 10h 10m |
| 2026-06-15 | AIZ591 | - | Jun 15, 08:40 UTC | Jun 15, 09:10 UTC | 30m |
| 2026-06-14 | AIZ591 | - | Jun 14, 21:20 UTC | Jun 15, 05:55 UTC | 8h 35m |
| 2026-06-14 | AIZ418 | TBS → TLV | Jun 14, 15:40 UTC | Jun 14, 17:55 UTC | 2h 15m |
| 2026-06-14 | AIZ417 | TLV → TBS | Jun 14, 11:00 UTC | Jun 14, 13:05 UTC | 2h 5m |
| 2026-06-13 | AIZ592 | BOM → BKK | Jun 13, 16:45 UTC | Jun 14, 03:35 UTC | 10h 50m |
| 2026-06-12 | AIZ591 | BOM → BKK | Jun 12, 16:45 UTC | Jun 12, 17:10 UTC | 25m |
| 2026-06-12 | AIZ591 | BOM → BKK | Jun 12, 05:30 UTC | Jun 12, 14:01 UTC | 8h 30m |
| 2026-06-11 | AIZ418 | TBS → TLV | Jun 11, 15:45 UTC | Jun 11, 18:10 UTC | 2h 25m |
| 2026-06-11 | AIZ417 | TLV → TBS | Jun 11, 09:25 UTC | Jun 11, 11:45 UTC | 2h 20m |
| 2026-06-10 | AIZ596 | HAN → TLV | Jun 10, 20:45 UTC | Jun 10, 23:45 UTC | 3h 0m |
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-TWO page for operator, model, and routing details .