sensors Mode-S transponder
51118B
ICAO 24-bit transponder address · allocated to Estonia
Currently assigned to ES-BTC · BOMBARDIER CL-600 Challenger
- Hex
- 51118B
- Octal
- 24210613
- Decimal
- 5,312,907
- Country
- EE
- Tail
- ES-BTC
- Type
- CL60
- Flights observed
- 43
- Distinct callsigns
- 1
- Country
- EE
- Last broadcast
- 17h ago
Last known position
Country allocation
The ICAO 24-bit address 51118B falls within the block assigned to Estonia (EE) by ICAO Annex 10, Volume III. Every aircraft registered in Estonia 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 |
|---|---|---|---|
| VPC004 | - | 43 | 2026-06-18 |
Recent flights last 43
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-18 | VPC004 | TLL → BQH | Jun 18, 15:20 UTC | Jun 18, 18:00 UTC | 2h 40m |
| 2026-06-13 | VPC004 | RKV → TLL | Jun 13, 12:15 UTC | Jun 13, 15:25 UTC | 3h 10m |
| 2026-06-10 | VPC004 | - | Jun 10, 12:15 UTC | Jun 10, 12:35 UTC | 20m |
| 2026-06-10 | VPC004 | - | Jun 10, 09:35 UTC | Jun 10, 11:05 UTC | 1h 30m |
| 2026-06-09 | VPC004 | - | Jun 9, 18:50 UTC | Jun 9, 19:25 UTC | 35m |
| 2026-06-09 | VPC004 | LIS → RIX | Jun 9, 14:35 UTC | Jun 9, 18:15 UTC | 3h 40m |
| 2026-06-09 | VPC004 | - | Jun 9, 09:30 UTC | Jun 9, 13:10 UTC | 3h 40m |
| 2026-06-08 | VPC004 | - | Jun 8, 12:35 UTC | Jun 8, 13:55 UTC | 1h 20m |
| 2026-06-07 | VPC004 | BER → NCE | Jun 7, 09:25 UTC | Jun 7, 11:10 UTC | 1h 45m |
| 2026-06-05 | VPC004 | - | Jun 5, 14:55 UTC | Jun 5, 16:10 UTC | 1h 15m |
| 2026-06-05 | VPC004 | - | Jun 5, 11:55 UTC | Jun 5, 13:30 UTC | 1h 35m |
| 2026-06-05 | VPC004 | - | Jun 5, 09:25 UTC | Jun 5, 10:50 UTC | 1h 25m |
| 2026-06-04 | VPC004 | - | Jun 4, 07:30 UTC | Jun 4, 17:10 UTC | 9h 40m |
| 2026-06-03 | VPC004 | - | Jun 3, 15:30 UTC | Jun 3, 18:40 UTC | 3h 10m |
| 2026-06-03 | VPC004 | TLL → BRN | Jun 3, 10:50 UTC | Jun 3, 13:20 UTC | 2h 30m |
| 2026-06-03 | VPC004 | - | Jun 3, 09:20 UTC | Jun 3, 09:55 UTC | 35m |
| 2026-06-01 | VPC004 | - | Jun 1, 12:50 UTC | Jun 1, 13:25 UTC | 35m |
| 2026-06-01 | VPC004 | NCE → TLL | Jun 1, 09:15 UTC | Jun 1, 12:00 UTC | 2h 45m |
| 2026-05-30 | VPC004 | - | May 30, 22:20 UTC | May 31, 00:05 UTC | 1h 45m |
| 2026-05-30 | VPC004 | - | May 30, 08:50 UTC | May 30, 10:35 UTC | 1h 45m |
| 2026-05-29 | VPC004 | MLA → NCE | May 29, 14:10 UTC | May 29, 15:40 UTC | 1h 30m |
| 2026-05-29 | VPC004 | - | May 29, 11:45 UTC | May 29, 13:10 UTC | 1h 25m |
| 2026-05-28 | VPC004 | - | May 28, 18:30 UTC | May 28, 22:55 UTC | 4h 25m |
| 2026-05-27 | VPC004 | - | May 27, 20:50 UTC | May 28, 20:00 UTC | 23h 10m |
| 2026-05-27 | VPC004 | - | May 27, 20:05 UTC | May 28, 18:45 UTC | 22h 40m |
| 2026-05-26 | VPC004 | MLA → ZRH | May 26, 16:05 UTC | May 26, 17:59 UTC | 1h 55m |
| 2026-05-26 | VPC004 | NCE → MLA | May 26, 09:04 UTC | May 26, 10:39 UTC | 1h 35m |
| 2026-05-23 | VPC004 | TLL → NCE | May 23, 12:20 UTC | May 23, 15:10 UTC | 2h 50m |
| 2026-05-20 | VPC004 | - | May 20, 14:15 UTC | May 20, 21:15 UTC | 7h 0m |
| 2026-05-19 | VPC004 | - | May 19, 14:05 UTC | May 19, 14:35 UTC | 30m |
| 2026-05-18 | VPC004 | - | May 18, 14:50 UTC | May 19, 14:35 UTC | 23h 44m |
| 2026-05-18 | VPC004 | - | May 18, 11:30 UTC | May 18, 16:00 UTC | 4h 30m |
| 2026-05-17 | VPC004 | - | May 17, 19:50 UTC | May 17, 20:25 UTC | 35m |
| 2026-05-17 | VPC004 | - | May 17, 09:45 UTC | May 17, 11:15 UTC | 1h 30m |
| 2026-05-14 | VPC004 | TLL → PRG | May 14, 12:25 UTC | May 14, 14:10 UTC | 1h 45m |
| 2026-05-08 | VPC004 | - | May 8, 12:39 UTC | May 8, 16:35 UTC | 3h 55m |
| 2026-05-05 | VPC004 | - | May 5, 23:10 UTC | May 6, 01:01 UTC | 1h 50m |
| 2026-05-05 | VPC004 | - | May 5, 15:01 UTC | May 5, 21:10 UTC | 6h 10m |
| 2026-05-05 | VPC004 | - | May 5, 08:15 UTC | May 5, 12:20 UTC | 4h 5m |
| 2026-05-04 | VPC004 | - | May 4, 09:30 UTC | May 4, 14:25 UTC | 4h 55m |
| 2026-05-02 | VPC004 | - | May 2, 16:40 UTC | May 2, 17:05 UTC | 25m |
| 2026-05-02 | VPC004 | - | May 2, 06:00 UTC | May 2, 06:30 UTC | 30m |
| 2026-05-01 | VPC004 | TLL → DWC | May 1, 10:45 UTC | May 1, 18:00 UTC | 7h 15m |
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 ES-BTC page for operator, model, and routing details .