sensors Mode-S transponder
0A0044
ICAO 24-bit transponder address · allocated to Algeria
Currently assigned to 7T-VJV · AIRBUS A-330-200
- Hex
- 0A0044
- Octal
- 02400104
- Decimal
- 655,428
- Country
- DZ
- Tail
- 7T-VJV
- Type
- A332
- Flights observed
- 133
- Distinct callsigns
- 20
- Country
- DZ
- Last broadcast
- 27d ago
Last known position
Country allocation
The ICAO 24-bit address 0A0044 falls within the block assigned to Algeria (DZ) by ICAO Annex 10, Volume III. Every aircraft registered in Algeria 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 |
|---|---|---|---|
| DAH463 | Air Algerie | 10 | 2026-06-16 |
| DAH329 | - | 8 | 2026-06-17 |
| DAH328 | Air Algerie | 7 | 2026-06-15 |
| DAH467 | Air Algerie | 6 | 2026-06-01 |
| DAH1003 | Air Algerie | 6 | 2026-05-27 |
| DAH1002 | Air Algerie | 6 | 2026-05-27 |
| DAH9017 | - | 5 | 2026-06-13 |
| DAH1005 | Air Algerie | 5 | 2026-05-30 |
| DAH1004 | Air Algerie | 5 | 2026-05-30 |
| DAH465 | Air Algerie | 4 | 2026-06-02 |
| DAH385 | Air Algerie | 4 | 2026-05-17 |
| DAH304 | Air Algerie | 4 | 2026-05-12 |
| DAH8015 | Air Algerie | 3 | 2026-05-15 |
| DAH483 | Air Algerie | 3 | 2026-06-11 |
| DAH384 | Air Algerie | 3 | 2026-06-06 |
| DAH383 | Air Algerie | 3 | 2026-05-14 |
| DAH330 | Air Algerie | 3 | 2026-05-11 |
| DAH327 | Air Algerie | 3 | 2026-05-07 |
| DAH305 | Air Algerie | 3 | 2026-05-17 |
| DAH9013 | - | 2 | 2026-06-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-20 | DAH3017 | IST → ALG | Jun 20, 15:24 UTC | Jun 20, 17:24 UTC | 2h 0m |
| 2026-06-20 | DAH3016 | - | Jun 20, 10:59 UTC | Jun 20, 13:14 UTC | 2h 15m |
| 2026-06-17 | DAH329 | - | Jun 17, 08:05 UTC | Jun 18, 02:20 UTC | 18h 15m |
| 2026-06-17 | DAH329 | - | Jun 17, 03:05 UTC | Jun 18, 02:20 UTC | 23h 15m |
| 2026-06-16 | DAH463 | JED → ORN | Jun 16, 17:10 UTC | Jun 17, 10:25 UTC | 17h 16m |
| 2026-06-16 | DAH463 | JED → ORN | Jun 16, 11:05 UTC | Jun 17, 10:25 UTC | 23h 21m |
| 2026-06-16 | DAH463 | JED → ORN | Jun 16, 09:20 UTC | Jun 17, 09:00 UTC | 23h 41m |
| 2026-06-16 | DAH463 | JED → ORN | Jun 16, 03:04 UTC | Jun 17, 02:20 UTC | 23h 16m |
| 2026-06-16 | DAH463 | JED → ORN | Jun 16, 01:25 UTC | Jun 17, 01:00 UTC | 23h 36m |
| 2026-06-15 | DAH329 | - | Jun 15, 19:05 UTC | Jun 16, 19:00 UTC | 23h 55m |
| 2026-06-15 | DAH328 | ORN → MED | Jun 15, 17:04 UTC | Jun 16, 11:45 UTC | 18h 40m |
| 2026-06-15 | DAH328 | ORN → MED | Jun 15, 16:09 UTC | Jun 16, 11:45 UTC | 19h 35m |
| 2026-06-15 | DAH463 | JED → ORN | Jun 15, 00:49 UTC | Jun 15, 12:49 UTC | 12h 0m |
| 2026-06-14 | DAH6627 | - | Jun 14, 06:45 UTC | Jun 14, 07:10 UTC | 25m |
| 2026-06-13 | DAH9017 | - | Jun 13, 11:25 UTC | Jun 14, 04:25 UTC | 17h 0m |
| 2026-06-13 | DAH9017 | - | Jun 13, 03:10 UTC | Jun 14, 02:55 UTC | 23h 44m |
| 2026-06-12 | DAH9017 | - | Jun 12, 23:05 UTC | Jun 13, 20:40 UTC | 21h 34m |
| 2026-06-12 | DAH9017 | - | Jun 12, 21:55 UTC | Jun 13, 20:40 UTC | 22h 44m |
| 2026-06-12 | DAH9017 | - | Jun 12, 20:55 UTC | Jun 13, 19:00 UTC | 22h 4m |
| 2026-06-12 | DAH9013 | - | Jun 12, 13:10 UTC | Jun 13, 13:00 UTC | 23h 49m |
| 2026-06-12 | DAH9013 | - | Jun 12, 12:50 UTC | Jun 13, 04:40 UTC | 15h 50m |
| 2026-06-11 | DAH382 | - | Jun 11, 23:20 UTC | Jun 12, 09:30 UTC | 10h 11m |
| 2026-06-11 | DAH483 | JED → ALG | Jun 11, 06:45 UTC | Jun 11, 18:40 UTC | 11h 55m |
| 2026-06-10 | DAH482 | GHA → JED | Jun 10, 12:00 UTC | Jun 11, 08:30 UTC | 20h 30m |
| 2026-06-09 | DAH328 | ORN → MED | Jun 9, 17:30 UTC | Jun 10, 09:40 UTC | 16h 10m |
| 2026-06-09 | DAH328 | ORN → MED | Jun 9, 07:05 UTC | Jun 10, 06:50 UTC | 23h 45m |
| 2026-06-09 | DAH328 | ORN → MED | Jun 9, 06:45 UTC | Jun 10, 00:50 UTC | 18h 5m |
| 2026-06-09 | DAH329 | MED → ALG | Jun 9, 03:00 UTC | Jun 9, 03:15 UTC | 15m |
| 2026-06-08 | DAH463 | JED → ORN | Jun 8, 10:00 UTC | Jun 9, 02:25 UTC | 16h 25m |
| 2026-06-08 | DAH463 | JED → ORN | Jun 8, 03:10 UTC | Jun 9, 02:25 UTC | 23h 15m |
| 2026-06-08 | DAH463 | JED → ORN | Jun 8, 01:10 UTC | Jun 9, 00:55 UTC | 23h 45m |
| 2026-06-06 | DAH384 | ELU → MED | Jun 6, 22:05 UTC | Jun 7, 08:05 UTC | 10h 0m |
| 2026-06-06 | DAH384 | ELU → MED | Jun 6, 07:05 UTC | Jun 7, 07:00 UTC | 23h 55m |
| 2026-06-06 | DAH384 | ELU → MED | Jun 6, 05:45 UTC | Jun 7, 01:00 UTC | 19h 15m |
| 2026-06-05 | DAH329 | MED → ALG | Jun 5, 23:05 UTC | Jun 6, 23:00 UTC | 23h 55m |
| 2026-06-05 | DAH328 | ORN → MED | Jun 5, 13:05 UTC | Jun 6, 07:30 UTC | 18h 25m |
| 2026-06-05 | DAH9001 | JED → BLJ | Jun 5, 12:15 UTC | Jun 6, 07:30 UTC | 19h 15m |
| 2026-06-05 | DAH9001 | JED → BLJ | Jun 5, 03:05 UTC | Jun 6, 00:05 UTC | 21h 0m |
| 2026-06-04 | DAH6601 | ORN → ALG | Jun 4, 01:20 UTC | Jun 4, 01:40 UTC | 20m |
| 2026-06-03 | DAH469 | JED → CZL | Jun 3, 06:55 UTC | Jun 4, 00:00 UTC | 17h 5m |
| 2026-06-02 | DAH465 | JED → CZL | Jun 2, 02:50 UTC | Jun 2, 16:35 UTC | 13h 45m |
| 2026-06-01 | DAH1543 | CDG → ALG | Jun 1, 19:30 UTC | Jun 1, 21:10 UTC | 1h 40m |
| 2026-06-01 | DAH1542 | ALG → CDG | Jun 1, 15:50 UTC | Jun 1, 17:55 UTC | 2h 5m |
| 2026-06-01 | DAH467 | JED → ALG | Jun 1, 04:50 UTC | Jun 1, 05:00 UTC | 10m |
| 2026-05-31 | DAH466 | ALG → JED | May 31, 16:25 UTC | Jun 1, 04:15 UTC | 11h 50m |
| 2026-05-30 | DAH1005 | ORY → ALG | May 30, 16:00 UTC | May 30, 17:35 UTC | 1h 35m |
| 2026-05-30 | DAH1004 | ALG → ORY | May 30, 12:00 UTC | May 30, 13:50 UTC | 1h 50m |
| 2026-05-29 | DAH2791 | ZRH → ZRH | May 29, 13:10 UTC | May 29, 14:50 UTC | 1h 40m |
| 2026-05-29 | DAH2790 | - | May 29, 08:45 UTC | May 29, 10:35 UTC | 1h 50m |
| 2026-05-27 | DAH1003 | CDG → ALG | May 27, 11:15 UTC | May 27, 13:00 UTC | 1h 45m |
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 7T-VJV page for operator, model, and routing details .