sensors Mode-S transponder
0A0048
ICAO 24-bit transponder address · allocated to Algeria
Currently assigned to 7T-VJZ · AIRBUS A-330-200
- Hex
- 0A0048
- Octal
- 02400110
- Decimal
- 655,432
- Country
- DZ
- Tail
- 7T-VJZ
- Type
- A332
- Flights observed
- 137
- Distinct callsigns
- 20
- Country
- DZ
- Last broadcast
- 16d ago
Last known position
Country allocation
The ICAO 24-bit address 0A0048 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 | 13 | 2026-06-12 |
| DAH330 | Air Algerie | 6 | 2026-06-22 |
| DAH328 | Air Algerie | 6 | 2026-06-19 |
| DAH305 | - | 6 | 2026-06-19 |
| DAH465 | Air Algerie | 5 | 2026-06-16 |
| DAH329 | - | 5 | 2026-06-19 |
| DAH2700 | Air Algerie | 5 | 2026-06-06 |
| DAH483 | Air Algerie | 4 | 2026-05-17 |
| DAH469 | Air Algerie | 4 | 2026-05-20 |
| DAH462 | Air Algerie | 4 | 2026-05-17 |
| DAH385 | Air Algerie | 4 | 2026-05-12 |
| DAH371 | Air Algerie | 4 | 2026-05-16 |
| DAH2701 | Air Algerie | 4 | 2026-06-06 |
| DAH467 | Air Algerie | 3 | 2026-06-10 |
| DAH331 | Air Algerie | 3 | 2026-06-23 |
| DAH326 | - | 3 | 2026-06-11 |
| DAH3019 | Air Algerie | 3 | 2026-04-18 |
| DAH3017 | Air Algerie | 3 | 2026-06-22 |
| DAH1005 | Air Algerie | 3 | 2026-05-22 |
| DAH1004 | Air Algerie | 3 | 2026-05-22 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-27 | DAH1007 | - | Jun 27, 18:49 UTC | Jun 27, 20:39 UTC | 1h 50m |
| 2026-06-27 | DAH1006 | - | Jun 27, 15:34 UTC | Jun 27, 17:25 UTC | 1h 50m |
| 2026-06-24 | DAH304 | - | Jun 24, 14:45 UTC | Jun 25, 00:24 UTC | 9h 40m |
| 2026-06-24 | DAH6962 | - | Jun 24, 07:50 UTC | Jun 24, 12:25 UTC | 4h 35m |
| 2026-06-24 | DAH6649 | - | Jun 24, 02:20 UTC | Jun 24, 02:34 UTC | 15m |
| 2026-06-23 | DAH331 | MED → ALG | Jun 23, 14:04 UTC | Jun 24, 00:49 UTC | 10h 45m |
| 2026-06-23 | DAH331 | MED → ALG | Jun 23, 04:09 UTC | Jun 24, 00:49 UTC | 20h 40m |
| 2026-06-23 | DAH331 | MED → ALG | Jun 23, 03:34 UTC | Jun 24, 00:49 UTC | 21h 15m |
| 2026-06-22 | DAH330 | CZL → MED | Jun 22, 22:05 UTC | Jun 23, 21:59 UTC | 23h 55m |
| 2026-06-22 | DAH384 | ELU → MED | Jun 22, 20:44 UTC | Jun 23, 16:29 UTC | 19h 45m |
| 2026-06-22 | DAH3017 | IST → ALG | Jun 22, 15:35 UTC | Jun 22, 18:09 UTC | 2h 35m |
| 2026-06-22 | DAH3016 | - | Jun 22, 11:24 UTC | Jun 22, 13:39 UTC | 2h 15m |
| 2026-06-21 | DAH1013 | - | Jun 21, 20:29 UTC | Jun 21, 22:10 UTC | 1h 40m |
| 2026-06-21 | DAH1012 | - | Jun 21, 16:39 UTC | Jun 21, 18:35 UTC | 1h 55m |
| 2026-06-19 | DAH329 | - | Jun 19, 22:14 UTC | Jun 20, 07:49 UTC | 9h 35m |
| 2026-06-19 | DAH328 | ORN → MED | Jun 19, 04:19 UTC | Jun 20, 00:49 UTC | 20h 30m |
| 2026-06-19 | DAH305 | - | Jun 19, 03:29 UTC | Jun 20, 00:49 UTC | 21h 20m |
| 2026-06-18 | DAH305 | - | Jun 18, 19:50 UTC | Jun 19, 05:24 UTC | 9h 34m |
| 2026-06-17 | DAH1535 | - | Jun 17, 12:00 UTC | Jun 17, 13:40 UTC | 1h 40m |
| 2026-06-17 | DAH1534 | - | Jun 17, 07:45 UTC | Jun 17, 09:45 UTC | 2h 0m |
| 2026-06-17 | DAH6501 | - | Jun 17, 00:55 UTC | Jun 17, 01:40 UTC | 45m |
| 2026-06-16 | DAH465 | JED → CZL | Jun 16, 11:00 UTC | Jun 16, 23:10 UTC | 12h 11m |
| 2026-06-16 | DAH6631 | - | Jun 16, 06:10 UTC | Jun 16, 06:50 UTC | 40m |
| 2026-06-15 | DAH461 | JED → ALG | Jun 15, 14:30 UTC | Jun 16, 04:00 UTC | 13h 30m |
| 2026-06-14 | DAH304 | - | Jun 14, 23:25 UTC | Jun 15, 10:45 UTC | 11h 20m |
| 2026-06-13 | DAH470 | - | Jun 13, 15:55 UTC | Jun 14, 04:00 UTC | 12h 5m |
| 2026-06-12 | DAH370 | TMR → MED | Jun 12, 16:05 UTC | Jun 13, 10:45 UTC | 18h 39m |
| 2026-06-12 | DAH463 | JED → ORN | Jun 12, 14:20 UTC | Jun 13, 10:45 UTC | 20h 24m |
| 2026-06-12 | DAH463 | JED → ORN | Jun 12, 14:01 UTC | Jun 13, 09:35 UTC | 19h 34m |
| 2026-06-12 | DAH463 | JED → ORN | Jun 12, 06:05 UTC | Jun 13, 02:50 UTC | 20h 45m |
| 2026-06-12 | DAH463 | JED → ORN | Jun 12, 04:55 UTC | Jun 13, 02:50 UTC | 21h 55m |
| 2026-06-11 | DAH327 | - | Jun 11, 12:50 UTC | Jun 11, 23:50 UTC | 11h 0m |
| 2026-06-11 | DAH326 | - | Jun 11, 11:50 UTC | Jun 11, 12:00 UTC | 10m |
| 2026-06-10 | DAH300 | ALG → MED | Jun 10, 21:10 UTC | Jun 11, 09:10 UTC | 12h 0m |
| 2026-06-10 | DAH467 | JED → ALG | Jun 10, 00:20 UTC | Jun 10, 18:55 UTC | 18h 35m |
| 2026-06-09 | DAH467 | JED → ALG | Jun 9, 18:05 UTC | Jun 10, 17:35 UTC | 23h 30m |
| 2026-06-09 | DAH301 | MED → ALG | Jun 9, 17:10 UTC | Jun 10, 16:00 UTC | 22h 50m |
| 2026-06-09 | DAH6613 | CZL → ALG | Jun 9, 06:10 UTC | Jun 9, 06:25 UTC | 15m |
| 2026-06-08 | DAH460 | ALG → JED | Jun 8, 14:30 UTC | Jun 9, 04:50 UTC | 14h 20m |
| 2026-06-07 | DAH305 | MED → AAE | Jun 7, 23:00 UTC | Jun 8, 09:55 UTC | 10h 55m |
| 2026-06-06 | DAH2701 | YUL → ALG | Jun 6, 20:39 UTC | Jun 7, 03:15 UTC | 6h 35m |
| 2026-06-06 | DAH2700 | ALG → YUL | Jun 6, 17:19 UTC | Jun 6, 18:04 UTC | 45m |
| 2026-06-06 | DAH2700 | ALG → YUL | Jun 6, 10:04 UTC | Jun 6, 17:15 UTC | 7h 10m |
| 2026-05-29 | DAH2701 | YUL → ALG | May 29, 20:35 UTC | May 30, 03:25 UTC | 6h 50m |
| 2026-05-29 | DAH2700 | ALG → YUL | May 29, 09:50 UTC | May 29, 17:35 UTC | 7h 45m |
| 2026-05-28 | DAH2701 | YUL → ALG | May 28, 20:30 UTC | May 29, 03:35 UTC | 7h 5m |
| 2026-05-28 | DAH2700 | ALG → YUL | May 28, 10:55 UTC | May 28, 18:25 UTC | 7h 30m |
| 2026-05-26 | DAH2701 | YUL → ALG | May 26, 20:40 UTC | May 27, 04:09 UTC | 7h 30m |
| 2026-05-26 | DAH2700 | ALG → YUL | May 26, 10:14 UTC | May 26, 17:50 UTC | 7h 35m |
| 2026-05-25 | DAH1011 | ORY → ALG | May 25, 12:15 UTC | May 25, 13:50 UTC | 1h 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 7T-VJZ page for operator, model, and routing details .