Eindhoven has ATC recordings on Live ATC. It's late here and I'm out all day tomorrow, perhaps someone could download the relevant files.
https://www.liveatc.net/archive.php?m=eheh7_twr1
This feed^ appears to be completely dead air from 1800-2400. Maybe that receiver is broken.
I am looking at the ground 3 feed (frequency 121.930)
https://www.liveatc.net/archive.php?m=eheh7_gnd
I downloaded starting at 1800 again but right at 1800Z they are already discussing the airport being closed due to drones. For the ground feed the first time I see drones mentioned is about 17:40Z, but it's when a pilot asks about the airport being closed. So it was already closed, due to some drone sighting prior to 17:40Z. Ground was talking to a pilot 24min into the 17:00Z recording, so approximately 17:24Z. A note about this is the liveatc.net recordings aren't aligned perfectly to the 00 and 30 minute boundaries so this is approximate (though within a minute or so) unless there is something else that can be used to align it (like the time a plane touched down or crossed a runway or something).
In the transcript it is clear that multiple drones are seen over an extended period of time. And, that they are seen by airport staff, including the person operating the ground radio.
I want to go through the other feeds especially the tower ones to see if there's any other information, but this is something to work with at least. I've concatenated all the .vtt subtitle files generated by whisper large-v2 and attached it as a txt file. I also put each filename ahead of each section so that you have the file it came from and the clock time it approximately starts at. (this does make it not a valid vtt subtitle file anymore).
Some selected lines (other lines interspersed between these are omitted but are in the attached txt file).
(All times are UTC)
From the 1730 file:
11:10.335 --> 11:13.500
We have some drone activities here.
30:37.847 --> 30:42.694
Well, we have some unknown drone activities above and around the airport.
30:43.775 --> 30:48.842
So we're currently checking with some specialized teams about the activities.
From the 1800 file:
03:30.513 --> 03:37.765
Ground, hello again, it's the Ryanair 93ZD, any update to the drone situation?
03:37.785 --> 03:39.027
Unfortunately not, sir.
03:39.327 --> 03:57.297
We spotted four in total at this point, and we have a team around the airport checking, and once they are not observing drones anymore, we have to discuss with the authorities if we can resume activities or not.
12:55.488 --> 13:03.700
What I can tell you is that once they don't spot any drones anymore, we have to wait for at least 15 to 30 minutes.
13:05.082 --> 13:09.309
We just got an observation of four other ones like five minutes ago.
13:10.390 --> 13:13.935
Okay, five minutes ago we had an observation that they don't show up anymore about 30 minutes.
From the 1830 file:
10:45.989 --> 10:55.501
And ground, Ryanair 93ZD, have the drones been spotted in the last 20 minutes or so?
11:02.791 --> 11:05.515
We're currently phoning with the management.
11:05.715 --> 11:10.461
The last observation was about 10 to 15 minutes ago.
12:21.393 --> 12:25.898
I just got a phone call that there's 3 observations 2-3 minutes ago.
28:46.814 --> 28:52.101
Yeah, just for your information, we're still observing drone activity around the airport.
28:57.369 --> 28:59.291
When was the last sighting now?
28:59.311 --> 29:00.192
I'm just looking at one.
29:00.713 --> 29:02.035
Oh, okay.
From the 1900 file:
14:34.960 --> 14:36.706
Any more drones?
14:36.727 --> 14:38.312
Yeah, they're still around, sir.
29:16.066 --> 29:17.590
Ryanair 19C, go ahead.
29:18.071 --> 29:20.797
Yeah, for your information, there's still observation of two drones.
From the 1930 file:
12:31.458 --> 12:36.705
Ground, Ryanair 93ZD, I assume are we still spotting drones in the area?
12:36.786 --> 12:37.851
Affirm sir.
From the 2000 file:
16:56.914 --> 16:58.336
Nothing new, right?
16:58.356 --> 17:05.027
No, we're currently phoning with the drone operations team and as soon as I've got some news I will get back to you.
28:28.207 --> 28:44.320
Yeah, just for information, we got a drone observation again like 2-3 minutes ago, and for your information, after the latest drone observation, we need to have at least 15 to 30 minutes no observations.
28:44.981 --> 28:50.726
After that, we need to do an extensive, sorry, intensive runway inspection.
28:51.226 --> 28:53.248
And after that, we can open the field again.
28:53.617 --> 28:58.226
Okay, that's copied, so you're planning on extending, if needed, the curfew?
28:59.167 --> 29:03.856
Yeah, we're in touch with the management about that.
From the 2030 file:
10:00.539 --> 10:04.485
According to my information, the latest observation was 10 minutes ago.
10:06.628 --> 10:09.913
We're in constant communication with the drone team.
10:10.231 --> 10:15.740
So every 10 minutes we're phoning each other about the latest observations.
10:16.822 --> 10:17.644
Okay, thank you.
10:18.205 --> 10:23.714
So possibly 5 to 15 minutes or so if there's no more sightings that we could possibly start.
10:25.818 --> 10:31.527
After the last observation we need at least a bracket of 15 to 30 minutes of no observations.
10:32.329 --> 10:33.150
Roger, thank you very much.
22:51.850 --> 22:56.745
Alright, 19SQ, do you have an update on the airport situation?
22:57.647 --> 23:00.717
That's negative, latest observation was 5 minutes ago.
From this log, the airport then appeared to resume departures a few minutes after 2130Z.
Ballparking from the estimated times here, drones being seen over the airport happened from ~17:40Z (or slightly earlier), to 20:47Z. This is a remarkable span of time to frequently be seeing drones. I would expect there to be tangible confirmation of there being a drone there, and there to be sensor data and a lot of camera footage. At 18:59Z the controller says they are currently looking at a drone.
