sensors Mode-S transponder

510077

ICAO 24-bit transponder address · allocated to Belarus

Currently assigned to EW-366PA · BOEING 737-300

Hex
510077
Octal
24200167
Decimal
5,308,535
Country
BY
Tail
EW-366PA
Type
B733
No current signal · last broadcast 25d ago
Flights observed
99
Distinct callsigns
20
Country
BY
Last broadcast
25d ago

Last known position

Most recent position reported by Mode-S 510077.

Country allocation

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

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-04 BRU946 LED → MSQ May 4, 17:15 UTCMay 4, 18:15 UTC1h 0m
2026-05-04 BRU945 MSQ → LED May 4, 15:10 UTCMay 4, 16:10 UTC1h 0m
2026-05-04 BRU940 LED → MSQ May 4, 12:30 UTCMay 4, 13:30 UTC1h 0m
2026-05-04 BRU939 MSQ → LED May 4, 10:30 UTCMay 4, 11:30 UTC1h 0m
2026-05-04 BRU942 LED → MSQ May 4, 08:10 UTCMay 4, 09:10 UTC1h 0m
2026-05-04 BRU941 MSQ → LED May 4, 05:55 UTCMay 4, 06:55 UTC1h 0m
2026-05-03 BRU740 GYD → MSQ May 3, 20:10 UTCMay 4, 04:29 UTC8h 20m
2026-05-03 BRU946 LED → MSQ May 3, 17:20 UTCMay 3, 18:09 UTC50m
2026-05-03 BRU945 MSQ → LED May 3, 15:00 UTCMay 3, 16:09 UTC1h 10m
2026-05-03 BRU942 LED → MSQ May 3, 09:00 UTCMay 3, 10:00 UTC1h 0m
2026-05-03 BRU941 MSQ → LED May 3, 06:45 UTCMay 3, 07:50 UTC1h 5m
2026-05-02 BRU739 MSQ → GYD May 2, 20:15 UTCMay 3, 05:10 UTC8h 54m
2026-05-02 BRU946 LED → MSQ May 2, 17:35 UTCMay 2, 18:30 UTC55m
2026-05-02 BRU945 MSQ → LED May 2, 15:30 UTCMay 2, 16:40 UTC1h 10m
2026-05-02 BRU940 LED → MSQ May 2, 13:25 UTCMay 2, 14:20 UTC55m
2026-05-02 BRU939 MSQ → LED May 2, 11:10 UTCMay 2, 12:20 UTC1h 10m
2026-05-02 BRU942 LED → MSQ May 2, 08:30 UTCMay 2, 09:50 UTC1h 20m
2026-05-02 BRU941 MSQ → LED May 2, 05:40 UTCMay 2, 07:25 UTC1h 45m
2026-05-01 BRU739 MSQ → GYD May 1, 20:05 UTCMay 2, 04:15 UTC8h 10m
2026-05-01 BRU946 LED → MSQ May 1, 17:15 UTCMay 1, 18:05 UTC50m
2026-05-01 BRU945 MSQ → LED May 1, 15:00 UTCMay 1, 16:10 UTC1h 10m
2026-05-01 BRU940 LED → MSQ May 1, 12:40 UTCMay 1, 13:30 UTC50m
2026-05-01 BRU939 MSQ → LED May 1, 10:20 UTCMay 1, 11:45 UTC1h 25m
2026-04-30 BRU740 GYD → MSQ Apr 30, 20:10 UTCMay 1, 04:30 UTC8h 20m
2026-04-30 BRU940 LED → MSQ Apr 30, 12:35 UTCApr 30, 13:25 UTC50m
2026-04-30 BRU939 MSQ → LED Apr 30, 10:20 UTCApr 30, 11:30 UTC1h 10m
2026-04-30 BRU942 LED → MSQ Apr 30, 07:55 UTCApr 30, 08:45 UTC50m
2026-04-30 BRU941 MSQ → LED Apr 30, 05:40 UTCApr 30, 06:45 UTC1h 5m
2026-04-30 BRU736 TBS → MSQ Apr 30, 00:50 UTCApr 30, 03:50 UTC3h 0m
2026-04-29 BRU735 MSQ → TBS Apr 29, 20:00 UTCApr 29, 23:25 UTC3h 24m
2026-04-29 BRU940 LED → MSQ Apr 29, 12:40 UTCApr 29, 13:30 UTC50m
2026-04-29 BRU939 MSQ → LED Apr 29, 10:20 UTCApr 29, 11:25 UTC1h 5m
2026-04-29 BRU982 VKO → MSQ Apr 29, 06:49 UTCApr 29, 07:40 UTC50m
2026-04-29 BRU981 MSQ → VKO Apr 29, 03:55 UTCApr 29, 04:55 UTC1h 0m
2026-04-28 BRU926 AER → MSQ Apr 28, 22:30 UTCApr 29, 01:40 UTC3h 10m
2026-04-28 BRU925 MSQ → AER Apr 28, 17:10 UTCApr 28, 20:55 UTC3h 45m
2026-04-28 BRU980 VKO → MSQ Apr 28, 14:20 UTCApr 28, 15:15 UTC55m
2026-04-28 BRU979 MSQ → VKO Apr 28, 11:50 UTCApr 28, 12:55 UTC1h 5m
2026-04-24 BRU946 LED → MSQ Apr 24, 17:10 UTCApr 24, 18:00 UTC50m
2026-04-24 BRU945 MSQ → LED Apr 24, 14:55 UTCApr 24, 16:05 UTC1h 10m
2026-04-22 BRU937 MSQ → KZN Apr 22, 09:35 UTCApr 22, 14:35 UTC5h 0m
2026-04-21 BRU940 LED → MSQ Apr 21, 12:50 UTCApr 21, 13:45 UTC55m
2026-04-21 BRU939 MSQ → LED Apr 21, 10:25 UTCApr 21, 11:40 UTC1h 15m
2026-04-20 BRU980 VKO → MSQ Apr 20, 14:25 UTCApr 20, 15:15 UTC50m
2026-04-20 BRU979 MSQ → VKO Apr 20, 11:45 UTCApr 20, 12:45 UTC1h 0m
2026-04-19 BRU739 MSQ → GYD Apr 19, 20:10 UTCApr 20, 04:05 UTC7h 55m
2026-04-19 BRU738 BUS → MSQ Apr 19, 01:25 UTCApr 19, 04:45 UTC3h 20m
2026-04-18 BRU737 MSQ → BUS Apr 18, 20:15 UTCApr 18, 23:55 UTC3h 40m
2026-04-18 BRU946 LED → MSQ Apr 18, 17:10 UTCApr 18, 18:05 UTC55m
2026-04-18 BRU945 - Apr 18, 15:00 UTCApr 18, 16:10 UTC1h 10m

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 EW-366PA page for operator, model, and routing details .

Mode-S 510077 frequently asked

What is Mode-S code 510077?
510077 is an ICAO 24-bit transponder address. Allocated to Belarus. Assigned to EW-366PA.
Where is Mode-S 510077 registered?
Mode-S code 510077 is allocated to Belarus (BY). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 510077 broadcasting right now?
No active broadcast right now. Last signal was 25d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 510077, octal 24200167, decimal 5,308,535.
What flights does 510077 operate?
Mode-S 510077 has broadcast 20 distinct callsigns, including BRU940, BRU939, BRU946, BRU945, BRU942.