sensors Mode-S transponder
48478E
ICAO 24-bit transponder address · allocated to Netherlands
Currently assigned to PH-957 · SZD-51 Junior
- Hex
- 48478E
- Octal
- 22043616
- Decimal
- 4,736,910
- Country
- NL
- Tail
- PH-957
- Type
- GLID
- Flights observed
- 58
- Distinct callsigns
- 1
- Country
- NL
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 48478E falls within the block assigned to Netherlands (NL) by ICAO Annex 10, Volume III. Every aircraft registered in Netherlands 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 |
|---|---|---|---|
| PH957 | - | 58 | 2026-07-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-12 | PH957 | - | Jul 12, 10:40 UTC | Jul 12, 14:10 UTC | 3h 30m |
| 2026-07-12 | PH957 | - | Jul 12, 09:50 UTC | Jul 12, 10:01 UTC | 10m |
| 2026-07-11 | PH957 | - | Jul 11, 10:40 UTC | Jul 11, 11:40 UTC | 1h 0m |
| 2026-07-10 | PH957 | - | Jul 10, 11:10 UTC | Jul 10, 15:30 UTC | 4h 20m |
| 2026-07-07 | PH957 | - | Jul 7, 14:30 UTC | Jul 7, 15:30 UTC | 1h 0m |
| 2026-07-07 | PH957 | - | Jul 7, 09:20 UTC | Jul 7, 13:35 UTC | 4h 15m |
| 2026-07-05 | PH957 | - | Jul 5, 12:25 UTC | Jul 5, 13:45 UTC | 1h 20m |
| 2026-07-05 | PH957 | - | Jul 5, 10:45 UTC | Jul 5, 11:15 UTC | 30m |
| 2026-07-05 | PH957 | - | Jul 5, 09:35 UTC | Jul 5, 09:45 UTC | 10m |
| 2026-07-04 | PH957 | - | Jul 4, 13:25 UTC | Jul 4, 15:05 UTC | 1h 40m |
| 2026-07-04 | PH957 | - | Jul 4, 10:30 UTC | Jul 4, 12:55 UTC | 2h 25m |
| 2026-06-30 | PH957 | - | Jun 30, 12:45 UTC | Jun 30, 15:15 UTC | 2h 30m |
| 2026-06-30 | PH957 | - | Jun 30, 10:20 UTC | Jun 30, 12:10 UTC | 1h 50m |
| 2026-06-28 | PH957 | - | Jun 28, 11:45 UTC | Jun 28, 15:44 UTC | 4h 0m |
| 2026-06-28 | PH957 | - | Jun 28, 10:35 UTC | Jun 28, 11:00 UTC | 25m |
| 2026-06-23 | PH957 | - | Jun 23, 13:50 UTC | Jun 23, 14:15 UTC | 25m |
| 2026-06-23 | PH957 | - | Jun 23, 12:49 UTC | Jun 23, 13:15 UTC | 25m |
| 2026-06-23 | PH957 | - | Jun 23, 09:34 UTC | Jun 23, 12:09 UTC | 2h 35m |
| 2026-06-20 | PH957 | - | Jun 20, 09:44 UTC | Jun 20, 15:04 UTC | 5h 20m |
| 2026-06-14 | PH957 | - | Jun 14, 12:25 UTC | Jun 14, 14:55 UTC | 2h 30m |
| 2026-06-14 | PH957 | - | Jun 14, 10:00 UTC | Jun 14, 10:20 UTC | 20m |
| 2026-06-13 | PH957 | - | Jun 13, 09:35 UTC | Jun 13, 13:45 UTC | 4h 10m |
| 2026-06-06 | PH957 | - | Jun 6, 09:50 UTC | Jun 6, 12:04 UTC | 2h 15m |
| 2026-05-31 | PH957 | - | May 31, 09:55 UTC | May 31, 13:00 UTC | 3h 5m |
| 2026-05-30 | PH957 | - | May 30, 13:40 UTC | May 30, 14:45 UTC | 1h 5m |
| 2026-05-30 | PH957 | - | May 30, 09:30 UTC | May 30, 12:00 UTC | 2h 30m |
| 2026-05-24 | PH957 | - | May 24, 12:40 UTC | May 24, 14:35 UTC | 1h 55m |
| 2026-05-24 | PH957 | - | May 24, 10:15 UTC | May 24, 12:05 UTC | 1h 50m |
| 2026-05-23 | PH957 | - | May 23, 08:55 UTC | May 23, 15:35 UTC | 6h 40m |
| 2026-05-16 | PH957 | - | May 16, 09:45 UTC | May 16, 11:25 UTC | 1h 40m |
| 2026-05-10 | PH957 | - | May 10, 11:50 UTC | May 10, 12:49 UTC | 1h 0m |
| 2026-05-09 | PH957 | - | May 9, 09:25 UTC | May 9, 16:35 UTC | 7h 10m |
| 2026-05-02 | PH957 | - | May 2, 09:55 UTC | May 2, 13:35 UTC | 3h 40m |
| 2026-05-01 | PH957 | - | May 1, 11:20 UTC | May 1, 14:30 UTC | 3h 10m |
| 2026-05-01 | PH957 | - | May 1, 08:30 UTC | May 1, 09:15 UTC | 45m |
| 2026-04-30 | PH957 | - | Apr 30, 11:40 UTC | Apr 30, 12:00 UTC | 21m |
| 2026-04-30 | PH957 | - | Apr 30, 10:00 UTC | Apr 30, 11:35 UTC | 1h 35m |
| 2026-04-29 | PH957 | - | Apr 29, 12:40 UTC | Apr 29, 13:35 UTC | 55m |
| 2026-04-29 | PH957 | - | Apr 29, 08:55 UTC | Apr 29, 11:00 UTC | 2h 6m |
| 2026-04-28 | PH957 | - | Apr 28, 12:35 UTC | Apr 28, 13:55 UTC | 1h 20m |
| 2026-04-28 | PH957 | - | Apr 28, 10:45 UTC | Apr 28, 11:25 UTC | 40m |
| 2026-04-27 | PH957 | - | Apr 27, 13:00 UTC | Apr 27, 13:45 UTC | 45m |
| 2026-04-27 | PH957 | - | Apr 27, 11:30 UTC | Apr 27, 11:55 UTC | 25m |
| 2026-04-27 | PH957 | - | Apr 27, 10:50 UTC | Apr 27, 11:00 UTC | 10m |
| 2026-04-26 | PH957 | - | Apr 26, 11:40 UTC | Apr 26, 14:50 UTC | 3h 10m |
| 2026-04-26 | PH957 | - | Apr 26, 10:15 UTC | Apr 26, 11:05 UTC | 50m |
| 2026-04-25 | PH957 | - | Apr 25, 09:15 UTC | Apr 25, 16:00 UTC | 6h 45m |
| 2026-04-21 | PH957 | - | Apr 21, 11:50 UTC | Apr 21, 15:05 UTC | 3h 15m |
| 2026-04-19 | PH957 | - | Apr 19, 13:40 UTC | Apr 19, 14:45 UTC | 1h 5m |
| 2026-04-19 | PH957 | - | Apr 19, 12:20 UTC | Apr 19, 13:05 UTC | 45m |
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 PH-957 page for operator, model, and routing details .