sensors Mode-S transponder
A2672A
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N254JH · operated by MHM LOGISTICS LLC
- Hex
- A2672A
- Octal
- 50463452
- Decimal
- 10,643,242
- Country
- US
- Tail
- N254JH
- Type
- H25B
- Flights observed
- 51
- Distinct callsigns
- 2
- Country
- US
- Last broadcast
- Jul 26, 18:05 UTC
Last known position
Country allocation
The ICAO 24-bit address A2672A falls within the block assigned to United States (US) by ICAO Annex 10, Volume III. Every aircraft registered in United States 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-26 | N254JH | - | Jul 26, 17:40 UTC | Jul 26, 18:05 UTC | 25m |
| 2026-07-26 | N254JH | - | Jul 26, 14:20 UTC | Jul 26, 16:50 UTC | 2h 30m |
| 2026-07-26 | N254JH | - | Jul 26, 12:40 UTC | Jul 26, 13:15 UTC | 35m |
| 2026-07-24 | FFL691 | - | Jul 24, 16:30 UTC | Jul 24, 17:45 UTC | 1h 15m |
| 2026-07-24 | FFL691 | - | Jul 24, 14:10 UTC | Jul 24, 15:45 UTC | 1h 35m |
| 2026-07-20 | FFL691 | - | Jul 20, 17:45 UTC | Jul 20, 19:50 UTC | 2h 5m |
| 2026-07-20 | FFL691 | - | Jul 20, 16:25 UTC | Jul 20, 17:00 UTC | 35m |
| 2026-07-19 | FFL691 | - | Jul 19, 15:10 UTC | Jul 19, 18:35 UTC | 3h 25m |
| 2026-07-17 | FFL691 | - | Jul 17, 17:20 UTC | Jul 17, 20:40 UTC | 3h 20m |
| 2026-07-17 | FFL691 | - | Jul 17, 00:25 UTC | Jul 17, 01:15 UTC | 50m |
| 2026-07-16 | FFL691 | - | Jul 16, 19:55 UTC | Jul 16, 20:45 UTC | 50m |
| 2026-07-14 | FFL691 | - | Jul 14, 16:20 UTC | Jul 14, 17:10 UTC | 50m |
| 2026-07-14 | FFL691 | - | Jul 14, 12:05 UTC | Jul 14, 12:40 UTC | 35m |
| 2026-07-12 | FFL691 | - | Jul 12, 22:55 UTC | Jul 12, 23:25 UTC | 30m |
| 2026-07-12 | FFL691 | - | Jul 12, 19:25 UTC | Jul 12, 22:25 UTC | 3h 0m |
| 2026-07-07 | FFL691 | - | Jul 7, 18:30 UTC | Jul 7, 21:30 UTC | 3h 0m |
| 2026-07-07 | FFL691 | - | Jul 7, 16:15 UTC | Jul 7, 16:55 UTC | 40m |
| 2026-06-29 | FFL691 | - | Jun 29, 19:00 UTC | Jun 29, 20:24 UTC | 1h 25m |
| 2026-06-25 | FFL691 | - | Jun 25, 15:20 UTC | Jun 25, 16:55 UTC | 1h 35m |
| 2026-06-15 | FFL691 | - | Jun 15, 22:35 UTC | Jun 16, 01:00 UTC | 2h 25m |
| 2026-06-13 | FFL691 | - | Jun 13, 20:25 UTC | Jun 13, 23:10 UTC | 2h 45m |
| 2026-06-12 | FFL691 | - | Jun 12, 15:55 UTC | Jun 12, 17:25 UTC | 1h 30m |
| 2026-05-30 | FFL691 | - | May 30, 00:20 UTC | May 30, 03:10 UTC | 2h 50m |
| 2026-05-29 | FFL691 | - | May 29, 20:35 UTC | May 29, 23:40 UTC | 3h 5m |
| 2026-05-25 | FFL691 | - | May 25, 18:10 UTC | May 25, 21:35 UTC | 3h 24m |
| 2026-05-25 | FFL691 | - | May 25, 15:50 UTC | May 25, 16:30 UTC | 40m |
| 2026-05-17 | FFL691 | - | May 17, 17:55 UTC | May 17, 20:01 UTC | 2h 5m |
| 2026-05-15 | FFL691 | - | May 15, 16:40 UTC | May 15, 17:40 UTC | 1h 0m |
| 2026-05-13 | FFL691 | - | May 13, 21:25 UTC | May 13, 23:20 UTC | 1h 55m |
| 2026-05-10 | FFL691 | - | May 10, 19:24 UTC | May 10, 22:05 UTC | 2h 40m |
| 2026-05-10 | N254JH | - | May 10, 17:10 UTC | May 10, 18:35 UTC | 1h 25m |
| 2026-05-06 | N254JH | - | May 6, 16:45 UTC | May 6, 18:45 UTC | 1h 59m |
| 2026-05-06 | FFL691 | - | May 6, 15:20 UTC | May 6, 16:10 UTC | 50m |
| 2026-05-06 | FFL691 | - | May 6, 14:00 UTC | May 6, 14:30 UTC | 30m |
| 2026-05-03 | FFL691 | - | May 3, 14:15 UTC | May 3, 16:09 UTC | 1h 55m |
| 2026-05-01 | FFL691 | - | May 1, 17:10 UTC | May 1, 18:45 UTC | 1h 35m |
| 2026-04-26 | FFL691 | - | Apr 26, 16:20 UTC | Apr 26, 17:00 UTC | 40m |
| 2026-04-24 | FFL691 | - | Apr 24, 15:15 UTC | Apr 24, 16:00 UTC | 45m |
| 2026-04-21 | FFL691 | - | Apr 21, 18:15 UTC | Apr 21, 20:20 UTC | 2h 5m |
| 2026-04-21 | FFL691 | - | Apr 21, 12:50 UTC | Apr 21, 14:50 UTC | 2h 0m |
| 2026-04-19 | N254JH | - | Apr 19, 20:35 UTC | Apr 19, 21:40 UTC | 1h 5m |
| 2026-04-19 | N254JH | - | Apr 19, 17:55 UTC | Apr 19, 20:00 UTC | 2h 5m |
| 2026-04-19 | N254JH | - | Apr 19, 15:55 UTC | Apr 19, 16:10 UTC | 15m |
| 2026-04-15 | N254JH | - | Apr 15, 17:55 UTC | Apr 15, 18:05 UTC | 10m |
| 2026-04-15 | N254JH | - | Apr 15, 15:05 UTC | Apr 15, 16:25 UTC | 1h 20m |
| 2026-04-15 | N254JH | - | Apr 15, 13:45 UTC | Apr 15, 14:55 UTC | 1h 9m |
| 2026-04-14 | FFL691 | - | Apr 14, 20:55 UTC | Apr 14, 21:45 UTC | 50m |
| 2026-04-14 | FFL691 | - | Apr 14, 19:30 UTC | Apr 14, 20:20 UTC | 50m |
| 2026-04-14 | FFL691 | - | Apr 14, 14:05 UTC | Apr 14, 14:45 UTC | 40m |
| 2026-04-14 | FFL691 | - | Apr 14, 12:50 UTC | Apr 14, 13:25 UTC | 35m |
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 N254JH page for operator, model, and routing details .