sensors Mode-S transponder
4D0257
ICAO 24-bit transponder address · allocated to Luxembourg
Currently assigned to LX-NJC · GULFSTREAM G500
- Hex
- 4D0257
- Octal
- 23201127
- Decimal
- 5,046,871
- Country
- LU
- Tail
- LX-NJC
- Type
- GA5C
- Flights observed
- 74
- Distinct callsigns
- 2
- Country
- LU
- Last broadcast
- 4d ago
Last known position
Country allocation
The ICAO 24-bit address 4D0257 falls within the block assigned to Luxembourg (LU) by ICAO Annex 10, Volume III. Every aircraft registered in Luxembourg 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-13 | PGQ01C | - | Jul 13, 09:20 UTC | Jul 13, 10:00 UTC | 40m |
| 2026-07-09 | PGQ01C | - | Jul 9, 22:55 UTC | Jul 10, 00:35 UTC | 1h 40m |
| 2026-07-06 | PGQ01C | - | Jul 6, 15:25 UTC | Jul 6, 16:55 UTC | 1h 30m |
| 2026-07-05 | PGQ01C | - | Jul 5, 11:55 UTC | Jul 5, 13:35 UTC | 1h 40m |
| 2026-07-02 | PGQ01 | - | Jul 2, 10:45 UTC | Jul 2, 11:45 UTC | 1h 0m |
| 2026-07-02 | PGQ01 | LBG → GVA | Jul 2, 08:40 UTC | Jul 2, 09:25 UTC | 45m |
| 2026-07-01 | PGQ01C | - | Jul 1, 08:25 UTC | Jul 1, 09:35 UTC | 1h 10m |
| 2026-07-01 | PGQ01C | - | Jul 1, 00:15 UTC | Jul 1, 07:00 UTC | 6h 45m |
| 2026-06-30 | PGQ01C | NTR → TEB | Jun 30, 05:45 UTC | Jun 30, 09:15 UTC | 3h 30m |
| 2026-06-29 | PGQ01C | - | Jun 29, 12:55 UTC | Jun 29, 16:15 UTC | 3h 20m |
| 2026-06-28 | PGQ01C | - | Jun 28, 18:05 UTC | Jun 28, 18:29 UTC | 25m |
| 2026-06-28 | PGQ01C | - | Jun 28, 08:29 UTC | Jun 28, 16:39 UTC | 8h 10m |
| 2026-06-27 | PGQ01C | - | Jun 27, 06:19 UTC | Jun 27, 07:24 UTC | 1h 5m |
| 2026-06-26 | PGQ01C | TEB → CUF | Jun 26, 22:40 UTC | Jun 27, 05:19 UTC | 6h 40m |
| 2026-06-24 | PGQ01C | IAD → TEB | Jun 24, 21:29 UTC | Jun 24, 22:19 UTC | 50m |
| 2026-06-23 | PGQ01C | - | Jun 23, 16:44 UTC | Jun 24, 00:49 UTC | 8h 5m |
| 2026-06-22 | PGQ01C | - | Jun 22, 15:54 UTC | Jun 22, 16:20 UTC | 25m |
| 2026-06-22 | PGQ01 | LUX → GVA | Jun 22, 13:25 UTC | Jun 22, 14:10 UTC | 45m |
| 2026-06-22 | PGQ01 | - | Jun 22, 07:25 UTC | Jun 22, 08:00 UTC | 35m |
| 2026-06-21 | PGQ01 | - | Jun 21, 15:05 UTC | Jun 21, 15:44 UTC | 40m |
| 2026-06-19 | PGQ01C | MLA → LBG | Jun 19, 11:39 UTC | Jun 19, 13:44 UTC | 2h 5m |
| 2026-06-19 | PGQ01C | - | Jun 19, 06:39 UTC | Jun 19, 08:44 UTC | 2h 5m |
| 2026-06-18 | PGQ01C | PRG → LBG | Jun 18, 11:25 UTC | Jun 18, 12:35 UTC | 1h 10m |
| 2026-06-18 | PGQ01C | - | Jun 18, 07:20 UTC | Jun 18, 08:35 UTC | 1h 15m |
| 2026-06-17 | PGQ01C | BUD → LBG | Jun 17, 14:50 UTC | Jun 17, 16:30 UTC | 1h 40m |
| 2026-06-17 | PGQ01C | - | Jun 17, 08:40 UTC | Jun 17, 10:10 UTC | 1h 30m |
| 2026-06-16 | PGQ01C | - | Jun 16, 13:00 UTC | Jun 16, 14:05 UTC | 1h 5m |
| 2026-06-16 | PGQ01C | - | Jun 16, 11:15 UTC | Jun 16, 12:20 UTC | 1h 5m |
| 2026-06-12 | PGQ01C | - | Jun 12, 22:35 UTC | Jun 13, 05:20 UTC | 6h 45m |
| 2026-06-11 | PGQ01C | - | Jun 11, 18:50 UTC | Jun 12, 02:10 UTC | 7h 21m |
| 2026-06-10 | PGQ01C | - | Jun 10, 18:20 UTC | Jun 10, 19:25 UTC | 1h 5m |
| 2026-06-06 | PGQ01C | - | Jun 6, 07:55 UTC | Jun 6, 09:04 UTC | 1h 10m |
| 2026-06-03 | PGQ01C | - | Jun 3, 14:25 UTC | Jun 3, 15:10 UTC | 45m |
| 2026-06-01 | PGQ01 | - | Jun 1, 10:40 UTC | Jun 1, 11:20 UTC | 40m |
| 2026-05-30 | PGQ01C | BUD → LBG | May 30, 23:00 UTC | May 31, 00:35 UTC | 1h 35m |
| 2026-05-30 | PGQ01C | - | May 30, 18:20 UTC | May 30, 19:55 UTC | 1h 35m |
| 2026-05-26 | PGQ01 | - | May 26, 10:14 UTC | May 26, 12:35 UTC | 2h 20m |
| 2026-05-25 | PGQ01 | - | May 25, 16:20 UTC | May 26, 12:35 UTC | 20h 15m |
| 2026-05-25 | PGQ01 | - | May 25, 15:15 UTC | May 26, 12:35 UTC | 21h 19m |
| 2026-05-25 | PGQ01 | - | May 25, 11:50 UTC | May 26, 11:44 UTC | 23h 54m |
| 2026-05-25 | PGQ01C | - | May 25, 11:05 UTC | May 25, 16:25 UTC | 5h 20m |
| 2026-05-21 | PGQ01C | - | May 21, 20:35 UTC | May 22, 04:50 UTC | 8h 15m |
| 2026-05-17 | PGQ01C | - | May 17, 06:10 UTC | May 17, 12:55 UTC | 6h 45m |
| 2026-05-16 | PGQ01C | - | May 16, 08:01 UTC | May 16, 14:41 UTC | 6h 40m |
| 2026-05-13 | PGQ01 | - | May 13, 09:55 UTC | May 13, 12:15 UTC | 2h 20m |
| 2026-05-08 | PGQ01C | - | May 8, 17:10 UTC | May 8, 19:00 UTC | 1h 50m |
| 2026-05-06 | PGQ01C | - | May 6, 10:20 UTC | May 6, 12:15 UTC | 1h 55m |
| 2026-05-06 | PGQ01C | - | May 6, 06:50 UTC | May 6, 07:50 UTC | 1h 0m |
| 2026-05-05 | PGQ01C | - | May 5, 15:20 UTC | May 5, 16:30 UTC | 1h 10m |
| 2026-05-05 | PGQ01C | - | May 5, 05:35 UTC | May 5, 06:45 UTC | 1h 10m |
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 LX-NJC page for operator, model, and routing details .