sensors Mode-S transponder
4D2110
ICAO 24-bit transponder address · allocated to Malta
Currently assigned to 9H-ILZ · BOMBARDIER Regional Jet CRJ-200
- Hex
- 4D2110
- Octal
- 23220420
- Decimal
- 5,054,736
- Country
- MT
- Tail
- 9H-ILZ
- Type
- CRJ2
- Flights observed
- 93
- Distinct callsigns
- 2
- Country
- MT
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 4D2110 falls within the block assigned to Malta (MT) by ICAO Annex 10, Volume III. Every aircraft registered in Malta 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 2 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-17 | VJT683 | - | Jun 17, 13:00 UTC | Jun 17, 13:55 UTC | 55m |
| 2026-06-17 | VJT683 | - | Jun 17, 08:55 UTC | Jun 17, 10:00 UTC | 1h 5m |
| 2026-06-16 | VJT683 | - | Jun 16, 17:45 UTC | Jun 16, 18:29 UTC | 45m |
| 2026-06-16 | VJT683 | LIN → LBG | Jun 16, 13:09 UTC | Jun 16, 14:20 UTC | 1h 10m |
| 2026-06-15 | VJT683 | - | Jun 15, 17:04 UTC | Jun 15, 17:59 UTC | 55m |
| 2026-06-15 | VJT683 | - | Jun 15, 12:25 UTC | Jun 15, 13:15 UTC | 50m |
| 2026-06-15 | VJT683 | - | Jun 15, 09:30 UTC | Jun 15, 11:30 UTC | 2h 0m |
| 2026-06-14 | VJT683 | - | Jun 14, 11:05 UTC | Jun 14, 14:45 UTC | 3h 40m |
| 2026-06-14 | VJT683 | - | Jun 14, 07:30 UTC | Jun 14, 08:25 UTC | 55m |
| 2026-06-13 | VJT683 | - | Jun 13, 13:20 UTC | Jun 13, 14:25 UTC | 1h 5m |
| 2026-06-13 | VJT683 | - | Jun 13, 10:35 UTC | Jun 13, 12:10 UTC | 1h 35m |
| 2026-06-13 | VJT683 | - | Jun 13, 06:10 UTC | Jun 13, 08:10 UTC | 2h 0m |
| 2026-06-13 | VJT683 | - | Jun 13, 04:20 UTC | Jun 13, 05:00 UTC | 40m |
| 2026-06-12 | VJT683 | - | Jun 12, 09:40 UTC | Jun 12, 12:00 UTC | 2h 20m |
| 2026-06-12 | VJT683 | - | Jun 12, 06:25 UTC | Jun 12, 07:20 UTC | 55m |
| 2026-06-11 | VJT683 | - | Jun 11, 10:05 UTC | Jun 11, 11:40 UTC | 1h 35m |
| 2026-06-10 | VJT683 | - | Jun 10, 18:15 UTC | Jun 10, 20:40 UTC | 2h 25m |
| 2026-06-10 | VJT683 | LIN → CIA | Jun 10, 16:35 UTC | Jun 10, 17:20 UTC | 45m |
| 2026-06-10 | VJT683 | BCN → LIN | Jun 10, 12:25 UTC | Jun 10, 13:30 UTC | 1h 5m |
| 2026-06-08 | VJT683 | - | Jun 8, 19:30 UTC | Jun 8, 21:10 UTC | 1h 40m |
| 2026-06-08 | VJT683 | - | Jun 8, 13:40 UTC | Jun 8, 15:04 UTC | 1h 25m |
| 2026-06-07 | VJT683 | - | Jun 7, 18:10 UTC | Jun 7, 20:35 UTC | 2h 25m |
| 2026-06-06 | VJT683 | - | Jun 6, 13:39 UTC | Jun 6, 14:20 UTC | 40m |
| 2026-06-06 | VJT683 | BRS → NCE | Jun 6, 09:30 UTC | Jun 6, 11:30 UTC | 2h 0m |
| 2026-06-05 | VJT683 | IBZ → BRS | Jun 5, 17:15 UTC | Jun 5, 19:25 UTC | 2h 10m |
| 2026-06-05 | VJT683 | MAN → IBZ | Jun 5, 12:55 UTC | Jun 5, 15:10 UTC | 2h 15m |
| 2026-06-05 | VJT683 | ORK → MAN | Jun 5, 10:35 UTC | Jun 5, 11:25 UTC | 50m |
| 2026-06-04 | VJT683 | FAO → ORK | Jun 4, 14:55 UTC | Jun 4, 17:20 UTC | 2h 25m |
| 2026-06-04 | VJT683 | MAN → FAO | Jun 4, 08:35 UTC | Jun 4, 11:25 UTC | 2h 50m |
| 2026-06-04 | VJT683 | - | Jun 4, 06:10 UTC | Jun 4, 06:45 UTC | 35m |
| 2026-06-03 | VJT683 | - | Jun 3, 15:40 UTC | Jun 3, 16:25 UTC | 45m |
| 2026-06-03 | VJT683 | - | Jun 3, 13:25 UTC | Jun 3, 14:20 UTC | 55m |
| 2026-06-03 | VJT683 | MAD → FAB | Jun 3, 07:25 UTC | Jun 3, 09:15 UTC | 1h 50m |
| 2026-06-01 | VJT683 | - | Jun 1, 10:50 UTC | Jun 1, 11:40 UTC | 50m |
| 2026-06-01 | VJT923W | BUD → LIS | Jun 1, 05:30 UTC | Jun 1, 09:05 UTC | 3h 35m |
| 2026-06-01 | VJT683 | - | Jun 1, 02:55 UTC | Jun 1, 03:55 UTC | 1h 0m |
| 2026-05-31 | VJT683 | - | May 31, 13:40 UTC | May 31, 14:05 UTC | 25m |
| 2026-05-31 | VJT683 | - | May 31, 08:25 UTC | May 31, 11:35 UTC | 3h 10m |
| 2026-05-30 | VJT683 | - | May 30, 12:50 UTC | May 30, 15:15 UTC | 2h 25m |
| 2026-05-30 | VJT683 | - | May 30, 10:25 UTC | May 30, 11:40 UTC | 1h 15m |
| 2026-05-30 | VJT683 | - | May 30, 07:25 UTC | May 30, 08:40 UTC | 1h 15m |
| 2026-05-29 | VJT683 | MXP → LTN | May 29, 15:20 UTC | May 29, 16:55 UTC | 1h 35m |
| 2026-05-29 | VJT683 | - | May 29, 12:35 UTC | May 29, 12:55 UTC | 20m |
| 2026-05-29 | VJT683 | NCL → ZRH | May 29, 09:05 UTC | May 29, 10:50 UTC | 1h 45m |
| 2026-05-27 | VJT683 | - | May 27, 14:35 UTC | May 27, 15:15 UTC | 40m |
| 2026-05-27 | VJT683 | - | May 27, 11:25 UTC | May 27, 13:20 UTC | 1h 55m |
| 2026-05-26 | VJT683 | - | May 26, 12:14 UTC | May 26, 12:50 UTC | 35m |
| 2026-05-26 | VJT683 | - | May 26, 09:49 UTC | May 26, 10:34 UTC | 45m |
| 2026-05-25 | VJT683 | - | May 25, 17:15 UTC | May 25, 17:50 UTC | 35m |
| 2026-05-25 | VJT683 | - | May 25, 06:50 UTC | May 25, 07:20 UTC | 30m |
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 9H-ILZ page for operator, model, and routing details .