sensors Mode-S transponder
02A196
ICAO 24-bit transponder address · allocated to Tunisia
Currently assigned to TS-IMW · AIRBUS A-320
- Hex
- 02A196
- Octal
- 00520626
- Decimal
- 172,438
- Country
- TN
- Tail
- TS-IMW
- Type
- A320
- Flights observed
- 149
- Distinct callsigns
- 20
- Country
- TN
- Last broadcast
- 1h ago
Current position
Country allocation
The ICAO 24-bit address 02A196 falls within the block assigned to Tunisia (TN) by ICAO Annex 10, Volume III. Every aircraft registered in Tunisia 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 |
|---|---|---|---|
| TAR634 | Tunisair | 17 | 2026-05-18 |
| TAR654 | Tunisair | 10 | 2026-05-19 |
| TAR655 | Tunisair | 9 | 2026-05-19 |
| TAR589 | Tunisair | 8 | 2026-05-20 |
| TAR588 | Tunisair | 8 | 2026-05-13 |
| TAR680 | Tunisair | 7 | 2026-05-28 |
| TAR463 | Tunisair | 7 | 2026-05-28 |
| TAR441 | Tunisair | 7 | 2026-05-29 |
| TAR635 | Tunisair | 6 | 2026-04-29 |
| TAR440 | Tunisair | 6 | 2026-05-29 |
| TAR682 | Tunisair | 4 | 2026-04-26 |
| TAR462 | Tunisair | 4 | 2026-05-27 |
| TAR895 | Tunisair | 3 | 2026-05-29 |
| TAR894 | Tunisair | 3 | 2026-05-28 |
| TAR695 | Tunisair | 3 | 2026-04-26 |
| TAR694 | Tunisair | 3 | 2026-04-23 |
| TAR498 | Tunisair | 3 | 2026-04-23 |
| TAR874 | Tunisair | 2 | 2026-04-15 |
| TAR850 | Tunisair | 2 | 2026-05-18 |
| TAR756 | Tunisair | 2 | 2026-05-11 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | TAR441 | ORY → MIR | May 29, 18:30 UTC | May 30, 07:30 UTC | 13h 0m |
| 2026-05-29 | TAR440 | MIR → CDG | May 29, 15:25 UTC | May 29, 17:15 UTC | 1h 50m |
| 2026-05-29 | TAR895 | HAM → MIR | May 29, 10:20 UTC | May 29, 12:40 UTC | 2h 20m |
| 2026-05-28 | TAR894 | MIR → HAM | May 28, 19:35 UTC | May 29, 08:55 UTC | 13h 20m |
| 2026-05-28 | TAR680 | MIR → MRS | May 28, 14:35 UTC | May 28, 18:35 UTC | 4h 0m |
| 2026-05-28 | TAR463 | LYS → MIR | May 28, 08:50 UTC | May 28, 13:10 UTC | 4h 20m |
| 2026-05-27 | TAR462 | MIR → LYS | May 27, 16:15 UTC | May 28, 07:20 UTC | 15h 5m |
| 2026-05-27 | TAR893 | MUC → MIR | May 27, 08:55 UTC | May 27, 15:00 UTC | 6h 5m |
| 2026-05-26 | TAR892 | MIR → MUC | May 26, 17:44 UTC | May 27, 07:25 UTC | 13h 41m |
| 2026-05-26 | TAR250 | MIR → NCE | May 26, 15:35 UTC | May 26, 16:24 UTC | 50m |
| 2026-05-26 | TAR441 | ORY → MIR | May 26, 11:30 UTC | May 26, 13:29 UTC | 2h 0m |
| 2026-05-25 | TAR440 | MIR → CDG | May 25, 20:04 UTC | May 26, 09:59 UTC | 13h 55m |
| 2026-05-25 | TAR680 | MIR → MRS | May 25, 14:35 UTC | May 25, 19:05 UTC | 4h 30m |
| 2026-05-25 | TAR463 | LYS → MIR | May 25, 08:30 UTC | May 25, 13:00 UTC | 4h 30m |
| 2026-05-24 | TAR441 | ORY → MIR | May 24, 18:00 UTC | May 25, 07:10 UTC | 13h 10m |
| 2026-05-24 | TAR440 | MIR → CDG | May 24, 11:10 UTC | May 24, 16:15 UTC | 5h 5m |
| 2026-05-23 | TAR681 | MRS → MIR | May 23, 19:40 UTC | May 24, 08:45 UTC | 13h 5m |
| 2026-05-23 | TAR680 | MIR → MRS | May 23, 14:20 UTC | May 23, 18:20 UTC | 4h 1m |
| 2026-05-23 | TAR463 | LYS → MIR | May 23, 08:25 UTC | May 23, 13:05 UTC | 4h 40m |
| 2026-05-22 | TAR441 | ORY → MIR | May 22, 17:55 UTC | May 23, 07:00 UTC | 13h 4m |
| 2026-05-22 | TAR895 | HAM → MIR | May 22, 10:05 UTC | May 22, 16:30 UTC | 6h 25m |
| 2026-05-21 | TAR894 | MIR → HAM | May 21, 19:40 UTC | May 22, 08:45 UTC | 13h 5m |
| 2026-05-21 | TAR680 | MIR → MRS | May 21, 14:30 UTC | May 21, 18:35 UTC | 4h 5m |
| 2026-05-21 | TAR463 | LYS → MIR | May 21, 08:55 UTC | May 21, 13:05 UTC | 4h 10m |
| 2026-05-20 | TAR462 | MIR → LYS | May 20, 16:45 UTC | May 21, 07:45 UTC | 15h 0m |
| 2026-05-20 | TAR589 | LYS → DJE | May 20, 09:40 UTC | May 20, 15:30 UTC | 5h 50m |
| 2026-05-19 | TAR655 | ORY → DJE | May 19, 18:30 UTC | May 20, 08:25 UTC | 13h 56m |
| 2026-05-19 | TAR654 | DJE → ORY | May 19, 10:30 UTC | May 19, 17:05 UTC | 6h 35m |
| 2026-05-18 | TAR634 | DJE → ORY | May 18, 17:10 UTC | May 19, 09:00 UTC | 15h 49m |
| 2026-05-18 | TAR850 | TUN → LYS | May 18, 14:30 UTC | May 18, 15:50 UTC | 1h 20m |
| 2026-05-18 | TAR215 | IST → TUN | May 18, 09:55 UTC | May 18, 12:05 UTC | 2h 10m |
| 2026-05-18 | TAR214 | TUN → IST | May 18, 06:20 UTC | May 18, 08:01 UTC | 1h 40m |
| 2026-05-17 | TAR655 | ORY → DJE | May 17, 18:20 UTC | May 17, 19:55 UTC | 1h 35m |
| 2026-05-17 | TAR654 | DJE → ORY | May 17, 10:40 UTC | May 17, 16:40 UTC | 6h 0m |
| 2026-05-17 | TAR634 | DJE → ORY | May 17, 09:25 UTC | May 17, 09:50 UTC | 25m |
| 2026-05-16 | TAR634 | DJE → ORY | May 16, 21:30 UTC | May 17, 09:20 UTC | 11h 50m |
| 2026-05-16 | TAR282 | TUN → TLS | May 16, 15:05 UTC | May 16, 20:15 UTC | 5h 10m |
| 2026-05-16 | TAR850 | TUN → LYS | May 16, 10:01 UTC | May 16, 13:55 UTC | 3h 55m |
| 2026-05-16 | TAR607 | MAD → TUN | May 16, 01:00 UTC | May 16, 07:45 UTC | 6h 46m |
| 2026-05-15 | TAR607 | MAD → TUN | May 15, 23:10 UTC | May 16, 00:05 UTC | 55m |
| 2026-05-15 | TAR606 | TUN → MAD | May 15, 16:15 UTC | May 15, 21:55 UTC | 5h 40m |
| 2026-05-15 | TAR700 | TUN → GVA | May 15, 09:40 UTC | May 15, 14:55 UTC | 5h 14m |
| 2026-05-14 | TAR362 | TUN → BLQ | May 14, 15:15 UTC | May 15, 08:20 UTC | 17h 5m |
| 2026-05-14 | TAR250 | MIR → NCE | May 14, 08:30 UTC | May 14, 14:01 UTC | 5h 30m |
| 2026-05-13 | TAR462 | MIR → LYS | May 13, 17:00 UTC | May 14, 07:15 UTC | 14h 15m |
| 2026-05-13 | TAR589 | LYS → DJE | May 13, 09:35 UTC | May 13, 15:35 UTC | 6h 0m |
| 2026-05-13 | TAR588 | DJE → LYS | May 13, 06:55 UTC | May 13, 08:10 UTC | 1h 15m |
| 2026-05-12 | TAR251 | NCE → MIR | May 12, 16:55 UTC | May 12, 17:50 UTC | 55m |
| 2026-05-12 | TAR757 | MXP → TUN | May 12, 10:00 UTC | May 12, 15:25 UTC | 5h 25m |
| 2026-05-11 | TAR756 | TUN → MXP | May 11, 19:50 UTC | May 12, 08:30 UTC | 12h 40m |
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 TS-IMW page for operator, model, and routing details .