sensors Mode-S transponder
4D209F
ICAO 24-bit transponder address · allocated to Malta
Currently assigned to 9H-GGG · BOEING 737-700
- Hex
- 4D209F
- Octal
- 23220237
- Decimal
- 5,054,623
- Country
- MT
- Tail
- 9H-GGG
- Type
- B737
- Flights observed
- 26
- Distinct callsigns
- 1
- Country
- MT
- Last broadcast
- Jul 22, 22:00 UTC
Last known position
Country allocation
The ICAO 24-bit address 4D209F 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| JML100 | - | 26 | 2026-07-22 |
Recent flights last 26
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-22 | JML100 | - | Jul 22, 20:50 UTC | Jul 22, 22:00 UTC | 1h 10m |
| 2026-07-21 | JML100 | - | Jul 21, 13:05 UTC | Jul 22, 01:05 UTC | 12h 0m |
| 2026-07-20 | JML100 | - | Jul 20, 08:20 UTC | Jul 20, 08:40 UTC | 20m |
| 2026-07-19 | JML100 | - | Jul 19, 22:05 UTC | Jul 20, 01:10 UTC | 3h 5m |
| 2026-07-16 | JML100 | - | Jul 16, 17:49 UTC | Jul 16, 19:20 UTC | 1h 30m |
| 2026-07-16 | JML100 | - | Jul 16, 13:20 UTC | Jul 16, 15:35 UTC | 2h 15m |
| 2026-07-08 | JML100 | - | Jul 8, 13:10 UTC | Jul 8, 18:40 UTC | 5h 30m |
| 2026-07-07 | JML100 | - | Jul 7, 16:30 UTC | Jul 8, 13:10 UTC | 20h 40m |
| 2026-07-07 | JML100 | - | Jul 7, 11:20 UTC | Jul 7, 16:50 UTC | 5h 30m |
| 2026-07-01 | JML100 | - | Jul 1, 13:55 UTC | Jul 1, 20:50 UTC | 6h 55m |
| 2026-06-30 | JML100 | - | Jun 30, 22:45 UTC | Jun 30, 23:05 UTC | 20m |
| 2026-06-29 | JML100 | TLV → ISP | Jun 29, 15:24 UTC | Jun 30, 03:00 UTC | 11h 36m |
| 2026-06-29 | JML100 | - | Jun 29, 13:09 UTC | Jun 29, 13:24 UTC | 15m |
| 2026-06-26 | JML100 | - | Jun 26, 22:49 UTC | Jun 26, 23:09 UTC | 20m |
| 2026-06-26 | JML100 | MXP → TLV | Jun 26, 18:20 UTC | Jun 26, 21:45 UTC | 3h 25m |
| 2026-06-26 | JML100 | - | Jun 26, 14:09 UTC | Jun 26, 15:25 UTC | 1h 15m |
| 2026-06-07 | JML100 | NCE → BTS | Jun 7, 16:50 UTC | Jun 7, 18:05 UTC | 1h 15m |
| 2026-06-04 | JML100 | BTS → NCE | Jun 4, 15:10 UTC | Jun 4, 16:45 UTC | 1h 35m |
| 2026-06-03 | JML100 | VIE → BTS | Jun 3, 18:45 UTC | Jun 3, 19:05 UTC | 20m |
| 2026-06-03 | JML100 | - | Jun 3, 15:35 UTC | Jun 3, 17:35 UTC | 2h 0m |
| 2026-06-01 | JML100 | - | Jun 1, 16:40 UTC | Jun 1, 17:50 UTC | 1h 10m |
| 2026-05-29 | JML100 | - | May 29, 08:20 UTC | May 29, 08:50 UTC | 30m |
| 2026-05-28 | JML100 | - | May 28, 14:40 UTC | May 28, 17:00 UTC | 2h 20m |
| 2026-05-28 | JML100 | - | May 28, 06:50 UTC | May 28, 08:40 UTC | 1h 50m |
| 2026-05-27 | JML100 | - | May 27, 17:15 UTC | May 27, 18:05 UTC | 50m |
| 2026-05-27 | JML100 | - | May 27, 11:35 UTC | May 27, 14:05 UTC | 2h 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-GGG page for operator, model, and routing details .