sensors Mode-S transponder
48B9E6
ICAO 24-bit transponder address · allocated to Poland
Currently assigned to SP-OPG · PARTENAVIA P-68 Observer
- Hex
- 48B9E6
- Octal
- 22134746
- Decimal
- 4,766,182
- Country
- PL
- Tail
- SP-OPG
- Type
- P68
- Flights observed
- 51
- Distinct callsigns
- 1
- Country
- PL
- Last broadcast
- 5d ago
Last known position
Country allocation
The ICAO 24-bit address 48B9E6 falls within the block assigned to Poland (PL) by ICAO Annex 10, Volume III. Every aircraft registered in Poland 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 |
|---|---|---|---|
| SPOPG | - | 50 | 2026-07-21 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-21 | SPOPG | - | Jul 21, 08:00 UTC | Jul 21, 08:10 UTC | 10m |
| 2026-07-21 | SPOPG | - | Jul 21, 03:50 UTC | Jul 21, 07:20 UTC | 3h 30m |
| 2026-07-20 | SPOPG | - | Jul 20, 04:25 UTC | Jul 20, 08:45 UTC | 4h 20m |
| 2026-07-20 | - | - | Jul 20, 03:35 UTC | Jul 20, 03:45 UTC | 10m |
| 2026-07-20 | SPOPG | - | Jul 20, 02:15 UTC | Jul 20, 02:25 UTC | 10m |
| 2026-07-17 | SPOPG | - | Jul 17, 18:19 UTC | Jul 17, 22:35 UTC | 4h 15m |
| 2026-07-17 | SPOPG | - | Jul 17, 17:35 UTC | Jul 17, 17:44 UTC | 10m |
| 2026-07-17 | SPOPG | - | Jul 17, 16:04 UTC | Jul 17, 16:24 UTC | 20m |
| 2026-07-16 | SPOPG | - | Jul 16, 08:40 UTC | Jul 16, 09:05 UTC | 25m |
| 2026-07-15 | SPOPG | - | Jul 15, 13:30 UTC | Jul 15, 17:40 UTC | 4h 10m |
| 2026-07-14 | SPOPG | - | Jul 14, 22:15 UTC | Jul 14, 23:55 UTC | 1h 39m |
| 2026-07-14 | SPOPG | - | Jul 14, 15:10 UTC | Jul 14, 20:40 UTC | 5h 30m |
| 2026-07-12 | SPOPG | - | Jul 12, 20:05 UTC | Jul 12, 20:45 UTC | 40m |
| 2026-07-11 | SPOPG | - | Jul 11, 16:05 UTC | Jul 11, 21:45 UTC | 5h 40m |
| 2026-07-10 | SPOPG | - | Jul 10, 20:55 UTC | Jul 11, 03:01 UTC | 6h 5m |
| 2026-07-10 | SPOPG | - | Jul 10, 10:00 UTC | Jul 10, 10:20 UTC | 20m |
| 2026-07-08 | SPOPG | - | Jul 8, 19:20 UTC | Jul 8, 23:30 UTC | 4h 10m |
| 2026-07-08 | SPOPG | - | Jul 8, 17:55 UTC | Jul 8, 18:15 UTC | 20m |
| 2026-07-03 | SPOPG | - | Jul 3, 05:50 UTC | Jul 3, 06:15 UTC | 25m |
| 2026-07-01 | SPOPG | - | Jul 1, 00:45 UTC | Jul 1, 01:25 UTC | 40m |
| 2026-06-30 | SPOPG | - | Jun 30, 19:20 UTC | Jun 30, 23:45 UTC | 4h 25m |
| 2026-06-27 | SPOPG | - | Jun 27, 23:00 UTC | Jun 28, 03:29 UTC | 4h 30m |
| 2026-06-27 | SPOPG | - | Jun 27, 05:49 UTC | Jun 27, 08:49 UTC | 3h 0m |
| 2026-06-24 | SPOPG | - | Jun 24, 05:40 UTC | Jun 24, 10:39 UTC | 5h 0m |
| 2026-06-23 | SPOPG | - | Jun 23, 14:19 UTC | Jun 23, 16:50 UTC | 2h 30m |
| 2026-06-23 | SPOPG | - | Jun 23, 06:24 UTC | Jun 23, 08:25 UTC | 2h 0m |
| 2026-06-22 | SPOPG | - | Jun 22, 12:15 UTC | Jun 22, 15:35 UTC | 3h 20m |
| 2026-06-22 | SPOPG | - | Jun 22, 07:14 UTC | Jun 22, 10:44 UTC | 3h 30m |
| 2026-06-22 | SPOPG | - | Jun 22, 04:59 UTC | Jun 22, 06:35 UTC | 1h 35m |
| 2026-06-20 | SPOPG | - | Jun 20, 04:14 UTC | Jun 20, 09:24 UTC | 5h 10m |
| 2026-06-16 | SPOPG | - | Jun 16, 09:34 UTC | Jun 16, 10:09 UTC | 35m |
| 2026-06-01 | SPOPG | - | Jun 1, 13:35 UTC | Jun 1, 14:00 UTC | 25m |
| 2026-05-27 | SPOPG | - | May 27, 06:34 UTC | May 27, 07:50 UTC | 1h 16m |
| 2026-05-26 | SPOPG | - | May 26, 09:15 UTC | May 26, 13:54 UTC | 4h 40m |
| 2026-05-26 | SPOPG | - | May 26, 04:54 UTC | May 26, 08:19 UTC | 3h 25m |
| 2026-05-25 | SPOPG | - | May 25, 12:10 UTC | May 25, 13:55 UTC | 1h 45m |
| 2026-05-25 | SPOPG | - | May 25, 05:20 UTC | May 25, 10:50 UTC | 5h 30m |
| 2026-05-05 | SPOPG | - | May 5, 06:15 UTC | May 5, 07:20 UTC | 1h 5m |
| 2026-05-03 | SPOPG | - | May 3, 13:45 UTC | May 3, 15:15 UTC | 1h 30m |
| 2026-05-03 | SPOPG | - | May 3, 06:20 UTC | May 3, 12:55 UTC | 6h 35m |
| 2026-05-02 | SPOPG | - | May 2, 09:50 UTC | May 2, 16:15 UTC | 6h 25m |
| 2026-05-01 | SPOPG | - | May 1, 10:20 UTC | May 1, 10:45 UTC | 25m |
| 2026-05-01 | SPOPG | - | May 1, 06:30 UTC | May 1, 09:05 UTC | 2h 35m |
| 2026-04-30 | SPOPG | - | Apr 30, 13:05 UTC | Apr 30, 13:50 UTC | 45m |
| 2026-04-29 | SPOPG | - | Apr 29, 06:25 UTC | Apr 29, 09:35 UTC | 3h 11m |
| 2026-04-28 | SPOPG | - | Apr 28, 06:20 UTC | Apr 28, 12:55 UTC | 6h 35m |
| 2026-04-27 | SPOPG | - | Apr 27, 06:20 UTC | Apr 27, 11:25 UTC | 5h 5m |
| 2026-04-26 | SPOPG | - | Apr 26, 13:40 UTC | Apr 26, 16:50 UTC | 3h 10m |
| 2026-04-23 | SPOPG | - | Apr 23, 13:30 UTC | Apr 23, 13:50 UTC | 20m |
| 2026-04-23 | SPOPG | - | Apr 23, 09:20 UTC | Apr 23, 13:25 UTC | 4h 5m |
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 SP-OPG page for operator, model, and routing details .