sensors Mode-S transponder
02A192
ICAO 24-bit transponder address · allocated to Tunisia
Currently assigned to TS-IMS · AIRBUS A-320
- Hex
- 02A192
- Octal
- 00520622
- Decimal
- 172,434
- Country
- TN
- Tail
- TS-IMS
- Type
- A320
- Flights observed
- 101
- Distinct callsigns
- 20
- Country
- TN
- Last broadcast
- 20d ago
Last known position
Country allocation
The ICAO 24-bit address 02A192 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 |
|---|---|---|---|
| TAR250 | Tunisair | 8 | 2026-04-27 |
| TAR441 | Tunisair | 7 | 2026-04-28 |
| TAR680 | Tunisair | 6 | 2026-04-27 |
| TAR635 | Tunisair | 6 | 2026-05-08 |
| TAR589 | Tunisair | 6 | 2026-05-07 |
| TAR440 | Tunisair | 6 | 2026-04-27 |
| TAR655 | Tunisair | 5 | 2026-05-02 |
| TAR634 | Tunisair | 5 | 2026-05-07 |
| TAR588 | Tunisair | 5 | 2026-05-07 |
| TAR463 | Tunisair | 5 | 2026-04-25 |
| TAR654 | Tunisair | 4 | 2026-05-02 |
| TAR462 | Tunisair | 4 | 2026-04-22 |
| TAR251 | Tunisair | 4 | 2026-04-26 |
| TAR895 | Tunisair | 3 | 2026-04-24 |
| TAR894 | Tunisair | 3 | 2026-04-23 |
| TAR903 | - | 2 | 2026-04-13 |
| TAR757 | Tunisair | 2 | 2026-05-09 |
| TAR695 | Tunisair | 2 | 2026-05-05 |
| TAR694 | Tunisair | 2 | 2026-05-05 |
| TAR362 | Tunisair | 2 | 2026-04-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-09 | TAR9166 | - | May 9, 13:35 UTC | May 9, 16:35 UTC | 3h 0m |
| 2026-05-09 | TAR757 | MXP → TUN | May 9, 10:00 UTC | May 9, 11:10 UTC | 1h 10m |
| 2026-05-08 | TAR649 | FRA → DJE | May 8, 20:40 UTC | May 9, 08:30 UTC | 11h 50m |
| 2026-05-08 | TAR635 | ORY → DJE | May 8, 12:04 UTC | May 8, 19:15 UTC | 7h 10m |
| 2026-05-07 | TAR634 | DJE → ORY | May 7, 21:35 UTC | May 8, 10:44 UTC | 13h 9m |
| 2026-05-07 | TAR683 | NCE → DJE | May 7, 14:55 UTC | May 7, 20:05 UTC | 5h 10m |
| 2026-05-07 | TAR589 | LYS → DJE | May 7, 08:45 UTC | May 7, 13:35 UTC | 4h 50m |
| 2026-05-07 | TAR588 | DJE → LYS | May 7, 06:15 UTC | May 7, 07:35 UTC | 1h 20m |
| 2026-05-06 | TAR875 | TUN → DJE | May 6, 18:35 UTC | May 6, 19:50 UTC | 1h 15m |
| 2026-05-06 | TAR874 | DJE → GVA | May 6, 15:35 UTC | May 6, 16:55 UTC | 1h 20m |
| 2026-05-06 | TAR635 | ORY → DJE | May 6, 09:45 UTC | May 6, 11:30 UTC | 1h 45m |
| 2026-05-06 | TAR634 | DJE → ORY | May 6, 06:55 UTC | May 6, 08:40 UTC | 1h 45m |
| 2026-05-05 | TAR589 | LYS → DJE | May 5, 19:15 UTC | May 5, 20:55 UTC | 1h 40m |
| 2026-05-05 | TAR588 | DJE → LYS | May 5, 16:35 UTC | May 5, 18:00 UTC | 1h 25m |
| 2026-05-05 | TAR695 | MRS → DJE | May 5, 09:00 UTC | May 5, 09:55 UTC | 55m |
| 2026-05-05 | TAR694 | DJE → MRS | May 5, 07:00 UTC | May 5, 08:05 UTC | 1h 5m |
| 2026-05-04 | TAR635 | ORY → DJE | May 4, 10:35 UTC | May 5, 08:05 UTC | 21h 31m |
| 2026-05-04 | TAR635 | ORY → DJE | May 4, 10:20 UTC | May 5, 08:05 UTC | 21h 46m |
| 2026-05-03 | TAR634 | DJE → ORY | May 3, 19:30 UTC | May 4, 08:50 UTC | 13h 20m |
| 2026-05-03 | TAR635 | ORY → DJE | May 3, 11:40 UTC | May 3, 18:14 UTC | 6h 35m |
| 2026-05-02 | TAR655 | ORY → DJE | May 2, 18:00 UTC | May 3, 10:30 UTC | 16h 29m |
| 2026-05-02 | TAR654 | DJE → ORY | May 2, 10:00 UTC | May 2, 16:45 UTC | 6h 45m |
| 2026-05-01 | TAR655 | ORY → DJE | May 1, 20:10 UTC | May 2, 08:40 UTC | 12h 30m |
| 2026-05-01 | TAR654 | DJE → ORY | May 1, 11:30 UTC | May 1, 18:25 UTC | 6h 55m |
| 2026-05-01 | TAR498 | DJE → MUC | May 1, 08:15 UTC | May 1, 09:55 UTC | 1h 40m |
| 2026-04-30 | TAR695 | MRS → DJE | Apr 30, 20:55 UTC | Apr 30, 21:50 UTC | 55m |
| 2026-04-30 | TAR694 | DJE → MRS | Apr 30, 15:05 UTC | Apr 30, 19:45 UTC | 4h 40m |
| 2026-04-30 | TAR589 | LYS → DJE | Apr 30, 08:50 UTC | Apr 30, 13:45 UTC | 4h 55m |
| 2026-04-29 | TAR527 | DUS → TUN | Apr 29, 16:20 UTC | Apr 30, 07:35 UTC | 15h 14m |
| 2026-04-29 | TAR526 | TUN → DUS | Apr 29, 13:15 UTC | Apr 29, 15:15 UTC | 2h 0m |
| 2026-04-29 | TAR757 | MXP → TUN | Apr 29, 10:15 UTC | Apr 29, 11:25 UTC | 1h 10m |
| 2026-04-29 | TAR756 | TUN → MXP | Apr 29, 07:29 UTC | Apr 29, 08:50 UTC | 1h 20m |
| 2026-04-28 | TAR283 | TLS → TUN | Apr 28, 17:35 UTC | Apr 28, 18:55 UTC | 1h 20m |
| 2026-04-28 | TAR441 | ORY → MIR | Apr 28, 09:50 UTC | Apr 28, 16:15 UTC | 6h 25m |
| 2026-04-27 | TAR440 | MIR → CDG | Apr 27, 19:40 UTC | Apr 28, 08:35 UTC | 12h 55m |
| 2026-04-27 | TAR680 | MIR → MRS | Apr 27, 14:15 UTC | Apr 27, 18:35 UTC | 4h 20m |
| 2026-04-27 | TAR250 | MIR → NCE | Apr 27, 11:50 UTC | Apr 27, 12:55 UTC | 1h 5m |
| 2026-04-26 | TAR441 | ORY → MIR | Apr 26, 17:45 UTC | Apr 26, 19:55 UTC | 2h 10m |
| 2026-04-26 | TAR440 | MIR → CDG | Apr 26, 14:05 UTC | Apr 26, 16:20 UTC | 2h 15m |
| 2026-04-26 | TAR251 | NCE → MIR | Apr 26, 10:25 UTC | Apr 26, 11:35 UTC | 1h 10m |
| 2026-04-25 | TAR250 | MIR → NCE | Apr 25, 19:50 UTC | Apr 26, 09:15 UTC | 13h 25m |
| 2026-04-25 | TAR680 | MIR → MRS | Apr 25, 14:10 UTC | Apr 25, 18:35 UTC | 4h 25m |
| 2026-04-25 | TAR463 | LYS → MIR | Apr 25, 08:35 UTC | Apr 25, 12:55 UTC | 4h 20m |
| 2026-04-24 | TAR441 | ORY → MIR | Apr 24, 17:35 UTC | Apr 25, 07:25 UTC | 13h 50m |
| 2026-04-24 | TAR895 | HAM → MIR | Apr 24, 10:00 UTC | Apr 24, 16:10 UTC | 6h 10m |
| 2026-04-23 | TAR894 | MIR → HAM | Apr 23, 19:45 UTC | Apr 24, 08:50 UTC | 13h 5m |
| 2026-04-23 | TAR680 | MIR → MRS | Apr 23, 14:35 UTC | Apr 23, 18:40 UTC | 4h 4m |
| 2026-04-23 | TAR463 | LYS → MIR | Apr 23, 08:45 UTC | Apr 23, 13:25 UTC | 4h 40m |
| 2026-04-22 | TAR462 | MIR → LYS | Apr 22, 16:30 UTC | Apr 23, 07:20 UTC | 14h 50m |
| 2026-04-22 | TAR589 | LYS → DJE | Apr 22, 09:25 UTC | Apr 22, 15:20 UTC | 5h 55m |
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-IMS page for operator, model, and routing details .