sensors Mode-S transponder
86953E
ICAO 24-bit transponder address · allocated to Japan
Currently assigned to JA794A · BOEING 777-300ER
- Hex
- 86953E
- Octal
- 41512476
- Decimal
- 8,820,030
- Country
- JP
- Tail
- JA794A
- Type
- B77W
- Flights observed
- 146
- Distinct callsigns
- 20
- Country
- JP
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 86953E falls within the block assigned to Japan (JP) by ICAO Annex 10, Volume III. Every aircraft registered in Japan 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 |
|---|---|---|---|
| ANA160 | - | 18 | 2026-07-07 |
| ANA109 | - | 18 | 2026-06-21 |
| ANA159 | - | 16 | 2026-07-08 |
| ANA110 | - | 13 | 2026-06-21 |
| ANA112 | - | 11 | 2026-07-12 |
| ANA11 | - | 11 | 2026-07-12 |
| ANA8 | - | 7 | 2026-07-13 |
| ANA7 | - | 6 | 2026-07-13 |
| ANA212 | - | 6 | 2026-07-10 |
| ANA211 | - | 6 | 2026-07-10 |
| ANA12 | - | 6 | 2026-07-14 |
| ANA111 | - | 5 | 2026-07-05 |
| ANA961 | - | 3 | 2026-07-09 |
| ANA126 | All Nippon Airways | 3 | 2026-05-30 |
| ANA125 | All Nippon Airways | 3 | 2026-05-31 |
| ANA962 | All Nippon Airways | 2 | 2026-04-16 |
| ANA8422 | All Nippon Airways | 2 | 2026-05-26 |
| ANA8421 | All Nippon Airways | 2 | 2026-05-26 |
| ANA108 | - | 2 | 2026-06-17 |
| ANA107 | - | 2 | 2026-06-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | ANA12 | - | Jul 14, 10:40 UTC | Jul 14, 19:30 UTC | 8h 50m |
| 2026-07-13 | ANA7 | SFO → NRT | Jul 13, 22:40 UTC | Jul 14, 08:20 UTC | 9h 40m |
| 2026-07-13 | ANA8 | - | Jul 13, 11:15 UTC | Jul 13, 20:30 UTC | 9h 15m |
| 2026-07-12 | ANA11 | - | Jul 12, 17:05 UTC | Jul 13, 05:15 UTC | 12h 10m |
| 2026-07-12 | ANA112 | HND → ORD | Jul 12, 02:01 UTC | Jul 12, 13:25 UTC | 11h 25m |
| 2026-07-10 | ANA212 | - | Jul 10, 18:40 UTC | Jul 11, 07:40 UTC | 13h 0m |
| 2026-07-10 | ANA211 | HND → LHR | Jul 10, 01:10 UTC | Jul 10, 15:10 UTC | 14h 0m |
| 2026-07-09 | ANA961 | HND → HND | Jul 9, 00:45 UTC | Jul 9, 10:25 UTC | 9h 40m |
| 2026-07-08 | ANA159 | JFK → HND | Jul 8, 06:10 UTC | Jul 8, 19:30 UTC | 13h 20m |
| 2026-07-07 | ANA160 | HND → JFK | Jul 7, 14:10 UTC | Jul 8, 02:45 UTC | 12h 35m |
| 2026-07-05 | ANA111 | - | Jul 5, 23:30 UTC | Jul 6, 12:00 UTC | 12h 30m |
| 2026-07-05 | ANA12 | - | Jul 5, 08:35 UTC | Jul 5, 19:40 UTC | 11h 5m |
| 2026-07-04 | ANA7 | SFO → NRT | Jul 4, 20:10 UTC | Jul 5, 06:15 UTC | 10h 5m |
| 2026-07-04 | ANA8 | - | Jul 4, 16:50 UTC | Jul 4, 17:35 UTC | 45m |
| 2026-07-04 | ANA8 | - | Jul 4, 08:30 UTC | Jul 4, 08:55 UTC | 25m |
| 2026-07-03 | ANA7 | SFO → NRT | Jul 3, 20:05 UTC | Jul 4, 06:05 UTC | 10h 0m |
| 2026-07-03 | ANA8 | - | Jul 3, 08:25 UTC | Jul 3, 17:10 UTC | 8h 45m |
| 2026-07-03 | ANA11 | - | Jul 3, 04:45 UTC | Jul 3, 05:20 UTC | 35m |
| 2026-07-02 | ANA11 | - | Jul 2, 17:20 UTC | Jul 3, 00:00 UTC | 6h 40m |
| 2026-07-02 | ANA112 | HND → ORD | Jul 2, 02:15 UTC | Jul 2, 13:35 UTC | 11h 20m |
| 2026-07-01 | ANA159 | JFK → HND | Jul 1, 06:10 UTC | Jul 1, 19:25 UTC | 13h 15m |
| 2026-06-30 | ANA160 | HND → JFK | Jun 30, 14:15 UTC | Jul 1, 02:40 UTC | 12h 25m |
| 2026-06-29 | ANA212 | - | Jun 29, 18:19 UTC | Jun 30, 07:40 UTC | 13h 21m |
| 2026-06-29 | ANA211 | HND → LHR | Jun 29, 01:25 UTC | Jun 29, 15:00 UTC | 13h 35m |
| 2026-06-28 | ANA159 | JFK → HND | Jun 28, 06:10 UTC | Jun 28, 19:25 UTC | 13h 15m |
| 2026-06-27 | ANA160 | HND → JFK | Jun 27, 14:20 UTC | Jun 28, 02:44 UTC | 12h 25m |
| 2026-06-26 | ANA212 | - | Jun 26, 18:24 UTC | Jun 27, 07:49 UTC | 13h 25m |
| 2026-06-26 | ANA211 | HND → LHR | Jun 26, 01:20 UTC | Jun 26, 15:15 UTC | 13h 55m |
| 2026-06-24 | ANA212 | - | Jun 24, 19:10 UTC | Jun 25, 08:24 UTC | 13h 15m |
| 2026-06-24 | ANA211 | HND → LHR | Jun 24, 01:19 UTC | Jun 24, 15:09 UTC | 13h 50m |
| 2026-06-23 | ANA159 | JFK → HND | Jun 23, 06:34 UTC | Jun 23, 19:24 UTC | 12h 50m |
| 2026-06-22 | ANA160 | HND → JFK | Jun 22, 14:24 UTC | Jun 23, 04:14 UTC | 13h 50m |
| 2026-06-21 | ANA109 | JFK → HND | Jun 21, 17:50 UTC | Jun 22, 07:25 UTC | 13h 35m |
| 2026-06-21 | ANA110 | HND → JFK | Jun 21, 02:04 UTC | Jun 21, 14:44 UTC | 12h 40m |
| 2026-06-19 | ANA109 | JFK → HND | Jun 19, 18:05 UTC | Jun 20, 06:45 UTC | 12h 40m |
| 2026-06-19 | ANA110 | HND → JFK | Jun 19, 02:04 UTC | Jun 19, 14:44 UTC | 12h 40m |
| 2026-06-18 | ANA107 | SFO → HND | Jun 18, 09:05 UTC | Jun 18, 19:15 UTC | 10h 10m |
| 2026-06-17 | ANA108 | HND → SFO | Jun 17, 14:30 UTC | Jun 17, 23:50 UTC | 9h 20m |
| 2026-06-16 | ANA109 | JFK → HND | Jun 16, 17:59 UTC | Jun 17, 07:25 UTC | 13h 26m |
| 2026-06-16 | ANA110 | HND → JFK | Jun 16, 02:20 UTC | Jun 16, 14:39 UTC | 12h 20m |
| 2026-06-14 | ANA111 | - | Jun 14, 23:10 UTC | Jun 15, 11:45 UTC | 12h 35m |
| 2026-06-14 | ANA12 | - | Jun 14, 08:25 UTC | Jun 14, 19:25 UTC | 11h 0m |
| 2026-06-14 | ANA11 | - | Jun 14, 04:25 UTC | Jun 14, 05:00 UTC | 35m |
| 2026-06-13 | ANA11 | - | Jun 13, 17:00 UTC | Jun 14, 00:00 UTC | 7h 0m |
| 2026-06-13 | ANA112 | HND → ORD | Jun 13, 02:20 UTC | Jun 13, 13:10 UTC | 10h 49m |
| 2026-06-11 | ANA212 | - | Jun 11, 18:25 UTC | Jun 12, 07:50 UTC | 13h 26m |
| 2026-06-11 | ANA211 | HND → LHR | Jun 11, 01:45 UTC | Jun 11, 15:05 UTC | 13h 20m |
| 2026-06-10 | ANA111 | ORD → HND | Jun 10, 00:05 UTC | Jun 10, 12:35 UTC | 12h 30m |
| 2026-06-09 | ANA12 | NRT → ORD | Jun 9, 09:10 UTC | Jun 9, 20:25 UTC | 11h 15m |
| 2026-06-08 | ANA7 | SFO → NRT | Jun 8, 19:50 UTC | Jun 9, 06:40 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 JA794A page for operator, model, and routing details .