sensors Mode-S transponder
424501
ICAO 24-bit transponder address · allocated to United Kingdom
Currently assigned to VQ-BHF · BOEING 737-800
- Hex
- 424501
- Octal
- 20442401
- Decimal
- 4,343,041
- Country
- GB
- Tail
- VQ-BHF
- Type
- B738
- Flights observed
- 79
- Distinct callsigns
- 20
- Country
- GB
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 424501 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| SMR275 | - | 21 | 2026-06-18 |
| SMR331 | Somon Air | 8 | 2026-06-22 |
| SMR231 | Somon Air | 8 | 2026-06-30 |
| SMR375 | Somon Air | 7 | 2026-04-24 |
| SMR337 | Somon Air | 5 | 2026-05-31 |
| SMR203 | Somon Air | 3 | 2026-05-10 |
| SMR105 | - | 3 | 2026-07-11 |
| SMR7426 | - | 2 | 2026-06-17 |
| SMR7408 | Somon Air | 2 | 2026-06-08 |
| SMR7404 | Somon Air | 2 | 2026-06-05 |
| SMR221 | - | 2 | 2026-06-26 |
| SMR213 | Somon Air | 2 | 2026-05-25 |
| SMR106 | - | 2 | 2026-07-14 |
| SMR8193 | - | 1 | 2026-07-10 |
| SMR7410 | Somon Air | 1 | 2026-06-09 |
| SMR7409 | - | 1 | 2026-06-08 |
| SMR376 | Somon Air | 1 | 2026-05-12 |
| SMR332 | Somon Air | 1 | 2026-04-30 |
| SMR232 | Somon Air | 1 | 2026-05-27 |
| SMR222 | - | 1 | 2026-04-15 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | SMR106 | - | Jul 14, 08:05 UTC | Jul 14, 08:15 UTC | 10m |
| 2026-07-11 | SMR106 | - | Jul 11, 22:10 UTC | Jul 12, 00:20 UTC | 2h 10m |
| 2026-07-11 | SMR105 | - | Jul 11, 16:35 UTC | Jul 11, 18:50 UTC | 2h 15m |
| 2026-07-10 | SMR8193 | - | Jul 10, 05:05 UTC | Jul 10, 17:40 UTC | 12h 35m |
| 2026-06-30 | SMR231 | DYU → LED | Jun 30, 21:35 UTC | Jun 30, 22:10 UTC | 35m |
| 2026-06-26 | SMR221 | - | Jun 26, 09:00 UTC | Jun 26, 12:29 UTC | 3h 30m |
| 2026-06-22 | SMR331 | DYU → ZIA | Jun 22, 21:49 UTC | Jun 22, 22:19 UTC | 30m |
| 2026-06-21 | SMR231 | DYU → LED | Jun 21, 20:54 UTC | Jun 21, 21:24 UTC | 30m |
| 2026-06-18 | SMR275 | - | Jun 18, 20:05 UTC | Jun 19, 12:39 UTC | 16h 34m |
| 2026-06-17 | SMR7426 | - | Jun 17, 05:45 UTC | Jun 17, 06:10 UTC | 25m |
| 2026-06-16 | SMR7426 | - | Jun 16, 22:35 UTC | Jun 17, 04:10 UTC | 5h 35m |
| 2026-06-15 | SMR275 | - | Jun 15, 20:00 UTC | Jun 15, 23:54 UTC | 3h 55m |
| 2026-06-14 | SMR275 | - | Jun 14, 23:54 UTC | Jun 15, 20:40 UTC | 20h 45m |
| 2026-06-14 | SMR275 | - | Jun 14, 20:20 UTC | Jun 15, 20:15 UTC | 23h 54m |
| 2026-06-14 | SMR275 | - | Jun 14, 20:00 UTC | Jun 15, 00:05 UTC | 4h 4m |
| 2026-06-13 | SMR331 | DYU → ZIA | Jun 13, 21:00 UTC | Jun 14, 20:15 UTC | 23h 15m |
| 2026-06-09 | SMR7410 | MED → DYU | Jun 9, 09:15 UTC | Jun 9, 09:45 UTC | 30m |
| 2026-06-08 | SMR7409 | - | Jun 8, 22:45 UTC | Jun 9, 07:30 UTC | 8h 45m |
| 2026-06-08 | SMR7408 | MED → DYU | Jun 8, 03:25 UTC | Jun 9, 01:45 UTC | 22h 20m |
| 2026-06-07 | SMR7408 | MED → DYU | Jun 7, 22:35 UTC | Jun 8, 04:00 UTC | 5h 25m |
| 2026-06-05 | SMR7404 | MED → DYU | Jun 5, 23:05 UTC | Jun 6, 19:19 UTC | 20h 15m |
| 2026-06-05 | SMR7404 | MED → DYU | Jun 5, 20:10 UTC | Jun 6, 08:30 UTC | 12h 20m |
| 2026-06-04 | SMR275 | LBD → ZIA | Jun 4, 20:20 UTC | Jun 5, 20:10 UTC | 23h 50m |
| 2026-06-04 | SMR275 | LBD → ZIA | Jun 4, 19:40 UTC | Jun 4, 20:25 UTC | 45m |
| 2026-06-02 | SMR231 | DYU → LED | Jun 2, 20:50 UTC | Jun 2, 21:20 UTC | 30m |
| 2026-06-02 | SMR231 | DYU → LED | Jun 2, 01:30 UTC | Jun 2, 21:20 UTC | 19h 50m |
| 2026-06-01 | SMR331 | DYU → ZIA | Jun 1, 06:20 UTC | Jun 2, 01:55 UTC | 19h 35m |
| 2026-06-01 | SMR331 | DYU → ZIA | Jun 1, 05:55 UTC | Jun 2, 01:55 UTC | 20h 0m |
| 2026-05-31 | SMR337 | DYU → ZIA | May 31, 16:05 UTC | Jun 1, 06:30 UTC | 14h 25m |
| 2026-05-29 | SMR231 | DYU → LED | May 29, 09:10 UTC | May 29, 21:40 UTC | 12h 30m |
| 2026-05-28 | SMR221 | DYU → OVB | May 28, 19:40 UTC | May 29, 09:35 UTC | 13h 55m |
| 2026-05-27 | SMR275 | LBD → ZIA | May 27, 21:55 UTC | May 28, 20:00 UTC | 22h 5m |
| 2026-05-27 | SMR275 | LBD → ZIA | May 27, 00:55 UTC | May 27, 18:10 UTC | 17h 15m |
| 2026-05-27 | SMR232 | LED → DYU | May 27, 00:04 UTC | May 27, 00:19 UTC | 15m |
| 2026-05-26 | SMR231 | DYU → LED | May 26, 21:55 UTC | May 26, 22:05 UTC | 10m |
| 2026-05-25 | SMR213 | DYU → KJA | May 25, 06:20 UTC | May 26, 01:05 UTC | 18h 44m |
| 2026-05-16 | SMR275 | LBD → ZIA | May 16, 17:35 UTC | May 16, 18:00 UTC | 25m |
| 2026-05-15 | SMR231 | DYU → LED | May 15, 20:55 UTC | May 16, 18:00 UTC | 21h 6m |
| 2026-05-14 | SMR275 | LBD → ZIA | May 14, 19:40 UTC | May 14, 20:05 UTC | 25m |
| 2026-05-13 | SMR275 | LBD → ZIA | May 13, 17:30 UTC | May 13, 18:10 UTC | 40m |
| 2026-05-12 | SMR376 | ZIA → LBD | May 12, 22:31 UTC | May 12, 22:55 UTC | 25m |
| 2026-05-11 | SMR110 | DEL → DYU | May 11, 11:05 UTC | May 11, 22:15 UTC | 11h 11m |
| 2026-05-10 | SMR109 | DYU → DEL | May 10, 20:05 UTC | May 11, 09:10 UTC | 13h 5m |
| 2026-05-10 | SMR203 | DYU → LED | May 10, 00:24 UTC | May 10, 20:30 UTC | 20h 5m |
| 2026-05-09 | SMR331 | DYU → ZIA | May 9, 20:34 UTC | May 10, 20:14 UTC | 23h 40m |
| 2026-05-07 | SMR203 | DYU → LED | May 7, 21:25 UTC | May 8, 10:04 UTC | 12h 40m |
| 2026-05-06 | SMR331 | DYU → ZIA | May 6, 09:40 UTC | May 6, 20:00 UTC | 10h 19m |
| 2026-05-04 | SMR275 | LBD → ZIA | May 4, 20:00 UTC | May 4, 20:45 UTC | 45m |
| 2026-05-03 | SMR275 | LBD → ZIA | May 3, 17:45 UTC | May 3, 18:25 UTC | 40m |
| 2026-05-02 | SMR275 | LBD → ZIA | May 2, 22:40 UTC | May 3, 18:25 UTC | 19h 44m |
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 VQ-BHF page for operator, model, and routing details .