sensors Mode-S transponder
48D982
ICAO 24-bit transponder address · allocated to Poland
Currently assigned to 0111 · BOEING 737-800
- Hex
- 48D982
- Octal
- 22154602
- Decimal
- 4,774,274
- Country
- PL
- Tail
- 0111
- Type
- B738
- Flights observed
- 68
- Distinct callsigns
- 3
- Country
- PL
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 48D982 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 3 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | PLF102 | ORY → WAW | Jul 14, 12:15 UTC | Jul 14, 14:00 UTC | 1h 45m |
| 2026-07-13 | PLF102 | WAW → ORY | Jul 13, 11:45 UTC | Jul 13, 14:00 UTC | 2h 15m |
| 2026-07-08 | PLF101 | - | Jul 8, 20:25 UTC | Jul 8, 20:40 UTC | 15m |
| 2026-07-08 | PLF101 | - | Jul 8, 18:30 UTC | Jul 8, 19:40 UTC | 1h 10m |
| 2026-07-07 | PLF101 | - | Jul 7, 09:20 UTC | Jul 7, 11:20 UTC | 2h 0m |
| 2026-07-06 | PLF102 | - | Jul 6, 11:20 UTC | Jul 6, 12:00 UTC | 40m |
| 2026-07-06 | PLF102 | WAW → BZG | Jul 6, 08:05 UTC | Jul 6, 08:45 UTC | 40m |
| 2026-06-30 | PLF101 | - | Jun 30, 12:05 UTC | Jun 30, 12:45 UTC | 40m |
| 2026-06-29 | PLF101 | POZ → WAW | Jun 29, 10:44 UTC | Jun 29, 11:25 UTC | 40m |
| 2026-06-28 | PLF101 | - | Jun 28, 11:55 UTC | Jun 28, 12:29 UTC | 35m |
| 2026-06-28 | PLF101 | - | Jun 28, 08:34 UTC | Jun 28, 09:10 UTC | 35m |
| 2026-06-26 | PLF101 | - | Jun 26, 16:05 UTC | Jun 26, 16:44 UTC | 40m |
| 2026-06-26 | PLF101 | - | Jun 26, 14:44 UTC | Jun 26, 15:20 UTC | 35m |
| 2026-06-24 | PLF101 | - | Jun 24, 13:00 UTC | Jun 24, 15:44 UTC | 2h 45m |
| 2026-06-22 | PLF101 | - | Jun 22, 16:34 UTC | Jun 22, 18:44 UTC | 2h 10m |
| 2026-06-17 | PLF101 | - | Jun 17, 13:00 UTC | Jun 17, 13:30 UTC | 30m |
| 2026-06-17 | PLF101 | - | Jun 17, 04:15 UTC | Jun 17, 12:10 UTC | 7h 55m |
| 2026-06-17 | PLF101 | TPA → IAD | Jun 17, 00:30 UTC | Jun 17, 02:35 UTC | 2h 5m |
| 2026-06-15 | PLF101 | IAD → TPA | Jun 15, 23:09 UTC | Jun 16, 01:10 UTC | 2h 0m |
| 2026-06-13 | PLF101 | - | Jun 13, 15:35 UTC | Jun 14, 01:15 UTC | 9h 40m |
| 2026-06-10 | PLF101 | - | Jun 10, 13:45 UTC | Jun 10, 14:15 UTC | 30m |
| 2026-06-10 | PLF101 | - | Jun 10, 10:20 UTC | Jun 10, 10:50 UTC | 30m |
| 2026-06-09 | PLF120 | - | Jun 9, 06:45 UTC | Jun 9, 07:30 UTC | 45m |
| 2026-06-08 | PLF120 | - | Jun 8, 08:00 UTC | Jun 8, 08:55 UTC | 55m |
| 2026-06-08 | PLF120 | - | Jun 8, 06:55 UTC | Jun 8, 07:25 UTC | 30m |
| 2026-06-06 | PLF101 | - | Jun 6, 13:30 UTC | Jun 6, 14:09 UTC | 40m |
| 2026-06-06 | PLF101 | - | Jun 6, 11:39 UTC | Jun 6, 12:20 UTC | 40m |
| 2026-06-05 | PLF101 | - | Jun 5, 16:25 UTC | Jun 5, 17:20 UTC | 55m |
| 2026-06-03 | PLF120 | WRO → WAW | Jun 3, 14:55 UTC | Jun 3, 15:30 UTC | 35m |
| 2026-06-03 | PLF120 | - | Jun 3, 00:00 UTC | Jun 3, 13:55 UTC | 13h 55m |
| 2026-06-01 | PLF120 | - | Jun 1, 07:40 UTC | Jun 1, 10:40 UTC | 3h 0m |
| 2026-06-01 | PLF120 | - | Jun 1, 06:10 UTC | Jun 1, 06:35 UTC | 25m |
| 2026-05-28 | PLF101 | - | May 28, 15:30 UTC | May 28, 17:20 UTC | 1h 50m |
| 2026-05-28 | PLF101 | - | May 28, 12:20 UTC | May 28, 14:15 UTC | 1h 55m |
| 2026-05-27 | PLF120 | - | May 27, 16:30 UTC | May 27, 23:20 UTC | 6h 50m |
| 2026-05-25 | PLF120 | - | May 25, 23:45 UTC | May 26, 00:35 UTC | 50m |
| 2026-05-25 | PLF120 | - | May 25, 10:40 UTC | May 25, 19:59 UTC | 9h 19m |
| 2026-05-25 | PLF120 | - | May 25, 08:10 UTC | May 25, 08:35 UTC | 25m |
| 2026-05-21 | PLF120 | - | May 21, 11:20 UTC | May 21, 11:55 UTC | 35m |
| 2026-05-21 | PLF120 | - | May 21, 05:45 UTC | May 21, 05:55 UTC | 10m |
| 2026-05-20 | PLF102 | - | May 20, 17:15 UTC | May 20, 17:55 UTC | 40m |
| 2026-05-20 | PLF102 | - | May 20, 12:30 UTC | May 20, 13:10 UTC | 40m |
| 2026-05-19 | PLF101 | - | May 19, 11:35 UTC | May 19, 12:35 UTC | 1h 0m |
| 2026-05-17 | PLF101 | - | May 17, 18:10 UTC | May 17, 20:05 UTC | 1h 55m |
| 2026-05-14 | PLF101 | - | May 14, 13:50 UTC | May 14, 15:10 UTC | 1h 20m |
| 2026-05-12 | PLF101 | - | May 12, 14:45 UTC | May 12, 15:10 UTC | 25m |
| 2026-05-12 | PLF101 | - | May 12, 11:00 UTC | May 12, 12:25 UTC | 1h 25m |
| 2026-05-08 | PLF101 | RZE → WAW | May 8, 15:45 UTC | May 8, 16:20 UTC | 35m |
| 2026-05-08 | PLF101 | WAW → RZE | May 8, 09:14 UTC | May 8, 09:54 UTC | 40m |
| 2026-05-07 | PLF101 | - | May 7, 14:30 UTC | May 7, 15:05 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 0111 page for operator, model, and routing details .