sensors Mode-S transponder
506E19
ICAO 24-bit transponder address · allocated to Slovenia
- Hex
- 506E19
- Octal
- 24067031
- Decimal
- 5,271,065
- Country
- SI
- Flights observed
- 27
- Distinct callsigns
- 11
- Country
- SI
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 506E19 falls within the block assigned to Slovenia (SI) by ICAO Annex 10, Volume III. Every aircraft registered in Slovenia 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 11 distinct
Recent flights last 27
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-20 | PUMA44 | - | Jul 20, 08:00 UTC | Jul 20, 10:20 UTC | 2h 20m |
| 2026-07-17 | PUMA23 | - | Jul 17, 06:45 UTC | Jul 17, 07:44 UTC | 1h 0m |
| 2026-07-07 | PUMA84 | - | Jul 7, 06:40 UTC | Jul 7, 09:55 UTC | 3h 15m |
| 2026-07-06 | PUMA23 | - | Jul 6, 10:45 UTC | Jul 6, 11:15 UTC | 30m |
| 2026-07-06 | PUMA84 | - | Jul 6, 06:35 UTC | Jul 6, 09:35 UTC | 3h 0m |
| 2026-07-03 | PUMA84 | - | Jul 3, 09:20 UTC | Jul 3, 10:15 UTC | 55m |
| 2026-07-03 | PUMA79 | - | Jul 3, 07:35 UTC | Jul 3, 08:35 UTC | 1h 0m |
| 2026-07-03 | PUMA79 | - | Jul 3, 06:50 UTC | Jul 3, 07:00 UTC | 10m |
| 2026-07-02 | PUMA84 | - | Jul 2, 15:55 UTC | Jul 2, 16:25 UTC | 30m |
| 2026-07-02 | PUMA84 | - | Jul 2, 14:10 UTC | Jul 2, 14:50 UTC | 40m |
| 2026-07-01 | PUMA79 | - | Jul 1, 09:20 UTC | Jul 1, 10:35 UTC | 1h 15m |
| 2026-07-01 | PUMA84 | - | Jul 1, 06:55 UTC | Jul 1, 08:25 UTC | 1h 30m |
| 2026-06-24 | PUMA27 | - | Jun 24, 16:45 UTC | Jun 24, 17:29 UTC | 45m |
| 2026-06-23 | PUMA27 | - | Jun 23, 07:55 UTC | Jun 23, 10:04 UTC | 2h 10m |
| 2026-06-22 | PUMA15 | - | Jun 22, 07:45 UTC | Jun 22, 08:19 UTC | 35m |
| 2026-06-22 | PUMA52 | - | Jun 22, 06:39 UTC | Jun 22, 07:04 UTC | 25m |
| 2026-06-19 | PUMA23 | - | Jun 19, 09:30 UTC | Jun 19, 09:59 UTC | 30m |
| 2026-06-19 | PUMA52 | - | Jun 19, 06:39 UTC | Jun 19, 08:54 UTC | 2h 15m |
| 2026-06-18 | PUMA41 | - | Jun 18, 19:30 UTC | Jun 18, 20:50 UTC | 1h 20m |
| 2026-06-18 | PUMA23 | - | Jun 18, 17:15 UTC | Jun 18, 17:40 UTC | 25m |
| 2026-06-18 | PUMA23 | - | Jun 18, 15:05 UTC | Jun 18, 15:30 UTC | 25m |
| 2026-05-13 | PUMA37 | - | May 13, 10:00 UTC | May 13, 10:40 UTC | 40m |
| 2026-05-08 | PUMA37 | - | May 8, 10:04 UTC | May 8, 10:35 UTC | 30m |
| 2026-05-08 | PUMA37 | - | May 8, 07:14 UTC | May 8, 09:14 UTC | 2h 0m |
| 2026-05-06 | PUMA39 | - | May 6, 08:01 UTC | May 6, 08:20 UTC | 20m |
| 2026-05-05 | PUMA37 | - | May 5, 07:50 UTC | May 5, 09:05 UTC | 1h 15m |
| 2026-04-17 | PUMA81 | - | Apr 17, 07:20 UTC | Apr 17, 08:30 UTC | 1h 10m |
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.