Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

407FA0

ICAO 24-bit transponder address · allocated to United Kingdom

Currently assigned to G-RORE · EMBRAER EMB-550 Praetor 600

Hex
407FA0
Octal
20077640
Decimal
4,226,976
Country
GB
Tail
G-RORE
Type
E550
No current signal · last broadcast 3h ago
Flights observed
110
Distinct callsigns
2
Country
GB
Last broadcast
3h ago

Last known position

Most recent position reported by Mode-S 407FA0.

Country allocation

The ICAO 24-bit address 407FA0 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 2 distinct

Callsign Airline Flights Last seen
FLJ64G - 106 2026-07-23
GRORE - 4 2026-07-17

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-23 FLJ64G - Jul 23, 15:35 UTCJul 23, 16:00 UTC25m
2026-07-23 FLJ64G - Jul 23, 12:25 UTCJul 23, 14:30 UTC2h 5m
2026-07-23 FLJ64G - Jul 23, 09:10 UTCJul 23, 11:05 UTC1h 55m
2026-07-23 FLJ64G - Jul 23, 07:10 UTCJul 23, 08:00 UTC50m
2026-07-23 FLJ64G MAN → MAN Jul 23, 06:45 UTCJul 23, 06:50 UTC5m
2026-07-23 FLJ64G MAN → MAN Jul 23, 06:35 UTCJul 23, 06:40 UTC5m
2026-07-22 FLJ64G - Jul 22, 12:20 UTCJul 22, 14:30 UTC2h 10m
2026-07-21 FLJ64G LCY → BLQ Jul 21, 07:35 UTCJul 21, 09:10 UTC1h 35m
2026-07-20 FLJ64G MAN → LCY Jul 20, 17:40 UTCJul 20, 18:20 UTC40m
2026-07-19 FLJ64G - Jul 19, 17:20 UTCJul 19, 18:00 UTC40m
2026-07-19 FLJ64G KRS → FAB Jul 19, 15:00 UTCJul 19, 16:25 UTC1h 25m
2026-07-19 FLJ64G - Jul 19, 12:15 UTCJul 19, 13:40 UTC1h 25m
2026-07-18 FLJ64G ANR → LCY Jul 18, 08:20 UTCJul 18, 09:00 UTC40m
2026-07-17 GRORE LCY → ANR Jul 17, 09:04 UTCJul 17, 09:40 UTC35m
2026-07-16 FLJ64G - Jul 16, 17:45 UTCJul 16, 18:19 UTC35m
2026-07-16 FLJ64G - Jul 16, 15:40 UTCJul 16, 16:40 UTC1h 0m
2026-07-15 FLJ64G - Jul 15, 08:55 UTCJul 15, 10:00 UTC1h 5m
2026-07-14 FLJ64G - Jul 14, 17:40 UTCJul 14, 18:45 UTC1h 5m
2026-07-14 FLJ64G - Jul 14, 14:45 UTCJul 14, 15:25 UTC40m
2026-07-13 FLJ64G MAN → MAN Jul 13, 17:45 UTCJul 13, 17:50 UTC5m
2026-07-13 FLJ64G - Jul 13, 17:00 UTCJul 13, 17:40 UTC40m
2026-07-13 FLJ64G EDI → FAB Jul 13, 15:15 UTCJul 13, 16:25 UTC1h 10m
2026-07-13 FLJ64G - Jul 13, 12:30 UTCJul 13, 12:55 UTC25m
2026-07-13 FLJ64G - Jul 13, 08:50 UTCJul 13, 10:00 UTC1h 10m
2026-07-08 FLJ64G - Jul 8, 18:55 UTCJul 8, 19:55 UTC1h 0m
2026-07-08 FLJ64G - Jul 8, 17:10 UTCJul 8, 18:10 UTC1h 0m
2026-07-08 FLJ64G - Jul 8, 14:25 UTCJul 8, 15:10 UTC45m
2026-07-08 FLJ64G FAB → LBG Jul 8, 11:30 UTCJul 8, 12:15 UTC45m
2026-07-07 FLJ64G NCE → FAB Jul 7, 16:25 UTCJul 7, 18:05 UTC1h 40m
2026-07-07 FLJ64G - Jul 7, 07:50 UTCJul 7, 10:00 UTC2h 10m
2026-07-06 FLJ64G - Jul 6, 14:05 UTCJul 6, 14:30 UTC25m
2026-07-06 FLJ64G - Jul 6, 12:15 UTCJul 6, 13:10 UTC55m
2026-07-06 FLJ64G - Jul 6, 09:05 UTCJul 6, 09:30 UTC25m
2026-07-05 FLJ64G - Jul 5, 15:10 UTCJul 5, 16:00 UTC50m
2026-07-05 FLJ64G - Jul 5, 12:20 UTCJul 5, 13:00 UTC40m
2026-07-05 FLJ64G MAN → LTN Jul 5, 01:00 UTCJul 5, 01:25 UTC25m
2026-07-04 FLJ64G NHT → MAN Jul 4, 15:00 UTCJul 4, 15:30 UTC30m
2026-07-03 FLJ64G - Jul 3, 15:45 UTCJul 3, 16:25 UTC40m
2026-07-03 FLJ64G - Jul 3, 13:35 UTCJul 3, 14:25 UTC50m
2026-07-03 FLJ64G EDI → FAB Jul 3, 11:45 UTCJul 3, 12:40 UTC55m
2026-07-03 FLJ64G - Jul 3, 08:30 UTCJul 3, 09:35 UTC1h 5m
2026-07-02 FLJ64G - Jul 2, 12:45 UTCJul 2, 13:15 UTC30m
2026-07-02 FLJ64G - Jul 2, 07:15 UTCJul 2, 07:35 UTC20m
2026-07-01 FLJ64G - Jul 1, 15:35 UTCJul 1, 16:10 UTC35m
2026-07-01 FLJ64G IBZ → MAN Jul 1, 12:25 UTCJul 1, 14:50 UTC2h 25m
2026-06-28 FLJ64G - Jun 28, 09:15 UTCJun 28, 11:45 UTC2h 30m
2026-06-28 FLJ64G MAN → MAN Jun 28, 08:34 UTCJun 28, 08:39 UTC5m
2026-06-27 FLJ64G - Jun 27, 18:04 UTCJun 27, 20:19 UTC2h 15m
2026-06-25 FLJ64G - Jun 25, 07:00 UTCJun 25, 09:20 UTC2h 20m
2026-06-25 FLJ64G MAN → MAN Jun 25, 06:20 UTCJun 25, 06:25 UTC5m

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

Mode-S 407FA0 frequently asked

What is Mode-S code 407FA0?
407FA0 is an ICAO 24-bit transponder address. Allocated to United Kingdom. Assigned to G-RORE.
Where is Mode-S 407FA0 registered?
Mode-S code 407FA0 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 407FA0 broadcasting right now?
No active broadcast right now. Last signal was 3h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 407FA0, octal 20077640, decimal 4,226,976.
What flights does 407FA0 operate?
Mode-S 407FA0 has broadcast 2 distinct callsigns, including FLJ64G, GRORE.