sensors Mode-S transponder
A548E3
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N44GJ · GULFSTREAM 4 · operated by N44GJ LLC
- Hex
- A548E3
- Octal
- 51244343
- Decimal
- 10,832,099
- Country
- US
- Tail
- N44GJ
- Type
- GLF4
- Flights observed
- 58
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address A548E3 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| MVJ44 | - | 58 | 2026-07-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-08 | MVJ44 | VNY → TEB | Jul 8, 16:10 UTC | Jul 8, 20:50 UTC | 4h 40m |
| 2026-07-01 | MVJ44 | - | Jul 1, 16:50 UTC | Jul 1, 18:20 UTC | 1h 30m |
| 2026-06-28 | MVJ44 | - | Jun 28, 20:29 UTC | Jun 28, 21:45 UTC | 1h 15m |
| 2026-06-28 | MVJ44 | - | Jun 28, 14:59 UTC | Jun 28, 19:09 UTC | 4h 10m |
| 2026-06-27 | MVJ44 | - | Jun 27, 19:05 UTC | Jun 27, 19:29 UTC | 25m |
| 2026-06-26 | MVJ44 | - | Jun 26, 17:25 UTC | Jun 26, 20:40 UTC | 3h 15m |
| 2026-06-24 | MVJ44 | - | Jun 24, 21:24 UTC | Jun 24, 22:29 UTC | 1h 5m |
| 2026-06-24 | MVJ44 | - | Jun 24, 17:59 UTC | Jun 24, 19:24 UTC | 1h 25m |
| 2026-06-20 | MVJ44 | - | Jun 20, 17:44 UTC | Jun 20, 19:40 UTC | 1h 55m |
| 2026-06-20 | MVJ44 | CLD → OAK | Jun 20, 14:14 UTC | Jun 20, 15:19 UTC | 1h 5m |
| 2026-06-20 | MVJ44 | SMF → CLD | Jun 20, 01:05 UTC | Jun 20, 02:24 UTC | 1h 20m |
| 2026-06-19 | MVJ44 | - | Jun 19, 20:59 UTC | Jun 20, 00:14 UTC | 3h 15m |
| 2026-06-19 | MVJ44 | - | Jun 19, 17:29 UTC | Jun 19, 17:59 UTC | 30m |
| 2026-06-19 | MVJ44 | - | Jun 19, 02:35 UTC | Jun 19, 03:29 UTC | 55m |
| 2026-06-19 | MVJ44 | - | Jun 19, 00:40 UTC | Jun 19, 01:45 UTC | 1h 5m |
| 2026-06-18 | MVJ44 | - | Jun 18, 20:40 UTC | Jun 19, 00:00 UTC | 3h 20m |
| 2026-06-18 | MVJ44 | - | Jun 18, 18:25 UTC | Jun 18, 19:10 UTC | 45m |
| 2026-06-17 | MVJ44 | - | Jun 17, 22:50 UTC | Jun 17, 23:30 UTC | 40m |
| 2026-06-17 | MVJ44 | IAD → TEB | Jun 17, 20:45 UTC | Jun 17, 21:35 UTC | 50m |
| 2026-06-16 | MVJ44 | TEB → IAD | Jun 16, 22:00 UTC | Jun 16, 22:40 UTC | 40m |
| 2026-06-16 | MVJ44 | IAD → TEB | Jun 16, 16:55 UTC | Jun 16, 17:45 UTC | 50m |
| 2026-06-16 | MVJ44 | - | Jun 16, 14:50 UTC | Jun 16, 15:40 UTC | 50m |
| 2026-06-15 | MVJ44 | - | Jun 15, 23:09 UTC | Jun 16, 01:55 UTC | 2h 45m |
| 2026-06-15 | MVJ44 | - | Jun 15, 19:14 UTC | Jun 15, 22:05 UTC | 2h 50m |
| 2026-06-15 | MVJ44 | VNY → CLD | Jun 15, 16:15 UTC | Jun 15, 16:45 UTC | 30m |
| 2026-06-13 | MVJ44 | - | Jun 13, 20:35 UTC | Jun 13, 22:05 UTC | 1h 30m |
| 2026-06-13 | MVJ44 | VNY → SLC | Jun 13, 16:45 UTC | Jun 13, 18:05 UTC | 1h 20m |
| 2026-06-12 | MVJ44 | - | Jun 12, 03:20 UTC | Jun 12, 08:55 UTC | 5h 35m |
| 2026-06-12 | MVJ44 | - | Jun 12, 00:35 UTC | Jun 12, 01:10 UTC | 35m |
| 2026-06-07 | MVJ44 | IAD → TEB | Jun 7, 17:40 UTC | Jun 7, 19:10 UTC | 1h 30m |
| 2026-06-07 | MVJ44 | - | Jun 7, 13:45 UTC | Jun 7, 14:50 UTC | 1h 5m |
| 2026-06-07 | MVJ44 | - | Jun 7, 07:25 UTC | Jun 7, 12:15 UTC | 4h 50m |
| 2026-06-07 | MVJ44 | VNY → HWD | Jun 7, 03:35 UTC | Jun 7, 04:25 UTC | 50m |
| 2026-05-31 | MVJ44 | - | May 31, 13:05 UTC | May 31, 18:20 UTC | 5h 15m |
| 2026-05-28 | MVJ44 | - | May 28, 19:15 UTC | May 28, 21:25 UTC | 2h 10m |
| 2026-05-28 | MVJ44 | - | May 28, 14:10 UTC | May 28, 14:20 UTC | 10m |
| 2026-05-23 | MVJ44 | - | May 23, 16:50 UTC | May 23, 17:35 UTC | 45m |
| 2026-05-23 | MVJ44 | - | May 23, 11:00 UTC | May 23, 15:45 UTC | 4h 45m |
| 2026-05-20 | MVJ44 | VNY → TEB | May 20, 15:20 UTC | May 20, 19:50 UTC | 4h 30m |
| 2026-05-13 | MVJ44 | - | May 13, 18:15 UTC | May 13, 23:30 UTC | 5h 15m |
| 2026-05-06 | MVJ44 | - | May 6, 18:45 UTC | May 7, 00:10 UTC | 5h 25m |
| 2026-05-04 | MVJ44 | - | May 4, 14:40 UTC | May 4, 20:40 UTC | 6h 1m |
| 2026-04-29 | MVJ44 | - | Apr 29, 15:10 UTC | Apr 29, 19:35 UTC | 4h 25m |
| 2026-04-25 | MVJ44 | LAS → VNY | Apr 25, 18:55 UTC | Apr 25, 19:40 UTC | 45m |
| 2026-04-23 | MVJ44 | - | Apr 23, 21:35 UTC | Apr 23, 22:40 UTC | 1h 5m |
| 2026-04-21 | MVJ44 | - | Apr 21, 23:10 UTC | Apr 21, 23:45 UTC | 35m |
| 2026-04-18 | MVJ44 | - | Apr 18, 05:25 UTC | Apr 18, 06:05 UTC | 40m |
| 2026-04-18 | MVJ44 | - | Apr 18, 03:25 UTC | Apr 18, 04:35 UTC | 1h 10m |
| 2026-04-18 | MVJ44 | - | Apr 18, 01:25 UTC | Apr 18, 03:20 UTC | 1h 55m |
| 2026-04-17 | MVJ44 | - | Apr 17, 23:25 UTC | Apr 18, 01:20 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 N44GJ page for operator, model, and routing details .