sensors Mode-S transponder
02A181
ICAO 24-bit transponder address · allocated to Tunisia
Currently assigned to TS-IMB · AIRBUS A-320neo
- Hex
- 02A181
- Octal
- 00520601
- Decimal
- 172,417
- Country
- TN
- Tail
- TS-IMB
- Type
- A20N
- Flights observed
- 182
- Distinct callsigns
- 20
- Country
- TN
- Last broadcast
- 10h ago
Last known position
Country allocation
The ICAO 24-bit address 02A181 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 |
|---|---|---|---|
| TAR955 | Tunisair | 13 | 2026-05-27 |
| TAR954 | Tunisair | 13 | 2026-05-26 |
| TAR756 | - | 9 | 2026-07-14 |
| TAR745 | Tunisair | 9 | 2026-06-04 |
| TAR744 | Tunisair | 9 | 2026-06-04 |
| TAR724 | Tunisair | 7 | 2026-06-01 |
| TAR902 | Tunisair | 5 | 2026-06-03 |
| TAR793 | - | 5 | 2026-07-13 |
| TAR792 | - | 5 | 2026-07-13 |
| TAR757 | - | 5 | 2026-07-14 |
| TAR725 | Tunisair | 5 | 2026-06-01 |
| TAR705 | Tunisair | 5 | 2026-06-02 |
| TAR702 | Tunisair | 5 | 2026-05-31 |
| TAR790 | Tunisair | 4 | 2026-06-02 |
| TAR750 | Tunisair | 4 | 2026-05-17 |
| TAR703 | Tunisair | 4 | 2026-06-01 |
| TAR362 | Tunisair | 4 | 2026-05-08 |
| TAR814 | Tunisair | 3 | 2026-05-15 |
| TAR791 | Tunisair | 3 | 2026-06-02 |
| TAR753 | Tunisair | 3 | 2026-06-01 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | TAR757 | MXP → TUN | Jul 14, 10:45 UTC | Jul 14, 12:05 UTC | 1h 20m |
| 2026-07-14 | TAR756 | - | Jul 14, 07:15 UTC | Jul 14, 08:50 UTC | 1h 35m |
| 2026-07-13 | TAR401 | - | Jul 13, 15:55 UTC | Jul 14, 03:35 UTC | 11h 40m |
| 2026-07-13 | TAR793 | - | Jul 13, 10:35 UTC | Jul 13, 13:00 UTC | 2h 25m |
| 2026-07-13 | TAR792 | - | Jul 13, 06:30 UTC | Jul 13, 08:55 UTC | 2h 25m |
| 2026-07-12 | TAR701 | - | Jul 12, 16:20 UTC | Jul 12, 17:40 UTC | 1h 20m |
| 2026-07-12 | TAR700 | TUN → GVA | Jul 12, 13:05 UTC | Jul 12, 14:45 UTC | 1h 40m |
| 2026-07-12 | TAR757 | - | Jul 12, 10:05 UTC | Jul 12, 11:20 UTC | 1h 15m |
| 2026-07-12 | TAR756 | - | Jul 12, 07:15 UTC | Jul 12, 08:35 UTC | 1h 20m |
| 2026-07-08 | TAR9970 | - | Jul 8, 14:15 UTC | Jul 8, 14:55 UTC | 40m |
| 2026-06-04 | TAR745 | FRA → TUN | Jun 4, 12:35 UTC | Jun 4, 14:25 UTC | 1h 50m |
| 2026-06-04 | TAR744 | TUN → FRA | Jun 4, 09:30 UTC | Jun 4, 11:10 UTC | 1h 40m |
| 2026-06-03 | TAR903 | MRS → TUN | Jun 3, 16:20 UTC | Jun 3, 17:15 UTC | 55m |
| 2026-06-03 | TAR902 | TUN → MRS | Jun 3, 13:55 UTC | Jun 3, 15:00 UTC | 1h 5m |
| 2026-06-03 | TAR757 | MXP → TUN | Jun 3, 10:50 UTC | Jun 3, 11:55 UTC | 1h 5m |
| 2026-06-03 | TAR706 | CMN → TUN | Jun 3, 01:45 UTC | Jun 3, 09:05 UTC | 7h 20m |
| 2026-06-02 | TAR705 | TUN → CMN | Jun 2, 23:20 UTC | Jun 3, 00:45 UTC | 1h 25m |
| 2026-06-02 | TAR791 | LHR → TUN | Jun 2, 18:35 UTC | Jun 2, 20:45 UTC | 2h 10m |
| 2026-06-02 | TAR790 | TUN → LHR | Jun 2, 14:35 UTC | Jun 2, 17:05 UTC | 2h 30m |
| 2026-06-02 | TAR757 | MXP → TUN | Jun 2, 10:40 UTC | Jun 2, 12:00 UTC | 1h 20m |
| 2026-06-01 | TAR725 | ORY → TUN | Jun 1, 20:35 UTC | Jun 2, 08:30 UTC | 11h 55m |
| 2026-06-01 | TAR724 | TUN → ORY | Jun 1, 17:10 UTC | Jun 1, 19:00 UTC | 1h 50m |
| 2026-06-01 | TAR753 | FCO → TUN | Jun 1, 14:35 UTC | Jun 1, 15:15 UTC | 40m |
| 2026-06-01 | TAR752 | TUN → FCO | Jun 1, 12:10 UTC | Jun 1, 13:00 UTC | 50m |
| 2026-06-01 | TAR703 | GVA → TUN | Jun 1, 08:55 UTC | Jun 1, 10:10 UTC | 1h 15m |
| 2026-05-31 | TAR702 | TUN → GVA | May 31, 22:10 UTC | Jun 1, 07:50 UTC | 9h 40m |
| 2026-05-31 | TAR514 | TUN → BCN | May 31, 19:30 UTC | May 31, 20:40 UTC | 1h 10m |
| 2026-05-31 | TAR745 | FRA → TUN | May 31, 15:40 UTC | May 31, 17:30 UTC | 1h 50m |
| 2026-05-31 | TAR744 | TUN → FRA | May 31, 12:10 UTC | May 31, 14:15 UTC | 2h 5m |
| 2026-05-30 | TAR343 | TUN → CKY | May 30, 23:20 UTC | May 31, 00:10 UTC | 50m |
| 2026-05-30 | TAR473 | VCE → TUN | May 30, 14:10 UTC | May 30, 22:10 UTC | 8h 0m |
| 2026-05-30 | TAR472 | TUN → VCE | May 30, 11:35 UTC | May 30, 12:50 UTC | 1h 15m |
| 2026-05-30 | TAR997 | NCE → TUN | May 30, 08:55 UTC | May 30, 09:35 UTC | 40m |
| 2026-05-29 | TAR725 | ORY → TUN | May 29, 20:15 UTC | May 30, 07:00 UTC | 10h 45m |
| 2026-05-29 | TAR724 | TUN → ORY | May 29, 14:25 UTC | May 29, 18:55 UTC | 4h 31m |
| 2026-05-29 | TAR997 | NCE → TUN | May 29, 08:55 UTC | May 29, 13:10 UTC | 4h 15m |
| 2026-05-28 | TAR996 | TUN → NCE | May 28, 12:20 UTC | May 29, 07:30 UTC | 19h 10m |
| 2026-05-28 | TAR793 | LGW → TUN | May 28, 10:25 UTC | May 29, 07:30 UTC | 21h 5m |
| 2026-05-27 | TAR792 | TUN → LGW | May 27, 17:45 UTC | May 28, 09:05 UTC | 15h 20m |
| 2026-05-27 | TAR955 | BRU → TUN | May 27, 10:40 UTC | May 27, 16:05 UTC | 5h 25m |
| 2026-05-26 | TAR954 | TUN → BRU | May 26, 18:24 UTC | May 27, 09:15 UTC | 14h 50m |
| 2026-05-26 | TAR473 | VCE → TUN | May 26, 13:34 UTC | May 26, 17:09 UTC | 3h 35m |
| 2026-05-26 | TAR472 | TUN → VCE | May 26, 11:05 UTC | May 26, 12:14 UTC | 1h 10m |
| 2026-05-25 | TAR745 | FRA → TUN | May 25, 14:20 UTC | May 26, 12:14 UTC | 21h 55m |
| 2026-05-25 | TAR745 | FRA → TUN | May 25, 13:55 UTC | May 26, 12:14 UTC | 22h 19m |
| 2026-05-25 | TAR744 | TUN → FRA | May 25, 10:50 UTC | May 25, 12:35 UTC | 1h 45m |
| 2026-05-24 | TAR744 | TUN → FRA | May 24, 14:30 UTC | May 25, 12:35 UTC | 22h 5m |
| 2026-05-24 | TAR703 | GVA → TUN | May 24, 08:15 UTC | May 24, 12:05 UTC | 3h 50m |
| 2026-05-23 | TAR723 | ORY → TUN | May 23, 20:10 UTC | May 24, 06:35 UTC | 10h 25m |
| 2026-05-23 | TAR722 | TUN → ORY | May 23, 13:40 UTC | May 23, 18:50 UTC | 5h 10m |
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-IMB page for operator, model, and routing details .