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
- 57
- Distinct callsigns
- 15
- Country
- BG
- Last broadcast
- 4d 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 15 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| AIZ591 | Arkia Israel Airlines | 17 | 2026-05-25 |
| AIZ592 | Arkia Israel Airlines | 16 | 2026-05-25 |
| AIZ636 | - | 4 | 2026-05-06 |
| AIZ635 | - | 3 | 2026-05-05 |
| AIZ596 | Arkia Israel Airlines | 3 | 2026-05-20 |
| AIZ595 | Arkia Israel Airlines | 3 | 2026-05-19 |
| AIZ104 | - | 2 | 2026-05-15 |
| AIZ103 | Arkia Israel Airlines | 2 | 2026-05-14 |
| GBG303F | - | 1 | 2026-05-26 |
| AIZ301 | Arkia Israel Airlines | 1 | 2026-04-19 |
| AIZ1163 | Arkia Israel Airlines | 1 | 2026-04-26 |
| AIZ1160 | - | 1 | 2026-04-14 |
| AIZ108 | - | 1 | 2026-04-24 |
| AIZ107 | - | 1 | 2026-04-23 |
| AIZ102 | Arkia Israel Airlines | 1 | 2026-04-22 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-26 | GBG303F | - | May 26, 00:44 UTC | May 26, 02:44 UTC | 2h 0m |
| 2026-05-25 | AIZ592 | BOM → BKK | May 25, 21:40 UTC | May 25, 22:10 UTC | 30m |
| 2026-05-25 | AIZ592 | BOM → BKK | May 25, 11:25 UTC | May 25, 14:45 UTC | 3h 20m |
| 2026-05-25 | AIZ591 | BOM → BKK | May 25, 08:40 UTC | May 25, 09:10 UTC | 30m |
| 2026-05-25 | AIZ591 | BOM → BKK | May 25, 05:30 UTC | May 25, 06:00 UTC | 30m |
| 2026-05-24 | AIZ591 | BOM → BKK | May 24, 21:30 UTC | May 24, 21:45 UTC | 15m |
| 2026-05-23 | AIZ592 | BOM → BKK | May 23, 16:15 UTC | May 24, 02:45 UTC | 10h 31m |
| 2026-05-22 | AIZ591 | BOM → BKK | May 22, 04:40 UTC | May 22, 16:20 UTC | 11h 40m |
| 2026-05-20 | AIZ596 | HAN → TLV | May 20, 21:55 UTC | May 21, 00:20 UTC | 2h 25m |
| 2026-05-19 | AIZ595 | LCA → HAN | May 19, 23:35 UTC | May 20, 23:30 UTC | 23h 56m |
| 2026-05-19 | AIZ595 | LCA → HAN | May 19, 22:20 UTC | May 20, 00:40 UTC | 2h 20m |
| 2026-05-18 | AIZ592 | BOM → BKK | May 18, 14:15 UTC | May 18, 14:50 UTC | 35m |
| 2026-05-18 | AIZ592 | BOM → BKK | May 18, 11:40 UTC | May 18, 11:55 UTC | 15m |
| 2026-05-17 | AIZ591 | BOM → BKK | May 17, 21:25 UTC | May 18, 08:30 UTC | 11h 5m |
| 2026-05-16 | AIZ592 | BOM → BKK | May 16, 16:40 UTC | May 16, 20:00 UTC | 3h 20m |
| 2026-05-15 | AIZ591 | BOM → BKK | May 15, 15:40 UTC | May 15, 19:20 UTC | 3h 40m |
| 2026-05-15 | AIZ591 | BOM → BKK | May 15, 08:00 UTC | May 15, 08:20 UTC | 20m |
| 2026-05-15 | AIZ104 | - | May 15, 05:35 UTC | May 15, 06:05 UTC | 30m |
| 2026-05-14 | AIZ103 | TLV → ATH | May 14, 14:40 UTC | May 14, 15:05 UTC | 25m |
| 2026-05-13 | AIZ596 | HAN → TLV | May 13, 21:40 UTC | May 14, 00:15 UTC | 2h 35m |
| 2026-05-12 | AIZ596 | HAN → TLV | May 12, 23:35 UTC | May 13, 23:30 UTC | 23h 55m |
| 2026-05-12 | AIZ595 | LCA → HAN | May 12, 22:20 UTC | May 13, 00:45 UTC | 2h 25m |
| 2026-05-11 | AIZ592 | BOM → BKK | May 11, 11:20 UTC | May 11, 22:05 UTC | 10h 45m |
| 2026-05-10 | AIZ591 | BOM → BKK | May 10, 21:40 UTC | May 11, 09:00 UTC | 11h 20m |
| 2026-05-09 | AIZ592 | BOM → BKK | May 9, 17:35 UTC | May 10, 04:25 UTC | 10h 50m |
| 2026-05-09 | AIZ592 | BOM → BKK | May 9, 14:30 UTC | May 9, 15:00 UTC | 30m |
| 2026-05-08 | AIZ591 | BOM → BKK | May 8, 10:25 UTC | May 8, 10:39 UTC | 15m |
| 2026-05-08 | AIZ591 | BOM → BKK | May 8, 08:05 UTC | May 8, 08:29 UTC | 25m |
| 2026-05-07 | AIZ591 | BOM → BKK | May 7, 21:30 UTC | May 8, 05:29 UTC | 8h 0m |
| 2026-05-06 | AIZ636 | - | May 6, 08:20 UTC | May 6, 18:00 UTC | 9h 39m |
| 2026-05-05 | AIZ635 | TLV → DEL | May 5, 17:20 UTC | May 6, 02:55 UTC | 9h 35m |
| 2026-05-04 | AIZ592 | BOM → BKK | May 4, 11:45 UTC | May 4, 15:05 UTC | 3h 20m |
| 2026-05-04 | AIZ591 | BOM → BKK | May 4, 07:55 UTC | May 4, 08:25 UTC | 30m |
| 2026-05-03 | AIZ591 | BOM → BKK | May 3, 21:05 UTC | May 4, 05:20 UTC | 8h 15m |
| 2026-05-03 | AIZ104 | - | May 3, 16:50 UTC | May 3, 18:45 UTC | 1h 55m |
| 2026-04-27 | AIZ103 | TLV → ATH | Apr 27, 17:40 UTC | Apr 27, 19:40 UTC | 2h 0m |
| 2026-04-27 | AIZ636 | - | Apr 27, 06:40 UTC | Apr 27, 15:10 UTC | 8h 30m |
| 2026-04-27 | AIZ636 | - | Apr 27, 05:20 UTC | Apr 27, 05:40 UTC | 20m |
| 2026-04-26 | AIZ635 | - | Apr 26, 14:50 UTC | Apr 27, 00:15 UTC | 9h 25m |
| 2026-04-26 | AIZ1163 | TLV → LCA | Apr 26, 05:15 UTC | Apr 26, 06:00 UTC | 45m |
| 2026-04-25 | AIZ592 | BOM → BKK | Apr 25, 18:15 UTC | Apr 26, 03:20 UTC | 9h 5m |
| 2026-04-25 | AIZ592 | BOM → BKK | Apr 25, 15:35 UTC | Apr 25, 15:55 UTC | 20m |
| 2026-04-24 | AIZ591 | BOM → BKK | Apr 24, 15:00 UTC | Apr 25, 02:25 UTC | 11h 25m |
| 2026-04-24 | AIZ108 | - | Apr 24, 12:15 UTC | Apr 24, 13:00 UTC | 45m |
| 2026-04-23 | AIZ107 | - | Apr 23, 21:15 UTC | Apr 23, 22:00 UTC | 45m |
| 2026-04-23 | AIZ636 | - | Apr 23, 09:10 UTC | Apr 23, 19:05 UTC | 9h 54m |
| 2026-04-22 | AIZ635 | - | Apr 22, 20:55 UTC | Apr 23, 06:20 UTC | 9h 25m |
| 2026-04-22 | AIZ102 | MAD → MAD | Apr 22, 11:00 UTC | Apr 22, 12:30 UTC | 1h 30m |
| 2026-04-19 | AIZ301 | TLV → IJK | Apr 19, 22:30 UTC | Apr 20, 00:30 UTC | 2h 0m |
| 2026-04-15 | AIZ592 | BOM → BKK | Apr 15, 15:05 UTC | Apr 15, 15:40 UTC | 35m |
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 .