Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

407F6E

ICAO 24-bit transponder address · allocated to United Kingdom

Currently assigned to G-OHJK · BOEING 737-800

Hex
407F6E
Octal
20077556
Decimal
4,226,926
Country
GB
Tail
G-OHJK
Type
B738
No current signal · last broadcast 20h ago
Flights observed
83
Distinct callsigns
5
Country
GB
Last broadcast
20h ago

Last known position

Most recent position reported by Mode-S 407F6E.

Country allocation

The ICAO 24-bit address 407F6E falls within the block assigned to United Kingdom (GB) by ICAO Annex 10, Volume III. Every aircraft registered in United Kingdom 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 5 distinct

Callsign Airline Flights Last seen
ABV8AN - 53 2026-06-12
ABV9AN - 25 2026-06-11
ABV737 - 2 2026-04-27
ABV4815 - 2 2026-05-22
ABV4816 - 1 2026-04-30

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-06-12 ABV8AN EMA → MAN Jun 12, 05:20 UTCJun 12, 05:40 UTC20m
2026-06-12 ABV8AN CDG → EMA Jun 12, 02:45 UTCJun 12, 04:00 UTC1h 15m
2026-06-11 ABV9AN MAN → CDG Jun 11, 20:50 UTCJun 11, 21:55 UTC1h 5m
2026-06-11 ABV8AN EMA → MAN Jun 11, 04:25 UTCJun 11, 04:40 UTC15m
2026-06-11 ABV8AN CDG → EMA Jun 11, 02:30 UTCJun 11, 03:25 UTC55m
2026-06-10 ABV9AN - Jun 10, 20:50 UTCJun 10, 21:50 UTC1h 0m
2026-06-10 ABV8AN EMA → MAN Jun 10, 04:10 UTCJun 10, 04:30 UTC20m
2026-06-10 ABV8AN - Jun 10, 02:20 UTCJun 10, 03:15 UTC55m
2026-06-09 ABV9AN MAN → CDG Jun 9, 20:50 UTCJun 9, 21:55 UTC1h 5m
2026-06-09 ABV8AN EMA → MAN Jun 9, 04:15 UTCJun 9, 04:30 UTC15m
2026-06-09 ABV8AN - Jun 9, 02:25 UTCJun 9, 03:15 UTC50m
2026-06-08 ABV9AN MAN → CDG Jun 8, 20:50 UTCJun 8, 21:55 UTC1h 5m
2026-06-05 ABV8AN EMA → MAN Jun 5, 04:05 UTCJun 5, 04:25 UTC20m
2026-06-05 ABV8AN - Jun 5, 02:10 UTCJun 5, 03:05 UTC55m
2026-06-04 ABV8AN MAN → CDG Jun 4, 21:40 UTCJun 4, 22:45 UTC1h 5m
2026-06-04 ABV8AN EMA → MAN Jun 4, 04:10 UTCJun 4, 04:30 UTC20m
2026-06-04 ABV8AN CDG → EMA Jun 4, 02:20 UTCJun 4, 03:15 UTC55m
2026-06-03 ABV9AN MAN → CDG Jun 3, 20:55 UTCJun 3, 22:00 UTC1h 5m
2026-06-03 ABV8AN EMA → MAN Jun 3, 04:25 UTCJun 3, 04:40 UTC15m
2026-06-03 ABV8AN - Jun 3, 02:30 UTCJun 3, 03:25 UTC55m
2026-06-02 ABV9AN MAN → CDG Jun 2, 21:05 UTCJun 2, 22:10 UTC1h 5m
2026-06-02 ABV8AN EMA → MAN Jun 2, 04:15 UTCJun 2, 04:35 UTC20m
2026-06-02 ABV8AN CDG → EMA Jun 2, 02:35 UTCJun 2, 03:25 UTC50m
2026-06-01 ABV9AN MAN → CDG Jun 1, 21:05 UTCJun 1, 22:10 UTC1h 5m
2026-05-29 ABV8AN EMA → MAN May 29, 04:00 UTCMay 29, 04:20 UTC20m
2026-05-29 ABV8AN - May 29, 02:10 UTCMay 29, 03:05 UTC55m
2026-05-28 ABV9AN MAN → CDG May 28, 21:10 UTCMay 28, 22:15 UTC1h 5m
2026-05-28 ABV8AN - May 28, 02:15 UTCMay 28, 03:25 UTC1h 10m
2026-05-27 ABV9AN MAN → CDG May 27, 20:45 UTCMay 27, 21:45 UTC1h 0m
2026-05-27 ABV8AN EMA → MAN May 27, 04:09 UTCMay 27, 04:30 UTC20m
2026-05-27 ABV8AN CDG → EMA May 27, 02:24 UTCMay 27, 03:14 UTC50m
2026-05-26 ABV9AN MAN → CDG May 26, 20:54 UTCMay 26, 21:49 UTC55m
2026-05-26 ABV8AN EMA → MAN May 26, 04:10 UTCMay 26, 04:30 UTC20m
2026-05-26 ABV8AN CDG → EMA May 26, 02:19 UTCMay 26, 03:09 UTC50m
2026-05-22 ABV9AN MAN → CDG May 22, 06:25 UTCMay 22, 07:20 UTC55m
2026-05-22 ABV4815 EMA → MAN May 22, 04:10 UTCMay 22, 04:25 UTC15m
2026-05-22 ABV8AN - May 22, 02:15 UTCMay 22, 03:05 UTC50m
2026-05-21 ABV9AN MAN → CDG May 21, 20:50 UTCMay 21, 21:50 UTC1h 0m
2026-05-21 ABV8AN EMA → MAN May 21, 04:15 UTCMay 21, 04:30 UTC15m
2026-05-21 ABV8AN CDG → EMA May 21, 02:20 UTCMay 21, 03:10 UTC50m
2026-05-20 ABV9AN MAN → CDG May 20, 20:50 UTCMay 20, 21:55 UTC1h 5m
2026-05-20 ABV8AN EMA → MAN May 20, 04:10 UTCMay 20, 04:30 UTC20m
2026-05-20 ABV8AN CDG → EMA May 20, 02:10 UTCMay 20, 03:00 UTC50m
2026-05-19 ABV9AN MAN → CDG May 19, 20:55 UTCMay 19, 22:05 UTC1h 10m
2026-05-19 ABV8AN EMA → MAN May 19, 04:15 UTCMay 19, 04:30 UTC15m
2026-05-19 ABV8AN CDG → EMA May 19, 02:10 UTCMay 19, 03:00 UTC50m
2026-05-18 ABV9AN MAN → CDG May 18, 21:05 UTCMay 18, 22:05 UTC1h 0m
2026-05-15 ABV8AN EMA → MAN May 15, 04:20 UTCMay 15, 04:45 UTC25m
2026-05-15 ABV8AN - May 15, 02:10 UTCMay 15, 03:00 UTC50m
2026-05-14 ABV9AN MAN → CDG May 14, 20:55 UTCMay 14, 21:55 UTC1h 0m

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

Mode-S 407F6E frequently asked

What is Mode-S code 407F6E?
407F6E is an ICAO 24-bit transponder address. Allocated to United Kingdom. Assigned to G-OHJK.
Where is Mode-S 407F6E registered?
Mode-S code 407F6E is allocated to United Kingdom (GB). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 407F6E broadcasting right now?
No active broadcast right now. Last signal was 20h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 407F6E, octal 20077556, decimal 4,226,926.
What flights does 407F6E operate?
Mode-S 407F6E has broadcast 5 distinct callsigns, including ABV8AN, ABV9AN, ABV737, ABV4815, ABV4816.