sensors Mode-S transponder
394A15
ICAO 24-bit transponder address · allocated to France
Currently assigned to F-GSQV · BOEING 777-300ER
- Hex
- 394A15
- Octal
- 16245025
- Decimal
- 3,754,517
- Country
- FR
- Tail
- F-GSQV
- Type
- B77W
- Flights observed
- 49
- Distinct callsigns
- 20
- Country
- FR
- Last broadcast
- 21d ago
Last known position
Country allocation
The ICAO 24-bit address 394A15 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| AFR454 | Air France | 11 | 2026-04-27 |
| AFR453 | Air France | 4 | 2026-04-27 |
| AFR33J | Air France | 4 | 2026-04-16 |
| AFR32J | Air France | 4 | 2026-04-15 |
| AFR719 | Air France | 3 | 2026-04-17 |
| AFR718 | Air France | 3 | 2026-04-16 |
| AFR2N | Air France | 3 | 2026-05-04 |
| AFR1U | Air France | 3 | 2026-05-04 |
| AFR706 | Air France | 2 | 2026-05-02 |
| AFR217 | Air France | 2 | 2026-05-07 |
| AFR8U | Air France | 1 | 2026-05-05 |
| AFR84E | Air France | 1 | 2026-04-19 |
| AFR83K | Air France | 1 | 2026-04-19 |
| AFR703 | Air France | 1 | 2026-04-28 |
| AFR702 | Air France | 1 | 2026-04-22 |
| AFR51N | Air France | 1 | 2026-04-21 |
| AFR50N | Air France | 1 | 2026-04-21 |
| AFR031 | Air France | 1 | 2026-05-01 |
| AFR030 | Air France | 1 | 2026-05-01 |
| AFR007 | - | 1 | 2026-05-06 |
Recent flights last 49
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-07 | AFR217 | BOM → CDG | May 7, 11:20 UTC | May 8, 06:50 UTC | 19h 30m |
| 2026-05-07 | AFR217 | BOM → CDG | May 7, 09:35 UTC | May 8, 06:50 UTC | 21h 15m |
| 2026-05-06 | AFR007 | - | May 6, 02:10 UTC | May 6, 08:55 UTC | 6h 45m |
| 2026-05-05 | AFR8U | CDG → JFK | May 5, 14:50 UTC | May 5, 22:15 UTC | 7h 25m |
| 2026-05-04 | AFR1U | JFK → CDG | May 4, 20:50 UTC | May 5, 03:25 UTC | 6h 35m |
| 2026-05-04 | AFR2N | CDG → JFK | May 4, 06:45 UTC | May 4, 14:00 UTC | 7h 15m |
| 2026-05-02 | AFR706 | ABJ → DSS | May 2, 16:35 UTC | May 3, 08:10 UTC | 15h 34m |
| 2026-05-01 | AFR031 | ATL → CDG | May 1, 20:40 UTC | May 2, 04:30 UTC | 7h 51m |
| 2026-05-01 | AFR030 | CDG → ATL | May 1, 08:50 UTC | May 1, 17:40 UTC | 8h 50m |
| 2026-04-30 | AFR1U | JFK → CDG | Apr 30, 20:50 UTC | May 1, 03:45 UTC | 6h 55m |
| 2026-04-30 | AFR2N | CDG → JFK | Apr 30, 07:00 UTC | Apr 30, 13:55 UTC | 6h 55m |
| 2026-04-29 | AFR1U | JFK → CDG | Apr 29, 21:05 UTC | Apr 30, 04:00 UTC | 6h 54m |
| 2026-04-29 | AFR2N | CDG → JFK | Apr 29, 06:49 UTC | Apr 29, 14:10 UTC | 7h 21m |
| 2026-04-28 | AFR703 | ABJ → CDG | Apr 28, 12:25 UTC | Apr 29, 03:55 UTC | 15h 30m |
| 2026-04-27 | AFR453 | GRU → CDG | Apr 27, 18:35 UTC | Apr 28, 05:10 UTC | 10h 35m |
| 2026-04-27 | AFR454 | CDG → GRU | Apr 27, 07:10 UTC | Apr 27, 08:45 UTC | 1h 35m |
| 2026-04-26 | AFR454 | CDG → GRU | Apr 26, 21:55 UTC | Apr 27, 07:00 UTC | 9h 5m |
| 2026-04-25 | AFR453 | GRU → CDG | Apr 25, 18:15 UTC | Apr 26, 05:05 UTC | 10h 50m |
| 2026-04-24 | AFR454 | CDG → GRU | Apr 24, 21:50 UTC | Apr 25, 08:55 UTC | 11h 5m |
| 2026-04-22 | AFR702 | CDG → ABJ | Apr 22, 12:40 UTC | Apr 23, 03:30 UTC | 14h 50m |
| 2026-04-21 | AFR51N | IAD → CDG | Apr 21, 22:30 UTC | Apr 22, 05:55 UTC | 7h 25m |
| 2026-04-21 | AFR50N | CDG → IAD | Apr 21, 12:05 UTC | Apr 21, 19:55 UTC | 7h 50m |
| 2026-04-20 | AFR706 | ABJ → DSS | Apr 20, 17:20 UTC | Apr 21, 08:15 UTC | 14h 55m |
| 2026-04-19 | AFR83K | SFO → CDG | Apr 19, 23:25 UTC | Apr 20, 09:25 UTC | 10h 0m |
| 2026-04-19 | AFR84E | CDG → SFO | Apr 19, 09:20 UTC | Apr 19, 20:25 UTC | 11h 5m |
| 2026-04-18 | AFR453 | GRU → CDG | Apr 18, 18:05 UTC | Apr 19, 04:40 UTC | 10h 35m |
| 2026-04-18 | AFR454 | CDG → GRU | Apr 18, 07:25 UTC | Apr 18, 09:20 UTC | 1h 55m |
| 2026-04-18 | AFR454 | CDG → GRU | Apr 18, 05:35 UTC | Apr 18, 07:20 UTC | 1h 45m |
| 2026-04-17 | AFR454 | CDG → GRU | Apr 17, 23:25 UTC | Apr 18, 00:00 UTC | 35m |
| 2026-04-17 | AFR454 | CDG → GRU | Apr 17, 21:45 UTC | Apr 18, 09:40 UTC | 11h 55m |
| 2026-04-17 | AFR719 | DSS → CDG | Apr 17, 03:20 UTC | Apr 17, 04:30 UTC | 1h 10m |
| 2026-04-17 | AFR719 | DSS → CDG | Apr 17, 02:00 UTC | Apr 17, 03:15 UTC | 1h 15m |
| 2026-04-16 | AFR719 | DSS → CDG | Apr 16, 23:35 UTC | Apr 16, 23:55 UTC | 20m |
| 2026-04-16 | AFR718 | CDG → DSS | Apr 16, 19:50 UTC | Apr 16, 20:30 UTC | 40m |
| 2026-04-16 | AFR718 | CDG → DSS | Apr 16, 17:15 UTC | Apr 16, 17:40 UTC | 25m |
| 2026-04-16 | AFR718 | CDG → DSS | Apr 16, 15:15 UTC | Apr 16, 17:10 UTC | 1h 55m |
| 2026-04-16 | AFR33J | ATL → CDG | Apr 16, 07:09 UTC | Apr 16, 08:04 UTC | 55m |
| 2026-04-16 | AFR33J | ATL → CDG | Apr 16, 06:34 UTC | Apr 16, 07:05 UTC | 30m |
| 2026-04-16 | AFR33J | ATL → CDG | Apr 16, 01:10 UTC | Apr 16, 03:04 UTC | 1h 55m |
| 2026-04-16 | AFR33J | ATL → CDG | Apr 16, 00:15 UTC | Apr 16, 01:05 UTC | 50m |
| 2026-04-15 | AFR32J | CDG → ATL | Apr 15, 21:05 UTC | Apr 15, 21:45 UTC | 40m |
| 2026-04-15 | AFR32J | CDG → ATL | Apr 15, 19:05 UTC | Apr 15, 21:00 UTC | 1h 55m |
| 2026-04-15 | AFR32J | CDG → ATL | Apr 15, 18:40 UTC | Apr 15, 19:00 UTC | 20m |
| 2026-04-15 | AFR32J | CDG → ATL | Apr 15, 13:01 UTC | Apr 15, 14:40 UTC | 1h 40m |
| 2026-04-13 | AFR453 | GRU → CDG | Apr 13, 18:15 UTC | Apr 13, 19:25 UTC | 1h 10m |
| 2026-04-13 | AFR454 | CDG → GRU | Apr 13, 08:25 UTC | Apr 13, 09:05 UTC | 40m |
| 2026-04-13 | AFR454 | CDG → GRU | Apr 13, 05:50 UTC | Apr 13, 07:50 UTC | 2h 0m |
| 2026-04-13 | AFR454 | CDG → GRU | Apr 13, 00:20 UTC | Apr 13, 01:00 UTC | 40m |
| 2026-04-13 | AFR454 | CDG → GRU | Apr 13, 00:05 UTC | Apr 13, 01:00 UTC | 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 F-GSQV page for operator, model, and routing details .