sensors Mode-S transponder
3954A0
ICAO 24-bit transponder address · allocated to France
Currently assigned to F-GVFA · CESSNA 172 Skyhawk
- Hex
- 3954A0
- Octal
- 16252240
- Decimal
- 3,757,216
- Country
- FR
- Tail
- F-GVFA
- Type
- C172
- Flights observed
- 68
- Distinct callsigns
- 1
- Country
- FR
- Last broadcast
- Jul 26, 01:30 UTC
Last known position
Country allocation
The ICAO 24-bit address 3954A0 falls within the block assigned to France (FR) by ICAO Annex 10, Volume III. Every aircraft registered in France 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 |
|---|---|---|---|
| FGVFA | - | 68 | 2026-07-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | FGVFA | - | Jul 26, 01:00 UTC | Jul 26, 01:30 UTC | 30m |
| 2026-07-25 | FGVFA | - | Jul 25, 20:00 UTC | Jul 25, 20:40 UTC | 40m |
| 2026-07-24 | FGVFA | - | Jul 24, 21:15 UTC | Jul 24, 21:50 UTC | 35m |
| 2026-07-23 | FGVFA | - | Jul 23, 22:35 UTC | Jul 23, 22:45 UTC | 10m |
| 2026-07-21 | FGVFA | - | Jul 21, 20:45 UTC | Jul 21, 22:00 UTC | 1h 15m |
| 2026-07-20 | FGVFA | - | Jul 20, 18:55 UTC | Jul 20, 20:00 UTC | 1h 5m |
| 2026-07-19 | FGVFA | - | Jul 19, 20:10 UTC | Jul 19, 20:45 UTC | 35m |
| 2026-07-19 | FGVFA | - | Jul 19, 19:25 UTC | Jul 19, 19:35 UTC | 10m |
| 2026-07-17 | FGVFA | - | Jul 17, 22:40 UTC | Jul 17, 23:55 UTC | 1h 15m |
| 2026-07-17 | FGVFA | - | Jul 17, 19:20 UTC | Jul 17, 19:40 UTC | 20m |
| 2026-07-15 | FGVFA | - | Jul 15, 00:15 UTC | Jul 15, 00:25 UTC | 10m |
| 2026-07-14 | FGVFA | MOZ → MOZ | Jul 14, 21:25 UTC | Jul 14, 23:00 UTC | 1h 34m |
| 2026-07-13 | FGVFA | - | Jul 13, 23:20 UTC | Jul 13, 23:50 UTC | 30m |
| 2026-07-13 | FGVFA | - | Jul 13, 20:00 UTC | Jul 13, 20:15 UTC | 15m |
| 2026-07-13 | FGVFA | - | Jul 13, 18:55 UTC | Jul 13, 19:15 UTC | 20m |
| 2026-07-13 | FGVFA | - | Jul 13, 18:15 UTC | Jul 13, 18:25 UTC | 10m |
| 2026-07-13 | FGVFA | - | Jul 13, 01:05 UTC | Jul 13, 02:40 UTC | 1h 35m |
| 2026-07-12 | FGVFA | - | Jul 12, 21:05 UTC | Jul 12, 21:40 UTC | 35m |
| 2026-07-11 | FGVFA | - | Jul 11, 19:55 UTC | Jul 11, 20:30 UTC | 35m |
| 2026-07-08 | FGVFA | - | Jul 8, 17:15 UTC | Jul 8, 18:40 UTC | 1h 25m |
| 2026-07-08 | FGVFA | - | Jul 8, 01:05 UTC | Jul 8, 01:30 UTC | 25m |
| 2026-07-07 | FGVFA | - | Jul 7, 18:25 UTC | Jul 7, 18:45 UTC | 20m |
| 2026-07-04 | FGVFA | - | Jul 4, 01:15 UTC | Jul 4, 01:25 UTC | 10m |
| 2026-07-03 | FGVFA | PPT → PPT | Jul 3, 20:50 UTC | Jul 3, 21:00 UTC | 10m |
| 2026-07-02 | FGVFA | - | Jul 2, 19:20 UTC | Jul 2, 20:45 UTC | 1h 25m |
| 2026-06-20 | FGVFA | - | Jun 20, 20:09 UTC | Jun 20, 20:20 UTC | 10m |
| 2026-06-14 | FGVFA | - | Jun 14, 22:30 UTC | Jun 14, 23:00 UTC | 30m |
| 2026-06-09 | FGVFA | - | Jun 9, 21:15 UTC | Jun 9, 22:05 UTC | 50m |
| 2026-06-06 | FGVFA | - | Jun 6, 23:15 UTC | Jun 6, 23:44 UTC | 30m |
| 2026-06-06 | FGVFA | - | Jun 6, 19:19 UTC | Jun 6, 19:54 UTC | 35m |
| 2026-06-03 | FGVFA | - | Jun 3, 21:05 UTC | Jun 3, 21:45 UTC | 40m |
| 2026-06-03 | FGVFA | - | Jun 3, 18:50 UTC | Jun 3, 20:00 UTC | 1h 10m |
| 2026-06-03 | FGVFA | - | Jun 3, 03:10 UTC | Jun 3, 03:30 UTC | 20m |
| 2026-06-01 | FGVFA | PPT → PPT | Jun 1, 20:25 UTC | Jun 1, 21:00 UTC | 35m |
| 2026-05-31 | FGVFA | - | May 31, 21:40 UTC | May 31, 22:15 UTC | 35m |
| 2026-05-31 | FGVFA | - | May 31, 21:15 UTC | May 31, 21:25 UTC | 10m |
| 2026-05-30 | FGVFA | - | May 30, 19:15 UTC | May 30, 20:15 UTC | 1h 0m |
| 2026-05-28 | FGVFA | - | May 28, 19:25 UTC | May 28, 20:05 UTC | 40m |
| 2026-05-27 | FGVFA | - | May 27, 19:00 UTC | May 27, 20:05 UTC | 1h 5m |
| 2026-05-25 | FGVFA | - | May 25, 20:34 UTC | May 25, 21:04 UTC | 30m |
| 2026-05-23 | FGVFA | - | May 23, 19:05 UTC | May 23, 20:05 UTC | 1h 0m |
| 2026-05-22 | FGVFA | - | May 22, 20:50 UTC | May 22, 21:45 UTC | 55m |
| 2026-05-22 | FGVFA | - | May 22, 18:45 UTC | May 22, 19:30 UTC | 45m |
| 2026-05-21 | FGVFA | - | May 21, 21:00 UTC | May 21, 21:10 UTC | 10m |
| 2026-05-21 | FGVFA | MOZ → MOZ | May 21, 20:00 UTC | May 21, 20:30 UTC | 30m |
| 2026-05-20 | FGVFA | - | May 20, 19:10 UTC | May 20, 19:35 UTC | 25m |
| 2026-05-17 | FGVFA | - | May 17, 01:25 UTC | May 17, 02:25 UTC | 1h 0m |
| 2026-05-16 | FGVFA | - | May 16, 23:15 UTC | May 17, 00:20 UTC | 1h 5m |
| 2026-05-16 | FGVFA | - | May 16, 18:45 UTC | May 16, 19:15 UTC | 30m |
| 2026-05-15 | FGVFA | - | May 15, 19:55 UTC | May 15, 20:10 UTC | 15m |
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 F-GVFA page for operator, model, and routing details .