sensors Mode-S transponder
407BC4
ICAO 24-bit transponder address · allocated to United Kingdom
Currently assigned to G-LOBX · BOMBARDIER BD-700 Global 7000/7500
- Hex
- 407BC4
- Octal
- 20075704
- Decimal
- 4,225,988
- Country
- GB
- Tail
- G-LOBX
- Type
- GL7T
- Flights observed
- 55
- Distinct callsigns
- 2
- Country
- GB
- Last broadcast
- 20h ago
Last known position
Country allocation
The ICAO 24-bit address 407BC4 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
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | JCO1 | - | Jul 17, 18:25 UTC | Jul 18, 02:40 UTC | 8h 15m |
| 2026-07-12 | JCO1 | - | Jul 12, 11:45 UTC | Jul 12, 13:45 UTC | 2h 0m |
| 2026-07-12 | JCO1 | - | Jul 12, 02:15 UTC | Jul 12, 09:50 UTC | 7h 35m |
| 2026-07-10 | JCO1 | BED → MIA | Jul 10, 14:45 UTC | Jul 10, 17:20 UTC | 2h 35m |
| 2026-07-09 | JCO1 | - | Jul 9, 15:05 UTC | Jul 9, 15:45 UTC | 40m |
| 2026-07-07 | JCO1 | - | Jul 7, 12:50 UTC | Jul 7, 17:05 UTC | 4h 15m |
| 2026-07-06 | JCO1 | EWR → BFI | Jul 6, 15:10 UTC | Jul 6, 20:10 UTC | 5h 0m |
| 2026-07-05 | JCO1 | SEN → EWR | Jul 5, 00:40 UTC | Jul 5, 07:45 UTC | 7h 5m |
| 2026-07-04 | JCO1 | - | Jul 4, 19:40 UTC | Jul 4, 22:00 UTC | 2h 20m |
| 2026-07-03 | JCO1 | - | Jul 3, 18:35 UTC | Jul 3, 20:40 UTC | 2h 5m |
| 2026-06-27 | JCO1 | BED → LTN | Jun 27, 01:59 UTC | Jun 27, 07:34 UTC | 5h 35m |
| 2026-06-26 | JCO1 | - | Jun 26, 08:24 UTC | Jun 26, 14:44 UTC | 6h 20m |
| 2026-06-24 | JCO1 | - | Jun 24, 15:49 UTC | Jun 24, 21:34 UTC | 5h 45m |
| 2026-06-24 | JCO1 | BED → TEB | Jun 24, 10:59 UTC | Jun 24, 11:54 UTC | 55m |
| 2026-06-22 | JCO1 | - | Jun 22, 15:59 UTC | Jun 22, 16:45 UTC | 45m |
| 2026-06-22 | JCO1 | - | Jun 22, 10:30 UTC | Jun 22, 15:54 UTC | 5h 25m |
| 2026-06-18 | JCO1 | TEB → LTN | Jun 18, 01:00 UTC | Jun 18, 07:15 UTC | 6h 15m |
| 2026-06-16 | JCO1 | - | Jun 16, 23:10 UTC | Jun 17, 05:50 UTC | 6h 40m |
| 2026-06-16 | JCO1 | - | Jun 16, 17:49 UTC | Jun 16, 19:25 UTC | 1h 35m |
| 2026-06-16 | JCO1 | - | Jun 16, 15:45 UTC | Jun 16, 16:50 UTC | 1h 5m |
| 2026-06-16 | JCO1 | - | Jun 16, 10:20 UTC | Jun 16, 11:05 UTC | 45m |
| 2026-06-12 | JCO1 | - | Jun 12, 11:30 UTC | Jun 12, 11:55 UTC | 25m |
| 2026-06-11 | JCO1 | CDW → SEN | Jun 11, 17:35 UTC | Jun 11, 23:45 UTC | 6h 10m |
| 2026-06-10 | JCO1 | BFI → TEB | Jun 10, 23:35 UTC | Jun 11, 04:05 UTC | 4h 30m |
| 2026-06-07 | JCO1 | - | Jun 7, 21:45 UTC | Jun 8, 07:55 UTC | 10h 10m |
| 2026-06-07 | JCO1 | - | Jun 7, 17:10 UTC | Jun 7, 18:40 UTC | 1h 30m |
| 2026-06-05 | JCO1 | - | Jun 5, 13:10 UTC | Jun 5, 14:50 UTC | 1h 40m |
| 2026-06-01 | JCO1 | - | Jun 1, 17:35 UTC | Jun 1, 18:35 UTC | 1h 0m |
| 2026-06-01 | JCO1 | - | Jun 1, 10:45 UTC | Jun 1, 11:45 UTC | 1h 0m |
| 2026-05-29 | JCO1 | DEL → LTN | May 29, 22:50 UTC | May 30, 07:30 UTC | 8h 40m |
| 2026-05-29 | JCO1 | - | May 29, 20:05 UTC | May 29, 20:45 UTC | 40m |
| 2026-05-28 | JCO1 | - | May 28, 22:35 UTC | May 29, 05:10 UTC | 6h 35m |
| 2026-05-28 | JCO1 | - | May 28, 19:00 UTC | May 28, 20:30 UTC | 1h 30m |
| 2026-05-25 | JCO1 | - | May 25, 06:55 UTC | May 25, 08:25 UTC | 1h 30m |
| 2026-05-25 | JCO1 | - | May 25, 01:55 UTC | May 25, 05:55 UTC | 4h 0m |
| 2026-05-24 | JCO1 | - | May 24, 21:15 UTC | May 24, 21:25 UTC | 10m |
| 2026-05-23 | JCO1 | - | May 23, 21:15 UTC | May 24, 05:50 UTC | 8h 35m |
| 2026-05-14 | JCO1 | - | May 14, 12:15 UTC | May 14, 13:35 UTC | 1h 20m |
| 2026-05-14 | JCO1 | - | May 14, 04:00 UTC | May 14, 05:55 UTC | 1h 55m |
| 2026-05-10 | JCO1 | - | May 10, 17:05 UTC | May 11, 01:50 UTC | 8h 45m |
| 2026-05-07 | JCO3 | - | May 7, 22:50 UTC | May 8, 05:09 UTC | 6h 20m |
| 2026-05-07 | JCO3 | - | May 7, 20:00 UTC | May 7, 21:35 UTC | 1h 35m |
| 2026-05-05 | JCO1 | - | May 5, 13:00 UTC | May 5, 14:40 UTC | 1h 40m |
| 2026-05-05 | JCO1 | - | May 5, 10:15 UTC | May 5, 11:45 UTC | 1h 30m |
| 2026-05-03 | JCO1 | BED → LTN | May 3, 03:25 UTC | May 3, 09:15 UTC | 5h 49m |
| 2026-05-02 | JCO1 | - | May 2, 17:25 UTC | May 2, 19:55 UTC | 2h 30m |
| 2026-04-30 | JCO1 | - | Apr 30, 15:50 UTC | Apr 30, 18:40 UTC | 2h 50m |
| 2026-04-28 | JCO1 | - | Apr 28, 12:25 UTC | Apr 28, 18:30 UTC | 6h 5m |
| 2026-04-24 | JCO1 | - | Apr 24, 01:10 UTC | Apr 24, 07:30 UTC | 6h 20m |
| 2026-04-23 | JCO1 | - | Apr 23, 15:05 UTC | Apr 23, 17:40 UTC | 2h 34m |
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-LOBX page for operator, model, and routing details .