sensors Mode-S transponder
4AC8DA
ICAO 24-bit transponder address · allocated to Sweden
Currently assigned to SE-RFZ · BOEING 787-9 Dreamliner
- Hex
- 4AC8DA
- Octal
- 22544332
- Decimal
- 4,901,082
- Country
- SE
- Tail
- SE-RFZ
- Type
- B789
- Flights observed
- 87
- Distinct callsigns
- 20
- Country
- SE
- Last broadcast
- 8h ago
Last known position
Country allocation
The ICAO 24-bit address 4AC8DA 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| TOM9CN | TUI Airways | 7 | 2026-06-17 |
| TOM8DT | TUI Airways | 7 | 2026-06-17 |
| TOM57K | TUI Airways | 7 | 2026-06-18 |
| TOM46V | TUI Airways | 7 | 2026-06-17 |
| TOM2CK | TUI Airways | 7 | 2026-06-17 |
| TOM37V | TUI Airways | 6 | 2026-06-18 |
| TOM9PL | - | 5 | 2026-06-18 |
| TOM52W | TUI Airways | 5 | 2026-06-18 |
| TOM169 | TUI Airways | 5 | 2026-06-15 |
| TOM157 | TUI Airways | 5 | 2026-06-19 |
| TOM134 | TUI Airways | 5 | 2026-06-13 |
| TOM168 | TUI Airways | 4 | 2026-06-08 |
| TOM118 | TUI Airways | 4 | 2026-06-16 |
| TOM8DL | - | 3 | 2026-06-19 |
| TOM119 | TUI Airways | 3 | 2026-06-09 |
| TOM21X | TUI Airways | 2 | 2026-05-14 |
| TOM1FM | - | 2 | 2026-05-15 |
| TOM9412 | - | 1 | 2026-06-20 |
| TOM412 | - | 1 | 2026-06-20 |
| BLX928P | TUIfly Nordic | 1 | 2026-04-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-20 | TOM412 | - | Jun 20, 11:09 UTC | Jun 20, 18:29 UTC | 7h 20m |
| 2026-06-20 | TOM9412 | - | Jun 20, 08:14 UTC | Jun 20, 08:55 UTC | 40m |
| 2026-06-19 | TOM157 | PUJ → MAN | Jun 19, 10:35 UTC | Jun 20, 06:10 UTC | 19h 35m |
| 2026-06-19 | TOM8DL | MAN → MAN | Jun 19, 10:29 UTC | Jun 20, 06:10 UTC | 19h 40m |
| 2026-06-18 | TOM9PL | RHO → MAN | Jun 18, 23:00 UTC | Jun 19, 02:50 UTC | 3h 49m |
| 2026-06-18 | TOM52W | HER → STN | Jun 18, 17:55 UTC | Jun 18, 21:30 UTC | 3h 35m |
| 2026-06-18 | TOM57K | BRS → KGS | Jun 18, 12:35 UTC | Jun 18, 15:55 UTC | 3h 20m |
| 2026-06-18 | TOM37V | ZTH → NCL | Jun 18, 06:55 UTC | Jun 18, 10:35 UTC | 3h 40m |
| 2026-06-17 | TOM9CN | STN → HER | Jun 17, 22:05 UTC | Jun 18, 01:50 UTC | 3h 45m |
| 2026-06-17 | TOM2CK | MAN → TFS | Jun 17, 17:00 UTC | Jun 17, 20:25 UTC | 3h 25m |
| 2026-06-17 | TOM8DT | LGW → LCA | Jun 17, 12:30 UTC | Jun 17, 14:40 UTC | 2h 10m |
| 2026-06-17 | TOM46V | MAN → PMI | Jun 17, 07:20 UTC | Jun 17, 09:30 UTC | 2h 10m |
| 2026-06-16 | TOM118 | MAN → PUJ | Jun 16, 09:40 UTC | Jun 17, 04:25 UTC | 18h 46m |
| 2026-06-15 | TOM169 | CUN → MAN | Jun 15, 12:35 UTC | Jun 16, 06:54 UTC | 18h 20m |
| 2026-06-15 | TOM169 | CUN → MAN | Jun 15, 12:19 UTC | Jun 16, 06:54 UTC | 18h 35m |
| 2026-06-13 | TOM134 | MAN → VRA | Jun 13, 10:35 UTC | Jun 14, 05:05 UTC | 18h 30m |
| 2026-06-13 | TOM134 | MAN → VRA | Jun 13, 10:20 UTC | Jun 14, 05:05 UTC | 18h 46m |
| 2026-06-12 | TOM157 | PUJ → MAN | Jun 12, 10:35 UTC | Jun 13, 05:45 UTC | 19h 9m |
| 2026-06-12 | TOM157 | PUJ → MAN | Jun 12, 10:00 UTC | Jun 13, 05:45 UTC | 19h 44m |
| 2026-06-11 | TOM9PL | RHO → MAN | Jun 11, 23:35 UTC | Jun 12, 03:25 UTC | 3h 51m |
| 2026-06-11 | TOM52W | HER → STN | Jun 11, 18:40 UTC | Jun 11, 22:05 UTC | 3h 25m |
| 2026-06-11 | TOM57K | BRS → KGS | Jun 11, 12:25 UTC | Jun 11, 16:15 UTC | 3h 50m |
| 2026-06-11 | TOM37V | ZTH → NCL | Jun 11, 07:00 UTC | Jun 11, 10:35 UTC | 3h 35m |
| 2026-06-10 | TOM9CN | STN → HER | Jun 10, 21:45 UTC | Jun 11, 01:35 UTC | 3h 50m |
| 2026-06-10 | TOM2CK | MAN → TFS | Jun 10, 16:25 UTC | Jun 10, 19:55 UTC | 3h 30m |
| 2026-06-10 | TOM8DT | LGW → LCA | Jun 10, 12:15 UTC | Jun 10, 14:25 UTC | 2h 10m |
| 2026-06-10 | TOM46V | MAN → PMI | Jun 10, 07:55 UTC | Jun 10, 10:10 UTC | 2h 15m |
| 2026-06-09 | TOM119 | PUJ → MAN | Jun 9, 10:35 UTC | Jun 10, 04:45 UTC | 18h 10m |
| 2026-06-09 | TOM119 | PUJ → MAN | Jun 9, 09:50 UTC | Jun 10, 04:45 UTC | 18h 55m |
| 2026-06-08 | TOM169 | CUN → MAN | Jun 8, 12:35 UTC | Jun 9, 07:15 UTC | 18h 40m |
| 2026-06-08 | TOM168 | MAN → CUN | Jun 8, 12:25 UTC | Jun 9, 07:15 UTC | 18h 50m |
| 2026-06-06 | TOM134 | MAN → VRA | Jun 6, 10:25 UTC | Jun 7, 04:25 UTC | 18h 0m |
| 2026-06-05 | TOM8DL | MAN → MAN | Jun 5, 11:05 UTC | Jun 6, 05:00 UTC | 17h 55m |
| 2026-06-04 | TOM9PL | RHO → MAN | Jun 4, 23:35 UTC | Jun 5, 03:25 UTC | 3h 50m |
| 2026-06-04 | TOM52W | HER → STN | Jun 4, 18:20 UTC | Jun 4, 21:50 UTC | 3h 30m |
| 2026-06-04 | TOM57K | BRS → KGS | Jun 4, 12:45 UTC | Jun 4, 16:20 UTC | 3h 35m |
| 2026-06-04 | TOM37V | ZTH → NCL | Jun 4, 10:15 UTC | Jun 4, 10:30 UTC | 15m |
| 2026-06-04 | TOM37V | ZTH → NCL | Jun 4, 06:55 UTC | Jun 4, 09:30 UTC | 2h 35m |
| 2026-06-03 | TOM9CN | STN → HER | Jun 3, 21:20 UTC | Jun 4, 01:00 UTC | 3h 40m |
| 2026-06-03 | TOM2CK | MAN → TFS | Jun 3, 16:10 UTC | Jun 3, 19:35 UTC | 3h 25m |
| 2026-06-03 | TOM8DT | LGW → LCA | Jun 3, 11:50 UTC | Jun 3, 14:00 UTC | 2h 10m |
| 2026-06-03 | TOM46V | MAN → PMI | Jun 3, 07:25 UTC | Jun 3, 09:35 UTC | 2h 10m |
| 2026-06-02 | TOM118 | MAN → PUJ | Jun 2, 09:55 UTC | Jun 3, 04:10 UTC | 18h 15m |
| 2026-06-02 | TOM169 | CUN → MAN | Jun 2, 00:25 UTC | Jun 2, 07:30 UTC | 7h 5m |
| 2026-06-01 | TOM168 | MAN → CUN | Jun 1, 12:40 UTC | Jun 1, 20:45 UTC | 8h 5m |
| 2026-05-30 | TOM134 | MAN → VRA | May 30, 10:25 UTC | May 30, 22:00 UTC | 11h 35m |
| 2026-05-29 | TOM157 | PUJ → MAN | May 29, 10:35 UTC | May 30, 04:45 UTC | 18h 10m |
| 2026-05-29 | TOM8DL | MAN → MAN | May 29, 10:05 UTC | May 30, 04:45 UTC | 18h 40m |
| 2026-05-28 | TOM9PL | RHO → MAN | May 28, 23:10 UTC | May 29, 03:05 UTC | 3h 55m |
| 2026-05-28 | TOM52W | HER → STN | May 28, 18:00 UTC | May 28, 21:40 UTC | 3h 40m |
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-RFZ page for operator, model, and routing details .