sensors Mode-S transponder
ACF1EC
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N933ML · BOMBARDIER BD-700 Global 5000/5500 · operated by TVPX AIRCRAFT SOLUTIONS INC TRUSTEE
- Hex
- ACF1EC
- Octal
- 53170754
- Decimal
- 11,334,124
- Country
- US
- Tail
- N933ML
- Type
- GL5T
- Flights observed
- 51
- Distinct callsigns
- 2
- Country
- US
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address ACF1EC 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-15 | MVJ93 | - | Jul 15, 02:25 UTC | Jul 15, 11:05 UTC | 8h 40m |
| 2026-07-15 | MVJ93 | - | Jul 15, 00:45 UTC | Jul 15, 01:05 UTC | 20m |
| 2026-07-14 | MVJ93 | HWD → PAE | Jul 14, 02:40 UTC | Jul 14, 04:05 UTC | 1h 25m |
| 2026-07-13 | MVJ93 | - | Jul 13, 20:40 UTC | Jul 14, 01:10 UTC | 4h 30m |
| 2026-07-05 | MVJ93 | - | Jul 5, 17:25 UTC | Jul 5, 17:55 UTC | 30m |
| 2026-07-03 | MVJ93 | - | Jul 3, 22:30 UTC | Jul 3, 23:25 UTC | 55m |
| 2026-07-03 | MVJ93 | - | Jul 3, 20:55 UTC | Jul 3, 21:35 UTC | 40m |
| 2026-07-03 | MVJ93 | COE → LAS | Jul 3, 17:00 UTC | Jul 3, 18:45 UTC | 1h 45m |
| 2026-06-30 | MVJ93 | VNY → COE | Jun 30, 17:25 UTC | Jun 30, 19:25 UTC | 2h 0m |
| 2026-06-29 | MVJ93 | VNY → VNY | Jun 29, 18:05 UTC | Jun 29, 18:19 UTC | 15m |
| 2026-06-29 | MVJ93 | VNY → VNY | Jun 29, 16:35 UTC | Jun 29, 16:50 UTC | 15m |
| 2026-06-28 | MVJ93 | - | Jun 28, 17:55 UTC | Jun 28, 19:49 UTC | 1h 55m |
| 2026-06-28 | MVJ93 | BUR → COE | Jun 28, 13:00 UTC | Jun 28, 14:54 UTC | 1h 55m |
| 2026-06-15 | MVJ93 | - | Jun 15, 05:35 UTC | Jun 15, 06:20 UTC | 45m |
| 2026-06-14 | MVJ93 | - | Jun 14, 23:59 UTC | Jun 15, 04:40 UTC | 4h 40m |
| 2026-06-14 | MVJ93 | - | Jun 14, 21:45 UTC | Jun 14, 22:50 UTC | 1h 5m |
| 2026-06-14 | MVJ93 | BUR → TPA | Jun 14, 05:35 UTC | Jun 14, 09:40 UTC | 4h 5m |
| 2026-06-02 | MVJ93 | - | Jun 2, 20:50 UTC | Jun 3, 01:40 UTC | 4h 50m |
| 2026-06-02 | MVJ93 | IAD → TPA | Jun 2, 17:25 UTC | Jun 2, 19:10 UTC | 1h 45m |
| 2026-06-01 | MVJ93 | - | Jun 1, 17:25 UTC | Jun 1, 21:50 UTC | 4h 25m |
| 2026-06-01 | MVJ93 | OAK → APC | Jun 1, 15:25 UTC | Jun 1, 15:40 UTC | 15m |
| 2026-05-31 | N933ML | - | May 31, 14:10 UTC | May 31, 20:25 UTC | 6h 15m |
| 2026-05-30 | N933ML | - | May 30, 17:50 UTC | May 31, 17:00 UTC | 23h 10m |
| 2026-05-28 | MVJ93 | - | May 28, 22:50 UTC | May 29, 03:40 UTC | 4h 50m |
| 2026-05-28 | MVJ93 | VNY → NUQ | May 28, 20:55 UTC | May 28, 21:45 UTC | 50m |
| 2026-05-10 | MVJ93 | OAK → VNY | May 10, 19:05 UTC | May 10, 20:00 UTC | 55m |
| 2026-05-09 | MVJ93 | - | May 9, 21:05 UTC | May 10, 02:50 UTC | 5h 45m |
| 2026-05-09 | MVJ93 | - | May 9, 12:50 UTC | May 9, 20:20 UTC | 7h 30m |
| 2026-05-09 | MVJ93 | - | May 9, 10:30 UTC | May 9, 10:55 UTC | 25m |
| 2026-05-04 | MVJ93 | - | May 4, 09:35 UTC | May 4, 10:10 UTC | 35m |
| 2026-05-04 | MVJ93 | BGR → VCE | May 4, 00:55 UTC | May 4, 08:00 UTC | 7h 5m |
| 2026-05-03 | MVJ93 | OAK → BGR | May 3, 18:50 UTC | May 3, 23:55 UTC | 5h 5m |
| 2026-05-02 | MVJ93 | BUR → OAK | May 2, 21:10 UTC | May 2, 21:55 UTC | 45m |
| 2026-04-30 | MVJ93 | - | Apr 30, 20:00 UTC | Apr 30, 20:30 UTC | 30m |
| 2026-04-30 | MVJ93 | - | Apr 30, 14:10 UTC | Apr 30, 19:00 UTC | 4h 50m |
| 2026-04-26 | MVJ93 | - | Apr 26, 16:10 UTC | Apr 26, 20:35 UTC | 4h 25m |
| 2026-04-24 | MVJ93 | - | Apr 24, 17:50 UTC | Apr 24, 18:20 UTC | 30m |
| 2026-04-24 | MVJ93 | - | Apr 24, 11:00 UTC | Apr 24, 16:10 UTC | 5h 10m |
| 2026-04-24 | MVJ93 | - | Apr 24, 08:45 UTC | Apr 24, 09:10 UTC | 25m |
| 2026-04-23 | MVJ93 | - | Apr 23, 02:35 UTC | Apr 23, 02:50 UTC | 15m |
| 2026-04-22 | MVJ93 | - | Apr 22, 20:25 UTC | Apr 23, 01:00 UTC | 4h 35m |
| 2026-04-22 | MVJ93 | HWD → VNY | Apr 22, 00:25 UTC | Apr 22, 01:20 UTC | 55m |
| 2026-04-20 | MVJ93 | - | Apr 20, 20:55 UTC | Apr 21, 00:25 UTC | 3h 30m |
| 2026-04-20 | MVJ93 | - | Apr 20, 14:40 UTC | Apr 20, 17:40 UTC | 3h 0m |
| 2026-04-20 | MVJ93 | OAK → HWD | Apr 20, 00:35 UTC | Apr 20, 01:15 UTC | 40m |
| 2026-04-19 | MVJ93 | BUR → OAK | Apr 19, 05:25 UTC | Apr 19, 06:15 UTC | 50m |
| 2026-04-18 | MVJ93 | OAK → BUR | Apr 18, 16:25 UTC | Apr 18, 17:15 UTC | 50m |
| 2026-04-18 | MVJ93 | VNY → OAK | Apr 18, 02:00 UTC | Apr 18, 02:50 UTC | 50m |
| 2026-04-16 | MVJ93 | - | Apr 16, 01:10 UTC | Apr 16, 03:04 UTC | 1h 55m |
| 2026-04-15 | MVJ93 | - | Apr 15, 23:10 UTC | Apr 16, 01:05 UTC | 1h 55m |
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 N933ML page for operator, model, and routing details .