sensors Mode-S transponder
3965A4
ICAO 24-bit transponder address · allocated to France
Currently assigned to F-GZNE · BOEING 777-300ER
- Hex
- 3965A4
- Octal
- 16262644
- Decimal
- 3,761,572
- Country
- FR
- Tail
- F-GZNE
- Type
- B77W
- Flights observed
- 158
- Distinct callsigns
- 20
- Country
- FR
- Last broadcast
- 9h ago
Last known position
Country allocation
The ICAO 24-bit address 3965A4 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 |
|---|---|---|---|
| AFR274 | Air France | 12 | 2026-07-01 |
| AFR256 | Air France | 12 | 2026-07-04 |
| AFR24X | - | 11 | 2026-07-08 |
| AFR257 | Air France | 10 | 2026-07-05 |
| AFR091 | - | 9 | 2026-06-28 |
| AFR025 | - | 9 | 2026-07-09 |
| AFR021 | - | 9 | 2026-07-13 |
| AFR020 | - | 8 | 2026-07-12 |
| AFR50N | Air France | 7 | 2026-04-15 |
| AFR23G | - | 7 | 2026-06-25 |
| AFR22J | Air France | 7 | 2026-06-25 |
| AFR090 | Air France | 7 | 2026-06-27 |
| AFR004 | - | 7 | 2026-06-30 |
| AFR51N | Air France | 6 | 2026-04-16 |
| AFR279 | Air France | 6 | 2026-07-02 |
| AFR007 | - | 5 | 2026-06-27 |
| AFR3T | - | 4 | 2026-06-30 |
| AFR8U | Air France | 3 | 2026-05-15 |
| AFR293 | Air France | 3 | 2026-05-20 |
| AFR003 | - | 3 | 2026-05-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | AFR5U | - | Jul 13, 23:00 UTC | Jul 14, 05:35 UTC | 6h 35m |
| 2026-07-13 | AFR006 | - | Jul 13, 11:55 UTC | Jul 13, 19:00 UTC | 7h 5m |
| 2026-07-13 | AFR021 | - | Jul 13, 06:25 UTC | Jul 13, 07:35 UTC | 1h 10m |
| 2026-07-12 | AFR021 | - | Jul 12, 21:25 UTC | Jul 13, 06:20 UTC | 8h 55m |
| 2026-07-12 | AFR020 | - | Jul 12, 07:55 UTC | Jul 12, 18:45 UTC | 10h 50m |
| 2026-07-09 | AFR025 | - | Jul 9, 01:45 UTC | Jul 9, 11:50 UTC | 10h 5m |
| 2026-07-08 | AFR24X | - | Jul 8, 11:50 UTC | Jul 8, 22:45 UTC | 10h 55m |
| 2026-07-07 | AFR703 | CDG → CDG | Jul 7, 12:45 UTC | Jul 8, 03:35 UTC | 14h 50m |
| 2026-07-06 | AFR021 | - | Jul 6, 21:20 UTC | Jul 7, 07:30 UTC | 10h 10m |
| 2026-07-06 | AFR020 | - | Jul 6, 07:35 UTC | Jul 6, 18:30 UTC | 10h 55m |
| 2026-07-05 | AFR257 | SIN → CDG | Jul 5, 14:45 UTC | Jul 6, 03:40 UTC | 12h 55m |
| 2026-07-04 | AFR256 | CDG → SIN | Jul 4, 21:50 UTC | Jul 5, 11:35 UTC | 13h 45m |
| 2026-07-03 | AFR021 | - | Jul 3, 21:20 UTC | Jul 4, 07:25 UTC | 10h 5m |
| 2026-07-03 | AFR020 | - | Jul 3, 07:35 UTC | Jul 3, 18:40 UTC | 11h 5m |
| 2026-07-02 | AFR279 | HND → CDG | Jul 2, 13:45 UTC | Jul 3, 03:30 UTC | 13h 45m |
| 2026-07-01 | AFR274 | CDG → HND | Jul 1, 21:15 UTC | Jul 2, 10:15 UTC | 13h 0m |
| 2026-06-30 | AFR3T | - | Jun 30, 22:05 UTC | Jul 1, 04:35 UTC | 6h 30m |
| 2026-06-30 | AFR004 | - | Jun 30, 09:40 UTC | Jun 30, 17:00 UTC | 7h 20m |
| 2026-06-29 | AFR257 | SIN → CDG | Jun 29, 14:50 UTC | Jun 30, 03:35 UTC | 12h 46m |
| 2026-06-28 | AFR256 | CDG → SIN | Jun 28, 21:45 UTC | Jun 29, 10:04 UTC | 12h 20m |
| 2026-06-28 | AFR091 | - | Jun 28, 00:50 UTC | Jun 28, 08:59 UTC | 8h 10m |
| 2026-06-27 | AFR090 | CDG → MIA | Jun 27, 12:19 UTC | Jun 27, 21:44 UTC | 9h 25m |
| 2026-06-27 | AFR007 | - | Jun 27, 01:54 UTC | Jun 27, 08:14 UTC | 6h 20m |
| 2026-06-26 | AFR8F | - | Jun 26, 15:29 UTC | Jun 26, 22:44 UTC | 7h 15m |
| 2026-06-25 | AFR23G | - | Jun 25, 22:34 UTC | Jun 26, 08:45 UTC | 10h 10m |
| 2026-06-25 | AFR22J | CDG → LAX | Jun 25, 09:20 UTC | Jun 25, 20:05 UTC | 10h 45m |
| 2026-06-24 | AFR257 | SIN → CDG | Jun 24, 14:50 UTC | Jun 25, 03:34 UTC | 12h 45m |
| 2026-06-24 | AFR256 | CDG → SIN | Jun 24, 06:20 UTC | Jun 24, 11:09 UTC | 4h 50m |
| 2026-06-23 | AFR256 | CDG → SIN | Jun 23, 21:39 UTC | Jun 24, 05:20 UTC | 7h 40m |
| 2026-06-23 | AFR091 | - | Jun 23, 01:25 UTC | Jun 23, 09:20 UTC | 7h 55m |
| 2026-06-22 | AFR090 | CDG → MIA | Jun 22, 13:19 UTC | Jun 22, 22:19 UTC | 9h 0m |
| 2026-06-22 | AFR007 | JFK → CDG | Jun 22, 02:04 UTC | Jun 22, 08:25 UTC | 6h 20m |
| 2026-06-21 | AFR8F | - | Jun 21, 14:54 UTC | Jun 21, 22:24 UTC | 7h 30m |
| 2026-06-21 | AFR009 | JFK → CDG | Jun 21, 03:55 UTC | Jun 21, 10:04 UTC | 6h 10m |
| 2026-06-20 | AFR010 | - | Jun 20, 17:04 UTC | Jun 21, 00:34 UTC | 7h 30m |
| 2026-06-19 | AFR021 | LAX → CDG | Jun 19, 21:24 UTC | Jun 20, 07:34 UTC | 10h 10m |
| 2026-06-19 | AFR020 | CDG → LAX | Jun 19, 08:04 UTC | Jun 19, 18:39 UTC | 10h 35m |
| 2026-06-18 | AFR3T | - | Jun 18, 22:00 UTC | Jun 19, 04:19 UTC | 6h 19m |
| 2026-06-18 | AFR004 | - | Jun 18, 09:45 UTC | Jun 18, 17:05 UTC | 7h 20m |
| 2026-06-17 | AFR257 | SIN → CDG | Jun 17, 14:50 UTC | Jun 18, 03:40 UTC | 12h 50m |
| 2026-06-16 | AFR256 | CDG → SIN | Jun 16, 21:35 UTC | Jun 17, 09:50 UTC | 12h 15m |
| 2026-06-15 | AFR021 | LAX → CDG | Jun 15, 22:45 UTC | Jun 16, 09:10 UTC | 10h 25m |
| 2026-06-15 | AFR020 | CDG → LAX | Jun 15, 09:54 UTC | Jun 15, 20:04 UTC | 10h 10m |
| 2026-06-14 | AFR5U | JFK → CDG | Jun 14, 23:05 UTC | Jun 15, 05:20 UTC | 6h 15m |
| 2026-06-14 | AFR006 | - | Jun 14, 11:55 UTC | Jun 14, 19:10 UTC | 7h 15m |
| 2026-06-13 | AFR021 | LAX → CDG | Jun 13, 21:20 UTC | Jun 14, 07:30 UTC | 10h 10m |
| 2026-06-13 | AFR020 | CDG → LAX | Jun 13, 08:05 UTC | Jun 13, 18:55 UTC | 10h 50m |
| 2026-06-12 | AFR279 | HND → CDG | Jun 12, 13:30 UTC | Jun 13, 04:20 UTC | 14h 49m |
| 2026-06-11 | AFR274 | CDG → HND | Jun 11, 21:15 UTC | Jun 12, 10:15 UTC | 13h 1m |
| 2026-06-11 | AFR025 | LAX → CDG | Jun 11, 01:45 UTC | Jun 11, 11:35 UTC | 9h 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-GZNE page for operator, model, and routing details .