sensors Mode-S transponder
4521BC
ICAO 24-bit transponder address · allocated to Bulgaria
- Hex
- 4521BC
- Octal
- 21220674
- Decimal
- 4,530,620
- Country
- BG
- Flights observed
- 27
- Distinct callsigns
- 11
- Country
- BG
- Last broadcast
- 18d ago
Last known position
Country allocation
The ICAO 24-bit address 4521BC falls within the block assigned to Bulgaria (BG) by ICAO Annex 10, Volume III. Every aircraft registered in Bulgaria 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 11 distinct
Recent flights last 27
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | EGT340 | - | Jul 25, 11:00 UTC | Jul 25, 12:00 UTC | 1h 0m |
| 2026-07-23 | EGT396 | - | Jul 23, 17:50 UTC | Jul 23, 19:10 UTC | 1h 20m |
| 2026-07-23 | EGT396 | - | Jul 23, 16:55 UTC | Jul 23, 17:45 UTC | 50m |
| 2026-07-23 | EGT396 | - | Jul 23, 14:00 UTC | Jul 23, 16:15 UTC | 2h 15m |
| 2026-07-23 | EGT395 | - | Jul 23, 10:50 UTC | Jul 23, 12:55 UTC | 2h 5m |
| 2026-07-23 | EGT395 | - | Jul 23, 08:50 UTC | Jul 23, 09:25 UTC | 35m |
| 2026-07-21 | EGT379 | - | Jul 21, 11:30 UTC | Jul 21, 12:35 UTC | 1h 5m |
| 2026-07-21 | EGT379 | LBG → JMK | Jul 21, 06:55 UTC | Jul 21, 10:25 UTC | 3h 30m |
| 2026-07-20 | EGT379 | JMK → LBG | Jul 20, 05:00 UTC | Jul 20, 08:30 UTC | 3h 30m |
| 2026-07-20 | EGT379 | - | Jul 20, 02:50 UTC | Jul 20, 04:10 UTC | 1h 20m |
| 2026-07-18 | EGT386 | - | Jul 18, 16:25 UTC | Jul 18, 16:50 UTC | 25m |
| 2026-07-18 | EGT386 | - | Jul 18, 08:10 UTC | Jul 18, 08:35 UTC | 25m |
| 2026-07-18 | EGT386 | - | Jul 18, 05:55 UTC | Jul 18, 06:30 UTC | 35m |
| 2026-07-17 | EGT303 | - | Jul 17, 10:40 UTC | Jul 17, 11:50 UTC | 1h 10m |
| 2026-07-16 | EGT186 | - | Jul 16, 08:50 UTC | Jul 16, 10:00 UTC | 1h 10m |
| 2026-07-12 | EGT356 | - | Jul 12, 14:15 UTC | Jul 12, 16:01 UTC | 1h 45m |
| 2026-07-12 | EGT356 | - | Jul 12, 06:01 UTC | Jul 12, 08:10 UTC | 2h 10m |
| 2026-07-03 | EGT347 | ATH → SOF | Jul 3, 13:10 UTC | Jul 3, 14:00 UTC | 50m |
| 2026-07-03 | EGT347 | - | Jul 3, 08:50 UTC | Jul 3, 12:00 UTC | 3h 10m |
| 2026-07-03 | EGT347 | - | Jul 3, 04:30 UTC | Jul 3, 07:05 UTC | 2h 35m |
| 2026-06-30 | EGT322 | - | Jun 30, 17:15 UTC | Jun 30, 17:35 UTC | 20m |
| 2026-06-30 | EGT322 | - | Jun 30, 15:10 UTC | Jun 30, 16:25 UTC | 1h 15m |
| 2026-06-30 | EGT322 | - | Jun 30, 12:40 UTC | Jun 30, 13:45 UTC | 1h 5m |
| 2026-06-26 | LZFTJ | - | Jun 26, 14:09 UTC | Jun 26, 17:25 UTC | 3h 15m |
| 2026-06-26 | LZFTJ | - | Jun 26, 11:14 UTC | Jun 26, 13:04 UTC | 1h 50m |
| 2026-06-25 | LZFTJ | BGR → KEF | Jun 25, 12:15 UTC | Jun 25, 18:39 UTC | 6h 25m |
| 2026-06-24 | LZFTJ | - | Jun 24, 15:14 UTC | Jun 24, 18:15 UTC | 3h 0m |
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.