sensors Mode-S transponder
394A08
ICAO 24-bit transponder address · allocated to France
Currently assigned to F-GSQI · BOEING 777-300ER
- Hex
- 394A08
- Octal
- 16245010
- Decimal
- 3,754,504
- Country
- FR
- Tail
- F-GSQI
- Type
- B77W
- Flights observed
- 159
- Distinct callsigns
- 20
- Country
- FR
- Last broadcast
- 4h ago
Current position
Country allocation
The ICAO 24-bit address 394A08 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 |
|---|---|---|---|
| AFR51N | - | 14 | 2026-06-21 |
| AFR50N | Air France | 14 | 2026-06-21 |
| AFR5U | - | 10 | 2026-07-08 |
| AFR454 | - | 10 | 2026-07-11 |
| AFR83K | - | 9 | 2026-07-10 |
| AFR84E | - | 8 | 2026-07-10 |
| AFR453 | - | 8 | 2026-07-12 |
| AFR257 | Air France | 8 | 2026-06-23 |
| AFR031 | - | 8 | 2026-06-27 |
| AFR030 | Air France | 8 | 2026-06-27 |
| AFR256 | Air France | 7 | 2026-06-22 |
| AFR006 | - | 7 | 2026-07-08 |
| AFR092 | Air France | 5 | 2026-06-19 |
| AFR093 | - | 4 | 2026-06-20 |
| AFR98G | - | 3 | 2026-07-13 |
| AFR703 | - | 3 | 2026-06-16 |
| AFR702 | - | 3 | 2026-06-28 |
| AFR099 | - | 3 | 2026-07-13 |
| AFR010 | Air France | 3 | 2026-06-05 |
| AFR009 | - | 3 | 2026-06-06 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | AFR099 | - | Jul 13, 22:40 UTC | Jul 14, 02:45 UTC | 4h 5m |
| 2026-07-13 | AFR98G | - | Jul 13, 10:00 UTC | Jul 13, 20:05 UTC | 10h 5m |
| 2026-07-12 | AFR453 | - | Jul 12, 17:55 UTC | Jul 13, 04:10 UTC | 10h 15m |
| 2026-07-11 | AFR454 | - | Jul 11, 22:10 UTC | Jul 12, 09:55 UTC | 11h 45m |
| 2026-07-10 | AFR83K | - | Jul 10, 23:05 UTC | Jul 11, 09:10 UTC | 10h 5m |
| 2026-07-10 | AFR84E | - | Jul 10, 09:50 UTC | Jul 10, 20:35 UTC | 10h 45m |
| 2026-07-09 | AFR357E | - | Jul 9, 22:30 UTC | Jul 10, 05:10 UTC | 6h 40m |
| 2026-07-09 | AFR356G | - | Jul 9, 12:20 UTC | Jul 9, 20:00 UTC | 7h 40m |
| 2026-07-08 | AFR5U | - | Jul 8, 23:40 UTC | Jul 9, 06:20 UTC | 6h 40m |
| 2026-07-08 | AFR006 | - | Jul 8, 12:55 UTC | Jul 8, 20:00 UTC | 7h 5m |
| 2026-07-08 | AFR377 | - | Jul 8, 01:55 UTC | Jul 8, 09:10 UTC | 7h 15m |
| 2026-07-07 | AFR378E | - | Jul 7, 15:15 UTC | Jul 7, 22:45 UTC | 7h 30m |
| 2026-07-06 | AFR099 | - | Jul 6, 23:45 UTC | Jul 7, 08:45 UTC | 9h 0m |
| 2026-07-06 | AFR98G | - | Jul 6, 11:25 UTC | Jul 6, 21:05 UTC | 9h 40m |
| 2026-07-05 | AFR099 | - | Jul 5, 23:00 UTC | Jul 6, 07:40 UTC | 8h 40m |
| 2026-07-05 | AFR98G | - | Jul 5, 10:00 UTC | Jul 5, 20:00 UTC | 10h 0m |
| 2026-07-04 | AFR453 | GRU → CDG | Jul 4, 18:00 UTC | Jul 5, 04:35 UTC | 10h 35m |
| 2026-07-03 | AFR454 | CDG → GRU | Jul 3, 22:00 UTC | Jul 4, 09:25 UTC | 11h 25m |
| 2026-07-02 | AFR345M | YUL → CDG | Jul 2, 00:25 UTC | Jul 2, 06:20 UTC | 5h 55m |
| 2026-07-01 | AFR344 | - | Jul 1, 13:40 UTC | Jul 1, 21:00 UTC | 7h 20m |
| 2026-06-30 | AFR149 | - | Jun 30, 14:25 UTC | Jul 1, 06:00 UTC | 15h 35m |
| 2026-06-29 | AFR83K | - | Jun 29, 22:39 UTC | Jun 30, 08:40 UTC | 10h 1m |
| 2026-06-29 | AFR84E | CDG → SFO | Jun 29, 09:00 UTC | Jun 29, 19:09 UTC | 10h 10m |
| 2026-06-28 | AFR702 | - | Jun 28, 13:00 UTC | Jun 29, 04:55 UTC | 15h 55m |
| 2026-06-27 | AFR031 | ATL → CDG | Jun 27, 20:44 UTC | Jun 28, 04:25 UTC | 7h 40m |
| 2026-06-27 | AFR030 | CDG → ATL | Jun 27, 09:24 UTC | Jun 27, 18:04 UTC | 8h 40m |
| 2026-06-26 | AFR031 | - | Jun 26, 20:59 UTC | Jun 27, 04:24 UTC | 7h 25m |
| 2026-06-26 | AFR030 | CDG → ATL | Jun 26, 09:20 UTC | Jun 26, 18:15 UTC | 8h 55m |
| 2026-06-25 | AFR453 | GRU → CDG | Jun 25, 18:00 UTC | Jun 26, 04:34 UTC | 10h 35m |
| 2026-06-25 | AFR454 | CDG → GRU | Jun 25, 00:49 UTC | Jun 25, 08:50 UTC | 8h 0m |
| 2026-06-24 | AFR454 | CDG → GRU | Jun 24, 22:00 UTC | Jun 25, 00:19 UTC | 2h 20m |
| 2026-06-23 | AFR257 | SIN → CDG | Jun 23, 15:19 UTC | Jun 24, 04:00 UTC | 12h 40m |
| 2026-06-22 | AFR256 | CDG → SIN | Jun 22, 22:10 UTC | Jun 23, 10:15 UTC | 12h 5m |
| 2026-06-21 | AFR51N | IAD → CDG | Jun 21, 22:40 UTC | Jun 22, 05:24 UTC | 6h 45m |
| 2026-06-21 | AFR50N | CDG → IAD | Jun 21, 12:14 UTC | Jun 21, 20:00 UTC | 7h 45m |
| 2026-06-20 | AFR705 | - | Jun 20, 16:59 UTC | Jun 21, 08:15 UTC | 15h 15m |
| 2026-06-20 | AFR093 | - | Jun 20, 03:44 UTC | Jun 20, 12:09 UTC | 8h 25m |
| 2026-06-19 | AFR092 | CDG → MIA | Jun 19, 15:24 UTC | Jun 20, 00:29 UTC | 9h 5m |
| 2026-06-18 | AFR83K | - | Jun 18, 22:35 UTC | Jun 19, 08:44 UTC | 10h 9m |
| 2026-06-18 | AFR84E | CDG → SFO | Jun 18, 09:15 UTC | Jun 18, 20:00 UTC | 10h 45m |
| 2026-06-17 | AFR51N | - | Jun 17, 23:10 UTC | Jun 18, 05:50 UTC | 6h 40m |
| 2026-06-17 | AFR50N | CDG → IAD | Jun 17, 12:05 UTC | Jun 17, 19:50 UTC | 7h 45m |
| 2026-06-16 | AFR703 | - | Jun 16, 13:04 UTC | Jun 17, 04:20 UTC | 15h 16m |
| 2026-06-15 | AFR031 | ATL → CDG | Jun 15, 20:50 UTC | Jun 16, 04:20 UTC | 7h 30m |
| 2026-06-15 | AFR030 | CDG → ATL | Jun 15, 09:05 UTC | Jun 15, 17:50 UTC | 8h 45m |
| 2026-06-12 | AFR703 | ABJ → CDG | Jun 12, 13:00 UTC | Jun 13, 03:40 UTC | 14h 40m |
| 2026-06-11 | AFR83K | SFO → CDG | Jun 11, 22:50 UTC | Jun 12, 08:50 UTC | 10h 0m |
| 2026-06-11 | AFR84E | CDG → SFO | Jun 11, 08:45 UTC | Jun 11, 19:50 UTC | 11h 5m |
| 2026-06-09 | AFR83K | SFO → CDG | Jun 9, 23:15 UTC | Jun 10, 09:05 UTC | 9h 50m |
| 2026-06-09 | AFR84E | CDG → SFO | Jun 9, 09:25 UTC | Jun 9, 20:15 UTC | 10h 50m |
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-GSQI page for operator, model, and routing details .