Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

5140DB

ICAO 24-bit transponder address · allocated to Georgia

Currently assigned to 4L-GTL · BOEING 737-900

Hex
5140DB
Octal
24240333
Decimal
5,325,019
Country
GE
Tail
4L-GTL
Type
B739
Transponder active on ground
Flights observed
73
Distinct callsigns
6
Country
GE
Last broadcast
9h ago

Last known position

Most recent position reported by Mode-S 5140DB.

Country allocation

The ICAO 24-bit address 5140DB falls within the block assigned to Georgia (GE) by ICAO Annex 10, Volume III. Every aircraft registered in Georgia 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 6 distinct

Callsign Airline Flights Last seen
TGZ932 Georgian Airways 27 2026-05-29
TGZ926 Georgian Airways 23 2026-05-29
TGZ931 Georgian Airways 14 2026-05-23
TGZ936 Georgian Airways 3 2026-05-27
TGZ925 Georgian Airways 3 2026-05-29
926 - 1 2026-04-29

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-29 TGZ932 TBS → VKO May 29, 20:00 UTCMay 29, 20:15 UTC15m
2026-05-29 TGZ925 VKO → TBS May 29, 17:10 UTCMay 29, 17:25 UTC15m
2026-05-29 TGZ926 TBS → VKO May 29, 10:10 UTCMay 29, 10:30 UTC20m
2026-05-28 TGZ926 TBS → VKO May 28, 10:05 UTCMay 28, 10:25 UTC20m
2026-05-27 TGZ932 TBS → VKO May 27, 21:25 UTCMay 27, 21:35 UTC10m
2026-05-27 TGZ936 TBS → VKO May 27, 05:14 UTCMay 27, 05:35 UTC20m
2026-05-24 TGZ932 TBS → VKO May 24, 19:50 UTCMay 24, 20:15 UTC25m
2026-05-24 TGZ926 TBS → VKO May 24, 10:05 UTCMay 24, 10:20 UTC15m
2026-05-23 TGZ932 TBS → VKO May 23, 20:00 UTCMay 23, 20:25 UTC25m
2026-05-23 TGZ931 VKO → TBS May 23, 06:00 UTCMay 23, 06:15 UTC15m
2026-05-22 TGZ932 TBS → VKO May 22, 19:45 UTCMay 22, 20:00 UTC15m
2026-05-21 TGZ931 VKO → TBS May 21, 05:30 UTCMay 21, 05:40 UTC10m
2026-05-20 TGZ932 TBS → VKO May 20, 20:00 UTCMay 20, 20:15 UTC15m
2026-05-17 TGZ932 TBS → VKO May 17, 20:15 UTCMay 18, 05:20 UTC9h 5m
2026-05-17 TGZ926 TBS → VKO May 17, 11:25 UTCMay 17, 12:25 UTC1h 0m
2026-05-16 TGZ932 TBS → VKO May 16, 19:30 UTCMay 16, 20:15 UTC45m
2026-05-15 TGZ932 TBS → VKO May 15, 20:00 UTCMay 15, 20:50 UTC50m
2026-05-15 - TBS → TBS May 15, 18:30 UTCMay 15, 18:40 UTC10m
2026-05-14 TGZ931 VKO → TBS May 14, 10:50 UTCMay 15, 05:55 UTC19h 5m
2026-05-14 TGZ931 VKO → TBS May 14, 10:05 UTCMay 15, 05:55 UTC19h 50m
2026-05-14 - TBS → TBS May 14, 09:00 UTCMay 14, 09:15 UTC15m
2026-05-14 TGZ931 VKO → TBS May 14, 06:20 UTCMay 14, 06:55 UTC35m
2026-05-13 TGZ932 TBS → VKO May 13, 20:40 UTCMay 13, 21:35 UTC55m
2026-05-12 TGZ932 TBS → VKO May 12, 20:30 UTCMay 13, 10:50 UTC14h 20m
2026-05-11 TGZ932 TBS → VKO May 11, 20:00 UTCMay 11, 21:05 UTC1h 5m
2026-05-11 TGZ926 TBS → VKO May 11, 10:25 UTCMay 11, 11:15 UTC50m
2026-05-10 TGZ926 TBS → VKO May 10, 10:10 UTCMay 10, 11:25 UTC1h 15m
2026-05-09 TGZ926 TBS → VKO May 9, 10:35 UTCMay 9, 11:55 UTC1h 20m
2026-05-08 TGZ932 TBS → VKO May 8, 20:05 UTCMay 8, 20:35 UTC30m
2026-05-06 TGZ932 TBS → VKO May 6, 19:35 UTCMay 6, 20:00 UTC25m
2026-05-06 TGZ936 TBS → VKO May 6, 05:00 UTCMay 6, 05:10 UTC10m
2026-05-05 TGZ926 TBS → VKO May 5, 11:50 UTCMay 5, 12:10 UTC20m
2026-05-04 TGZ932 TBS → VKO May 4, 01:15 UTCMay 4, 01:40 UTC25m
2026-05-03 TGZ926 TBS → VKO May 3, 11:50 UTCMay 3, 12:15 UTC25m
2026-05-03 TGZ931 VKO → TBS May 3, 05:30 UTCMay 3, 05:45 UTC15m
2026-05-02 TGZ932 TBS → VKO May 2, 19:40 UTCMay 2, 19:55 UTC15m
2026-05-01 TGZ932 TBS → VKO May 1, 19:45 UTCMay 1, 20:10 UTC25m
2026-05-01 TGZ926 TBS → VKO May 1, 10:00 UTCMay 1, 10:15 UTC15m
2026-04-30 TGZ926 TBS → VKO Apr 30, 09:55 UTCApr 30, 10:15 UTC20m
2026-04-29 926 - Apr 29, 10:00 UTCApr 29, 10:20 UTC20m
2026-04-28 TGZ932 TBS → VKO Apr 28, 19:55 UTCApr 28, 20:20 UTC25m
2026-04-27 TGZ931 VKO → TBS Apr 27, 06:05 UTCApr 27, 06:15 UTC10m
2026-04-26 TGZ926 TBS → VKO Apr 26, 10:15 UTCApr 26, 20:35 UTC10h 20m
2026-04-26 TGZ931 VKO → TBS Apr 26, 05:35 UTCApr 26, 05:40 UTC5m
2026-04-25 TGZ925 VKO → TBS Apr 25, 10:55 UTCApr 25, 16:55 UTC6h 0m
2026-04-25 TGZ926 TBS → VKO Apr 25, 10:10 UTCApr 25, 10:25 UTC15m
2026-04-25 TGZ931 VKO → TBS Apr 25, 05:15 UTCApr 25, 05:25 UTC10m
2026-04-24 TGZ932 TBS → VKO Apr 24, 19:55 UTCApr 24, 20:05 UTC10m
2026-04-24 TGZ926 TBS → VKO Apr 24, 10:00 UTCApr 24, 10:50 UTC50m
2026-04-24 TGZ931 VKO → TBS Apr 24, 05:40 UTCApr 24, 05:50 UTC10m

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 4L-GTL page for operator, model, and routing details .

Mode-S 5140DB frequently asked

What is Mode-S code 5140DB?
5140DB is an ICAO 24-bit transponder address. Allocated to Georgia. Assigned to 4L-GTL.
Where is Mode-S 5140DB registered?
Mode-S code 5140DB is allocated to Georgia (GE). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 5140DB broadcasting right now?
Mode-S 5140DB is currently broadcasting from the ground.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 5140DB, octal 24240333, decimal 5,325,019.
What flights does 5140DB operate?
Mode-S 5140DB has broadcast 6 distinct callsigns, including TGZ932, TGZ926, TGZ931, TGZ936, TGZ925.