sensors Mode-S transponder

7020BD

ICAO 24-bit transponder address · allocated to Bangladesh

Currently assigned to S2-ALA · AIRBUS A-330-300

Hex
7020BD
Octal
34020275
Decimal
7,348,413
Country
BD
Tail
S2-ALA
Type
A333
No current signal · last broadcast 22h ago
Flights observed
273
Distinct callsigns
16
Country
BD
Last broadcast
22h ago

Last known position

Most recent position reported by Mode-S 7020BD.

Country allocation

The ICAO 24-bit address 7020BD falls within the block assigned to Bangladesh (BD) by ICAO Annex 10, Volume III. Every aircraft registered in Bangladesh 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 16 distinct

Callsign Airline Flights Last seen
UBG315 - 82 2026-07-13
UBG316 - 55 2026-07-13
UBG382 - 22 2026-07-10
UBG381 - 17 2026-07-12
UBG362 - 15 2026-07-11
UBG307 - 13 2026-06-29
UBG341 - 12 2026-07-13
UBG326 - 12 2026-07-04
UBG308 - 12 2026-06-29
UBG361 - 11 2026-07-07
UBG325 - 9 2026-06-16
UBG342 - 5 2026-07-07
UBG334 - 3 2026-06-23
UBG382D - 2 2026-04-28
UBG333 - 2 2026-06-23
UBG316D - 1 2026-06-27

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-13 UBG341 - Jul 13, 21:35 UTCJul 13, 21:45 UTC10m
2026-07-13 UBG341 - Jul 13, 17:35 UTCJul 13, 20:20 UTC2h 45m
2026-07-13 UBG316 - Jul 13, 08:25 UTCJul 13, 11:50 UTC3h 25m
2026-07-13 UBG315 - Jul 13, 06:01 UTCJul 13, 06:20 UTC20m
2026-07-13 UBG315 - Jul 13, 02:50 UTCJul 13, 05:15 UTC2h 25m
2026-07-12 UBG381 DAC → DAC Jul 12, 08:35 UTCJul 12, 22:35 UTC14h 0m
2026-07-11 UBG362 - Jul 11, 11:45 UTCJul 12, 03:25 UTC15h 40m
2026-07-10 UBG382 - Jul 10, 10:10 UTCJul 11, 02:10 UTC16h 0m
2026-07-10 UBG381 - Jul 10, 08:05 UTCJul 10, 09:05 UTC1h 0m
2026-07-09 UBG362 JED → DAC Jul 9, 11:50 UTCJul 10, 03:20 UTC15h 30m
2026-07-08 UBG362 JED → DAC Jul 8, 11:40 UTCJul 9, 03:20 UTC15h 40m
2026-07-07 UBG362 JED → DAC Jul 7, 22:10 UTCJul 8, 03:20 UTC5h 10m
2026-07-07 UBG361 - Jul 7, 11:55 UTCJul 7, 16:10 UTC4h 15m
2026-07-07 UBG342 - Jul 7, 00:20 UTCJul 7, 04:50 UTC4h 30m
2026-07-06 UBG341 DAC → DXB Jul 6, 22:00 UTCJul 6, 22:10 UTC10m
2026-07-06 UBG341 DAC → DXB Jul 6, 17:45 UTCJul 6, 20:45 UTC3h 0m
2026-07-06 UBG316 - Jul 6, 08:35 UTCJul 6, 12:00 UTC3h 25m
2026-07-06 UBG315 - Jul 6, 06:05 UTCJul 6, 06:20 UTC15m
2026-07-06 UBG315 - Jul 6, 04:05 UTCJul 6, 05:05 UTC1h 0m
2026-07-06 UBG315 - Jul 6, 02:50 UTCJul 6, 03:20 UTC30m
2026-07-05 UBG381 DAC → DAC Jul 5, 08:15 UTCJul 5, 22:35 UTC14h 20m
2026-07-04 UBG326 DAC → DAC Jul 4, 16:15 UTCJul 5, 01:25 UTC9h 10m
2026-07-04 UBG316 - Jul 4, 08:30 UTCJul 4, 11:55 UTC3h 25m
2026-07-04 UBG315 - Jul 4, 06:00 UTCJul 4, 06:20 UTC20m
2026-07-04 UBG315 - Jul 4, 02:55 UTCJul 4, 05:10 UTC2h 15m
2026-07-03 UBG382 DAC → DAC Jul 3, 08:00 UTCJul 3, 21:55 UTC13h 55m
2026-07-02 UBG361 DAC → DAC Jul 2, 11:25 UTCJul 3, 03:05 UTC15h 40m
2026-07-01 UBG361 DAC → DAC Jul 1, 11:55 UTCJul 2, 03:05 UTC15h 10m
2026-06-30 UBG382 - Jun 30, 17:35 UTCJun 30, 22:00 UTC4h 25m
2026-06-30 UBG381 - Jun 30, 08:10 UTCJun 30, 17:30 UTC9h 20m
2026-06-29 UBG308 - Jun 29, 22:05 UTCJun 30, 01:45 UTC3h 41m
2026-06-29 UBG307 - Jun 29, 16:25 UTCJun 29, 20:00 UTC3h 35m
2026-06-29 UBG316 - Jun 29, 08:35 UTCJun 29, 12:00 UTC3h 25m
2026-06-29 UBG315 - Jun 29, 06:09 UTCJun 29, 06:29 UTC20m
2026-06-29 UBG315 - Jun 29, 02:59 UTCJun 29, 05:20 UTC2h 20m
2026-06-28 UBG381 DAC → DAC Jun 28, 08:44 UTCJun 28, 22:10 UTC13h 25m
2026-06-27 UBG326 DAC → DAC Jun 27, 16:24 UTCJun 28, 01:19 UTC8h 55m
2026-06-27 UBG316D - Jun 27, 07:30 UTCJun 27, 10:54 UTC3h 25m
2026-06-27 UBG315 - Jun 27, 04:29 UTCJun 27, 04:49 UTC20m
2026-06-27 UBG315 - Jun 27, 01:19 UTCJun 27, 03:34 UTC2h 15m
2026-06-26 UBG382 - Jun 26, 11:55 UTCJun 26, 21:30 UTC9h 35m
2026-06-26 UBG381 - Jun 26, 07:45 UTCJun 26, 10:50 UTC3h 5m
2026-06-25 UBG362 JED → DAC Jun 25, 11:19 UTCJun 26, 03:24 UTC16h 5m
2026-06-24 UBG362 JED → DAC Jun 24, 13:40 UTCJun 25, 02:49 UTC13h 10m
2026-06-24 UBG361 - Jun 24, 11:29 UTCJun 24, 12:30 UTC1h 0m
2026-06-23 UBG334 - Jun 23, 20:40 UTCJun 24, 01:49 UTC5h 10m
2026-06-23 UBG333 - Jun 23, 12:49 UTCJun 23, 17:50 UTC5h 0m
2026-06-22 UBG308 - Jun 22, 21:59 UTCJun 23, 01:40 UTC3h 40m
2026-06-22 UBG307 - Jun 22, 16:29 UTCJun 22, 19:49 UTC3h 20m
2026-06-22 UBG316 - Jun 22, 08:25 UTCJun 22, 11:44 UTC3h 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 S2-ALA page for operator, model, and routing details .

Mode-S 7020BD frequently asked

What is Mode-S code 7020BD?
7020BD is an ICAO 24-bit transponder address. Allocated to Bangladesh. Assigned to S2-ALA.
Where is Mode-S 7020BD registered?
Mode-S code 7020BD is allocated to Bangladesh (BD). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 7020BD broadcasting right now?
No active broadcast right now. Last signal was 22h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 7020BD, octal 34020275, decimal 7,348,413.
What flights does 7020BD operate?
Mode-S 7020BD has broadcast 16 distinct callsigns, including UBG315, UBG316, UBG382, UBG381, UBG362.