Back to the log
Aircraft
EC-KRN
263 of the 304 contacts seen on this address carry an uncertain identity (corrupted frames from neighbours, flagged by the detectors). The figures on this page distinguish contacts attributable to the airframe from contacts on the address; the rarity badge is suspended.
- Mode S hex
- 3431C9
- Manufacturer
- Gulfstream Aerospace
- Serial number
- 188
- Year built
- 200818 years old
- Country of registration
Spain- First contact
- 2 May 2016, 10:08
- Last contact
- 8 Oct 2026, 12:13
- Logged visits
- 304
The station's story
- Cumulative contact time
- 127 h
- Distinct days
- 270
- Highest captured altitude
- 41,000 ft
- 263 corrupted frame(s) excluded from this maximum
- Discovery rank
- #9,274 of 60,434
- Longest contact
- 0 h 56 min
Observed callsigns
JME (226 contacts, 2018-2026) · EXU (52 contacts, 2016-2018)
Operator as per the registry of 12 Oct 2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| JME210N | route not resolved | 13 Nov 2022, 10:3413 Nov 2022 | 13 Nov 2022, 11:17 | 35,000 ft | 2,183 |
| JME210N | route not resolved | 23 Oct 2022, 18:3023 Oct 2022 | 23 Oct 2022, 18:33 | 23,000 ft | 1 |
| not transmitted | route not resolved | 22 Oct 2022, 12:2022 Oct 2022 | 22 Oct 2022, 12:34 | 34,775 ft | 25 |
| JME210N | route not resolved | 25 Sept 2022, 14:1725 Sept 2022 | 25 Sept 2022, 14:40 | 41,000 ft | 1,241 |
| JME210N | route not resolved | 23 Sept 2022, 18:0723 Sept 2022 | 23 Sept 2022, 18:39 | 40,000 ft | 1,518 |
| JME210N | route not resolved | 23 Sept 2022, 10:1923 Sept 2022 | 23 Sept 2022, 10:47 | 41,000 ft | 1,289 |
| JME210N | route not resolved | 15 Sept 2022, 20:0715 Sept 2022 | 15 Sept 2022, 20:44 | 34,000 ft | 1,735 |
| JME210N | route not resolved | 14 Sept 2022, 10:3114 Sept 2022 | 14 Sept 2022, 11:01 | 33,000 ft | 1,533 |
| JME210N | route not resolved | 27 Aug 2022, 17:4527 Aug 2022 | 27 Aug 2022, 18:30 | 41,000 ft | 2,029 |
| JME210N | route not resolved | 16 Aug 2022, 20:1816 Aug 2022 | 16 Aug 2022, 21:05 | 38,975 ft | 2,407 |
| JME210N | route not resolved | 24 Jul 2022, 13:3824 Jul 2022 | 24 Jul 2022, 14:03 | 36,000 ft | 1,253 |
| JME210N | route not resolved | 22 Jul 2022, 11:2822 Jul 2022 | 22 Jul 2022, 11:47 | 29,500 ft | 461 |
| JME210N | route not resolved | 21 Jul 2022, 15:2421 Jul 2022 | 21 Jul 2022, 15:52 | 1,175 ft | 1,475 |
| not transmitted | route not resolved | 16 Jul 2022, 18:1216 Jul 2022 | 16 Jul 2022, 18:12 | not transmitted | no position received |
| JME210N | route not resolved | 16 Jul 2022, 12:1616 Jul 2022 | 16 Jul 2022, 12:32 | 33,975 ft | 750 |
| JME210N | route not resolved | 17 Jun 2022, 18:2917 Jun 2022 | 17 Jun 2022, 18:57 | 39,025 ft | 1,212 |
| JME210N | route not resolved | 16 Jun 2022, 14:2816 Jun 2022 | 16 Jun 2022, 14:53 | 39,000 ft | 443 |
| JME210N | route not resolved | 10 Jun 2022, 13:0010 Jun 2022 | 10 Jun 2022, 13:16 | 39,000 ft | 525 |
| JME210N | route not resolved | 29 May 2022, 19:1129 May 2022 | 29 May 2022, 19:14 | 40,000 ft | 14 |
| JME210N | route not resolved | 25 May 2022, 15:4225 May 2022 | 25 May 2022, 16:14 | 34,950 ft | 959 |
| JME210N | route not resolved | 20 May 2022, 14:1020 May 2022 | 20 May 2022, 14:41 | 38,975 ft | 1,167 |
| JME210N | route not resolved | 19 May 2022, 13:1619 May 2022 | 19 May 2022, 13:45 | 19,025 ft | 716 |
| JME210N | route not resolved | 5 May 2022, 12:575 May 2022 | 5 May 2022, 13:17 | 40,000 ft | 1,126 |
| JME210N | route not resolved | 4 May 2022, 12:214 May 2022 | 4 May 2022, 12:35 | 32,000 ft | 187 |
| not transmitted | route not resolved | 29 Apr 2022, 19:0029 Apr 2022 | 29 Apr 2022, 19:00 | 37,000 ft | 13 |
