sensors Mode-S transponder
485920
ICAO 24-bit transponder address · allocated to Netherlands
Currently assigned to PH-GOV · BOEING 737-700 · operated by Government of the Netherlands
- Hex
- 485920
- Octal
- 22054440
- Decimal
- 4,741,408
- Country
- NL
- Tail
- PH-GOV
- Type
- B737
- Flights observed
- 54
- Distinct callsigns
- 1
- Country
- NL
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 485920 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 |
|---|---|---|---|
| PHGOV | - | 54 | 2026-07-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | PHGOV | - | Jul 14, 12:45 UTC | Jul 14, 13:35 UTC | 50m |
| 2026-07-13 | PHGOV | - | Jul 13, 11:05 UTC | Jul 13, 12:00 UTC | 55m |
| 2026-07-10 | PHGOV | - | Jul 10, 19:15 UTC | Jul 10, 22:25 UTC | 3h 11m |
| 2026-07-10 | PHGOV | AMS → ATH | Jul 10, 15:15 UTC | Jul 10, 18:00 UTC | 2h 45m |
| 2026-07-08 | PHGOV | - | Jul 8, 15:30 UTC | Jul 8, 18:45 UTC | 3h 15m |
| 2026-07-07 | PHGOV | - | Jul 7, 05:55 UTC | Jul 7, 08:35 UTC | 2h 40m |
| 2026-06-30 | PHGOV | - | Jun 30, 10:45 UTC | Jun 30, 13:00 UTC | 2h 15m |
| 2026-06-30 | PHGOV | - | Jun 30, 03:40 UTC | Jun 30, 05:25 UTC | 1h 45m |
| 2026-06-25 | PHGOV | - | Jun 25, 17:05 UTC | Jun 25, 18:29 UTC | 1h 25m |
| 2026-06-25 | PHGOV | - | Jun 25, 14:20 UTC | Jun 25, 15:34 UTC | 1h 15m |
| 2026-06-24 | PHGOV | LCA → AMS | Jun 24, 20:24 UTC | Jun 25, 00:35 UTC | 4h 10m |
| 2026-06-24 | PHGOV | - | Jun 24, 14:50 UTC | Jun 24, 18:50 UTC | 4h 0m |
| 2026-06-24 | PHGOV | - | Jun 24, 11:24 UTC | Jun 24, 12:44 UTC | 1h 20m |
| 2026-06-24 | PHGOV | - | Jun 24, 01:49 UTC | Jun 24, 09:49 UTC | 8h 0m |
| 2026-06-22 | PHGOV | AMS → IAD | Jun 22, 08:15 UTC | Jun 22, 16:29 UTC | 8h 15m |
| 2026-06-21 | PHGOV | - | Jun 21, 03:19 UTC | Jun 21, 11:40 UTC | 8h 20m |
| 2026-06-20 | PHGOV | - | Jun 20, 21:10 UTC | Jun 20, 22:39 UTC | 1h 30m |
| 2026-06-19 | PHGOV | - | Jun 19, 16:39 UTC | Jun 20, 03:04 UTC | 10h 25m |
| 2026-06-16 | PHGOV | - | Jun 16, 13:04 UTC | Jun 16, 14:00 UTC | 55m |
| 2026-06-15 | PHGOV | - | Jun 15, 15:25 UTC | Jun 15, 16:09 UTC | 45m |
| 2026-06-08 | PHGOV | - | Jun 8, 14:00 UTC | Jun 8, 15:55 UTC | 1h 55m |
| 2026-06-07 | PHGOV | - | Jun 7, 17:55 UTC | Jun 7, 19:35 UTC | 1h 40m |
| 2026-06-05 | PHGOV | - | Jun 5, 15:10 UTC | Jun 5, 17:20 UTC | 2h 10m |
| 2026-06-05 | PHGOV | - | Jun 5, 13:40 UTC | Jun 5, 13:50 UTC | 10m |
| 2026-06-05 | PHGOV | - | Jun 5, 08:10 UTC | Jun 5, 08:25 UTC | 15m |
| 2026-06-05 | PHGOV | - | Jun 5, 05:10 UTC | Jun 5, 07:15 UTC | 2h 5m |
| 2026-06-03 | PHGOV | - | Jun 3, 19:30 UTC | Jun 3, 20:15 UTC | 45m |
| 2026-06-03 | PHGOV | - | Jun 3, 17:10 UTC | Jun 3, 18:45 UTC | 1h 35m |
| 2026-06-03 | PHGOV | - | Jun 3, 11:00 UTC | Jun 3, 12:15 UTC | 1h 15m |
| 2026-06-02 | PHGOV | - | Jun 2, 13:20 UTC | Jun 2, 16:00 UTC | 2h 40m |
| 2026-05-28 | PHGOV | - | May 28, 13:40 UTC | May 28, 17:55 UTC | 4h 15m |
| 2026-05-27 | PHGOV | - | May 27, 09:10 UTC | May 27, 13:00 UTC | 3h 50m |
| 2026-05-14 | PHGOV | - | May 14, 22:30 UTC | May 15, 07:20 UTC | 8h 50m |
| 2026-05-13 | PHGOV | - | May 13, 19:45 UTC | May 13, 19:55 UTC | 10m |
| 2026-05-12 | PHGOV | - | May 12, 20:50 UTC | May 12, 21:10 UTC | 20m |
| 2026-05-11 | PHGOV | - | May 11, 21:10 UTC | May 11, 21:30 UTC | 20m |
| 2026-05-08 | PHGOV | - | May 8, 17:05 UTC | May 8, 18:50 UTC | 1h 45m |
| 2026-05-07 | PHGOV | VCE → AMS | May 7, 08:30 UTC | May 7, 10:15 UTC | 1h 45m |
| 2026-05-06 | PHGOV | AMS → VCE | May 6, 10:10 UTC | May 6, 11:40 UTC | 1h 30m |
| 2026-05-04 | PHGOV | - | May 4, 15:30 UTC | May 4, 17:15 UTC | 1h 45m |
| 2026-05-03 | PHGOV | - | May 3, 13:45 UTC | May 3, 15:25 UTC | 1h 40m |
| 2026-04-24 | PHGOV | - | Apr 24, 13:05 UTC | Apr 24, 17:25 UTC | 4h 20m |
| 2026-04-23 | PHGOV | - | Apr 23, 11:01 UTC | Apr 23, 15:00 UTC | 4h 0m |
| 2026-04-22 | PHGOV | - | Apr 22, 14:30 UTC | Apr 23, 02:00 UTC | 11h 30m |
| 2026-04-21 | PHGOV | - | Apr 21, 12:10 UTC | Apr 21, 14:20 UTC | 2h 10m |
| 2026-04-21 | PHGOV | - | Apr 21, 09:55 UTC | Apr 21, 10:30 UTC | 35m |
| 2026-04-20 | PHGOV | - | Apr 20, 15:00 UTC | Apr 20, 15:45 UTC | 45m |
| 2026-04-19 | PHGOV | AMS → VIY | Apr 19, 16:50 UTC | Apr 19, 17:55 UTC | 1h 5m |
| 2026-04-16 | PHGOV | - | Apr 16, 03:14 UTC | Apr 16, 04:40 UTC | 1h 25m |
| 2026-04-15 | PHGOV | - | Apr 15, 20:00 UTC | Apr 15, 20:35 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 PH-GOV page for operator, model, and routing details .