sensors Mode-S transponder

846250

ICAO 24-bit transponder address · allocated to Japan

Currently assigned to JA12AN · BOEING 737-700

Hex
846250
Octal
41061120
Decimal
8,675,920
Country
JP
Tail
JA12AN
Type
B737
No current signal · last broadcast 24m ago
Flights observed
388
Distinct callsigns
20
Country
JP
Last broadcast
24m ago

Last known position

Most recent position reported by Mode-S 846250.

Country allocation

The ICAO 24-bit address 846250 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
ADO128 - 15 2026-07-14
ADO127 - 15 2026-07-14
ADO135 - 14 2026-07-09
ADO130 - 14 2026-07-14
ADO78 - 13 2026-07-07
ADO77 - 13 2026-07-07
ADO43 - 13 2026-07-12
ADO74 - 12 2026-07-12
ADO73 - 12 2026-07-12
ADO111 - 12 2026-07-09
ADO110 - 12 2026-07-09
ADO44 - 11 2026-07-11
ADO121 - 11 2026-07-11
ADO120 - 11 2026-07-11
ADO119 - 11 2026-07-11
ADO118 - 11 2026-07-10
ADO107 - 11 2026-07-11
ADO58 - 10 2026-07-07
ADO57 Hokkaido International Airlines 10 2026-07-06
ADO79 - 9 2026-06-14

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 ADO128 - Jul 14, 04:55 UTCJul 14, 05:55 UTC1h 0m
2026-07-14 ADO127 - Jul 14, 02:30 UTCJul 14, 03:35 UTC1h 5m
2026-07-14 ADO130 - Jul 14, 00:00 UTCJul 14, 01:15 UTC1h 15m
2026-07-13 ADO37 HND → CTS Jul 13, 11:40 UTCJul 13, 12:55 UTC1h 15m
2026-07-13 ADO28 - Jul 13, 07:45 UTCJul 13, 09:25 UTC1h 40m
2026-07-13 ADO25 - Jul 13, 05:05 UTCJul 13, 06:30 UTC1h 25m
2026-07-13 ADO18 - Jul 13, 02:40 UTCJul 13, 03:50 UTC1h 10m
2026-07-13 ADO101 - Jul 13, 00:45 UTCJul 13, 01:40 UTC55m
2026-07-12 ADO100 - Jul 12, 23:00 UTCJul 12, 23:40 UTC40m
2026-07-12 ADO43 - Jul 12, 13:05 UTCJul 12, 14:25 UTC1h 20m
2026-07-12 ADO74 - Jul 12, 10:20 UTCJul 12, 11:35 UTC1h 15m
2026-07-12 ADO73 - Jul 12, 07:40 UTCJul 12, 08:55 UTC1h 15m
2026-07-11 ADO44 - Jul 11, 12:45 UTCJul 11, 14:15 UTC1h 30m
2026-07-11 ADO121 - Jul 11, 10:20 UTCJul 11, 11:55 UTC1h 35m
2026-07-11 ADO120 - Jul 11, 08:05 UTCJul 11, 09:35 UTC1h 30m
2026-07-11 ADO107 - Jul 11, 06:05 UTCJul 11, 07:00 UTC55m
2026-07-11 HD106 - Jul 11, 04:15 UTCJul 11, 05:01 UTC45m
2026-07-11 ADO119 - Jul 11, 01:40 UTCJul 11, 03:25 UTC1h 45m
2026-07-10 ADO118 - Jul 10, 23:15 UTCJul 11, 00:50 UTC1h 35m
2026-07-10 ADO37 - Jul 10, 11:35 UTCJul 10, 12:50 UTC1h 15m
2026-07-10 ADO28 CTS → HND Jul 10, 07:15 UTCJul 10, 08:30 UTC1h 15m
2026-07-10 ADO25 HND → CTS Jul 10, 05:00 UTCJul 10, 06:15 UTC1h 15m
2026-07-10 ADO18 - Jul 10, 02:40 UTCJul 10, 03:55 UTC1h 15m
2026-07-10 ADO101 - Jul 10, 01:10 UTCJul 10, 01:45 UTC35m
2026-07-09 ADO100 - Jul 9, 23:00 UTCJul 9, 23:40 UTC40m
2026-07-09 ADO111 - Jul 9, 10:55 UTCJul 9, 11:50 UTC55m
2026-07-09 ADO110 - Jul 9, 09:00 UTCJul 9, 09:45 UTC45m
2026-07-09 ADO135 - Jul 9, 06:50 UTCJul 9, 08:10 UTC1h 20m
2026-07-09 ADO128 - Jul 9, 04:30 UTCJul 9, 05:35 UTC1h 5m
2026-07-09 ADO127 - Jul 9, 02:25 UTCJul 9, 03:35 UTC1h 10m
2026-07-09 ADO130 - Jul 9, 00:00 UTCJul 9, 01:15 UTC1h 15m
2026-07-08 ADO43 - Jul 8, 12:45 UTCJul 8, 14:00 UTC1h 15m
2026-07-08 ADO74 - Jul 8, 09:55 UTCJul 8, 11:15 UTC1h 20m
2026-07-08 ADO73 - Jul 8, 07:30 UTCJul 8, 08:45 UTC1h 15m
2026-07-08 ADO72 - Jul 8, 01:20 UTCJul 8, 02:35 UTC1h 15m
2026-07-07 ADO71 HND → KUH Jul 7, 23:10 UTCJul 8, 00:15 UTC1h 5m
2026-07-07 ADO68 OBO → HND Jul 7, 10:30 UTCJul 7, 11:50 UTC1h 20m
2026-07-07 ADO67 - Jul 7, 08:30 UTCJul 7, 09:35 UTC1h 5m
2026-07-07 ADO78 - Jul 7, 05:00 UTCJul 7, 06:30 UTC1h 30m
2026-07-07 ADO77 - Jul 7, 02:45 UTCJul 7, 04:15 UTC1h 30m
2026-07-07 ADO58 - Jul 7, 00:35 UTCJul 7, 01:40 UTC1h 5m
2026-07-06 ADO57 HND → HKD Jul 6, 22:40 UTCJul 6, 23:45 UTC1h 5m
2026-07-06 ADO68 OBO → HND Jul 6, 10:35 UTCJul 6, 11:50 UTC1h 15m
2026-07-06 ADO67 - Jul 6, 08:25 UTCJul 6, 09:30 UTC1h 5m
2026-07-06 ADO78 - Jul 6, 04:55 UTCJul 6, 06:30 UTC1h 35m
2026-07-06 ADO77 - Jul 6, 02:40 UTCJul 6, 04:10 UTC1h 30m
2026-07-06 ADO58 - Jul 6, 00:30 UTCJul 6, 01:30 UTC1h 0m
2026-07-05 ADO57 HND → HKD Jul 5, 22:40 UTCJul 5, 23:45 UTC1h 5m
2026-07-04 ADO9052 - Jul 4, 17:35 UTCJul 4, 19:20 UTC1h 45m
2026-06-15 ADO9053 - Jun 15, 18:10 UTCJun 15, 20:25 UTC2h 15m

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 JA12AN page for operator, model, and routing details .

Mode-S 846250 frequently asked

What is Mode-S code 846250?
846250 is an ICAO 24-bit transponder address. Allocated to Japan. Assigned to JA12AN.
Where is Mode-S 846250 registered?
Mode-S code 846250 is allocated to Japan (JP). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 846250 broadcasting right now?
No active broadcast right now. Last signal was 24m ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 846250, octal 41061120, decimal 8,675,920.
What flights does 846250 operate?
Mode-S 846250 has broadcast 20 distinct callsigns, including ADO128, ADO127, ADO135, ADO130, ADO78.