There's a live preview panel for exactly this reasons.
Lots of people read these forums, and many of them will simply skip over a post that is difficult to read, because it's just too large an investment of their time to try and follow a wall of badly formatted text.
If your goal is to get an answer to your questions, it's in your interest to make it as easy to read and understand as possible.
Please update your post.
You should try a simple _search using a bool query with a must array which contains a term query and a range query.
If you don't know how to do it, please share a minimal reproduction script as described in About the Elasticsearch category. It will help to better understand what you are doing. Please, try to keep the example as simple as possible.
A full reproduction script is something anyone can copy and paste in Kibana dev console, click on the run button to reproduce your use case. It will help readers to understand, reproduce and if needed fix your problem. It will also most likely help to get a faster answer.
Thanks very much for your help, I've found the problem, this part :
was the origin of the problem only because an @ was missing in @timestamp.
It's working now but there now another problem :
When I run my script at 15:31 for example, I'm only getting hits that have a @timestamp during the 15:26 minute, (31-5 = 26) but I don't get any hits between 15:26 and 15:31. It should be related to
but I don't know what is not correct with this. I'll check again the documentation about date range but if you have any idea of what could be the problem I would be glad to hear it.