sensors Mode-S transponder
33FC7F
ICAO 24-bit transponder address · allocated to Italy
Currently assigned to MM82212 · AGUSTA AW-169
- Hex
- 33FC7F
- Octal
- 14776177
- Decimal
- 3,406,975
- Country
- IT
- Tail
- MM82212
- Type
- A169
- Flights observed
- 85
- Distinct callsigns
- 1
- Country
- IT
- Last broadcast
- 10h ago
Last known position
Country allocation
The ICAO 24-bit address 33FC7F falls within the block assigned to Italy (IT) by ICAO Annex 10, Volume III. Every aircraft registered in Italy 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| FIAMM33 | - | 85 | 2026-07-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-19 | FIAMM33 | - | Jul 19, 09:00 UTC | Jul 19, 09:30 UTC | 30m |
| 2026-07-19 | FIAMM33 | - | Jul 19, 08:05 UTC | Jul 19, 08:55 UTC | 50m |
| 2026-07-17 | FIAMM33 | - | Jul 17, 13:45 UTC | Jul 17, 14:20 UTC | 35m |
| 2026-07-17 | FIAMM33 | - | Jul 17, 08:20 UTC | Jul 17, 09:25 UTC | 1h 5m |
| 2026-07-16 | FIAMM33 | - | Jul 16, 07:35 UTC | Jul 16, 08:05 UTC | 30m |
| 2026-07-15 | FIAMM33 | - | Jul 15, 08:10 UTC | Jul 15, 09:40 UTC | 1h 30m |
| 2026-07-13 | FIAMM33 | - | Jul 13, 13:20 UTC | Jul 13, 13:55 UTC | 35m |
| 2026-07-13 | FIAMM33 | - | Jul 13, 08:15 UTC | Jul 13, 09:00 UTC | 45m |
| 2026-07-12 | FIAMM33 | - | Jul 12, 09:05 UTC | Jul 12, 09:40 UTC | 35m |
| 2026-07-12 | FIAMM33 | - | Jul 12, 08:15 UTC | Jul 12, 08:25 UTC | 10m |
| 2026-07-11 | FIAMM33 | - | Jul 11, 07:45 UTC | Jul 11, 09:15 UTC | 1h 30m |
| 2026-07-07 | FIAMM33 | - | Jul 7, 18:05 UTC | Jul 7, 19:00 UTC | 55m |
| 2026-07-07 | FIAMM33 | BGY → BGY | Jul 7, 07:15 UTC | Jul 7, 08:00 UTC | 45m |
| 2026-06-28 | FIAMM33 | - | Jun 28, 07:20 UTC | Jun 28, 08:39 UTC | 1h 20m |
| 2026-06-27 | FIAMM33 | - | Jun 27, 07:24 UTC | Jun 27, 07:34 UTC | 10m |
| 2026-06-26 | FIAMM33 | - | Jun 26, 18:04 UTC | Jun 26, 19:35 UTC | 1h 30m |
| 2026-06-26 | FIAMM33 | - | Jun 26, 10:20 UTC | Jun 26, 10:30 UTC | 10m |
| 2026-06-26 | FIAMM33 | - | Jun 26, 09:05 UTC | Jun 26, 09:24 UTC | 20m |
| 2026-06-24 | FIAMM33 | BGY → BGY | Jun 24, 19:55 UTC | Jun 24, 20:49 UTC | 55m |
| 2026-06-23 | FIAMM33 | - | Jun 23, 19:50 UTC | Jun 23, 21:39 UTC | 1h 50m |
| 2026-06-22 | FIAMM33 | - | Jun 22, 06:39 UTC | Jun 22, 07:00 UTC | 20m |
| 2026-06-21 | FIAMM33 | BGY → BGY | Jun 21, 18:00 UTC | Jun 21, 19:09 UTC | 1h 10m |
| 2026-06-21 | FIAMM33 | - | Jun 21, 08:40 UTC | Jun 21, 09:00 UTC | 20m |
| 2026-06-20 | FIAMM33 | - | Jun 20, 07:19 UTC | Jun 20, 08:14 UTC | 55m |
| 2026-06-17 | FIAMM33 | - | Jun 17, 14:45 UTC | Jun 17, 15:50 UTC | 1h 5m |
| 2026-06-17 | FIAMM33 | - | Jun 17, 11:10 UTC | Jun 17, 12:30 UTC | 1h 20m |
| 2026-06-16 | FIAMM33 | - | Jun 16, 20:00 UTC | Jun 16, 20:50 UTC | 50m |
| 2026-06-16 | FIAMM33 | - | Jun 16, 11:10 UTC | Jun 16, 13:04 UTC | 1h 55m |
| 2026-06-15 | FIAMM33 | - | Jun 15, 19:55 UTC | Jun 15, 21:50 UTC | 1h 55m |
| 2026-06-14 | FIAMM33 | - | Jun 14, 08:45 UTC | Jun 14, 09:15 UTC | 30m |
| 2026-06-13 | FIAMM33 | - | Jun 13, 08:25 UTC | Jun 13, 09:20 UTC | 55m |
| 2026-06-08 | FIAMM33 | - | Jun 8, 07:15 UTC | Jun 8, 08:30 UTC | 1h 15m |
| 2026-06-05 | FIAMM33 | - | Jun 5, 08:45 UTC | Jun 5, 08:55 UTC | 10m |
| 2026-06-04 | FIAMM33 | - | Jun 4, 17:55 UTC | Jun 4, 18:05 UTC | 10m |
| 2026-06-04 | FIAMM33 | - | Jun 4, 15:55 UTC | Jun 4, 16:10 UTC | 15m |
| 2026-06-04 | FIAMM33 | - | Jun 4, 13:30 UTC | Jun 4, 13:45 UTC | 15m |
| 2026-05-31 | FIAMM33 | BGY → BGY | May 31, 08:55 UTC | May 31, 09:20 UTC | 25m |
| 2026-05-29 | FIAMM33 | - | May 29, 07:35 UTC | May 29, 08:50 UTC | 1h 15m |
| 2026-05-28 | FIAMM33 | - | May 28, 07:30 UTC | May 28, 09:00 UTC | 1h 30m |
| 2026-05-27 | FIAMM33 | - | May 27, 13:00 UTC | May 27, 13:40 UTC | 40m |
| 2026-05-27 | FIAMM33 | - | May 27, 12:15 UTC | May 27, 12:25 UTC | 10m |
| 2026-05-26 | FIAMM33 | - | May 26, 12:40 UTC | May 26, 13:19 UTC | 40m |
| 2026-05-26 | FIAMM33 | - | May 26, 07:49 UTC | May 26, 08:34 UTC | 45m |
| 2026-05-25 | FIAMM33 | - | May 25, 12:45 UTC | May 25, 13:25 UTC | 40m |
| 2026-05-25 | FIAMM33 | - | May 25, 08:00 UTC | May 25, 08:40 UTC | 40m |
| 2026-05-24 | FIAMM33 | - | May 24, 07:40 UTC | May 24, 07:50 UTC | 10m |
| 2026-05-23 | FIAMM33 | - | May 23, 08:30 UTC | May 23, 09:10 UTC | 40m |
| 2026-05-23 | FIAMM33 | - | May 23, 07:10 UTC | May 23, 07:45 UTC | 35m |
| 2026-05-22 | FIAMM33 | - | May 22, 12:10 UTC | May 22, 12:50 UTC | 40m |
| 2026-05-22 | FIAMM33 | - | May 22, 07:35 UTC | May 22, 08:15 UTC | 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 MM82212 page for operator, model, and routing details .