sensors Mode-S transponder

868DB5

ICAO 24-bit transponder address · allocated to Japan

Currently assigned to JA771F · BOEING 777-200LR

Hex
868DB5
Octal
41506665
Decimal
8,818,101
Country
JP
Tail
JA771F
Type
B77L
No current signal · last broadcast 5h ago
Flights observed
81
Distinct callsigns
12
Country
JP
Last broadcast
5h ago

Last known position

Most recent position reported by Mode-S 868DB5.

Country allocation

The ICAO 24-bit address 868DB5 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 12 distinct

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-30 ANA8422 NRT → ORD May 30, 00:35 UTCMay 30, 01:00 UTC25m
2026-05-29 ANA8403 NRT → PVG May 29, 13:10 UTCMay 29, 21:15 UTC8h 5m
2026-05-28 ANA8404 PVG → NRT May 28, 12:55 UTCMay 28, 21:05 UTC8h 10m
2026-05-27 ANA8401 ORD → NRT May 27, 20:25 UTCMay 28, 09:05 UTC12h 40m
2026-05-27 ANA8402 NRT → ORD May 27, 05:55 UTCMay 27, 17:10 UTC11h 16m
2026-05-26 ANA840D - May 26, 13:10 UTCMay 26, 21:09 UTC8h 0m
2026-05-25 ANA8531 ORD → NRT May 25, 20:34 UTCMay 26, 08:39 UTC12h 5m
2026-05-21 ANA8422 NRT → ORD May 21, 01:10 UTCMay 21, 12:00 UTC10h 50m
2026-05-20 ANA8404 PVG → NRT May 20, 13:50 UTCMay 20, 21:40 UTC7h 50m
2026-05-19 ANA8417 NRT → OKA May 19, 18:10 UTCMay 20, 05:25 UTC11h 16m
2026-05-19 ANA8418 OKA → NRT May 19, 06:35 UTCMay 19, 15:50 UTC9h 15m
2026-05-18 ANA8421 ORD → NRT May 18, 14:55 UTCMay 19, 04:10 UTC13h 14m
2026-05-18 ANA8422 NRT → ORD May 18, 00:35 UTCMay 18, 11:55 UTC11h 20m
2026-05-16 ANA8407 LAX → NRT May 16, 23:35 UTCMay 17, 10:55 UTC11h 20m
2026-05-16 ANA8408 NRT → LAX May 16, 11:35 UTCMay 16, 20:40 UTC9h 5m
2026-05-15 ANA8401 ORD → NRT May 15, 20:35 UTCMay 16, 08:55 UTC12h 21m
2026-05-15 ANA8402 NRT → ORD May 15, 05:45 UTCMay 15, 17:35 UTC11h 49m
2026-05-10 ANA8407 LAX → NRT May 10, 00:05 UTCMay 10, 11:20 UTC11h 15m
2026-05-09 ANA8408 NRT → LAX May 9, 12:40 UTCMay 9, 21:40 UTC9h 0m
2026-05-08 ANA8401 ORD → NRT May 8, 20:50 UTCMay 9, 09:50 UTC13h 0m
2026-05-08 ANA8402 NRT → ORD May 8, 05:59 UTCMay 8, 16:55 UTC10h 55m
2026-05-07 ANA8403 NRT → PVG May 7, 12:55 UTCMay 7, 21:20 UTC8h 25m
2026-05-06 ANA8401 ORD → NRT May 6, 21:05 UTCMay 7, 10:00 UTC12h 55m
2026-05-06 ANA8402 NRT → ORD May 6, 06:25 UTCMay 6, 17:25 UTC11h 0m
2026-05-05 ANA8421 ORD → NRT May 5, 14:45 UTCMay 6, 03:35 UTC12h 50m
2026-05-05 ANA8422 NRT → ORD May 5, 00:20 UTCMay 5, 11:05 UTC10h 45m
2026-05-03 ANA8401 ORD → NRT May 3, 21:10 UTCMay 4, 10:30 UTC13h 20m
2026-05-03 ANA8402 NRT → ORD May 3, 06:10 UTCMay 3, 17:10 UTC11h 0m
2026-05-02 ANA8421 ORD → NRT May 2, 14:40 UTCMay 3, 03:40 UTC12h 59m
2026-05-02 ANA8422 NRT → ORD May 2, 00:20 UTCMay 2, 11:30 UTC11h 10m
2026-05-01 ANA8403 NRT → PVG May 1, 13:05 UTCMay 1, 21:05 UTC8h 0m
2026-04-30 ANA8403 NRT → PVG Apr 30, 13:10 UTCApr 30, 21:50 UTC8h 40m
2026-04-29 ANA8401 ORD → NRT Apr 29, 20:10 UTCApr 30, 08:55 UTC12h 44m
2026-04-29 ANA8402 NRT → ORD Apr 29, 06:05 UTCApr 29, 17:01 UTC10h 56m
2026-04-28 ANA8421 ORD → NRT Apr 28, 14:20 UTCApr 29, 03:04 UTC12h 45m
2026-04-28 ANA8422 NRT → ORD Apr 28, 00:05 UTCApr 28, 11:10 UTC11h 5m
2026-04-27 ANA8403 NRT → PVG Apr 27, 13:10 UTCApr 27, 21:10 UTC8h 0m
2026-04-26 ANA8401 ORD → NRT Apr 26, 20:10 UTCApr 27, 08:50 UTC12h 40m
2026-04-26 ANA8402 NRT → ORD Apr 26, 05:50 UTCApr 26, 16:55 UTC11h 5m
2026-04-25 ANA8421 ORD → NRT Apr 25, 14:15 UTCApr 26, 02:35 UTC12h 20m
2026-04-25 ANA8422 NRT → ORD Apr 25, 00:20 UTCApr 25, 11:35 UTC11h 15m
2026-04-24 ANA8403 NRT → PVG Apr 24, 13:20 UTCApr 24, 21:10 UTC7h 50m
2026-04-23 ANA8403 NRT → PVG Apr 23, 13:45 UTCApr 23, 22:00 UTC8h 15m
2026-04-22 ANA8401 ORD → NRT Apr 22, 22:20 UTCApr 23, 11:01 UTC12h 41m
2026-04-22 ANA8402 NRT → ORD Apr 22, 08:10 UTCApr 22, 19:15 UTC11h 5m
2026-04-21 ANA8417 NRT → OKA Apr 21, 18:25 UTCApr 22, 05:30 UTC11h 5m
2026-04-21 ANA8418 OKA → NRT Apr 21, 06:35 UTCApr 21, 15:51 UTC9h 15m
2026-04-20 ANA8421 ORD → NRT Apr 20, 14:55 UTCApr 21, 04:05 UTC13h 10m
2026-04-20 ANA8422 NRT → ORD Apr 20, 00:15 UTCApr 20, 11:20 UTC11h 5m
2026-04-19 ANA8407 LAX → NRT Apr 19, 00:45 UTCApr 19, 11:40 UTC10h 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 JA771F page for operator, model, and routing details .

Mode-S 868DB5 frequently asked

What is Mode-S code 868DB5?
868DB5 is an ICAO 24-bit transponder address. Allocated to Japan. Assigned to JA771F.
Where is Mode-S 868DB5 registered?
Mode-S code 868DB5 is allocated to Japan (JP). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 868DB5 broadcasting right now?
No active broadcast right now. Last signal was 5h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 868DB5, octal 41506665, decimal 8,818,101.
What flights does 868DB5 operate?
Mode-S 868DB5 has broadcast 12 distinct callsigns, including ANA8401, ANA8402, ANA8422, ANA8421, ANA8403.