sensors Mode-S transponder
4A81F4
ICAO 24-bit transponder address · allocated to Sweden
Currently assigned to 100008 · SAAB 340
- Hex
- 4A81F4
- Octal
- 22500764
- Decimal
- 4,882,932
- Country
- SE
- Tail
- 100008
- Type
- SF34
- Flights observed
- 87
- Distinct callsigns
- 9
- Country
- SE
- Last broadcast
- 15d ago
Last known position
Country allocation
The ICAO 24-bit address 4A81F4 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 9 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-02 | SVF608 | - | Jul 2, 10:40 UTC | Jul 2, 13:05 UTC | 2h 25m |
| 2026-07-02 | SVF608 | - | Jul 2, 07:35 UTC | Jul 2, 09:45 UTC | 2h 10m |
| 2026-07-02 | SVF608 | - | Jul 2, 06:30 UTC | Jul 2, 07:00 UTC | 30m |
| 2026-07-01 | SVF608 | - | Jul 1, 11:30 UTC | Jul 1, 11:40 UTC | 10m |
| 2026-07-01 | SVF608 | - | Jul 1, 09:35 UTC | Jul 1, 09:40 UTC | 5m |
| 2026-06-30 | SVF640 | - | Jun 30, 18:25 UTC | Jun 30, 18:55 UTC | 30m |
| 2026-06-30 | SVF640 | VNO → ARN | Jun 30, 15:45 UTC | Jun 30, 17:35 UTC | 1h 50m |
| 2026-06-29 | SVF640 | ARN → VNO | Jun 29, 11:45 UTC | Jun 29, 13:14 UTC | 1h 30m |
| 2026-06-29 | SVF640 | - | Jun 29, 09:44 UTC | Jun 29, 10:20 UTC | 35m |
| 2026-06-26 | SVF608 | - | Jun 26, 15:15 UTC | Jun 26, 15:45 UTC | 30m |
| 2026-06-26 | SVF608 | - | Jun 26, 14:09 UTC | Jun 26, 14:39 UTC | 30m |
| 2026-06-26 | SVF608 | - | Jun 26, 12:19 UTC | Jun 26, 12:50 UTC | 30m |
| 2026-06-24 | SVF644 | - | Jun 24, 13:44 UTC | Jun 24, 15:59 UTC | 2h 15m |
| 2026-06-24 | SVF644 | - | Jun 24, 04:30 UTC | Jun 24, 06:50 UTC | 2h 20m |
| 2026-06-23 | SVF608 | - | Jun 23, 08:04 UTC | Jun 23, 09:45 UTC | 1h 40m |
| 2026-06-16 | SVF632 | - | Jun 16, 19:15 UTC | Jun 16, 19:40 UTC | 25m |
| 2026-06-16 | SVF632 | - | Jun 16, 16:00 UTC | Jun 16, 18:29 UTC | 2h 30m |
| 2026-06-16 | SVF632 | - | Jun 16, 15:15 UTC | Jun 16, 15:55 UTC | 40m |
| 2026-06-16 | SVF632 | ARN → LUX | Jun 16, 03:25 UTC | Jun 16, 06:30 UTC | 3h 5m |
| 2026-06-15 | SVF667 | - | Jun 15, 15:10 UTC | Jun 15, 18:25 UTC | 3h 15m |
| 2026-06-14 | SVF667 | ARN → LUX | Jun 14, 15:20 UTC | Jun 14, 18:15 UTC | 2h 55m |
| 2026-06-14 | SVF667 | - | Jun 14, 13:20 UTC | Jun 14, 13:55 UTC | 35m |
| 2026-06-12 | SVF608 | - | Jun 12, 07:50 UTC | Jun 12, 09:15 UTC | 1h 25m |
| 2026-06-12 | SVF608 | - | Jun 12, 06:50 UTC | Jun 12, 07:15 UTC | 25m |
| 2026-06-11 | SVF608 | - | Jun 11, 12:05 UTC | Jun 11, 12:45 UTC | 40m |
| 2026-06-10 | SVF675 | - | Jun 10, 18:20 UTC | Jun 10, 19:40 UTC | 1h 20m |
| 2026-06-08 | SVF675 | - | Jun 8, 19:00 UTC | Jun 8, 21:05 UTC | 2h 5m |
| 2026-06-08 | SVF675 | - | Jun 8, 17:55 UTC | Jun 8, 18:20 UTC | 25m |
| 2026-06-08 | SVF662 | - | Jun 8, 14:20 UTC | Jun 8, 17:15 UTC | 2h 55m |
| 2026-06-08 | SVF662 | - | Jun 8, 10:20 UTC | Jun 8, 13:30 UTC | 3h 10m |
| 2026-06-08 | SVF662 | - | Jun 8, 08:15 UTC | Jun 8, 09:10 UTC | 55m |
| 2026-06-08 | SVF662 | - | Jun 8, 07:00 UTC | Jun 8, 07:30 UTC | 30m |
| 2026-06-07 | SVF679 | - | Jun 7, 11:55 UTC | Jun 7, 12:30 UTC | 35m |
| 2026-06-07 | SVF679 | - | Jun 7, 09:25 UTC | Jun 7, 11:10 UTC | 1h 45m |
| 2026-06-07 | SVF679 | - | Jun 7, 06:10 UTC | Jun 7, 08:40 UTC | 2h 30m |
| 2026-06-05 | SVF608 | - | Jun 5, 11:25 UTC | Jun 5, 13:30 UTC | 2h 5m |
| 2026-06-05 | SVF608 | - | Jun 5, 08:35 UTC | Jun 5, 10:35 UTC | 2h 0m |
| 2026-06-05 | SVF608 | - | Jun 5, 07:25 UTC | Jun 5, 08:00 UTC | 35m |
| 2026-06-04 | SVF608 | - | Jun 4, 11:30 UTC | Jun 4, 11:50 UTC | 20m |
| 2026-06-04 | SVF608 | - | Jun 4, 10:25 UTC | Jun 4, 11:00 UTC | 35m |
| 2026-06-04 | SVF608 | - | Jun 4, 08:30 UTC | Jun 4, 08:55 UTC | 25m |
| 2026-06-04 | SVF608 | - | Jun 4, 07:35 UTC | Jun 4, 08:00 UTC | 25m |
| 2026-06-03 | SVF669 | - | Jun 3, 16:00 UTC | Jun 3, 16:30 UTC | 30m |
| 2026-06-03 | SVF669 | - | Jun 3, 13:25 UTC | Jun 3, 15:25 UTC | 2h 0m |
| 2026-06-03 | SVF669 | - | Jun 3, 10:35 UTC | Jun 3, 12:40 UTC | 2h 5m |
| 2026-06-03 | SVF608 | - | Jun 3, 08:35 UTC | Jun 3, 09:05 UTC | 30m |
| 2026-06-03 | SVF608 | - | Jun 3, 08:05 UTC | Jun 3, 08:30 UTC | 25m |
| 2026-05-29 | SVF608 | - | May 29, 15:30 UTC | May 29, 17:30 UTC | 2h 0m |
| 2026-05-29 | SVF608 | - | May 29, 13:40 UTC | May 29, 14:10 UTC | 30m |
| 2026-05-29 | SVF608 | - | May 29, 08:30 UTC | May 29, 09:20 UTC | 50m |
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 100008 page for operator, model, and routing details .