sensors Mode-S transponder
48DA43
ICAO 24-bit transponder address · allocated to Poland
Currently assigned to 633 · MIL Mi-8/9/17/19/171/172
- Hex
- 48DA43
- Octal
- 22155103
- Decimal
- 4,774,467
- Country
- PL
- Tail
- 633
- Type
- MI8
- Flights observed
- 77
- Distinct callsigns
- 1
- Country
- PL
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 48DA43 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 |
|---|---|---|---|
| PLF633 | - | 77 | 2026-07-15 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-15 | PLF633 | - | Jul 15, 21:10 UTC | Jul 15, 21:50 UTC | 40m |
| 2026-07-15 | PLF633 | - | Jul 15, 19:10 UTC | Jul 15, 20:15 UTC | 1h 5m |
| 2026-07-15 | PLF633 | - | Jul 15, 18:15 UTC | Jul 15, 18:35 UTC | 20m |
| 2026-07-15 | PLF633 | - | Jul 15, 14:55 UTC | Jul 15, 16:35 UTC | 1h 40m |
| 2026-07-15 | PLF633 | - | Jul 15, 11:55 UTC | Jul 15, 12:25 UTC | 30m |
| 2026-07-15 | PLF633 | - | Jul 15, 10:50 UTC | Jul 15, 11:00 UTC | 10m |
| 2026-07-15 | PLF633 | - | Jul 15, 07:15 UTC | Jul 15, 07:40 UTC | 25m |
| 2026-07-14 | PLF633 | - | Jul 14, 22:15 UTC | Jul 15, 00:00 UTC | 1h 44m |
| 2026-07-14 | PLF633 | - | Jul 14, 19:05 UTC | Jul 14, 21:15 UTC | 2h 10m |
| 2026-07-10 | PLF633 | - | Jul 10, 11:25 UTC | Jul 10, 11:50 UTC | 25m |
| 2026-07-10 | PLF633 | - | Jul 10, 07:15 UTC | Jul 10, 08:00 UTC | 45m |
| 2026-07-09 | PLF633 | - | Jul 9, 21:10 UTC | Jul 9, 21:50 UTC | 40m |
| 2026-07-09 | PLF633 | - | Jul 9, 16:00 UTC | Jul 9, 16:25 UTC | 25m |
| 2026-07-09 | PLF633 | - | Jul 9, 13:55 UTC | Jul 9, 14:25 UTC | 30m |
| 2026-07-09 | PLF633 | - | Jul 9, 12:45 UTC | Jul 9, 13:05 UTC | 20m |
| 2026-07-09 | PLF633 | - | Jul 9, 10:40 UTC | Jul 9, 11:00 UTC | 20m |
| 2026-07-06 | PLF633 | - | Jul 6, 11:30 UTC | Jul 6, 12:50 UTC | 1h 20m |
| 2026-07-06 | PLF633 | - | Jul 6, 06:05 UTC | Jul 6, 06:55 UTC | 50m |
| 2026-07-06 | PLF633 | - | Jul 6, 05:05 UTC | Jul 6, 05:30 UTC | 25m |
| 2026-07-01 | PLF633 | - | Jul 1, 10:35 UTC | Jul 1, 11:15 UTC | 40m |
| 2026-07-01 | PLF633 | - | Jul 1, 07:10 UTC | Jul 1, 07:30 UTC | 20m |
| 2026-06-26 | PLF633 | - | Jun 26, 15:25 UTC | Jun 26, 15:54 UTC | 30m |
| 2026-06-26 | PLF633 | - | Jun 26, 14:19 UTC | Jun 26, 14:35 UTC | 15m |
| 2026-06-26 | PLF633 | - | Jun 26, 01:34 UTC | Jun 26, 03:05 UTC | 1h 30m |
| 2026-06-25 | PLF633 | - | Jun 25, 17:25 UTC | Jun 25, 17:44 UTC | 20m |
| 2026-06-25 | PLF633 | - | Jun 25, 16:24 UTC | Jun 25, 16:39 UTC | 15m |
| 2026-06-25 | PLF633 | - | Jun 25, 12:50 UTC | Jun 25, 13:00 UTC | 10m |
| 2026-06-25 | PLF633 | - | Jun 25, 07:39 UTC | Jun 25, 08:09 UTC | 30m |
| 2026-06-17 | PLF633 | - | Jun 17, 14:40 UTC | Jun 17, 15:15 UTC | 35m |
| 2026-06-17 | PLF633 | - | Jun 17, 05:25 UTC | Jun 17, 05:50 UTC | 25m |
| 2026-06-09 | PLF633 | - | Jun 9, 12:05 UTC | Jun 9, 12:40 UTC | 35m |
| 2026-06-09 | PLF633 | - | Jun 9, 10:45 UTC | Jun 9, 11:05 UTC | 20m |
| 2026-06-09 | PLF633 | WAW → WAW | Jun 9, 07:35 UTC | Jun 9, 09:40 UTC | 2h 5m |
| 2026-06-05 | PLF633 | - | Jun 5, 11:10 UTC | Jun 5, 11:30 UTC | 20m |
| 2026-06-05 | PLF633 | - | Jun 5, 07:00 UTC | Jun 5, 07:35 UTC | 35m |
| 2026-06-02 | PLF633 | - | Jun 2, 16:45 UTC | Jun 2, 17:10 UTC | 25m |
| 2026-06-02 | PLF633 | - | Jun 2, 12:10 UTC | Jun 2, 13:15 UTC | 1h 5m |
| 2026-05-29 | PLF633 | - | May 29, 14:50 UTC | May 29, 15:20 UTC | 30m |
| 2026-05-29 | PLF633 | - | May 29, 08:30 UTC | May 29, 08:55 UTC | 25m |
| 2026-05-28 | PLF633 | - | May 28, 10:20 UTC | May 28, 10:50 UTC | 30m |
| 2026-05-28 | PLF633 | - | May 28, 05:25 UTC | May 28, 05:50 UTC | 25m |
| 2026-05-26 | PLF633 | - | May 26, 11:00 UTC | May 26, 11:34 UTC | 35m |
| 2026-05-26 | PLF633 | - | May 26, 07:10 UTC | May 26, 07:34 UTC | 25m |
| 2026-05-20 | PLF633 | RZE → WAW | May 20, 10:25 UTC | May 20, 12:00 UTC | 1h 35m |
| 2026-05-19 | PLF633 | - | May 19, 16:45 UTC | May 19, 17:20 UTC | 35m |
| 2026-05-19 | PLF633 | - | May 19, 15:00 UTC | May 19, 15:20 UTC | 20m |
| 2026-05-19 | PLF633 | - | May 19, 09:30 UTC | May 19, 09:45 UTC | 15m |
| 2026-05-19 | PLF633 | - | May 19, 08:45 UTC | May 19, 09:00 UTC | 15m |
| 2026-05-15 | PLF633 | - | May 15, 10:00 UTC | May 15, 11:40 UTC | 1h 40m |
| 2026-05-15 | PLF633 | - | May 15, 06:45 UTC | May 15, 07:05 UTC | 20m |
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 633 page for operator, model, and routing details .