sensors Mode-S transponder
4AB5E6
ICAO 24-bit transponder address · allocated to Sweden
Currently assigned to SE-MOF · BEECHCRAFT Super King Air 350
- Hex
- 4AB5E6
- Octal
- 22532746
- Decimal
- 4,896,230
- Country
- SE
- Tail
- SE-MOF
- Type
- B350
- Flights observed
- 69
- Distinct callsigns
- 1
- Country
- SE
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 4AB5E6 falls within the block assigned to Sweden (SE) by ICAO Annex 10, Volume III. Every aircraft registered in Sweden 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 |
|---|---|---|---|
| JON09 | - | 69 | 2026-07-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-16 | JON09 | - | Jul 16, 14:35 UTC | Jul 16, 17:05 UTC | 2h 30m |
| 2026-07-16 | JON09 | BMA → IGS | Jul 16, 05:15 UTC | Jul 16, 08:00 UTC | 2h 45m |
| 2026-07-15 | JON09 | - | Jul 15, 09:50 UTC | Jul 15, 10:15 UTC | 25m |
| 2026-07-15 | JON09 | - | Jul 15, 08:20 UTC | Jul 15, 08:45 UTC | 25m |
| 2026-07-08 | JON09 | - | Jul 8, 09:20 UTC | Jul 8, 10:35 UTC | 1h 15m |
| 2026-07-08 | JON09 | - | Jul 8, 07:05 UTC | Jul 8, 08:20 UTC | 1h 15m |
| 2026-07-06 | JON09 | AGH → BMA | Jul 6, 17:30 UTC | Jul 6, 18:35 UTC | 1h 5m |
| 2026-07-06 | JON09 | - | Jul 6, 15:05 UTC | Jul 6, 16:55 UTC | 1h 50m |
| 2026-07-06 | JON09 | - | Jul 6, 07:40 UTC | Jul 6, 08:40 UTC | 1h 0m |
| 2026-07-06 | JON09 | - | Jul 6, 06:50 UTC | Jul 6, 07:10 UTC | 20m |
| 2026-07-06 | JON09 | - | Jul 6, 05:05 UTC | Jul 6, 06:05 UTC | 1h 0m |
| 2026-07-03 | JON09 | - | Jul 3, 17:15 UTC | Jul 3, 17:45 UTC | 30m |
| 2026-07-03 | JON09 | - | Jul 3, 15:40 UTC | Jul 3, 16:05 UTC | 25m |
| 2026-07-03 | JON09 | - | Jul 3, 12:35 UTC | Jul 3, 14:50 UTC | 2h 15m |
| 2026-07-01 | JON09 | - | Jul 1, 07:05 UTC | Jul 1, 08:00 UTC | 55m |
| 2026-07-01 | JON09 | - | Jul 1, 05:30 UTC | Jul 1, 06:30 UTC | 1h 0m |
| 2026-06-28 | JON09 | ARN → BMA | Jun 28, 10:10 UTC | Jun 28, 10:24 UTC | 15m |
| 2026-06-27 | JON09 | - | Jun 27, 18:24 UTC | Jun 27, 19:29 UTC | 1h 5m |
| 2026-06-27 | JON09 | - | Jun 27, 16:49 UTC | Jun 27, 17:44 UTC | 55m |
| 2026-06-25 | JON09 | - | Jun 25, 15:10 UTC | Jun 25, 15:44 UTC | 35m |
| 2026-06-25 | JON09 | - | Jun 25, 13:59 UTC | Jun 25, 14:24 UTC | 25m |
| 2026-06-24 | JON09 | - | Jun 24, 11:39 UTC | Jun 24, 12:34 UTC | 55m |
| 2026-06-23 | JON09 | - | Jun 23, 19:50 UTC | Jun 23, 20:44 UTC | 55m |
| 2026-06-23 | JON09 | - | Jun 23, 06:19 UTC | Jun 23, 06:49 UTC | 30m |
| 2026-06-23 | JON09 | - | Jun 23, 05:15 UTC | Jun 23, 05:45 UTC | 30m |
| 2026-06-22 | JON09 | - | Jun 22, 16:50 UTC | Jun 22, 17:04 UTC | 15m |
| 2026-06-17 | JON09 | NRK → BMA | Jun 17, 10:30 UTC | Jun 17, 10:55 UTC | 25m |
| 2026-06-17 | JON09 | - | Jun 17, 09:35 UTC | Jun 17, 09:55 UTC | 20m |
| 2026-06-17 | JON09 | - | Jun 17, 07:40 UTC | Jun 17, 08:00 UTC | 20m |
| 2026-06-17 | JON09 | - | Jun 17, 06:00 UTC | Jun 17, 06:25 UTC | 25m |
| 2026-06-14 | JON09 | - | Jun 14, 10:25 UTC | Jun 14, 11:30 UTC | 1h 5m |
| 2026-06-12 | JON09 | - | Jun 12, 09:20 UTC | Jun 12, 10:25 UTC | 1h 5m |
| 2026-06-11 | JON09 | - | Jun 11, 08:35 UTC | Jun 11, 09:35 UTC | 1h 0m |
| 2026-06-11 | JON09 | BMA → TLL | Jun 11, 06:15 UTC | Jun 11, 07:05 UTC | 50m |
| 2026-05-22 | JON09 | - | May 22, 07:40 UTC | May 22, 08:10 UTC | 30m |
| 2026-05-22 | JON09 | - | May 22, 06:40 UTC | May 22, 07:10 UTC | 30m |
| 2026-05-21 | JON09 | - | May 21, 10:45 UTC | May 21, 11:15 UTC | 30m |
| 2026-05-21 | JON09 | BMA → LPI | May 21, 09:45 UTC | May 21, 10:15 UTC | 30m |
| 2026-05-18 | JON09 | - | May 18, 13:30 UTC | May 18, 14:25 UTC | 55m |
| 2026-05-18 | JON09 | KRS → OSL | May 18, 12:10 UTC | May 18, 12:50 UTC | 40m |
| 2026-05-18 | JON09 | - | May 18, 07:05 UTC | May 18, 07:45 UTC | 40m |
| 2026-05-18 | JON09 | - | May 18, 05:20 UTC | May 18, 06:20 UTC | 1h 0m |
| 2026-05-15 | JON09 | - | May 15, 15:10 UTC | May 15, 15:40 UTC | 30m |
| 2026-05-15 | JON09 | - | May 15, 13:55 UTC | May 15, 14:20 UTC | 25m |
| 2026-05-15 | JON09 | - | May 15, 11:05 UTC | May 15, 11:30 UTC | 25m |
| 2026-05-15 | JON09 | - | May 15, 09:45 UTC | May 15, 10:10 UTC | 25m |
| 2026-05-12 | JON09 | - | May 12, 13:40 UTC | May 12, 14:00 UTC | 20m |
| 2026-05-12 | JON09 | - | May 12, 11:05 UTC | May 12, 13:10 UTC | 2h 5m |
| 2026-05-12 | JON09 | - | May 12, 07:15 UTC | May 12, 09:20 UTC | 2h 5m |
| 2026-05-07 | JON09 | - | May 7, 10:05 UTC | May 7, 12:25 UTC | 2h 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 SE-MOF page for operator, model, and routing details .