[{"data":1,"prerenderedAt":1610},["ShallowReactive",2],{"$fUKc16HfoUbfenQ3zyHNzVk3QLXdCkADlWh3m_WRwWhw":3,"$fj8HIewlzbOKbBgCEMp4UWGudJ2ackDnKXOmljQ2yEdU":156,"$f8Df_UOWXoCr9spQQ8ZFT8GoLMEekyg4zituKQ9DcI5s":674,"$fOoXAD2EM8KFJV4cStg4LccSaAo7w5tntgQLo-zziCtA":777},{"data":4},[5],{"id":6,"documentId":7,"title":8,"description":9,"slug":10,"publicationDate":11,"createdAt":12,"updatedAt":13,"publishedAt":14,"locale":15,"blocks":16,"localizations":21,"seo":62},84,"hw3vtojm2m4nv6c9slbj21e1","Telegram OSINT",null,"telegram-osint-guide","2026-06-07T14:30:00.000Z","2026-06-07T16:37:24.326Z","2026-06-08T12:55:05.952Z","2026-06-08T12:55:06.122Z","en",[17],{"__component":18,"id":19,"body":20},"shared.rich-text",2849,"Welcome, dear readers!\nToday, we're exploring Telegram from an OSINT perspective. More specifically, how to search for information, people, and connections within the platform and, more importantly, how to actually find them.\n\nTelegram can be viewed in many ways. However, it’s hard to argue with the fact that it has firmly established its own niche and is widely regarded as a convenient tool. It is also equally obvious that a massive amount of information circulates within Telegram. And wherever information exists, OSINT investigators tend to follow. In the background, you will often encounter discussions about free software, anonymity, and other somewhat mythologized concepts. In most cases, the best approach is simply to agree and move on rather than engage in endless debates.\n\nThis article will not focus on Telegram’s anonymity or security aspects. First, because that is not the purpose of this text. Second, because the topic has already been discussed, analyzed, and debated extensively across articles, videos, and talks, and it is probably long past the point where anything truly new can be added at a general level.\n\nHowever, there are still several aspects worth examining through an OSINT lens. In fact, it makes sense to cover them at the very beginning, since they represent the basic mechanics of how the platform works from an investigative perspective.\n\n## Phone Number\n- - -\n\nIf you register your phone number in Telegram, that fact is publicly discoverable by default. To check whether a specific number is associated with a Telegram account, you can simply save the number, for example in your Saved Messages, and then tap on it. If the number is registered in Telegram, you will see an option such as “View Profile”.\n\nThis method will not work if the user has disabled the ability to be found by phone number in their privacy settings. However, in practice, relatively few users change this setting, and the check itself takes very little time. For this reason, it is generally recommended to verify it whenever possible.\n\n![Telegram OSINT_Phone_Number](https://cdn.osintflow.com/39/42/Telegram_OSINT_Phone_Number_b158aa4a0f.webp)\n\nUnfortunately, this does not work in the opposite direction either. In other words, knowing a Telegram account does not allow you to view the associated phone number. The only exception is if the user has made their number visible to everyone in their privacy settings. However, accounts will be discussed separately.\n\n## Telegram ID\n- - -\n\nUsernames, bot names, channel names, and chat titles in Telegram are not permanent and can be changed as many times as needed. Moreover, phone numbers can also be changed multiple times. However, in order to keep track of who is who, Telegram uses identifiers known as Telegram IDs.\n\nA Telegram ID is a unique numeric identifier assigned to a user at the moment of registration, and it cannot be changed. The most common way to find someone’s ID is by using dedicated bots designed for this purpose. For example, one of the most widely used ones is:\n\n[https://t.me/telesint_channel​](https://t.me/telesint_channel).\n\nWe send the bot a username or a channel or chat name, and in response we receive the corresponding ID. This is of course quite simple, but if you need to work with Telegram identifiers more often than just once, constantly switching to a bot becomes inconvenient.\n\n![TelegramID](https://cdn.osintflow.com/39/42/Telegram_ID_b86a9aec59.webp)\n\nMoreover, Telegram itself does not hide these IDs from the system. They are simply not shown by default because they are not needed by most users most of the time.\n\nThis can be easily changed. In the desktop application, go to Settings and then open Advanced settings. At the very bottom, you will find Experimental settings. There, locate and enable “Show Peer IDs in Profile”. After that, IDs will appear in the profiles of channels, chats, bots, and users. From there, they can be easily copied when needed.\n\n![Telegram_ID](https://cdn.osintflow.com/39/42/Telegram_ID_39d179277c.webp)\n\nSometimes you may need to find out the creation date of a specific account. The simplest way to do this is to send the bot \u003Chttps://t.me/creationdatebot> the ID of the target user. \n\n## Nickname\n- - -\n\nTelegram users have two types of names, and both are optional. The first is the “First name / Last name” field. This is what you typically see in contact lists and chats. It can contain anything, and there is no requirement for uniqueness. As a result, it usually carries little to no reliable identifying value. There are exceptions, of course, such as cases where a real first and last name are used, but this is always context-dependent and should be assessed individually.\n\nThe second is the username, which starts with “@”. Although it is commonly referred to as a nickname, it effectively functions as a unique identifier within Telegram. No two users can have the same username, although it can be changed at any time.\n\nThis uniqueness allows us to quickly verify whether a username exists. You simply add “@” in front of the username, save it in Telegram Saved Messages, for example, and try to open it.\n\nIn addition, you can format the username as a link in the form https://t.me/USERNAME and open it in a browser. If it redirects you to the main Telegram website page, it means the user does not exist. If the user exists, it will open their profile and prompt you to continue in the app or web version.\n\nLinks in this format are not limited to user profiles. Channels, chats, and bots also use the same structure. As a result, the same method can be applied to them as well.\n\nIn addition, these links are indexed by Google, which means they can also be found using the site: search operator, for example: site: `site:t.me dstoun`\n\n![Nickname](https://cdn.osintflow.com/39/42/Nickname_e9562b2e23.webp)\n\nThe same approach can also be used in reverse. If we know a Telegram account and see that it uses a fairly unique username, we can try to search for other accounts across social networks or other platforms. For a quick overview, Google can be used. For a more structured and in-depth search, tools such as https://whatsmyname.app/ can be helpful.\n\nIn general, username-based search is a topic on its own. There is a separate article covering the nuances of this process and offering different approaches and methods. If you haven’t read it yet, it is worth checking out.\n\n> Among the suggested tools, I would add (or even replace them with)\nhttps://github.com/soxoj/maigret. This is a case where the implementation is genuinely well done. First, it is capable of checking a large number of sources. Second, it generates a convenient report with the results. At the same time, it collects a significant amount of useful information from found accounts, including profile photos.\n\n\n## Telegram User De-anonymization\n- - -\n\nAll of the above is, in most cases, used to determine the real identity of a person behind a Telegram account. This is a very common task in OSINT investigations. The main issue is that there is no universal method for de-anonymizing Telegram users. Likewise, there is no fixed algorithm that guarantees results.\n\nMoreover, if a person intentionally tries to stay hidden and has at least a basic understanding of operational security, the chances of successfully identifying them are, to put it mildly, quite low. However, this is not a reason not to try.\n\nLet’s now look at how this can be approached in practice.\n\n## Telegram Bots\n- - -\n\nThe first thing worth trying, simply because it is fast, is checking information through bots that aggregate data from leaks and compromised databases. There are many such bots, but the main issue is that they tend to disappear over time, meaning they are periodically removed by Telegram. However, they usually reappear later under new links. \n\nIn my experience, some of the more effective ones, meaning those with the largest databases, include  [OsintKit](https://osintkit.net/), [Глаз Бога](https://draco.eog.bz/), and [Horus](https://t.me/horusteam_officiall), which tend to provide decent results at a relatively reasonable cost. Another well-known service is [Himera Search](https://himera-search.net/).\n\nIt generally performs well, but in my opinion, the pricing is not justified. Overall, it comes down to personal preference, and everyone chooses the tools they find most convenient.\n\nWe check information in such bots because there is a possibility that they may reveal a person’s phone number or other data based on an ID or username. I think this is fairly straightforward.\n\n## Profile analysis\n- - -\n\nThe next step, even if it seems obvious, is to carefully examine the account. More precisely, the content it contains. This means not just looking at it quickly, but assessing how unique the data published by the user is and how useful it may be for our objectives.\n\nIn some cases, before deciding how to work with this data, it is also important to understand how reliable it is. This is not always an easy task because there is a possibility that we are dealing with Sock Puppets.\n\n> Sock Puppets — are fake accounts created to protect \n> identity. Хor those who missed it, there is an article and video on the topic:\n> https://hacker-basement.com/2023/08/01/feikovie-akaunti-v-osint-sock-pupets/\n\nWhen we come across a profile photo, full name, username, or any other details in an account description, the first step is to verify each piece of information individually.\n\nHow do we approach this? If we have additional context or external sources that can be cross-referenced with the account, this is the most effective option and should be used first. If no such context is available, each element should be analyzed on its own and then compared against the rest. We repeat this process until we either find reliable matches or conclude that the information is being used in a misleading way.\n\nWe come across a profile picture showing a person, but we cannot yet confirm whether it actually belongs to the person of interest. The next step is to take this image and analyze it. We try to determine who appears in the photo or where else it has been used online. If a donor account was used to build a fake profile, there is a possibility of tracing it back to its original source. If the image is authentic, this approach can also help us collect additional information about the individual.\n\nAdditionally, we also pay attention to what else is visible in the photo besides the person. This can help assess its credibility or provide extra context. For example, if we know that the person of interest lives in Paris and the background of the photo also shows Paris, this supports the assumption that the image is likely authentic.\n\nWe apply the same approach to any other information in the account. We examine it, look for matches, analyze it, and compare it with other available data. Based on this, we decide whether it is relevant for our purposes or not.\n\n## User activity\n- - -\n\nAnalyzing profile information and data from bots does not always lead to the results we need. In addition, the task may be more specific than basic data collection. For this reason, it can be useful to examine the groups and chats the user participates in. This often provides additional context, as people tend to engage in thematic communities.\n\nFor example, if a person is active in a city-related chat, it is reasonable to assume they may have some connection to that place. Interest-based groups can also reveal hobbies or personal preferences. This information can be useful for understanding the person of interest, especially if future interaction is planned. Shared communities and awareness of interests can significantly improve the ability to establish contact and maintain communication.\n\nIt is also important not only to identify the groups an account belongs to, but also to analyze the content the user posts there. This can be valuable, as useful information may be contained in their messages. There is no need to manually scroll through entire conversations, since most chats allow you to search and filter all messages from a specific user.\n\n![Telegram_groups](https://cdn.osintflow.com/39/42/groups_43b50896e3.webp)\n\nThe main question in such a situation is how to identify the groups and chats a user is a member of. This typically has to be done using third-party resources. In addition, if higher-quality results are required, it may also involve using paid tools or services.\n\nHere, once again, I’ll suggest a few options, and everyone can choose the one that suits them best:\n\n► https://www.telegramdb.org - There is a website with an integrated bot. You can use either the bot directly or the website interface, but in both cases you will ultimately be redirected to the bot. The free version only allows searches for chats by keywords and user accounts by username. It can also find groups if a user is mentioned in the group description.\n\nBy making a small payment, you gain access to more advanced functionality, including searching for groups and chats a user is or has been part of. The service has a large and continuously expanding database of both users and communities.\n\nOne of the main advantages is that you can check for available results before paying, which lets you see whether the target account appears in any groups and how extensive the data coverage is.\n\n► https://tgdev.io/tgscan — It is similar to the previous one, but it does not offer any free functionality at all, except for showing the number of results found. At the same time, it also has a fairly large database that is constantly being updated.\n\nOne useful feature is that it shows in the results when the user last posted in a group, which can help assess how active they are.\n\n►https://t.me/where_a_person_wrote_bot (Their channel in case the bot is removed: https://t.me/where_a_person_wrote) — a free bot with a smaller database, but it still delivers reasonably good results. Among free tools, this one is quite reliable and can be used effectively.\n\nOverall conclusions regarding investigating individuals: as mentioned earlier, there is no single formula for success. Instead, there is a systematic approach that may lead to results, although it is not guaranteed, as everything depends on the specific situation.\n\nIn short, this approach is based on collecting all available information by any means possible. We then analyze it, enrich it where we can, and cross-check the data. The process is driven by two main objectives: first, to verify or disprove the reliability of the information, and second, to establish whether the data actually belongs to a specific individual.\n\n## Telegram information gathering\n- - -\n\nWith investigating individuals, I think we have more or less covered the basics. Now we move on to another, no less common direction, namely information gathering in Telegram. In my opinion, this process is more creative than investigating individuals. However, this does not change the fact that its effectiveness largely depends on a systematic approach.\n\nWhat does this mean? It means that the first step is to clearly define what exactly we are looking for and in what form we expect to find it. In other words, we need to understand the end goal. Only then can we plan our actions in reverse. Based on a clear understanding of what we are searching for, we can determine what form that information might take and, consequently, which methods are best suited for finding it.\n\n## Telegram built-in search\n- - -\n\nIt is worth taking a moment to discuss Telegram’s built-in search feature. There is a common belief that it is completely useless. However, this is not entirely accurate. While it is, to put it mildly, not well suited for broad searches, it works quite effectively when used within channels and groups you are already subscribed to.\n\nIn other words, if you have an idea of which channels may contain the information you are looking for, you can subscribe to them and use the internal search to look for specific keywords. This becomes even more effective if you use a separate account for this purpose and periodically clean it when starting a new topic. In such a setup, the built-in search can perform quite reliably.\n\nHowever, it is important to note that Telegram’s internal search is only truly useful when you already know exactly which channels or groups you want to search within. In all other cases, its effectiveness is significantly limited.\n\n## Telegram channels and groups search\n- - -\n\nIn most cases, searching for and collecting information in Telegram comes down to identifying the channels and groups where that information is actually published. This is quite logical, because once we know which group contains the information we need, finding it there is usually straightforward. The real question is how to find these channels and groups effectively, since there is more than one approach.\n\nThe method we choose mainly depends on how well we understand the topic we are working with. If we have no prior knowledge and need to build a basic understanding of the subject while getting familiar with relevant channels, the simplest option is often to start with Google. For example:\n\n`site:t.me/* (\"osint\" OR \"intelligence\")`\n\nIn this context, we understand that all Telegram objects have links in the format `t.me/` followed by some string of characters. Accordingly, we narrow our search to items that contain links of this type. In brackets, we can include any number of keywords or combinations of them. This is a broad search approach that helps us quickly get an overview of the topic.\n\nAnother less obvious aspect related to links concerns invitation links for groups, chats, or channels. These links are often unique, which makes it possible to track their public distribution simply by searching for an exact match. Such links usually look like this: `https://t.me/+randomstringofcharacters`. . Everything after the “+” can be taken in quotes and searched to find where it has been published.\n\nThe method described above can be loosely called a “search everywhere” approach. It works well in two situations: when we are looking for something quite unique, or when we are not yet sure what exactly we need and are exploring the topic broadly. In other, more intermediate cases, it is usually better to narrow the focus in some way.\n\nSometimes it also makes sense to search through channel names. In some cases, administrators choose names that clearly reflect or hint at the channel’s topic. This can be especially useful when looking for thematic groups. It can also help in situations where a private corporate chat has accidentally been left public. This happens more often than you might think.\n\n`site:t.me/* intitle:osint`\n\nFor this purpose, as in the example above, we use the intitle: operator and include something that is likely to appear in the name of a channel or chat. This can be a keyword related to the topic, or, if we are looking for a company’s channel, it can be the company name or part of its name.\n\n## Telegram search engines\n- - -\n\nAnother universal way to search in Telegram is by using search engines specifically designed for Telegram content.\n\nIn this context, I often see people recommend lyzem.com. I have to say I find this somewhat confusing, as I cannot tell whether I am using it incorrectly or whether those recommending it have never actually tested it in real-world scenarios. Despite multiple attempts, it has never produced any meaningful results in practice. Out of curiosity, I also checked the documentation, assuming I might be missing some functionality. It turns out that this tool does not index group content, only group descriptions.\n\nIn practice, lyzem.com is only useful for giving the impression of doing thorough research, or for showing that all possible options have been explored, even when no real results are expected. In any other case, there is little reason to use it, as it does not serve this purpose effectively. This brief note is meant to save time for anyone exploring the topic independently. Now we can move on to tools that actually work. At present, the most effective option is custom search engines built on Google CSE.\n\nFirst of all, Telegago:\n\n► \u003Chttps://cse.google.com/cse?&cx=006368593537057042503:efxu7xprihg>\n\n![Telegago](https://cdn.osintflow.com/39/42/Telegago_24668f3150.webp)\n\nIt searches through post content, as well as channel names and descriptions. It can also be used to find channels, users, bots, and chats. The next option has a slightly smaller coverage of sources, but still provides fairly solid search results.\n\n► \u003Chttps://cse.google.com/cse?cx=004805129374225513871:p8lhfo0g3hg>\n\nIt searches channel names and descriptions, as well as post content. It can also find user profiles and articles on telegra.ph.\n\nIf, like me, you prefer to run both search engines from a single place, this can be done using \u003Chttps://intelx.io/tools?tab=telegram> .\n\nAnother useful alternative for searching is \u003Chttps://tgfind.org/> —  it allows keyword-based searches within channel posts over a specified time period.\n\n## Telegram channel directories\n- - -\n\nReturning to the search for channels and groups, all the previously mentioned methods are relevant here as well, including Google, Telegram’s built-in search, and specialized search engines. However, another equally versatile and sometimes even more effective approach is using Telegram channel directories.\n\nThese directories often provide additional analytics, statistics, and other useful metadata about channels. In some cases, they may also show posts that have been deleted from a channel, which can be valuable for understanding its history and activity patterns.\n\nThese tools are primarily designed for advertising analytics and related use cases. However, as is often the case, marketing-oriented tools tend to work quite well for OSINT purposes as well, and Telegram is no exception.\n\nThere are quite a few such channel directories available. I am highlighting the ones that I personally find the most convenient to use.\n\n► \u003Chttps://telemetr.io>\nThe standard functionality here is searching by channel name. The name does not necessarily have to be entered exactly as it is.\n\nAnother useful tool, telemetr.io, is its post search feature. It allows searching by keywords or phrases. The results can be filtered by language, country, and category. However, the way categories are assigned in these directories is often quite inconsistent, so it is generally better to ignore this filter. In the free version, post search is limited to content from the last 7 days.\n\n![telemetr](https://cdn.osintflow.com/39/42/telemetr_4f40e7075d.webp)\n\nAnother useful feature available here is mention tracking across channels and chats. It allows you to monitor both specific phrases and mentions of channels. The free version includes one active tracking query.\n\nThe setup is quite simple. You enter the phrase you want to track and, if needed, specify a phrase to exclude. Then you define the scope of monitoring. You can search across Telegram in general or limit it to specific channels. It is also possible to exclude certain channels from tracking.\n\nAdditionally, if needed, you can enable bot notifications, which can be quite convenient in some cases.\n\n► \u003Chttps://uk.tgstat.com>\nThis is also a channel directory, but with a few additional nuances. It offers a more advanced search for channels, including filters based on channel statistics such as subscriber count or channel age. It is also quite convenient that you can search not only by channel name, but also by description.\n\nThe statistics themselves are not necessarily of primary interest, but there are some useful features. For example, it is possible to view the history of username changes, as well as changes to a channel’s name and description. It also supports finding related channels, for instance when the same contact accounts are listed in their descriptions.\n\nPost search is available as well, but using filters requires a paid subscription. Without filters, it returns a very large number of posts, which are often difficult to work with in practice.\n\n## Telegram Wayback Machine\n- - -\n\nChannel directories are useful and convenient, but they also have limitations. For example, a channel may be deleted, and even within directories, images are not always preserved. A post might also contain a video that gets removed later. In such cases, even if a deleted post can still be found in a directory, there is no way to access the original video. Or at least that may seem to be the case.\n\nIn situations like this, it is worth knowing that since 2022 the  [Wayback Machine](https://web.archive.org/) has been archiving Telegram in the same way it archives regular websites. It does this by creating a separate collection for Telegram(\u003Chttps://web.archive.org/collection-search/telegram>).\n\nThis is not the most convenient tool to use, but given the lack of alternatives, we have to work with what is available.\n\n![Telegram_Wayback_Machine](https://cdn.osintflow.com/39/42/Telegram_Wayback_Machine_6ebe1ebe0f.webp)\n\nTo start searching, you need to go to the main page, open the Collection Search section, enter a keyword or phrase, select the relevant collection, and run the search.\n\nIn most cases, this will return several thousand results, which can then be further filtered by date. Guidance on how to do this is usually provided on the results page. For each entry, you can also view the earliest and latest snapshots, if they are available. There is also typically a link to the original post.\n\nOverall, if you need to find deleted content and no other options are available, it is worth checking the Internet Archive. It is a slow and somewhat tedious process, but as a last-resort tool, it can sometimes produce results.\n\n## Parsing Telegram channels and groups\n- - -\n\nOften, we do not need a specific piece of information from a single post. Instead, we may need to analyze an entire channel, a network of channels, or track an event that has been covered by a channel over a period of time. In other words, the goal is not a single post, but a broader set of content within a specific timeframe.\n\nManually browsing channels and reviewing content is possible, but it is not the most efficient approach from a productivity standpoint. Let’s look at how this process can be optimized.\n\nIf we want to avoid working directly in Telegram, the first step is to extract all available data. This can be done in several ways, so I will go over two optimal approaches depending on the type of task.\n\n**First option**. This is done using the Telegram desktop application. Open the required channel, click the three dots in the upper right corner, and select “Export chat history.” An export window will appear, where you can choose what type of content you want to export, the format for downloading it, and other related settings.\n\n![Telegram_Parsing](https://cdn.osintflow.com/39/42/Telegram_Parsing_f5a77f16ce.webp)\n\nThis method is best suited for cases where you need to download not only text messages, but also images, videos, and other types of content.\n\n**Second option.**. This involves using [TG collector](https://www.tgcollector.com/).. In this case, it is not possible to download images and videos, but you can export a batch of channels or chats at once, which can save a significant amount of time. If an image or video is needed from a chat, a link is provided, so you can simply open Telegram and retrieve it there.\n\nTo authorize TG collector, you will need a Telegram API key. To obtain it, go to [my.telegram.org](https://my.telegram.org/apps) and log in using your phone number.It is strongly recommended to use a separate account for this purpose, ideally one that you do not mind using for experimental or OSINT-related tasks. In general, maintaining separate accounts for such activities is a good practice. Next, create a new application by entering any placeholder details, and then obtain your API ID and API Hash.\n\nNow we can move on to exporting channels. First, we create a new collection (1), then add links to the channels or chats we need (2), which will appear in the list. After adding them, we select (3) the ones we want to export and click (4) “Collect messages.” Then we just need to wait a bit, depending on how many items we added and how much data they contain.\n\n![TG_collector](https://cdn.osintflow.com/39/42/TG_collector_c73eef580a.webp)\n\nOnce everything has been exported, we can go to the “Collected messages” tab (5). There, after selecting either JSON or CSV as the format, we can download the data.\n\n## Analyzing exported data. Google Pinpoint\n- - -\n\nWe have downloaded the data and stored it for further use. However, to actually make it useful, it still needs to be analyzed in line with our goals and objectives. Of course, this could be done manually, but in that case, exporting it would not make much sense. Instead, we will take a more efficient approach and use [Google Pinpoint](https://journaliststudio.google.com/pinpoint/). It is a highly effective tool for this type of analysis.\n\nIn Pinpoint, we need to create a new collection and upload our files into it. You can simply drag and drop an entire folder, and the system will automatically organize everything. After that, depending on the volume of data, we will need to wait while the analysis is processed. Once it is complete, we can start working with the content.\n\nA major advantage of Pinpoint is its flexibility. It supports documents, images, and videos. If there is any text content, it will detect and extract it. For videos, it can also generate transcripts of the audio. In addition, Pinpoint automatically identifies mentions in all cases, including people, organizations, and locations. These are displayed in the panel on the right. Any of these entities, or their combinations, can be used as filters. There is also an option to filter by date.\n\nStandard filters are useful, but they are never enough on their own. That is why manual search is also available. It supports quotation marks for exact matches, a minus sign to exclude unwanted keywords, and the OR operator to combine queries. These search options can also be combined with Pinpoint’s built-in filters, such as entity mentions.\n\nBut that is not all. Since this is a Google product, it also includes built-in Gemini integration, which can assist with analysis. In some cases, quite significantly. For example, it can generate summaries, perform calculations, identify relevant mentions, and support various other analytical tasks depending on the need.\n\n![Google_Pinpoint](https://cdn.osintflow.com/39/42/Google_Pinpoint_37ae4ca1c6.webp)\n\nIn addition, to make navigation easier, we can assign labels to documents and files. This involves defining a name for each label and selecting a color. These labels are visible in the overall file list and also appear in the filter panel. As a result, they can be used as filters to view only the documents marked with a specific label.\n\nWe can also open any file and highlight specific text fragments. On images, text can be selected in the same way as in regular documents. Once a fragment is highlighted, a link is automatically generated, which can be copied, or we can simply copy the selected text itself. Inside an open document, there is also a built-in search function, as well as the option to assign a label directly to the file.\n\nOverall, the idea is fairly straightforward. The exact workflow depends on the specific goal, but in general Google Pinpoint can significantly save time and effort, making the analysis of channels or chats much more convenient and efficient.\n\nFinally, there is one more tool that is situational, but can still be useful. If a chat administrator has not restricted access to the list of participants, it is possible to export that list. For this purpose, there is a dedicated bot available (link to the website in case the bot becomes unavailable):\n[https://pocketdetective-terms-and-conditions.mі.canva.site](https://t.me/PocketDetective_bot)\n\n\u003Chttps://t.me/PocketDetective_bot>\n\n## Final thoughts\n- - -\n\nI believe that, based on the information provided, it should now be clearer how Telegram can be used to search for and gather the information you need. At the same time, it is important to understand that I have only outlined a set of methods and approaches that may produce results. However, the final outcome always depends on you and the actions you take in a specific situation.\n\nIt depends on which methods you choose, how you combine them, and, perhaps most importantly, how you analyze the information you obtain. Ultimately, these factors determine the results you will achieve.\n",[22],{"id":23,"documentId":7,"title":24,"description":9,"slug":10,"publicationDate":25,"createdAt":26,"updatedAt":27,"publishedAt":28,"locale":29,"blocks":30,"authors":34,"seo":35,"localizations":60},81,"OSINT в Telegram","2025-03-04T00:01:00.000Z","2025-07-12T11:05:53.531Z","2026-06-08T12:45:00.372Z","2026-06-08T12:45:00.548Z","uk",[31],{"__component":18,"id":32,"body":33},2846,"Вітаю, шановне панство. Сьогодні про Telegram. А точніше про те, як там щось чи когось шукати і, що важливо, знаходити. До Telegram можна ставитися як завгодно. Але безглуздо сперечатися з тим, що він зайняв свою нішу і що він дуже зручний у використанні. Ну і не менш очевидний факт у тому, що в Telegram обертається величезний обсяг інформації. А якщо десь є інформація, то десь поруч труться осінтери. Там ще, як правило, десь на фоні завивають адепти культу «невловимого Джо». На предмет вільного програмного забезпечення, анонімності та інших міфологічних явищ. Але з ними, найголовніше, з усім погоджуватись і не сперечатися.\n\nМи в цій статті не будемо розглядати тему анонімності та безпеки Telegram. По-перше, стаття не про це, по-друге на цю тему вже сказано, написано і знято відосів стільки що, скажімо прямо, пора вже розібратися. Але при цьому деякі моменти через призму OSINT розглянути потрібно. До того ж розглянути на початку т.я. це, скажімо так, базові механіки.\n\n## Номер телефону\n- - -\n\nЯкщо ти зареєстрував свій номер у Telegram то за замовчуванням цей факт є загальнодоступним. Щоб перевірити чи зареєстрований обліковий запис на якийсь номер, зберігаємо цей номер, наприклад, у Обране, там тиснемо на нього і, якщо номер зареєстрований у Telegram, ми побачимо кнопку «Показати профіль». Це не спрацює, якщо людина в налаштуваннях конфіденційності відключила можливість шукати її за номером. Але, як показує практика, мало хто це робить, а часу така перевірка займає небагато. Тому краще завжди перевіряти.\n\n![Telegram OSINT_Phone_Number](https://cdn.osintflow.com/39/42/Telegram_OSINT_Phone_Number_b158aa4a0f.webp)\n\nНу і на жаль, у зворотний бік це теж не працює. Тобто знаючи акаунт подивитися номер не можна. Тільки якщо людина залишила його видимим для всіх. Але про акаунти поговоримо окремо.\n\n## Telegram ID\n- - -\n\nІмена користувачів, ботів, назви каналів та чатів у Telegram це штука не постійна і змінювати їх можна скільки завгодно разів. Більше того, номер телефону теж можна змінювати скільки завгодно разів. Але розуміти, хто є хто, якось потрібно, тому в телеграмі є ідентифікатори — Telegram ID. Це унікальний цифровий ідентифікатор, який надається користувачеві в момент реєстрації і його неможливо змінити.\n\nНайпоширеніший спосіб дізнатися чийсь ID це використання ботів, заточених під це. Наприклад, напевно, найпоширеніший:\n[https://t.me/telesint_channel​](https://t.me/telesint_channel).\nСкидаємо йому ім'я користувача або назву каналу або чату, у відповідь отримуємо ID. Це звичайно досить просто, але якщо доводиться працювати з ідентифікаторами Telegram трохи частіше ніж один раз, то бігати постійно в бота це не дуже зручно.\n\n![TelegramID](https://cdn.osintflow.com/39/42/Telegram_ID_b86a9aec59.webp)\n\nТим більше, що сам Telegram ці ID ні від кого не приховує. Просто потрібні вони не всім і не завжди, тому він їх за замовчуванням не показує. Це не важко змінити. У десктопному додатку йдемо в \"Налаштування\", там вибираємо \"Просунуті налаштування\". У них, в самому низу, є «Експериментальні налаштування». Там знаходимо і вмикаємо «Show Peer IDs in Profile».\nТепер в описі каналів, чатів, ботів та користувачів з'явиться їхній ID. Звідти можна зручно копіювати.\n\n![Telegram_ID](https://cdn.osintflow.com/39/42/Telegram_ID_39d179277c.webp)\n\nІноді може статися ситуація, коли тобі знадобиться дізнатися дату створення якогось облікового запису. Найпростіший спосіб це зробити - це надіслати боту \u003Chttps://t.me/creationdatebot> ID потрібного користувача.\n\n## Нікнейм\n- - -\n\nІмен у користувача в Telegram в наявності два. І обидва не є обов'язковими для заповнення. Одне у форматі Ім'я/Прізвище, саме його ми бачимо у списку контактів та чатів. Вписати туди можна все, що завгодно. Якихось вимог до унікальності теж немає. Тому, як правило, якогось смислового навантаження воно теж не несе.\nБувають звичайно винятки, наприклад, там може бути реальне прізвище та ім'я. Але це все ситуативно, і тут потрібно дивитися за контекстом та ситуацією.\n\nДруге ім'я, це те, що починається з @. Хоч це і нікнейм, але за своєю суттю це ще й унікальне посилання на обліковий запис. І відповідно їх не може бути двох однакових. Але його теж можна будь-якої миті змінити. Унікальність цього посилання дає нам можливість перевірити, чи існує відповідний користувач. Беремо будь-який потрібний нікнейм, додаємо @ на початок, зберігаємо це, наприклад, в папку Обране в самому клієнті Telegram, і пробуємо перейти\n\nКрім того, можна записати це ім'я у вигляді посилання:`https://t.me/USERNAME` і відкрити у браузері. Якщо перекине на головну сторінку телеграмівського сайту, то такого користувача немає. Якщо користувач є, покаже його профіль і запропонує перейти до програми або веб-версії.\n\nПосилання такого формату мають не тільки профілі користувачів, а й канали, чати та боти. Відповідно все те саме можна робити і з ними.\n\nКрім того, ці посилання індексуються Google, а значить їх можна знаходити, використовуючи оператор site: `site:t.me dstoun`\n\n![Nickname](https://cdn.osintflow.com/39/42/Nickname_e9562b2e23.webp)\n\nУ зворотний бік це також можна використовувати. Тобто якщо ми знаємо обліковий запис Telegram і бачимо, що там досить унікальний нікнейм, можна спробувати пошукати інші облікові записи, в соцмережах або ще десь. Можна через Google, якщо потрібно швидко зорієнтуватися. Або можна подивитися на https://whatsmyname.app/, там можна пошукати більш комплексно та вдумливо.\nВзагалі, на тему пошуку за нікнеймом є окрема СТАТТЯ. Там розглянуто нюанси цього процесу та запропоновано варіанти як це можна робити. Хто не читав, можна ознайомитись, зайвим не буде.\n\n> До запропонованих там утиліт я б додав (або взагалі замінив)\nhttps://github.com/soxoj/maigret. Це той випадок, коли пряме добре зроблено. По-перше вміє перевіряти безліч джерел. По-друге, робить зручний звіт з результатами. При цьому збираючи зі знайдених облікових записів купу корисної інформації, включаючи фото профілю.\n\n## Деанон користувача Telegram\n\n- - -\n\nВсе перераховане вище, в більшості випадків, необхідно нам для того щоб дізнатися реальну особистість людини, яка використовує аккаунт. Це сама по собі дуже поширена задача. Проблема в тому, що якогось універсального способу деанону користувачів телеграма не існує. Так само як і не існує якогось алгоритму дій, що гарантує результат. Більше того, якщо людина вирішила сховатися і вона не дебіл, шанси знайти її, скажімо прямо, не надто великі. Але це не привід не пробувати. А як саме і що пробувати, давай розбиратися.\n\n## Боти в Telegram\n- - -\n\nПерше що варто спробувати, просто тому що це швидко, це глянути інфу, по ботах що агрегують інформацію з витоків та злитих баз. Таких ботів існує багато, але проблема у тому, що вони періодично відлітають, тобто видаляються телеграмом.\nАле потім знову з'являються вже з новим посиланням. Найбільш толкові, тобто мають найбільшу базу, як на мене, це [OsintKit](https://osintkit.net/), [Глаз Бога](https://draco.eog.bz/), [Horus](https://t.me/horusteam_officiall) — це те, що дає непоганий результат за цілком розумні гроші. Є ще, багатьом відома, [Himera Search](https://himera-search.net/).\nШукає звичайно не погано, але цінник, як на мене, не адекватний. Загалом, все це справа смаку, кому що подобається те і використовуємо.\n\nІнфу в подібних ботах ми перевіряємо, тому що є вирогідність, що нам по ID або юзернейму покаже телефон або інші дані людини. Тут я думаю все має бути зрозумілим.\n\n## Аналіз профілю\n- - -\n\nНаступне, що потрібно зробити, як би очевидно це не прозвучало, це потрібно уважно подивитися на обліковий запис. Точніше на його наповнення. Не просто подивитися, звичайно, а оцінити унікальність, опублікованих користувачем даних. Ну і їх корисність для подальшого використання в наших цілях.\n\nКрім того, в деяких випадках, для того щоб оцінити і зрозуміти, що робити далі з цими даними, в першу чергу, потрібно зрозуміти наскільки це достовірна інформація. І ось це не завжди просте завдання. Тому що є ймовірність, що ми маємо справу з тими самими Sock Puppets.\n\n> Sock Puppets — фейковий обліковий запис, створений з метою захисту\n> особистості. Хто пропустив, на цю тему є стаття та відео:\n> https://hacker-basement.com/2023/08/01/feikovie-akaunti-v-osint-sock-pupets/\n\nВідповідно, побачивши фотографію профілю, прізвище та ім'я, нікнейм, якусь іншу інформацію з опису, перше, що ми повинні зробити, це перевірити достовірність цієї інформації. Кожної з цих інформацій.\n\nЯк це зробити? Якщо у нас є якийсь контекст або якась додаткова інформація з інших джерел, з якою ми можемо зіставити дані облікового запису, це чудово, так і робимо. Якщо такого немає, доведеться вивчати кожен елемент окремо, а потім зіставляти їх між собою. І так поки не знайдемо те, що потрібно, або поки не зрозуміємо, що нас намагаються ввести в оману.\n\nПриклад. Ми бачимо фотографію профілю. Допустимо там зображено якусь людину. Але, при цьому, ми не знаємо, чи це наш фігурант на фото. Відповідно беремо це фото та починаємо з ним працювати. Пробуємо знайти того, хто там зображений, або пробуємо знайти де ще зустрічалася ця фотографія. Тому що, якщо для створення фейку використовувався донорський обліковий запис, то є ймовірність, що вдасться його знайти. Якщо ж фото справжнє, то в такий спосіб ми ще й якусь додаткову інформацію про фігуранта можемо зібрати.\n\nКрім того звертаємо увагу, на те що ще зображено на фотографії, крім людини. Це також може допомогти оцінити достовірність, або дати додаткову інформацію. Наприклад, якщо ми знаємо, що фігурант живе в Парижі, а на фотографії, на фоні у людини теж Париж. Це плюс на користь того, що фото справжнє.\n\nРівно так само робимо з будь-якою іншою інформацією з облікового запису. Вивчаємо, шукаємо збіги, аналізуємо, порівнюємо з іншою наявною інформацією та приймаємо рішення: потрібно воно нам чи ні.\n\n## Активність користувача\n- - -\n\nАналіз інформації з профілю та даних з ботів, на жаль, далеко не завжди дає потрібний нам результат. Крім того, перед нами може стояти трохи більш специфічне завдання, ніж банальний збір даних. Тому іноді є сенс пошукати групи та чати у яких состоїть наш юзер. Це саме собою може дати додаткову інформацію, т.я. людина може перебувати та спілкуватися у якихось тематичних групах.\n\nТак, наприклад, якщо людина спілкується в чаті якогось міста, логічно припустити, що вона може мати відношення до цього міста. А групи за інтересами можуть дати уявлення про його хобі або захоплення. Це може бути корисно для розуміння особистості фігуранта, особливо якщо ми в майбутньому плануємо з ним взаємодіяти. Наявність спільного чату та розуміння інтересів це практично безпрограшний варіант налагодження контакту та подальшого спілкування.\n\nКрім того, що варто ознайомитися з групами в яких перебуває акаунт, що цікавить нас, не менш важливо ознайомиться і з тим, що він там пише. Це важливо з тих самих причин. Там може бути цінна інформація. Крутити всю стрічку не потрібно, в будь-якому чаті можна через пошук, знайти всі повідомлення конкретного користувача.\n\n![Telegram_groups](https://cdn.osintflow.com/39/42/groups_43b50896e3.webp)\n\nНайголовніше питання, що постає в подібній ситуації, це як знайти групи та чати в яких перебуває користувач. Робити це доведеться через сторонні ресурси, більше того, якщо хочеш, щоб було дійсно якісно, ​доведеться ще й пару доларів занести.\n\nТут, знову ж таки, запропоную кілька варіантів, а кожен сам вибере, що йому до вподоби:\n\n► https://www.telegramdb.org - Сайт, там же є бот. Можна шукати відразу в боті, можна через сайт, але потім все одно перекине в бот. Безкоштовно шукає тільки чати за ключовими словами, а також облікові записи користувачів по юзернейму.\n\nЯкщо користувач зазначений в описі групи, він таку групу теж знайде. Якщо занести пару доларів, можна знаходити групи та чати в яких перебуває або перебував користувач. Дуже велика база як користувачів, так і чатів із групами, причому вона постійно поповнюється. Дуже великий плюс у тому, що перед тим як заносити та витрачати гроші, ти можеш подивитися чи взагалі є якісь результати і в скількох групах знайдений потрібний акаунт.\n\n► https://tgdev.io/tgscan — приблизно те саме, що й попередній, але взагалі немає безкоштовних функцій, лише кількість знайдених результатів. При цьому база теж досить велика і постійно поповнюється. Зі зручних фішок, прикольно те що він у результатах показує коли останній раз користувач щось писав у групі.\n\n►https://t.me/where_a_person_wrote_bot (їх канал у разі видалення бота: https://t.me/where_a_person_wrote)- Безкоштовний бот з менш великою базою, але при цьому дає цілком гідні результати. З безкоштовних, цей дуже непоганий, можна використовувати.\n\nЗагалом, як висновки щодо пошуку людей. Як я вже казав, єдиного рецепту успіху не існує. Існує системний підхід, який може дати результат. А може й не дати. Все залежить від конкретної ситуації. А суть цього підходу, якщо стисло, у тому, що ми будь-якими доступними способами збираємо всю доступну інформацію. Аналізуємо її, доповнюємо та порівнюємо дані між собою. При цьому прагнемо вирішити два завдання. Перше це підтвердити чи спростувати достовірність інформації. А друге це визначити належність цих даних до тієї чи іншої особи.\n\n## Пошук інформації в Telegram\n- - -\n\nЗ пошуком людей, гадаю, більш-менш розібралися. Тепер переходимо до іншого, не менш поширеного напрямку. А саме пошук та збирання інформації в Telegram. Як на мене, цей процес більш творчий, ніж пошук людей. Тим не менш, це не скасовує того факту, що ефективність у цій ситуації, більшою мірою залежить від системності підходу.\n\nЩо це означає? Те, що в першу чергу потрібно чітко сформулювати, що саме і в якому вигляді ми хочемо знайти. Тобто зрозуміти кінцеву мету. І вже тоді, від зворотного, планувати наші дії. Тому що виходячи з розуміння того, що ми шукаємо, ми, відповідно, розуміємо в якому вигляді це може бути, а значить розуміємо яким способом це шукати.\n\n## Вбудований пошук\n- - -\n\nОкремо треба сказати кілька слів про вбудований пошук телеграма. Є думка, що він абсолютно марний. Це не зовсім так. Так, він, м'яко кажучи, не дуже зручний для пошуку загалом. Але він досить непогано справляється при пошуку по каналам та групами на які ми підписані.\n\nТобто, якщо є розуміння в яких каналах може бути опублікована інформація, що нас цікавить, ми на них підписуємося і, використовуючи внутрішній пошук, шукаємо за ключовими словами. А якщо для цих цілей ще й окремий обліковий запис завести, щоб можна було його чистити щоразу, коли починаємо нову тему, то буде взагалі непогано. І вбудований пошук цілком буде відпрацьовувати.\n\nАле, на жаль, вбудований пошук можна використовувати лише тоді, коли ми точно розуміємо по яким каналам і групам ми хочемо шукати. У решті випадків результ\n\n## Пошук каналів та груп у Telegram\n- - -\n\nСуть пошуку та збору інформації в Telegram, в більшості випадків, зводиться до пошуку каналів та груп, де ця інформація є. Це логічно, тому що якщо ми знаємо в якій групі опубліковано потрібну нам інформацію, то там знайти її взагалі не проблема. А тому давай розбиратися, як їх краще шукати. Тому що способів це робити, скажімо так, більше одного.\n\nТе який підхід до пошуку інформації вибрати, в основному залежить від того, наскільки добре ми орієнтуємося в темі що вивчається. Якщо взагалі не орієнтуємось і потрібно створити якесь базове розуміння питання та ознайомиться з тематичними каналами, то найкращим вибором буде просто загуглити. Наприклад так:\n\n`site:t.me/* (\"osint\" OR \"intelligence\")`\n\nУ цій ситуації ми розуміємо, що всі об'єкти в Telegram мають посилання формату `t.me/` і потім якийсь набір символів. Відповідно ми обмежуємо пошук об'єктами, що мають посилання подібного виду. При цьому в дужках ми вказуємо будь-яку кількість ключових слів чи їх комбінацій. Це максимально узагальнений спосіб пошуку, що дозволяє зорієнтуватися в темі, що вивчається.\n\nЩе один не очевидний момент, пов'язаний із посиланнями. Для запрошення до груп, чатів або каналів можуть використовуватися унікальні посилання. Ця унікальність дає можливість відстежити їхнє публічне поширення, просто використовуючи пошук за точним збігом. Такі посилання мають формат: `https://t.me/+якийсьрандомнийнабірсимволів` . Ось це все, що після плюса, беремо в лапки і шукаємо, де воно було опубліковано.\n\nОписаний трохи вище спосіб пошуку, умовно, можна назвати «шукаємо все і скрізь». Він добре працює у двох випадках. Коли ми шукаємо щось досить унікальне або коли ми не дуже розуміємо, що нам потрібно, а тому вивчаємо все підряд. У решті, тобто якихось середніх ситуаціях, краще все ж таки якось звужувати поле пошуку.\n\nІноді є сенс пошукати у назвах каналів. Т.я. буває адміни називають канал так, щоб назва натякала на тематику. Особливо непогано це працює для пошуку якихось тематичних груп. Ну або якщо якийсь свій корпоративний чатик забули зробити закритим. Таке також буває.\n\n`site:t.me/* intitle:osint`\n\nДля цього, як у цьому прикладі, ми в операторі intitle: вписує щось таке, що потенційно може міститися в назві каналу або чату. Це може бути ключове слово на тему каналу або якщо ми шукаємо, наприклад канал якоїсь компанії, це може бути її назва, або якась частина назви.\n\n## Пошукові системи Telegram\n- - -\n\nЩе один універсальний спосіб шукати в Telegram це використання пошукових систем заточених під Telegram.\n\nНа цю тему, я часто бачу, що деякі особи рекомендують використовувати lyzem.com. І ось тут я збентежений, бо не можу зрозуміти: або я якось не так ним користуюся, або ті, хто його радять, самі ніколи його не пробували використовувати. Тому що скільки б я не намагався, в реальних ситуаціях цей шматочок жодного разу не видав нічого хоч скільки-небудь схожого на нормальний результат. Більше того, щиро вірячи, що є якась фішка, просто я її не знаю, я навіть сходив подивитися матчасть. І з'ясував, що ця штука взагалі не індексує вміст груп, лише їх опис. Коротше, використовувати lyzem.com можна лише задля імітації обсягу роботи та позамежної\nзайнятості тобто, коли потрібно показати, що ми спробували все що могли, але, на жаль, нічого не вийшло. У решті випадків не варто туди навіть заходити, воно не працює. Це був невеликий відступ, щоб заощадити час тим, хто розбиратиметься в темі самостійно. Тепер переходимо до робочих пошукових систем. І тут, на даний момент, оптимальний варіант – це кастомні пошукові системи створені на основі Google CSE.\n\nНасамперед Telegago:\n\n► \u003Chttps://cse.google.com/cse?&cx=006368593537057042503:efxu7xprihg>\n\n![Telegago](https://cdn.osintflow.com/39/42/Telegago_24668f3150.webp)\n\nШукає за вмістом постів, назв та описів, також може шукати як канали, так і користувачів, ботів і чати. Наступний варіант трохи менше за охопленням джерел, але теж шукає досить не\nпогано.\n\n► \u003Chttps://cse.google.com/cse?cx=004805129374225513871:p8lhfo0g3hg>\n\nШукає за назвами та описом каналів, за вмістом постів. Вміє шукати профілі користувачів та статті в telegra.ph.\n\nЯкщо комусь, як мені, більше подобається щоб обидва пошукові системи запускалися з одного місця, це можна робити з \u003Chttps://intelx.io/tools?tab=telegram> .\n\nТакож іноді, як альтернативний варіант пошуку, може бути корисний \u003Chttps://tgfind.org/> — пошук за ключовими словами у публікаціях каналів за вказаний проміжок часу.\n\n## Каталоги каналів Telegram\n- - -\n\nПовертаючись до пошуку каналів чи груп. У цій ситуації працюють усі перелічені вище способи пошуку. А саме Google, вбудований пошук самого месенджера, пошукові системи тощо. Але не менш універсальний, а іноді навіть результативніший спосіб шукати канали, це каталоги цих самих каналів. Там, як правило, є ще й усяка аналітика, статистика і взагалі все, що хочеш. До речі, якщо потрібно дізнатися, які пости видалялися з якогось каналу, там це теж можна побачити.\n\nЦе все створено для всілякої рекламної аналітики, і всього, що з цим пов'язано. Але так вже склалося, що майже завжди рекламні інструменти дуже непогано працюють для цілей OSINT. І Telegram не є винятком.\n\nЦих каталогів каналів існує чимало. Я показую ті, які особисто мені здаються зручнішими.\n\n► \u003Chttps://telemetr.io>\nСтандартний функціонал тут, це пошук за назвою каналу. Назву не обов'язкововводити точно.\n\nЩе один корисний інструмент telemetr.io, який гідно працює, це пошук постів. Шукає за ключовими словами чи фразами. Знайдені результати можна відфільтрувати за мовою, країною та категорією. Але розподіл категорій працює дуже загадково у цих каталогах, тому, як на мене, краще взагалі пропускати цей пункт. За часом, у безкоштовній версії шукає пости лише за останні 7 днів.\n\n![telemetr](https://cdn.osintflow.com/39/42/telemetr_4f40e7075d.webp)\n\nЩе одна корисна штука, яка тут є, це відстеження згадок у каналах та чатах. Можна відстежувати як появу якихось фраз, так і згадки каналів. Безкоштовна версія доступна за одним таким відстеженням.\n\nПрацює дуже просто. Вводимо фразу, яка нас цікавить, якщо треба вказуємо яку фразу потрібно пропускати. Потім вказуємо, де саме шукати. Можна в цілому по Telegram, а можна в конкретних каналах. Також непотрібні канали можна виключити із відстеження. Ну і якщо є бажання, можна підключити повідомлення в боті, що теж іноді зручно.\n\n► \u003Chttps://uk.tgstat.com>\nЦе теж каталог, але із деякими своїми нюансами. Тут трохи наворочений пошук каналів. Можна шукати з урахуванням статистики каналу, наприклад, кількості підписників або віку каналу. Також, що дуже зручно, можна шукати не лише за назвою, а й за описом.\n\nСама статистика нас навряд цікавитиме, але є корисні фішки. Наприклад можна переглянути історію змін нікнейма користувача, назви та описи каналу. Також він вміє шукати пов'язані канали, наприклад, якщо в описі вказані однакові акаунти для зв'язку. Пошук за публікаціями тут теж є, але щоб використовувати фільтри потрібно купувати підписку. А без фільтрів знайде безліч постів, розібрати які буде практично не реально.\n\n## Telegram Wayback Machine\n- - -\n\nКаталоги це добре та зручно. Але є нюанс. Наприклад, якщо канал видалили. Та й самі фото не завжди зберігаються у каталогах. Або, наприклад, у якомусь каналі було відео і його видалили. Відповідно, навіть якщо ми знайдемо в каталозі видалений пост, подивитися відео не буде жодної можливості. Або так лише здається. У подібних ситуаціях потрібно знати що [Wayback Machine](https://web.archive.org/) починаючи з 2022 року, архівує Telegram, так само як вони архівують звичайні сайти. Просто створюючи окрему колекцію під Telegram (\u003Chttps://web.archive.org/collection-search/telegram>).\n\nЦе, звичайно, не найзручніша у використанні штука, але, враховуючи що вибирати нема з чого, доведеться працювати з тим, що є.\n\n![Telegram_Wayback_Machine](https://cdn.osintflow.com/39/42/Telegram_Wayback_Machine_6ebe1ebe0f.webp)\n\nЩоб почати шукати, потрібно на головній сторінці, у розділі Collection Search, ввести потрібне ключове слово чи фразу, вибрати колекцію та натиснути пошук.\n\nШвидше за все в такому варіанті ми отримаємо кілька тисяч результатів, які потім можна додатково відфільтровувати. За датами, наприклад. Підказка, як це зробити буде на сторінці з результатами. Також по кожному результату ми можемо подивитися найраніші та останні знімки (якщо вони були звичайно). Також буде посилання на оригінал повідомлення.\n\nЗагалом, якщо потрібно знайти якийсь видалений контент і інших варіантів немає, то варто спробувати поритися в Інтернет Архіві. Так, це довго і нудно, але як інструмент останнього шансу може спрацювати.\n\n## Парсинг каналів та груп\n- - -\n\nЧасто буває, що нам потрібна не якась точкова інформація з якогось конкретного посту. А треба вивчити загалом канал. Або сітку каналів. Або вивчити якусь подію, про яку автор каналу деякий час щось писав. Коротше може бути таке, що нам потрібен більше ніж один пост, при цьому ще й за якийсь проміжок часу.\n\nКрутити канали вручну та вивчати інформацію, звичайно можна. Але це не оптимальний варіант з точки зору продуктивності. Розберемо, як цей процес оптимізувати.\n\nОчевидно, що якщо ми не хочемо працювати з самим додатком Telegram, то для початку потрібно скачати всю інформацію. Зробити це можна кількома способами. Я покажу два оптимальні, під різні завдання.\n\n**Перший**. Це з десктопного додатку Telegram. Заходимо в потрібний канал, там у верхньому правому кутку тиснемо на три крапки і вибираємо «Експорт історії чату». З'явиться вікно експорту, в якому потрібно вибрати який контент нас цікавить і в якому форматі качати, та й інші нюанси.\n\n![Telegram_Parsing](https://cdn.osintflow.com/39/42/Telegram_Parsing_f5a77f16ce.webp)\n\nЦей спосіб оптимальний, якщо потрібно скачати не тільки текстові повідомлення, але і картинки, і відео, і все інше.\n\n**Другий**. Це використання [TG collector](https://www.tgcollector.com/). У цьому варіанті качати зображення та відео не можна, зате можна скачати відразу пачку каналів або чатів. Що іноді дуже заощаджує час. Ну а якщо буде потрібна картинка або відео з чату, там буде посилання і можна сходити в додаток телеграма та забрати там.\n\nЩоб авторизуватися в TG collector, знадобиться API Telegram. Для його отримання йдемо на [my.telegram.org](https://my.telegram.org/apps). Там авторизуємось зі свого номера. При чому, дуже рекомендую, про всяк випадок, використовувати обліковий запис який взагалі не шкода. Та й взагалі, під всі ці осінтерські справи потрібно мати окремі облікові записи. Я думаю це очевидно. Далі ми створюємо новий додаток, ввівши будь-які рандомні дані, та забираємо API ID та API Hash.\n\nТепер можемо переходити до викачування каналів. Для початку створюємо нову колекцію (1), потім додаємо посилання на потрібні нам канали або чати (2), вони з'являтимуться у списку. Після їх додавання, вибираеэмо (3) ті які потрібно викачати і тиснемо (4) Collect messages. Ну і треба буде трохи почекати, залежно від того, скільки і чого ми додали.\n\n![TG_collector](https://cdn.osintflow.com/39/42/TG_collector_c73eef580a.webp)\n\nКоли все вивантажиться, ми зможемо перейти на вкладку Collected messages (5). І там, попередньо вибравши формат JSON або CSV, завантажити все собі.\n\n## Аналіз вивантаженої інформації. Google Pinpoint\n- - -\n\nІнформацію ми завантажили. І навіть кудись її собі поклали, тобто зафіксували. Ось тільки, щоб з цього всього, був якийсь толк, її потрібно якось ще й проаналізувати, з урахуванням наших поставлених цілей та намічених завдань. Можна звичайно ручками, але тоді нашо ми її качали? Ми підемо більш оптимальним шляхом і будемо використовувати [Google Pinpoint](https://journaliststudio.google.com/pinpoint/). Тому що це майже ідеальний інструмент для таких завдань.\n\nУ Pinpoint нам потрібно створити нову колекцію про додати туди наші файли. Можна просто перетягнути всю папку, воно саме розбереться. Після чого, залежно від обсягу інформації, потрібно буде трохи почекати, поки закінчиться аналіз. І можна починати з усім цим розбиратися.\n\nВеликий плюс Pinpoint у тому, що він всеїдний. Документи, фотографії, відео – не важливо. Якщо десь є текст, він його знайде і розпізнає. А по відео ще й стенограму звуку зробить. За деякими даними, Pinpoint проводить аналіз у всіх випадках. А саме, він робить добірку згадок щодо людей, організацій та місць. Ці згадки ми побачимо на панелі праворуч. Будь-яке з них, їх комбінацій, можна використовувати як фільтр. Там також можна додати фільтр за датою.\n\nСтандартні фільтри це добре. Але їх завжди мало. Тому тут можна шукати потрібну інформацію в ручну. У пошуку працюють лапки для отримання точного збігу, мінус щоб прибрати не потрібні ключові слова та оператор OR для поєднання запитів. Ну і відповідно ми можемо комбінувати наші запити з тими фільтрами, які створимв сам Pinpoint. Тобто згадками людей, організацій чи місць.\n\nАле це ще не все. Так як це гугловська історія, то тут, передбачувано є вбудований Gemini. Що теж може допомогти щось поаналізувати. При чому іноді допомогти дуже не слабо. Наприклад зробити якусь вибірку, щось порахувати, знайти згадку про щось. І так далі, на що вистачить фантазії.\n\n![Google_Pinpoint](https://cdn.osintflow.com/39/42/Google_Pinpoint_37ae4ca1c6.webp)\n\nКрім того, щоб нам було легше орієнтуватися, ми можемо надавати документам та файлам ярлики. Попередньо придумавши їм назву та обравши колір. Ці ярлики буде видно у загальному списку файлів, а також вони з'являться у списку фільтрів. Ну, і, відповідно, їх теж можна використовувати як фільтри, щоб шукати тільки за тими документами, які ми помітили.\n\nТакож ми можемо відкрити будь-який файл і там виділити будь-який фрагмент тексту. Причому на фотографіях текст виділяється так само, як і в друкованих документах. На виділений фрагмент автоматично буде створено посилання, яке ми можемо скопіювати собі. Або можемо скопіювати виділений текст. При цьому у самому відкритому документі також є можливість текстового пошуку. І можливість привласнити самому документу ярлик.\n\nЗагалом, я гадаю, сенс зрозумілий. Конкретний набір дій залежить від намічених цілей, але сам по собі Google Pinpoint може дуже заощадити час і зусилля, зробивши аналіз якихось каналів або чатів набагато комфортніше і зручніше.\n\nНу і насамкінець. Теж ситуативна штука, але може стати в нагоді. Якщо адмін чату не закрив доступ до списку учасників, можна завантажити цей список учасників чату. Для цього є спеціальний бот (даю посилання на сайт, якщо бот відлетить):\n[https://pocketdetective-terms-and-conditions.mі.canva.site](https://t.me/PocketDetective_bot)\n\n\u003Chttps://t.me/PocketDetective_bot>\n\n## Загалом\n- - -\n\nЯ думаю, з урахуванням викладеної інформації, стало зрозуміліше, як і що можна пробувати робити в Telegram, щоб знайти якусь потрібну інформацію. Але, при цьому, я думаю, ти розумієш, що я просто перерахував ті способи та методи, які можуть давати результат. Але кінцевий успіх, у будь-якому разі, залежить від тебе та твоїх дій у конкретній ситуації. Від того які методи ти вибереш, як їх скомбінуєш і, напевно найважливіше, як проаналізуєш отриману інформацію залежатиме, який результат ти отримаєш.\n",[],{"id":36,"metaTitle":24,"metaDescription":37,"keywords":38,"metaRobots":39,"metaViewport":40,"canonicalURL":41,"structuredData":42},370,"Гайд з OSINT у Telegram: інструменти та підходи для пошуку і аналізу інформації.","Телеграм ОСІНТ, телеграм групи, ідентифікатори Телеграм, telegram osint, osint telegram, telegram investigation, telegram analysis, telegram information gathering, telegram search, telegram channel search, telegram group search, telegram tools","index, follow","width=device-width, initial-scale=1","https://osintflow.com/educational/telegram-osint-guide",{"url":43,"@type":44,"author":45,"@context":48,"headline":49,"keywords":50,"publisher":51,"inLanguage":53,"description":54,"dateModified":55,"datePublished":56,"articleSection":57,"mainEntityOfPage":58},"https://osintflow.com/educational/telegram-osint-guide/","Article",{"name":46,"@type":47},"OsintFlow","Organization","https://schema.org","Telegram OSINT. Посібник з розслідувань у Telegram","Telegram OSINT, OSINT, Telegram, розслідування в Telegram, пошук у Telegram, Telegram ID, Telegram канали, Telegram групи, SOCMINT, Open Source Intelligence, цифрові розслідування, аналіз Telegram",{"url":52,"name":46,"@type":47},"https://osintflow.com","uk-UA","Практичний посібник з Telegram OSINT: пошук користувачів, каналів, груп, аналіз профілів, Telegram ID, інструменти та методи збору інформації.","2026-06-08","2025-03-04","OSINT",{"@id":43,"@type":59},"WebPage",[61],{"id":6,"documentId":7,"title":8,"description":9,"slug":10,"publicationDate":11,"createdAt":12,"updatedAt":13,"publishedAt":14,"locale":15},{"id":63,"metaTitle":8,"metaDescription":64,"keywords":65,"metaRobots":39,"metaViewport":40,"canonicalURL":66,"structuredData":67,"openGraph":76,"metaImage":119},373,"Telegram OSINT guide: practical tools and approaches for searching and analyzing information.","telegram osint, telegram osint guide, osint telegram, telegram investigation, telegram analysis, telegram information gathering, telegram search, telegram channel search, telegram group search, telegram tools, telegram data collection, telegram intelligence, telegram search engines, tg collector, google pinpoint osint, telemetr.io, telegago","https://osintflow.com/en/educational/telegram-osint-guide/",{"url":68,"@type":44,"author":69,"@context":48,"headline":70,"keywords":71,"publisher":72,"inLanguage":15,"description":73,"dateModified":55,"datePublished":55,"articleSection":74,"mainEntityOfPage":75},"https://osintflow.com/en/educational/telegram-osint-guide",{"name":46,"@type":47},"Telegram OSINT Guide","Telegram OSINT, Telegram investigation, Telegram search, Telegram search operators, OSINT, SOCMINT, Telegram channels, Telegram groups, Telegram username search, Telegram ID lookup, Telegram intelligence, Telegram OSINT tools, digital investigations, social media intelligence",{"url":52,"name":46,"@type":47},"Learn how to conduct Telegram OSINT investigations using search operators, usernames, IDs, channels, groups, bots, directories, and intelligence tools.","Educational",{"@id":68,"@type":59},{"id":77,"ogTitle":8,"ogDescription":64,"ogUrl":66,"ogType":78,"ogImage":79},240,"article",{"id":80,"documentId":81,"name":82,"alternativeText":83,"caption":83,"width":84,"height":85,"formats":86,"hash":113,"ext":88,"mime":91,"size":114,"url":115,"previewUrl":9,"provider":116,"provider_metadata":9,"createdAt":117,"updatedAt":117,"publishedAt":118},1979,"i0zbe0d8olk2d46y4wcvs8oz","telegram osint.webp","telegram osint",1280,720,{"large":87,"medium":97,"thumbnail":105},{"ext":88,"url":89,"hash":90,"mime":91,"name":92,"path":9,"size":93,"width":94,"height":95,"sizeInBytes":96},".webp","https://cdn.osintflow.com/large_telegram_osint_ff50ab5c0c.webp","large_telegram_osint_ff50ab5c0c","image/webp","large_telegram osint.webp",100.63,1200,675,100632,{"ext":88,"url":98,"hash":99,"mime":91,"name":100,"path":9,"size":101,"width":102,"height":103,"sizeInBytes":104},"https://cdn.osintflow.com/medium_telegram_osint_ff50ab5c0c.webp","medium_telegram_osint_ff50ab5c0c","medium_telegram osint.webp",27.66,600,338,27662,{"ext":88,"url":106,"hash":107,"mime":91,"name":108,"path":9,"size":109,"width":110,"height":111,"sizeInBytes":112},"https://cdn.osintflow.com/thumbnail_telegram_osint_ff50ab5c0c.webp","thumbnail_telegram_osint_ff50ab5c0c","thumbnail_telegram osint.webp",6.6,245,138,6600,"telegram_osint_ff50ab5c0c",96.18,"https://cdn.osintflow.com/39/telegram_osint_ff50ab5c0c.webp","strapi-provider-cloudflare-r2","2026-06-07T19:11:27.920Z","2026-06-07T19:11:27.921Z",{"id":80,"documentId":81,"name":82,"alternativeText":83,"caption":83,"width":84,"height":85,"formats":120,"hash":113,"ext":88,"mime":91,"size":114,"url":115,"previewUrl":9,"provider":116,"provider_metadata":9,"createdAt":117,"updatedAt":117,"publishedAt":118,"related":124},{"large":121,"medium":122,"thumbnail":123},{"ext":88,"url":89,"hash":90,"mime":91,"name":92,"path":9,"size":93,"width":94,"height":95,"sizeInBytes":96},{"ext":88,"url":98,"hash":99,"mime":91,"name":100,"path":9,"size":101,"width":102,"height":103,"sizeInBytes":104},{"ext":88,"url":106,"hash":107,"mime":91,"name":108,"path":9,"size":109,"width":110,"height":111,"sizeInBytes":112},[125,128,135,137,142,144,150,151],{"__type":126,"id":127,"ogTitle":24,"ogDescription":37,"ogUrl":41,"ogType":78},"shared.open-graph",212,{"__type":129,"id":130,"metaTitle":24,"metaDescription":37,"keywords":38,"metaRobots":39,"metaViewport":40,"canonicalURL":41,"structuredData":131},"shared.seo",345,{"url":43,"@type":44,"author":132,"@context":48,"headline":49,"keywords":50,"publisher":133,"inLanguage":53,"description":54,"dateModified":55,"datePublished":56,"articleSection":57,"mainEntityOfPage":134},{"name":46,"@type":47},{"url":52,"name":46,"@type":47},{"@id":43,"@type":59},{"__type":126,"id":136,"ogTitle":24,"ogDescription":37,"ogUrl":41,"ogType":78},237,{"__type":129,"id":36,"metaTitle":24,"metaDescription":37,"keywords":38,"metaRobots":39,"metaViewport":40,"canonicalURL":41,"structuredData":138},{"url":43,"@type":44,"author":139,"@context":48,"headline":49,"keywords":50,"publisher":140,"inLanguage":53,"description":54,"dateModified":55,"datePublished":56,"articleSection":57,"mainEntityOfPage":141},{"name":46,"@type":47},{"url":52,"name":46,"@type":47},{"@id":43,"@type":59},{"__type":126,"id":143,"ogTitle":8,"ogDescription":64,"ogUrl":66,"ogType":78},214,{"__type":129,"id":145,"metaTitle":8,"metaDescription":64,"keywords":65,"metaRobots":39,"metaViewport":40,"canonicalURL":66,"structuredData":146},347,{"url":68,"@type":44,"author":147,"@context":48,"headline":70,"keywords":71,"publisher":148,"inLanguage":15,"description":73,"dateModified":55,"datePublished":55,"articleSection":74,"mainEntityOfPage":149},{"name":46,"@type":47},{"url":52,"name":46,"@type":47},{"@id":68,"@type":59},{"__type":126,"id":77,"ogTitle":8,"ogDescription":64,"ogUrl":66,"ogType":78},{"__type":129,"id":63,"metaTitle":8,"metaDescription":64,"keywords":65,"metaRobots":39,"metaViewport":40,"canonicalURL":66,"structuredData":152},{"url":68,"@type":44,"author":153,"@context":48,"headline":70,"keywords":71,"publisher":154,"inLanguage":15,"description":73,"dateModified":55,"datePublished":55,"articleSection":74,"mainEntityOfPage":155},{"name":46,"@type":47},{"url":52,"name":46,"@type":47},{"@id":68,"@type":59},{"data":157,"meta":670},[158,290,394,491,573],{"id":159,"documentId":160,"title":161,"description":162,"slug":163,"publicationDate":164,"createdAt":165,"updatedAt":166,"publishedAt":167,"locale":15,"cover":168,"authors":195,"category":202,"blocks":210,"tags":231,"seo":254,"localizations":280},841,"sas4xivbu83h1yfgo3m43m06","Russian Armed Forces UAV Operator Involved in the War Against Ukraine","Maria Viktorovna Krupoderova (сallsign: \"Kino\") is a UAV operator serving with the FSB Border Service in Russia's Rostov Region and has received multiple FSB awards for participation in military operations during Russia's war against Ukraine.","krupoderova-russian-uav-operator","2026-06-04T09:15:00.000Z","2026-06-02T13:29:35.805Z","2026-06-05T12:51:05.015Z","2026-06-05T12:51:05.290Z",{"id":169,"documentId":170,"name":171,"alternativeText":172,"caption":172,"width":173,"height":174,"formats":175,"hash":190,"ext":88,"mime":91,"size":191,"url":192,"previewUrl":9,"provider":116,"provider_metadata":9,"createdAt":193,"updatedAt":193,"publishedAt":194},1976,"npzbe55d9lzt4ntpilhjrx4t","круподерова путін_обкладинка.webp","круподерова_фсб_оператор БПЛА",960,576,{"medium":176,"thumbnail":183},{"ext":88,"url":177,"hash":178,"mime":91,"name":179,"path":9,"size":180,"width":102,"height":181,"sizeInBytes":182},"https://cdn.osintflow.com/medium_krupoderova_putin_obkladinka_df698f50e3.webp","medium_krupoderova_putin_obkladinka_df698f50e3","medium_круподерова путін_обкладинка.webp",28.82,360,28820,{"ext":88,"url":184,"hash":185,"mime":91,"name":186,"path":9,"size":187,"width":110,"height":188,"sizeInBytes":189},"https://cdn.osintflow.com/thumbnail_krupoderova_putin_obkladinka_df698f50e3.webp","thumbnail_krupoderova_putin_obkladinka_df698f50e3","thumbnail_круподерова путін_обкладинка.webp",8.07,147,8066,"krupoderova_putin_obkladinka_df698f50e3",59.82,"https://cdn.osintflow.com/38/krupoderova_putin_obkladinka_df698f50e3.webp","2026-06-02T11:43:59.870Z","2026-06-02T11:43:59.871Z",[196],{"id":197,"documentId":198,"name":199,"email":9,"createdAt":200,"updatedAt":200,"publishedAt":201},9,"mzdy1tgc523oe1lb6gm2vpcr","Nick Bell","2026-03-03T01:35:51.852Z","2026-03-03T01:35:51.847Z",{"id":203,"documentId":204,"name":205,"slug":206,"description":9,"createdAt":207,"updatedAt":208,"publishedAt":209,"locale":15},6,"a8dzci9uwkqli6fs8qjd4fu0","Investigations","investigations","2025-07-12T11:03:34.691Z","2026-01-29T01:31:46.466Z","2026-01-29T01:31:46.420Z",[211,214,218,221,224,226,229],{"__component":18,"id":212,"body":213},2804,"Maryia Viktorivna Krupoderova (call sign “Kino”) is reported to be an active participant in the Russian Federation’s armed aggression against Ukraine and to serve as a UAV (unmanned aerial vehicle) operator. She is stated to be serving in the Border Guard Service of the FSB of the Russian Federation in the Rostov Region and to have received three medals as well as a commendation from the FSB for participation in military operations.\n\n![Згадки ТГ Круподерова](https://cdn.osintflow.com/38/tg_b1caae61b2.webp)\n\nHer social media accounts reportedly contain material suggesting involvement in combat operations, including references to activity in the temporarily occupied territories of Ukraine (including Avdiivka) and in active conflict zones, such as the Kursk region. She is also reported to have been present in the Kursk region since 07.08.2024.\n\n![круподерова-авдіївка](https://cdn.osintflow.com/38/krupoderova_avdiyivka_82215532ce.webp)\n\nHer Telegram channel («девичье приграничье») is also reported to contain photo and video materials depicting so-called “trophies” allegedly taken from the bodies of fallen servicemen of the Armed Forces of Ukraine.\n![круподерова_фото шевронів.](https://cdn.osintflow.com/38/krupoderova_foto_shevroniv_b01840c9f3.webp)\n\nKrupoderova is reported to have received three medals and a commendation from the Border Guard Service of the FSB for participation in military operations. Public references to UAV-related activities, as well as content linked to occupied territories (Avdiivka) and the Kursk region, are cited as indications of her active involvement in the Russian Federation’s armed aggression against Ukraine.\n\n![круподерова-нагороди](https://cdn.osintflow.com/38/krupoderova_nagorodi_34d3b8830c.webp)\n\nAccording to data from [OsintKit](https://osintkit.net/), Maria’s military service reportedly began in 2018, when she was assigned as a UAV operator. On 19 April 2024, she publicly confirmed that she was serving in this role.",{"__component":215,"id":216,"content":217},"shared.person-card",2770,"**Personal data**\n**Full name: Krupoderova Maria Viktorovna**\nDate of birth: 25.07.2004\nPassport: 6018375076\nTIN (INN): 741806910509\nSNILS: 16546771298\nKnown addresses:\nRostov-on-Don, Siversa St., 20\nRostov-on-Don, Magnitogorskaya St., 9/2\nTroitsk, Kultury St., 8A, Apt. 54\n\n**Contacts:**\nPhone numbers: +79287766010 (active): +78632563842\nTelegram: https://t.me/+79287766010\nWhatsApp: https://wa.me/+79287766010\nVKontakte: https://vk.com/id323567172; https://archive.is/mc9HH\nInstagram: www.instagram.com/krupoderovaaaaa (http://www.instagram.com/krupoderovaaaaa)\nTikTok: https://www.tiktok.com/@bbymaryboo\nhttps://archive.is/3ZwfA\nEmails: \nmariatehnik@yandex.ru\nmariatehniiik@yandex.ru\nhotspot-shop@mail.ru\n\n**Media mentions:**\n https://uralpress.ru/news/novyy-glava-troicka-dmitriy-gatov-vernulsya-v-mirnuyu-zhizn-iz-zony-svo",{"__component":219,"id":220},"shared.slider",510,{"__component":215,"id":222,"content":223},2771,"**Personal data. Mother**\n**Full name: Krupoderova Natalya Aleksandrovna**\nDate of birth: 24.10.1975\nPassport: 7009096278\nTIN (INN): 710304982844\nKnown addresses: Tula, Puzakova St., 76, Apt. 142\n\n**Contacts:**\nPhone number: +79207660984\nVKontakte: https://vk.com/id148919703, https://archive.is/BmJ5q\nOdnoklassniki: https://ok.ru/profile/459711544356, https://archive.is/fT3IQ\nFacebook: https://facebook.com/profile.php/?id=100004035420441, https://archive.is/9D5EG\nInstagram: https://www.instagram.com/nataliakrupoderova1975\nEmail: n.a.k.1975@mail.ru",{"__component":219,"id":225},511,{"__component":215,"id":227,"content":228},2772,"**Personal data. Sister**\n**Full name: Krupoderova Yulia Viktorovna**\nDate of birth: 08.07.2002\nPassport: 6017000700\nTIN (INN): 741805589000\nKnown addresses: \nRostov-on-Don, Siversa St., 20\nTroitsk, Kultury St., 8A, Apt. 54\n\n**Contacts:**\nPhone number: +79207475956\nWhatsApp: https://wa.me/+79207475956\nTelegram: https://t.me/+79207475956\nVKontakte: https://vk.com/id344539872 https://archive.ph/FIF2u\nEmail: yulyashasssss@gmail.com",{"__component":219,"id":230},512,[232,239,247],{"id":233,"documentId":234,"name":235,"slug":235,"createdAt":236,"updatedAt":237,"publishedAt":238},28,"zdk0ugj9cf5cwxdcqq8zqgpj","russia","2025-07-12T11:02:30.832Z","2026-01-19T14:53:50.578Z","2026-01-19T14:53:50.519Z",{"id":240,"documentId":241,"name":242,"slug":243,"createdAt":244,"updatedAt":245,"publishedAt":246},55,"n9kln95qsaz6cnvhihi9s7at","Osint Profile","osint-profile","2026-01-13T17:09:00.199Z","2026-01-19T12:21:44.598Z","2026-01-19T12:21:44.534Z",{"id":248,"documentId":249,"name":250,"slug":250,"createdAt":251,"updatedAt":252,"publishedAt":253},27,"tdkx24l2orx9b5jcc8cgfy1d","deanon","2025-07-12T11:02:30.823Z","2026-01-13T20:43:31.982Z","2026-01-13T20:43:31.933Z",{"id":255,"metaTitle":256,"metaDescription":161,"keywords":257,"metaRobots":39,"metaViewport":40,"canonicalURL":258,"structuredData":259},332,"Russian UAV operator involved in the war against Ukraine.","Krupoderova, Russian UAV Operator, Russian Drone Operator, Russian FPV Drone Operator, UAV Pilot, FPV Drone Pilot, Russian Military Personnel, Russian Armed Forces, Drone Warfare, Combat Drone Operations, UAV Operations, Russian Occupation Forces, Russo-Ukrainian War, Ukraine War, OSINT Investigation, OSINT Profile, Open Source Intelligence, Military Identification","https://osintflow.com/en/news/krupoderova-russian-uav-operator",{"@type":260,"image":261,"author":264,"@context":48,"headline":266,"keywords":267,"publisher":275,"inLanguage":15,"description":161,"dateModified":276,"datePublished":276,"articleSection":277,"mainEntityOfPage":278,"alternativeHeadline":279},"NewsArticle",{"url":192,"@type":262,"width":94,"height":263},"ImageObject",630,{"name":199,"@type":265},"Person","Krupoderova (Kino): Russian UAV Operator in FSB Border Service",[57,268,269,270,271,272,273,274],"Russia","FSB","UAV","drone operator","Ukraine war","Krupoderova","Kino",{"url":52,"name":46,"@type":47},"2026-06-05","OSINT Investigation",{"@id":258,"@type":59},"OSINT Profile: Maria Viktorovna Krupoderova",[281],{"id":282,"documentId":160,"title":283,"description":284,"slug":285,"publicationDate":286,"createdAt":287,"updatedAt":288,"publishedAt":289,"locale":29},840,"Оператор БПЛА ЗС РФ, учасниця збройної агресії РФ проти України","Круподерова Марія Вікторівна (позивний «Кино») є активною учасницею збройної агресії РФ проти України та виконує функції оператора безпілотного літального апарата (БПЛА). Проходить службу у Прикордонній службі ФСБ Російської Федерації по Ростовській області та отримала три медалі й подяку від ФСБ за участь у військових операціях.","krupoderova-bpla-zs-rf","2026-06-02T11:45:00.000Z","2026-06-02T11:10:01.070Z","2026-06-05T12:51:05.609Z","2026-06-05T12:47:50.865Z",{"id":291,"documentId":292,"title":293,"description":294,"slug":295,"publicationDate":296,"createdAt":297,"updatedAt":298,"publishedAt":299,"locale":15,"cover":300,"authors":335,"category":344,"blocks":345,"tags":349,"seo":363,"localizations":385},832,"cmdpv4wri0v4w32hbw1u4w28","How Kremlin propagandist and lawyer Ilya Remeslo embezzled funds during the construction of the Tuapse oil refinery","During 2013–2014, Ilya Remeslo was directly involved in a case concerning embezzlement in the reconstruction project of LLC “RN-Tuapse Oil Refinery\" as director of the company which supplied goods. ","remeslo-tuapse-refinery-scheme","2026-05-26T09:00:00.000Z","2026-05-22T15:59:17.945Z","2026-05-26T13:49:43.899Z","2026-05-26T13:49:46.019Z",{"id":301,"documentId":302,"name":303,"alternativeText":304,"caption":304,"width":305,"height":306,"formats":307,"hash":329,"ext":88,"mime":91,"size":330,"url":331,"previewUrl":9,"provider":116,"provider_metadata":9,"createdAt":332,"updatedAt":333,"publishedAt":334},1929,"v3f7afrrwuhroyrgrcochlej","ремесло_НПЗ.webp","ремесло_НПЗ",1402,1122,{"large":308,"medium":314,"thumbnail":321},{"ext":88,"url":309,"hash":310,"mime":91,"name":311,"path":9,"size":312,"width":94,"height":173,"sizeInBytes":313},"https://cdn.osintflow.com/large_remeslo_NPZ_78144961f9.webp","large_remeslo_NPZ_78144961f9","large_ремесло_НПЗ.webp",115.38,115382,{"ext":88,"url":315,"hash":316,"mime":91,"name":317,"path":9,"size":318,"width":102,"height":319,"sizeInBytes":320},"https://cdn.osintflow.com/medium_remeslo_NPZ_78144961f9.webp","medium_remeslo_NPZ_78144961f9","medium_ремесло_НПЗ.webp",47.05,480,47046,{"ext":88,"url":322,"hash":323,"mime":91,"name":324,"path":9,"size":325,"width":326,"height":327,"sizeInBytes":328},"https://cdn.osintflow.com/thumbnail_remeslo_NPZ_78144961f9.webp","thumbnail_remeslo_NPZ_78144961f9","thumbnail_ремесло_НПЗ.webp",8.6,195,156,8602,"remeslo_NPZ_78144961f9",171.97,"https://cdn.osintflow.com/37/remeslo_NPZ_78144961f9.webp","2026-05-19T14:11:29.733Z","2026-05-22T15:53:00.595Z","2026-05-19T14:11:29.734Z",[336],{"id":337,"documentId":338,"name":339,"email":340,"createdAt":341,"updatedAt":342,"publishedAt":343},10,"vl8m4hkw69k7q1ntjqe2rurr","PPMaster","kk.macnamara@gmail.com","2026-05-13T07:38:05.001Z","2026-05-19T14:13:30.877Z","2026-05-19T14:13:30.796Z",{"id":203,"documentId":204,"name":205,"slug":206,"description":9,"createdAt":207,"updatedAt":208,"publishedAt":209,"locale":15},[346],{"__component":18,"id":347,"body":348},2795,"Many of those who worked or are still working for Putin’s regime have recently begun to change their stance. This trend has become especially common after Ukraine intensified its successful strikes on military facilities and oil refining enterprises, when even Putin’s servants started to realize that the operation was not going according to plan. One such example is [Ilya Remeslo](https://ru.wikipedia.org/wiki/%D0%A0%D0%B5%D0%BC%D0%B5%D1%81%D0%BB%D0%BE,_%D0%98%D0%BB%D1%8C%D1%8F_%D0%91%D0%BE%D1%80%D0%B8%D1%81%D0%BE%D0%B2%D0%B8%D1%87), who had been actively working for the Russian presidential administration since 2015 and fighting against opposition figures such as Navalny and the FBK, but has now begun expressing opposition views. One example of this was his post regarding the strike on the oil refinery in Tuapse, where he [wrote](https://t.me/remeslaw/2921) that it’s time to put an end to «all of this», and that no gains from the war are worth the destruction of Russian cities and the harm done to the health of their residents.\n\n![ремесло про туапсе](https://cdn.osintflow.com/37/remeslo_pro_tuapse_c46486612b.webp)\n\nThis is not his first statement of this kind. In fact, he gained significant attention after a [post](https://t.me/remeslaw/2869) on his Telegram channel titled “Five Reasons Why I Stopped Supporting Vladimir Putin.”\n\n![5 причин ремесло](https://cdn.osintflow.com/37/5_prichin_remeslo_1720f2b1b8.webp)\n\nSurprisingly, after this statement he was not arrested, but was only placed in a psychiatric hospital for some time (many believe this was done by his relatives in order to protect him from arrest). After [being released](https://www.dw.com/ru/kritikovavsij-putina-bloger-ila-remeslo-vysel-iz-psihbolnicy/a-76839521) from the hospital, Remeslo continued to criticize Putin, the so-called “special military operation,” and everything connected to it, even giving a lengthy interview to [Ksenia Sobchak](https://www.youtube.com/watch?v=dlc7y1aYT2I) and [Echo of Moscow](https://www.youtube.com/watch?v=Aoa1fsl9M00).\n\nHowever, our article is not about another case of people working for the Kremlin changing their position, but rather about how the former Kremlin propagandist and lawyer is also connected to the Tuapse oil refinery that we mentioned at the very beginning.\nThe fact is that during 2013–2014, Ilya Remeslo was directly involved in a case concerning embezzlement in the reconstruction project of LLC “RN-Tuapse Oil Refinery.” This is how things often turn out with “patriots” in Russia. So, let us go through the events step by step and in chronological order.\n\nBack in 2007, Rosneft officially [announced](https://portnews.ru/news/23916/) an investment project and plans for reconstruction, declaring its intention to invest around $2 billion and begin construction in the third quarter of 2007. In 2009, large-scale construction and installation work effectively began, including the construction of the ELOU-AVT-12 crude oil primary processing unit, while in 2011–2013 the key facilities of the first phase were [commissioned](https://www.rosneft.ru/press/releases/item/22672/).\nOne of the main contractors for this project was KMUS-2 - one of the largest enterprises in southern Russia in the field of construction and reconstruction of fuel and energy infrastructure facilities, trunk pipelines, and chemical production facilities. The company had been involved in the reconstruction project of LLC “RN-Tuapse Oil Refinery” commissioned by Rosneft since 2011. According to information published on the company’s [website](https://web.archive.org/web/20190225104632/http:/www.kmus2.ru/content.php?id=11), “KMUS-2” replaced heat exchanger units, furnaces, overpass structures, and storage tanks at the refinery with a total capacity exceeding 120,000 cubic meters.\n\nAt approximately the same time, specifically on October 21, 2009 - [LLC “Master-Torg”](https://companies.rbc.ru/id/1097847296040-ooo-master-torg/?ysclid=mp2gtiytfi15475857) (Taxpayer ID: 7814449817) was registered in Saint Petersburg at Rimsky-Korsakov Avenue, Building 33, Block K, Letter A, Apartment Premises 1N. Its sole founder was Stanislav Sergeyevich Ovchinnikov (Taxpayer ID: 781900440800). Here is the full [list](https://www.find-org.net/search/chief/ovchinnikov_stanislav_sergeevich) of companies where he was a founder and/or director, and this list already strongly suggests involvement in fictitious business activities.\n\n![компанії Овчинникова](https://cdn.osintflow.com/37/kompaniyi_Ovchinnikova_5ff28d03a1.webp)\n\nIn November 2013, the director of LLC “Master-Torg” became Ilya Borisovich Remeslo (Taxpayer ID: 781412018094).\n\n![ремесло директор ТОВ Мастер-торг](https://cdn.osintflow.com/37/remeslo_direktor_TOV_Master_torg_a613d7b2cc.webp)\n\nLet us take a look at who Ilya Remeslo was in 2013.\nAccording to Remeslo’s own [statements](https://echofm.online/programs/breakfast-show/ilya-remeslo-v-breakfast-show-o-svoyom-bunte-koncze-vlasti-putina-i-pochemu-on-mochil-fbk), back in 2011–2012 he had even been a supporter of Alexei Navalny, but by 2013 he had already begun working for Putin’s presidential administration and, as we mentioned above, became the director of the aforementioned company.\n\n![ремесло про навального](https://cdn.osintflow.com/37/remeslo_pro_navalnogo_c012251285.webp)\n\nReturning to the case that connects Ilya Remeslo and the Tuapse Oil Refinery, we are referring to the specific court case [No. A32-6471/2017](https://sudact.ru/arbitral/doc/FNSghpwI5FNu/?ysclid=mp2c3tnypa335681965).\n\nBased on agreements between LLC “RN-Tuapse Oil Refinery” and KMUS-2, the latter, acting as the general contractor, engaged LLC “Impex Electro” as a subcontractor for installation work, while LLC “Master-Torg” acted as the supplier of self-heating cables, electric pipeline heating cabinets, and related components. In turn, the suppliers of inventory and materials for LLC “Master-Torg” were LLC “Estetika” and LLC “Stroytorg,” while the cargo carrier was LLC “BTK Partner.”\n\nContract No. 14-09 between KMUS-2 and LLC “Master-Torg” was signed on October 20, 2011, for the supply of cable products and electrical equipment for the installation of a pipeline electric heating system at the “Tuapse Oil Refinery” facility in the city of Tuapse, Krasnodar Krai. The actual execution of the contract began in 2013.\n\nAccording to the documents, in fulfillment of this contract, LLC “Master-Torg” supplied inventory and materials worth 576,087,340 rubles and 99 kopecks: 524,056,948 rubles and 56 kopecks in 2013, and 52,030,392 rubles and 43 kopecks in 2014.\n\nHowever, in 2016, a field tax audit of KMUS-2 concerning the correctness of tax calculation and the timely payment (withholding and transfer) of taxes for the period from January 1, 2013 to December 31, 2014 reached a different conclusion. This was documented in the field tax audit report dated June 7, 2016, No. 20-21/156/900, which questioned the actual supply of goods.\n\nFollowing the review of this report, the inspection authority issued decision No. 10-21/163/1112 dated November 1, 2016, on bringing the company to responsibility for committing a tax offense. According to this decision, KMUS-2 was held liable under Paragraph 1 of Article 122, and Articles 123 and 126 of the Tax Code of the Russian Federation. The company was fined a total of 46,104,537 rubles, ordered to pay tax arrears totaling 198,789,380 rubles, and charged penalties amounting to 63,644,025 rubles. In addition, the company was instructed to withhold and transfer personal income tax (PIT) to the budget in the amount of 2,831,690 rubles.\n\n![проверка по Мастер Торг 1](https://cdn.osintflow.com/37/proverka_po_Master_Torg_1_a5fb762a01.webp)\n\nSimply said: during 2013–2014, according to the documentation submitted to KMUS-2, LLC “Master-Torg” allegedly supplied goods to LLC “RN-Tuapse Oil Refinery” worth 576,087,340 rubles. Based on this, KMUS-2 filed the corresponding tax declarations. However, the tax audit failed to find evidence confirming the actual delivery of the goods, identifying only formal paperwork and document circulation. As a result, the tax authorities issued a decision imposing additional tax liabilities on KMUS-2 along with fines for violations of tax legislation.\nOne more interesting detail: according to the case materials, Ilya Remeslo appears as the director who signed the documents under which the alleged supply of goods supposedly took place:\n\n![ремесло директор мастер торг подпись](https://cdn.osintflow.com/37/remeslo_direktor_master_torg_podpis_3da05b5648.webp)\n\nIn addition, the audit revealed that LLC “Master-Torg” displays all the signs of a shell company, lacking the premises, facilities, and capacity to fulfill the contract.\n\n![мастер-торг](https://cdn.osintflow.com/37/master_torg_19ddf2c16b.webp)\n\nThis tax audit took place in 2016, so let us take a look at what Ilya Remeslo had become by that point. By then, Ilya Remeslo was already fully working for the Russian presidential administration and was actively [engaged](https://echofm.online/programs/breakfast-show/ilya-remeslo-v-breakfast-show-o-svoyom-bunte-koncze-vlasti-putina-i-pochemu-on-mochil-fbk) in activities against Alexei Navalny and the Anti-Corruption Foundation in the interests of the presidential administration.\n\n![ремесло мочит ФБК.](https://cdn.osintflow.com/37/remeslo_mochit_FBK_6cfd95286b.webp)\n\nThe head of the legal department of the Anti-Corruption Foundation, Vyacheslav Gimadi, [describes](https://meduza.io/feature/2026/03/18/bloger-i-donoschik-ilya-remeslo-on-stoyal-za-ugolovnym-delom-navalnogo-vystupil-protiv-putina-i-potreboval-sudit-ego-kak-voennogo-prestupnika) Remeslo as “part of Putin’s vertical of power” since at least 2015, “when he ‘appeared’ during the searches of the FBK, accompanied the FBK case in the media with fake lawsuits and denunciations,” and also acted as a fake “witness” against Alexei Navalny and his associates.\n\nBy 2016, he was already actively operating as a blogger, lawyer, and author of materials directed against the Russian opposition. In the same year, Remeslo filed complaints with Russian law enforcement authorities under Article 282 of the Criminal Code of the Russian Federation (“extremism”). The most well-known case was his appeal to the Investigative Committee of the Russian Federation against blogger Anton Nosik over his statements about Syria.\n\nThat same year, in 2016, he became a laureate of the “Truth and Justice” award from the All-Russia People's Front foundation for “anti-corruption investigations.” He was also nominated in 2016 for the “I Am a Citizen!” award from the Public Chamber of the Russian Federation in the category of “civic journalism.” In media appearances at the time, he commented on the projects and activities of opposition figure Mikhail Khodorkovsky, in particular criticizing his project “Open Media.”\n\n## Returning to the case involving KMUS-2, LLC “Master-Torg,” and LLC “RN-Tuapse Oil Refinery.”\nKMUS-2 filed a claim with the Arbitration Court of Krasnodar Krai against the Interdistrict Inspectorate of the Federal Tax Service of Russia, seeking to invalidate the decision dated November 1, 2016, No. 10-21/163/1112, concerning liability for committing a tax offense.\nInitially, by decision of the Arbitration Court of Krasnodar Krai dated July 14, 2017, in case No. A32-6471/2017, the decision of the Interdistrict Inspectorate of the Federal Tax Service for Major Taxpayers in Krasnodar Krai dated November 1, 2016, No. 10/21/163/1112, was declared invalid. However, the Arbitration Court of Appeal in Rostov-on-Don overturned the decision of the Arbitration Court of Krasnodar Krai in case No. A32-6471/2017.\nThen, on March 28, 2018, the Arbitration Court of the North Caucasus District, acting as the cassation court, ruled that the decision of the arbitration appellate court dated December 29, 2017, in case No. A32-6471/2017 should remain unchanged, while the cassation appeal should be dismissed.\n\nThus, the court of final instance confirmed the findings of the tax inspection and the legality of its report and decision concerning violations of tax legislation, which had been based on the absence of evidence of the actual (physical) performance by LLC “Master-Torg” of its contractual obligations. This ruling ultimately led to [bankruptcy](https://kuban.rbc.ru/krasnodar/freenews/5ad04e2e9a7947d9335fa045?ysclid=mp2c1pgyr4847516100) proceedings against KMUS-2, while LLC “Master-Torg” itself was liquidated in December 2016, literally one month later.\n\n![банкроство ПрАТ «КМУС-2»](https://cdn.osintflow.com/37/bankrostvo_Pr_AT_KMUS_2_d9d65c5a09.webp)\n\nThus, the court established that no real delivery of goods had taken place. So what happened to the general director of LLC “Master-Torg,” Ilya Remeslo? Based on the materials of the tax audit, which confirmed the fictitious nature of the supplies, a criminal case would have been opened and he would have faced imprisonment. But we should remember that by 2016, Ilya Remeslo had already become a fairly significant part of Putin’s political machinery.\nThe key point is that during the field audit, a handwriting examination was conducted (incidentally, the only one) regarding the signature of the general director of LLC “Master-Torg,” Remeslo I.B. According to expert conclusion No. EBP-1-557/2016 dated March 29, 2016, Remeslo’s actual signature did not match the signature appearing on the primary documentation. The documents of LLC “Master-Torg” — including invoices, VAT invoices, and appendices to the contract — which had been accepted and processed by KMUS-2, were signed by another person rather than Remeslo himself. Consequently, the information contained in those documents could not be considered reliable.\nWhy this examination was conducted solely within the framework of a tax audit, and why no criminal case was ever initiated regarding the fictitious document circulation, remains unknown.\n\n![про підпис Ремесла](https://cdn.osintflow.com/37/pro_pidpis_Remesla_ac587ba507.webp)\n\nMoreover, as Remeslo himself later confirmed, he did not sign the documents. Accordingly, he was considered “innocent” and uninvolved :)\n\n![ремесло не підписував](https://cdn.osintflow.com/37/remeslo_ne_pidpisuvav_de134e1ec9.webp)\n\nHAPPY END\n\n\n",[350,356,362],{"id":351,"documentId":352,"name":205,"slug":205,"createdAt":353,"updatedAt":354,"publishedAt":355},54,"gain2lvpa6n0hq5r4v72imk9","2026-01-13T17:06:56.543Z","2026-01-19T12:10:26.886Z","2026-01-19T12:10:26.829Z",{"id":357,"documentId":358,"name":359,"slug":359,"createdAt":360,"updatedAt":360,"publishedAt":361},36,"fksbxw1l8pfxeecc8nteyqgz","osint","2025-07-12T11:11:26.316Z","2025-07-12T11:11:26.311Z",{"id":233,"documentId":234,"name":235,"slug":235,"createdAt":236,"updatedAt":237,"publishedAt":238},{"id":364,"metaTitle":365,"metaDescription":366,"keywords":367,"metaRobots":368,"metaViewport":40,"canonicalURL":369,"structuredData":370},323,"How Ilya Remeslo Embezzled Tuapse Oil Refinery Funds","Ilya Remeslo involved in a case concerning embezzlement in the reconstruction project of LLC “RN-Tuapse Oil Refinery.","Ilya Remeslo investigation, Tuapse Oil Refinery, Tuapse refinery fraud, Remeslo, Ilya Borisovich Remeslo, Rosneft, LLC Master-Torg, JSC KMUS-2, fictitious deliveries, Russian oil refinery corruption, shell company scheme, tax fraud investigation, Kremlin propaganda, Russian propagandist, Alexei Navalny, Russian opposition, Z-bloggers, Stanislav Sergeyevich Ovchinnikov, Tuapse refinery strike, refinery reconstruction, Tuapse Oil Refinery reconstruction","\u003Cmeta name=\"robots\" content=\"index, follow\">","https://osintflow.com/news/remeslo-tuapse-refinery-scheme/",{"url":371,"@type":260,"image":309,"author":372,"@context":48,"headline":373,"keywords":374,"publisher":379,"inLanguage":380,"description":381,"dateModified":382,"datePublished":382,"mainEntityOfPage":383,"alternativeHeadline":384},"https://osintflow.com/en/news/remeslo-tuapse-refinery-scheme",{"name":46,"@type":47},"How Illya Remeslo Was Involved in the Tuapse Refinery Scheme",[57,375,376,377,46,378],"investigation","Remeslo","Tuapse refinery","oil refinery",{"name":46,"@type":47},"en-US","OsintFlow investigates Illya Remeslo’s alleged involvement in fictitious supply schemes during the reconstruction of the Tuapse oil refinery in 2013–2014.","2026-05-26",{"@id":371,"@type":59},"OsintFlow Investigation",[386],{"id":387,"documentId":292,"title":388,"description":389,"slug":390,"publicationDate":296,"createdAt":391,"updatedAt":392,"publishedAt":393,"locale":29},831,"Як Ілля Ремесло крав на будівництві Туапсинського НПЗ","Ілля Ремесло російский юрист та пропагандист, як директор ТОВ «Мастер-Торг», у 2013-2014 роках здійснював фіктивні поставки матеріалів в рамках договору субподряду при реконструкції ТОВ «РН-Туапсинський НПЗ» ","remeslo-tuapsinsky-npz","2026-05-19T14:12:27.350Z","2026-05-26T13:49:47.657Z","2026-05-26T13:47:38.979Z",{"id":395,"documentId":396,"title":397,"description":398,"slug":399,"publicationDate":400,"createdAt":401,"updatedAt":402,"publishedAt":403,"locale":15,"cover":404,"authors":437,"category":439,"blocks":440,"tags":462,"seo":466,"localizations":481},812,"ohg5i2tp6fgv2o68irh7veid","UAV Platoon Commander, 1429th Motor Rifle Regiment, Dnepr Group of Forces","Call sign “Tekhnik,” a serviceman involved in Russia’s full-scale invasion of Ukraine. He advanced from serving as a sniper to becoming a UAV platoon commander. He is currently engaged in combat operations in the  Zaporizhzhia direction.","uav-commander-khvatov-dnepr","2026-05-06T12:31:00.000Z","2026-05-06T11:50:28.889Z","2026-05-06T13:36:33.000Z","2026-05-06T13:36:34.818Z",{"id":405,"documentId":406,"name":407,"alternativeText":408,"caption":408,"width":84,"height":409,"formats":410,"hash":432,"ext":88,"mime":91,"size":433,"url":434,"previewUrl":9,"provider":116,"provider_metadata":9,"createdAt":435,"updatedAt":435,"publishedAt":436},1899,"k5g1ndvfut42gsqr1kkiz4kv","Khvatov_screen.webp","Хватов скрін з відео",725,{"large":411,"medium":418,"thumbnail":425},{"ext":88,"url":412,"hash":413,"mime":91,"name":414,"path":9,"size":415,"width":94,"height":416,"sizeInBytes":417},"https://cdn.osintflow.com/large_Khvatov_screen_a161fbdcb8.webp","large_Khvatov_screen_a161fbdcb8","large_Khvatov_screen.webp",81.08,680,81080,{"ext":88,"url":419,"hash":420,"mime":91,"name":421,"path":9,"size":422,"width":102,"height":423,"sizeInBytes":424},"https://cdn.osintflow.com/medium_Khvatov_screen_a161fbdcb8.webp","medium_Khvatov_screen_a161fbdcb8","medium_Khvatov_screen.webp",34.73,340,34734,{"ext":88,"url":426,"hash":427,"mime":91,"name":428,"path":9,"size":429,"width":110,"height":430,"sizeInBytes":431},"https://cdn.osintflow.com/thumbnail_Khvatov_screen_a161fbdcb8.webp","thumbnail_Khvatov_screen_a161fbdcb8","thumbnail_Khvatov_screen.webp",9.03,139,9028,"Khvatov_screen_a161fbdcb8",87.55,"https://cdn.osintflow.com/19/34/Khvatov_screen_a161fbdcb8.webp","2026-05-06T13:03:33.185Z","2026-05-06T13:03:33.186Z",[438],{"id":197,"documentId":198,"name":199,"email":9,"createdAt":200,"updatedAt":200,"publishedAt":201},{"id":203,"documentId":204,"name":205,"slug":206,"description":9,"createdAt":207,"updatedAt":208,"publishedAt":209,"locale":15},[441,444,446,450,453,456,459],{"__component":18,"id":442,"body":443},2775,"Khvatov Nikolay Nikolaevich (17.01.1998), call sign “Tekhnik,” was born in Moscow. He completed his compulsory military service in the 810th Naval Infantry Brigade, followed by an additional year under contract.\n\nAfter leaving the military, he worked as an auto mechanic. When partial mobilisation was announced in Russia, he said goodbye to his parents and fiancée and reported to a mobilisation assembly point. He underwent training at a military range, which was sufficient to restore his proficiency with a sniper rifle, and later began carrying out combat missions in the Zaporizhzhia direction.\n\nUnder the call sign “Tekhnik,” he worked as part of a sniper team alongside an experienced marksman known as “Max,” originally from Donetsk. Max served as a mentor to him, sharing hands-on experience in establishing firing positions and carrying out surveillance tasks in the field.\n\n>_– “In the fighting near the village of Nesterianka, in the Orikhiv area, Max and I set up a position in a four-storey building. At first, we conducted observation and reported on the movement of Ukrainian Armed Forces units. When our assault troops advanced, we provided fire support. We targeted Ukrainian command personnel and suppressed firing positions,” Khvatov said in [an interview](http://redstar.ru/ego-bespilotniki-navodyat-uzhas-na-nepriyatelya/) with Russian state media._\n\n![Хватов фото з ВК](https://cdn.osintflow.com/19/34/khavatov_vk2_8557515148.webp)\n\nAccording to the aforementioned interview, he initially served as a sniper and later became a UAV platoon commander within the unmanned systems units of the 1429th Guards Motor Rifle Regiment, part of the “Dnepr” Group of Forces, where he was promoted to the rank of junior lieutenant (NATO code OF-1). As of now, he states that he is operating in the Zaporizhzhia [direction](https://t.me/Koordinatorzp/8873).\n\nBased on tags linked to the individual, he is believed to have had attempts or interest in joining the Federal Protective Service (FSO) of Russia.",{"__component":219,"id":445},463,{"__component":447,"id":448,"description":449},"shared.media",326,"Khvatov video",{"__component":215,"id":451,"content":452},2709,"**Personal data**\nData source: open sources and https://osintkit.net/\n**Full name: Khvatov Nikolay Nikolaevich**\nDate of birth: 17.01.1998\nPassport:  4518500624 \nTIN (INN): 772146830090\nSNILS: 19091305566  \nDriver's license: 7736785109 \nKnown addresses:\n28 Privolnaya St., Moscow, Russia\n\n**Contacts:**\nPhone number: +79858355128 \nTelegram: https://t.me/+79858355128 (id 421471047)\nWhatsApp: https://wa.me/+79858355128\nVKontakte: https://vk.com/id449014803, https://vk.com/id1065637942 (empty VK profile) \nEmail: omen_97@mail.ru, stone.plant@yandex.ru \nhttps://archive.is/LqeUr \nhttps://archive.is/0kd8v \n\n**Online classifieds platforms:**\nhttps://youla.ru/user/5ac35033f202637bb44462f9/active \nhttps://archive.is/jkDnr \n\n**Media mentions:**\nhttps://t.me/orly_rs/5066 \nhttps://archive.is/OuhiQ \nhttps://t.me/orly_rs/5080\nhttps://archive.ph/y7jJH \nhttp://redstar.ru/ego-bespilotniki-navodyat-uzhas-na-nepriyatelya/ \nhttps://archive.ph/EDLy0 \nhttps://dzen.ru/a/ZnBiaI5PDUGa6ULf \nhttps://archive.ph/uW5op \nhttps://aif.ru/society/people/delo-tehnika-snayper-iz-moskvy-posle-boya-s-leopardami-stal-pilotom-bpla \nhttps://web.archive.org/web/20260420194740/https://aif.ru/society/people/delo-tehnika-snayper-iz-moskvy-posle-boya-s-leopardami-stal-pilotom-bpla",{"__component":215,"id":454,"content":455},2710,"**Wife. Personal data:**\nData source: open sources and https://osintkit.net/\n**Full name: Khvatova (Gul) Yulia Alexandrovna**\nDate of birth: 04.09.1997\nPassport:  4523061406, 4523247345 (verification via the “Gos. Oplata” service: two passport numbers are valid)\nTIN (INN): 772148248603 \nSNILS: 18467601300 \nDriver's license:  9902387170 \nKnown addresses:\n16, bldg. 1, 107 Yunykh Lenivtsev St., Moscow, Russia\n28 Privolnaya St., Moscow, Russia\n\n**Contacts:**\nPhone number: +79268399973 \nTelegram: https://t.me/+79268399973 \nWhatsApp: http://wa.me/+79268399973 \nMAX: https://max.me/+79268399973 \nVKontakte: https://vk.com/id310088015 https://archive.is/t4W2F \nOdnoklassniki: https://ok.ru/profile/342460908658 https://archive.is/WQgt6 \nInstagram: http://instagram.com/ms.juliaaa, https://www.instagram.com/black_birdgy (empty profile)\nOnline classifieds platforms: https://youla.ru/user/5c31db0a85e9d20eb563e9bf/active \nEmail: 89268399973@mail.ru \n\nAccording to leaked databases, she worked in government institutions, including the Main Directorate of the Ministry of Internal Affairs of Russia for Moscow (GU MVD of Russia for Moscow).\n\n**Son:**\n**Full name: Khvatov Dobrynya Nikolaevich**\nDate of birth: 09.05.2024",{"__component":215,"id":457,"content":458},2711,"**Mother. Personal data:**\nData source: open sources and https://osintkit.net/\n**Full name: Khvatova Ella Vladimirovna**\nDate of birth:15.06.1962\nPassport:  4509113203  \nTIN (INN): 772151277805 \nSNILS: 11997647926  \nKnown addresses:\n28 Privolnaya St., Moscow, Russia\n\n**Contacts:**\nPhone number: +79688959743\nTelegram: http://t.me/+79688959743 \nWhatsApp: http://wa.me/+79688959743 \nVKontakte: \nOdnoklassniki: https://ok.ru/profile/125929711985 https://archive.is/zKxlv \nMail: ella_mel@mail.ru",{"__component":215,"id":460,"content":461},2712,"**Father. Personal data:**\nData source: open sources and https://osintkit.net/\n**Full name: Khvatov Nikolay Borisovich**\nDate of birth: 26.05.1960\nPassport:  4511490671 \nTIN (INN): 772137657001 \nSNILS: 07597428420 \nKnown addresses:\n28 Privolnaya St., Moscow, Russia\nApt. 6, bldg. 28, Samarkandsky Blvd., Moscow, Russia\n\n**Contacts:**\nPhone number: +79652598340\nFacebook: https://facebook.com/100007259658581 (empty profile), https://web.archive.org/web/20260421175904/https://www.facebook.com/people/%D0%9D%D0%B8%D0%BA%D0%BE%D0%BB%D0%B0%D0%B9-%D0%A5%D0%B2%D0%B0%D1%82%D0%BE%D0%B2/pfbid02qBMA4hg1ziZ6ymSLhDq1HbqaP1ahGodTqWrZHTSPpyCMKqkYZZeHx3LezseAZKPWl/ \nInstagram: https://www.instagram.com/nikolaikhvatov \nEmail: friar216@yandex.ru",[463,464,465],{"id":248,"documentId":249,"name":250,"slug":250,"createdAt":251,"updatedAt":252,"publishedAt":253},{"id":233,"documentId":234,"name":235,"slug":235,"createdAt":236,"updatedAt":237,"publishedAt":238},{"id":240,"documentId":241,"name":242,"slug":243,"createdAt":244,"updatedAt":245,"publishedAt":246},{"id":467,"metaTitle":468,"metaDescription":397,"keywords":469,"metaRobots":39,"metaViewport":40,"canonicalURL":470,"structuredData":471},304,"UAV Platoon Commander, 1429th Motor Rifle Regiment,","UAV commander, Khvatov Nikolay, Tekhnik, Russian serviceman, 810th Naval Infantry Brigade, sniper, UAV platoon commander, 1429th Motor Rifle Regiment, Dnepr Group of Forces, Zaporizhzhia sector, Russian military, OSINT, junior lieutenant","https://osintflow.com/en/news/uav-commander-khvatov-dnepr/",{"@type":260,"image":412,"author":472,"@context":48,"headline":474,"keywords":475,"publisher":476,"inLanguage":15,"description":477,"dateModified":478,"datePublished":478,"articleSection":57,"mainEntityOfPage":479},{"name":473,"@type":47},"OSINTFlow","UAV Commander Khvatov (Dnepr Group of Forces)","UAV commander, Khvatov, Russian military, Dnepr Group of Forces, 1429th Motor Rifle Regiment, Zaporizhzhia sector, OSINT profile",{"name":473,"@type":47},"OSINT profile of Khvatov Nikolay Nikolaevich, a Russian serviceman who progressed from sniper to UAV platoon commander within the 1429th Guards Motor Rifle Regiment of the Dnepr Group of Forces.","2026-05-06",{"@id":480,"@type":59},"https://osintflow.com/en/news/uav-commander-khvatov-dnepr",[482],{"id":483,"documentId":396,"title":484,"description":485,"slug":486,"publicationDate":487,"createdAt":488,"updatedAt":489,"publishedAt":490,"locale":29},811,"Командир взводу БПЛА 1429-го гвардійського мсп, угрупування військ «Днепр»","Позивний «Техник», учасник повномасштабного вторгнення. Пройшов шлях від снайпера до командира взводу БПЛА. Виконує бойові завдання на Запорізькому напрямку.\n","khvatov_dnepr","2026-05-06T08:45:00.000Z","2026-05-05T20:16:58.783Z","2026-05-06T13:36:35.699Z","2026-05-06T13:34:44.329Z",{"id":492,"documentId":493,"title":494,"description":495,"slug":496,"publicationDate":497,"createdAt":498,"updatedAt":499,"publishedAt":500,"locale":15,"cover":501,"authors":535,"category":536,"blocks":543,"tags":550,"seo":559,"localizations":564},788,"dxzcg0joq341z8kepc7sntc5","AI Assistant: From a Single Identifier to a Full Profile","OsintKit has further expanded its capabilities with the integration of an AI-powered analytics module. The most time-consuming part of investigations, recursive searching and uncovering hidden connections, is now fully automated.","osintkit-ai","2026-04-27T14:45:00.000Z","2026-04-28T08:06:24.161Z","2026-04-28T09:15:33.442Z","2026-04-28T09:15:33.614Z",{"id":502,"documentId":503,"name":504,"alternativeText":505,"caption":505,"width":84,"height":506,"formats":507,"hash":529,"ext":88,"mime":91,"size":530,"url":531,"previewUrl":9,"provider":116,"provider_metadata":9,"createdAt":532,"updatedAt":533,"publishedAt":534},1881,"fizrhd3ifg1g02i6sly6pzdn","osintkitAI_en.webp","AI Assistant OsintKit",714,{"large":508,"medium":515,"thumbnail":522},{"ext":88,"url":509,"hash":510,"mime":91,"name":511,"path":9,"size":512,"width":94,"height":513,"sizeInBytes":514},"https://cdn.osintflow.com/large_osintkit_AI_en_845669b47c.webp","large_osintkit_AI_en_845669b47c","large_osintkitAI_en.webp",25.65,669,25646,{"ext":88,"url":516,"hash":517,"mime":91,"name":518,"path":9,"size":519,"width":102,"height":520,"sizeInBytes":521},"https://cdn.osintflow.com/medium_osintkit_AI_en_845669b47c.webp","medium_osintkit_AI_en_845669b47c","medium_osintkitAI_en.webp",12.39,335,12388,{"ext":88,"url":523,"hash":524,"mime":91,"name":525,"path":9,"size":526,"width":110,"height":527,"sizeInBytes":528},"https://cdn.osintflow.com/thumbnail_osintkit_AI_en_845669b47c.webp","thumbnail_osintkit_AI_en_845669b47c","thumbnail_osintkitAI_en.webp",3.84,137,3844,"osintkit_AI_en_845669b47c",30.39,"https://cdn.osintflow.com/33/osintkit_AI_en_845669b47c.webp","2026-04-28T08:10:52.358Z","2026-04-28T08:11:34.451Z","2026-04-28T08:10:52.362Z",[],{"id":537,"documentId":538,"name":539,"slug":540,"description":9,"createdAt":541,"updatedAt":541,"publishedAt":542,"locale":15},5,"l40js64og5qd7l8i734m2jxl","Company news","company-news","2025-07-12T11:02:31.199Z","2025-07-12T11:02:31.196Z",[544,547],{"__component":18,"id":545,"body":546},2731,"OsintKit has further expanded its capabilities with the integration of an AI-powered analytics module. The most time-consuming part of investigations, recursive searching and uncovering hidden connections, is now fully automated.\n\n![OsintKitAI_example](https://cdn.osintflow.com/33/Osint_Kit_AI_example_04dec1988f.webp)\n\n## **What this changes in practice:**\n\n### - **Automated pivoting**\nStart with a single entry point—phone number, email, or VIN—and the system expands it into a complete intelligence dossier. It automatically initiates new search cycles for every discovered identifier, with no manual input required.\n\n### - **Relationship graph & IC scoring**\nThe system builds a network graph of connections with automated confidence scoring. Instead of raw data, you get clear investigative context—from direct identifiers (passport, tax identification number) to indirect relationships and associations.\n\n### - **Source-based validation**\nThe AI operates as an analytical engine, not a content generator. Every statement is traceable to its source, while low-confidence findings are clearly separated from verified intelligence—ensuring transparency and auditability.\n\n### - **Ready-to-use Word (.docx) reports**\nReplace scattered tabs and fragmented notes with structured reports containing ready-to-use contact tables, activity insights, and clear analytical conclusions.\n\n#### 🔗 **Explore the AI assistant: https://osintkit.net/search**\n\n",{"__component":447,"id":548,"description":549},301,"OsintKit AI Assistant",[551,552],{"id":357,"documentId":358,"name":359,"slug":359,"createdAt":360,"updatedAt":360,"publishedAt":361},{"id":553,"documentId":554,"name":555,"slug":555,"createdAt":556,"updatedAt":557,"publishedAt":558},39,"xrbrxsjrxylrqlhgnsstuy9c","osintkit","2025-07-12T11:12:58.826Z","2026-01-13T20:38:59.622Z","2026-01-13T20:38:59.581Z",{"id":560,"metaTitle":494,"metaDescription":561,"keywords":562,"metaRobots":39,"metaViewport":40,"canonicalURL":563,"structuredData":9},281,"OsintKit integrates an AI-powered analytics module that automates recursive search and discovery of hidden connections in OSINT investigations.","OSINT, OSINT tools, OSINTKit AI\nAI in OSINT, open source intelligence, AI tools for OSINT, OSINT automation","https://osintflow.com/en/news/osintkit-ai/",[565],{"id":566,"documentId":493,"title":567,"description":568,"slug":496,"publicationDate":569,"createdAt":570,"updatedAt":571,"publishedAt":572,"locale":29},785,"ШІ-асистент для пошуку й аналізу від OsintKit ","Команда OsintKit оновила функціонал , інтегрувавши аналітичний ШІ-модуль. Тепер найбільш марудна частина розслідування - рекурсивний пошук та виявлення прихованих зв’язків - автоматизована","2026-04-26T21:00:00.000Z","2026-04-27T10:16:28.824Z","2026-04-28T09:15:33.750Z","2026-04-27T12:27:58.030Z",{"id":574,"documentId":575,"title":576,"description":577,"slug":578,"publicationDate":579,"createdAt":580,"updatedAt":581,"publishedAt":582,"locale":15,"cover":583,"authors":616,"category":617,"blocks":618,"tags":628,"seo":632,"localizations":660},765,"vkyrjfmpivso754qqqx2rhem","Engine failures, accidental bomb drops, and helicopter damage in Crimea: Key findings from an internal Russian aviation report","During our work, the OsintFlow team obtained an interesting document titled “Flight Safety Information” covering the period from December 29, 2025, to January 18, 2026, which provides a detailed list of aviation incidents involving Russia’s military transport and state aviation fleets.","russian-aviation-report-engine-failures-fab-crimea","2026-03-21T13:15:00.000Z","2026-03-21T19:15:14.310Z","2026-03-28T13:49:13.476Z","2026-03-28T13:49:13.641Z",{"id":584,"documentId":585,"name":586,"alternativeText":587,"caption":587,"width":588,"height":589,"formats":590,"hash":612,"ext":88,"mime":91,"size":613,"url":614,"previewUrl":9,"provider":116,"provider_metadata":9,"createdAt":615,"updatedAt":615,"publishedAt":615},1820,"cblvohp8xashwlpl9amt0tqu","мапа.webp","авіаподії рф",1209,598,{"large":591,"medium":598,"thumbnail":605},{"ext":88,"url":592,"hash":593,"mime":91,"name":594,"path":9,"size":595,"width":94,"height":596,"sizeInBytes":597},"https://cdn.osintflow.com/large_mapa_2b5a4d992b.webp","large_mapa_2b5a4d992b","large_мапа.webp",19.1,594,19100,{"ext":88,"url":599,"hash":600,"mime":91,"name":601,"path":9,"size":602,"width":102,"height":603,"sizeInBytes":604},"https://cdn.osintflow.com/medium_mapa_2b5a4d992b.webp","medium_mapa_2b5a4d992b","medium_мапа.webp",8.03,297,8026,{"ext":88,"url":606,"hash":607,"mime":91,"name":608,"path":9,"size":609,"width":110,"height":610,"sizeInBytes":611},"https://cdn.osintflow.com/thumbnail_mapa_2b5a4d992b.webp","thumbnail_mapa_2b5a4d992b","thumbnail_мапа.webp",2.15,121,2150,"mapa_2b5a4d992b",22.49,"https://cdn.osintflow.com/31/mapa_2b5a4d992b.webp","2026-03-18T20:30:46.997Z",[],{"id":203,"documentId":204,"name":205,"slug":206,"description":9,"createdAt":207,"updatedAt":208,"publishedAt":209,"locale":15},[619,622,625],{"__component":18,"id":620,"body":621},2601,"**During our work, the OsintFlow team obtained an interesting document titled “Flight Safety Information” covering the period from December 29, 2025, to January 18, 2026, which provides a detailed list of aviation incidents involving Russia’s military transport and state aviation fleets.**\n\nThe geographical scope of the incidents spans a wide range of airfields and air bases, including Plesetsk, Severny Air Base, Orenburg-2 Air Base, Engels Air Base, Marinovka Air Base, Zernograd Air Base, Voronezh Baltimor Air Base, Dzhankoy Air Base, Millerovo Air Base, Akhtubinsk (Vladimirovka Air Base), Morozovsk Air Base, Monchegorsk Air Base, and others.\n\nDeparture points and home bases (where the departure point was not specified, the home base was used) from which flights were conducted are shown on a map to illustrate the geographic distribution of aviation incidents over the reporting period.\n\n**In total, the document records 24 incidents. The vast majority are linked to technical malfunctions or in-flight system checks. The breakdown shows 5 incidents in military transport aviation and 19 incidents in Russia’s state aviation fleet.**\n\nThe primary types of Military Transport Aviation (VTA) flights during the reporting period included training and evaluation sorties, troop and equipment transport, and cargo delivery missions. Flights were frequently conducted outside standard routes, alongside routine checks of aircraft systems and crew performance.\n\nFor Russia’s state (combat and special-purpose) aviation, the document lists several categories of missions: special flights, inspection and control sorties, crew training, zone flying, and emergency services (EMERCOM) operations. **A significant proportion of recorded incidents occurred during so-called “special flights.”**\n\nIn Russian military usage, the term “special flight” is often a broad designation that can include combat sorties, strike missions, patrol operations, the transport of personnel and armaments, and missions conducted in or near active combat zones. In practice, this means that many of the recorded incidents took place during operational activity rather than routine training.\n\n**While a single document is not sufficient to assess the overall condition of Russia’s aviation fleet, it does provide a useful snapshot of the types of issues occurring in real-world operations. The recurring nature of certain failures is particularly notable. For instance, repeated engine malfunctions may point to sustained operational stress and broader technical strain across the fleet.**\n\nIncident data indicates that most events are linked to the technical condition of aircraft systems, primarily engines, as well as hydraulic and navigation systems and wing mechanization components. These categories account for the majority of recorded incidents during the reporting period.\n\nBack in July 2025, aviation expert Anatolii Khrapchynskyi, in [an interview with OBOZ.UA](https://war.obozrevatel.com/ukr/rf-bilshe-ne-panue-v-ukrainskomu-nebi-aviaekspert-hrapchinskij-nazvav-najbilshi-problemi-i-strahi-okupanta.htm), emphasized that despite Moscow’s public claims, Russia’s military aviation was facing a serious crisis. He noted that, due to sanctions and technological backwardness, the Russian aircraft fleet was gradually losing combat effectiveness. According to him, the main problem of Russia’s aviation is its engines. At the time, the expert stated:\n\n_>“Most notably, despite loud claims about the ‘revival’ of its aviation industry, Russia remains hostage to a single critical issue — engines. Since losing access to Ukraine’s Motor Sich and Ivchenko-Progress in 2014, the entire import substitution program has been stalling at the turbine level. Without modern engines, even the most high-profile Tu-160 is effectively just an expensive white coffin. One example is the reported engine fire on one of these aircraft, previously used by Vladimir Putin himself, which was caused by the installation of old components removed from another aircraft.”_\n\nAnalytical reports published in 2025 suggested that Russia’s defense industry faces significant constraints in scaling up production of new combat aircraft due to sanctions and shortages of critical technologies and components. The Institute for the Study of War (ISW) [noted (https://understandingwar.org/research/russia-ukraine/russian-offensive-campaign-assessment-june-29-2025/) that while Russia continues efforts to increase aircraft production, Western sanctions and technological limitations are likely to hinder its ability to achieve meaningful expansion in the near term.\n\n![службова записка авіаподії](https://cdn.osintflow.com/31/Informacziya_po_bezopasnosti_poletov_29_12_25_18_9618ca12e1.webp)\nThe full document is available for reading and/or download below.",{"__component":447,"id":623,"description":624},294,"Aviation Safety Information Report (29 December 2025 – 18 January 2026)",{"__component":18,"id":626,"body":627},2602,"Following a general classification of each incident by its primary cause, the resulting structure is as follows:\n\n- **Engine failures account for the largest share of technical incidents.**\n\nThis category includes cases explicitly described in the document as “metal shavings in oil,” “low oil pressure,” “engine vibration,” and in-flight engine shutdowns. Such incidents were recorded on **Su-34** (multiple cases), **Su-30SM / Su-30SM2**, **Su-35S, Il-76, An-124**, and** Il-76M** aircraft.\n\nA key pattern in the dataset is the unusually high number of engine-related failures across multiple aircraft types. These incidents generally follow a similar sequence: a low oil pressure warning is triggered, often accompanied by a “metal particles in oil” alert. In some cases, engine vibration or a loud bang is reported. The crew then reduces thrust to idle, and following repeated warnings, the engine is shut down, with the aircraft continuing flight and landing on a single engine.\n\nThe recurrence of this pattern across different aircraft types may point to broader systemic operational issues, including elevated engine wear, extended maintenance cycles, the use of refurbished or reused components, and uneven technical condition across the propulsion systems in service.\n\nIt is also worth noting that such failures were recorded across a wide range of platforms, including both combat aircraft and military transport aviation.\n\nIn Russian technical literature on aviation incidents, including reports by the Interstate Aviation Committee (IAC), activation of the “metal particles in oil” warning is treated as an indication of metallic debris within the engine or gearbox lubrication system. It is generally interpreted as a marker of abnormal technical condition, potentially linked to accelerated wear or the early stages of damage to friction components.\n\nIn particular,[ the IAC investigation into an An-24](https://www.baaa-acro.com/sites/default/files/2021-08/RA-47302.pdf) accident recorded the activation of the “metal particles in oil” warning, followed by a decrease in oil pressure and the subsequent progression to a complete engine failure.\n\n- **Aircraft systems malfunctions**\n\nThis is a generalized category that includes incidents such as a **Ka-52M** total hydraulic system failure, a **MiG-31BM** failure of both inertial navigation systems, a **Su-34** loss of airspeed indication, and an **Il-76MD-M **stabilizer jam.\n\n- **Wing and flight control system malfunctions**\n\nIncidents involving malfunctions of movable aerodynamic surfaces and flight control systems, affecting aircraft controllability and handling. Examples include a **Be-200ES** leading-edge slat jam and an **Il-76MD-M** stabilizer jam.\n\nIn IAC materials, such events are typically described in terms of specific component failures, including flap or slat malfunctions, high-lift system faults, or flight control system anomalies.\n\n- **External factors**\nSingle case: Ka-27PS bird strike resulting in engine damage and compressor damage.\n\n- **Ordnance-related incidents**\n\n**Su-34** — an uncommanded release of a FAB-500 bomb fitted with a UMPK glide kit during takeoff. The incident occurred during the aircraft’s takeoff run. According to available information, at the moment of liftoff (when the aircraft had already left the runway but was still at very low altitude), an uncommanded release of one FAB-500 aerial bomb equipped with a UMPK glide kit occurred. The munition impacted approximately 300 meters beyond the runway threshold along the takeoff heading.\n\nUncommanded releases of FAB-series bombs have been repeatedly observed and are not isolated incidents. According to[ ASTRA](https://astra.press/english/2026/03/06/12139/), at least 10 aerial bombs have been dropped by Russian aircraft on the territory of the Russian Federation in 2026. ASTRA also previously reported at least 143 such incidents in 2025 involving Russian bombs falling on both Russian and occupied territories, and at least 165 cases in 2024.\n\n- **Possible combat-related damage**\n\n**Mi-8** — observed damage includes a punctured tail boom, severed control cables, a large metal fragment, and penetration of an armored panel. Such damage is highly unlikely under normal operating conditions. One possible source is fragmentation from an air defense missile; however, in the absence of photographic evidence, the exact nature of the fragment cannot be determined. \n\n- **Human factors and operational errors**\n\n**Su-34** — overran the runway following an aborted takeoff. The incident occurred due to crew actions and flight operation procedures.\n**Su-35S** — aircraft damaged while taxiing after striking a shelter gate.\n**An-72**— took off in wind conditions exceeding the allowable limits.\n\n##### **Although pilots are not within the scope of this analysis and merit separate consideration, a brief selection of cases is provided below.**\n\nThe last incident mentioned in the structure appears, at first glance, to be a routine aviation event, in which the crew made a formally incorrect decision to proceed with a flight despite forecast meteorological conditions exceeding the aircraft’s operational limits. In this case, the more notable aspect is not the incident itself, but the personnel being transported. In particular, the flight involved senior leadership of the 12th Military Transport Aviation Division (12 VTAD), including the group commander, Colonel L.I. Rusin.\n\nBack in 2023, Ukrainian hackers from the 256 Cyber Assault Division (formerly Cyber Resistance), in cooperation with volunteers from the InformNapalm international intelligence community, conducted a CYBINT & OSINT operation to gain access to and analyze email correspondence of[ Russian Colonel Leonid Rusin](https://informnapalm.org/en/hacking-colonel-leonid-rusin/), former commander of military unit 41520. Rusin’s personal data [was published](https://osintbees.com/vony-navodiat-rakety-na-tsyvilni-obiek/) by OSINT Bees in the same year.\n\nUntil July 2022, Rusin was in command of the 610th Center for Combat Training and Retraining of Military Pilots (military unit 41520), Ivanovo city, Severny airfield.\n\n![Русин ВТА](https://cdn.osintflow.com/31/Rusin_76469bee42.webp)\n_A 2025 photo of Rusin. At the Tver Military Transport Aviation formation, unit commander Guards Colonel Leonid Rusin personally awarded state and departmental medals to Military Transport Aviation personnel and veterans ahead of February 23, 2025._\n\nThe aircraft carrying Rusin was commanded by aircraft **captain A.A. Gladkikh**, 1st class. During identification of the pilot, the most likely match was determined to be Artem Andreevich Gladkikh, born 10 May 1991.\n\nOn an old, now inactive public VKontakte account, Gladkikh posted a photo of his wedding in 2017, where he appears in uniform still holding lieutenant’s shoulder boards and wearing a pilot qualification badge marked with the number “3” — a basic level of pilot qualification in Russian state aviation, awarded after completing flight training and authorizing flights under instructor supervision or independently.\n\nNotably, in 2023, the individual reportedly registered a “Phoenix DPR” license plate — “Phoenix” being a local mobile operator in the self-proclaimed Donetsk People’s Republic operating in Russia-occupied territory.\n\n![Капитан Гладких_свадьба](https://cdn.osintflow.com/31/Kapitan_Gladkih_svadba_68db50d657.webp)\n_Source: VKontakte https://vk.com/id425381079, uploaded in 2017._\n\n![Глаких_капитан_випуск](https://cdn.osintflow.com/31/Glakih_kapitan_vipusk_21d14d9f6f.webp)\n_Source: VKontakte_\n\nAnother pilot referenced in the document is **Major V.V. Cheremukhin**, 1st class. Based on information previously shared on social media, Vitaliy Viktorovich Cheremukhin (born 16 February 1987) is a graduate of the Krasnodar Higher Military Aviation School of Pilots (Military Institute) named after Serov.\n\n![черемухин_майор_пилот](https://cdn.osintflow.com/31/cheremuhin_major_1_b81050f362.webp)\n_Source: MoiMir, publicly available photos of Cheremukhin, uploaded in 2011_\n\n![черемухин_майор_фото2011](https://cdn.osintflow.com/31/cheremuhin_major_3_af848d9b56.webp)\n_Source: MoiMir, publicly available photos of Cheremukhin, uploaded in 2011_\n\n  ![черемухин_майор_летчик](https://cdn.osintflow.com/31/cheremuhin_major_2_0f27aa233e.webp)\n_Source:VKontakte_\n\n**Major P.Yu. Kozhevnikov,** also mentioned in the document, has previously appeared in public sources. In 2022, the Main Directorate of Intelligence of the Ministry of Defense of Ukraine (HUR MO) published lists of servicemen of the[ 117th Separate Military Transport Aviation Regiment (military unit 45097, Omsk) ](https://gur.gov.ua/content/spysok-viiskovosluzhbovtsiv-117-okremoho-transportnoho-aviatsiinoho-polku-viiskova-chastyna-45097-m-omsk-iaki-dostavliaiut-zbroiu-ta-boieprypasy-dlia-vbyvstva-myrnykh-hromadian-ukrainy.html) involved in the delivery of weapons and ammunition used in the war against Ukraine, where Kozhevnikov is listed as a senior lieutenant at the time.\n\nA Military Transport Aviation pilot involved in an Il-76M incident was aircraft commander **Captain A.S. Ryabykh.** Artem Sergeyevich Ryabykh (born 29 November 1996) comes from a military family; his father served in military unit 28004-T from at least 2013 to 2022, which was also listed as his place of service.\n\nAccording to FOMS leak data related to Artem Ryabykh, an address associated with “Balashov, military unit 78474-A” appeared in 2007, likely indicating his father’s service there as well. The same address also reappeared in 2023 datasets. As is known, the Balashov airbase in the Saratov region hosts the 606th Training Aviation Regiment, which is part of the Russian Air Force pilot training system and operates transport aircraft, including the An-26.\n\n“Ulyanovsk-Vostochny Airport” was listed by Artem as his place of employment when registering as a volunteer on the dobro.ru platform. In public Telegram chats, he also referenced the number of locations and airfields he had visited. The list includes more than 60 cities and places, including locations in occupied Crimea, as well as distant countries: “59 Syria, 60 Algeria, 61 Mali, 62 the Central African Republic, 63 Libya.” The messages have since been deleted, however, message parsing and archiving services continue to preserve copies of the correspondence.\n\n![капитан_рябых](https://cdn.osintflow.com/31/kapitan_ryabyh_1_27c1293852.webp)\n_Source: Telegram profile picture_\n\n![капитан_рябых_вк](https://cdn.osintflow.com/31/ryabyh_2_10df13e9db.webp)\n_Source: Screenshot of a VKontakte page_\n\nFlight instructor and aviation unit commander **Bogdan Pavel Pavlovich** (born 17 December 1993) was involved in a Military Transport Aviation incident involving an Il-76M flight on 14 January along the route Ulan-Ude (Vostochny) – Knevichi.\n\nAccording to Instagram stories posted by Captain Bogdan, he was in Ulan-Ude in the second half of January. Notably, according to “Kordon” database leaks aggregated in [OsintKit](https://osintkit.net/), he made at least 11 flights to the Syrian Arab Republic in 2020–2021. He also visited occupied Crimea in 2024, as stated in his own social media posts. Leak data associated with the individual also references an address in a hotel complex in Feodosia.\n\n![богдан_капитан_тг_сторіз_спорт](https://cdn.osintflow.com/31/bogdan3_638e5b61c1.webp)\n_Source: Telegram stories_\n\n![богдан_капитан_тг_сторіз](https://cdn.osintflow.com/31/bogdan_2_056512a42b.webp)\n_Source: Telegram stories._\n\n![Богдан_сирія](https://cdn.osintflow.com/31/Bogdan_siriya_aeaa943570.webp)\n_Source: OsintKit https://osintkit.net/_\n\n![богдан_капитан_вк](https://cdn.osintflow.com/31/bogdan_v_yunosti2_8004f0b8cb.webp)\n_Source:VKontakte _\n\n![богдан_капитан_крим](https://cdn.osintflow.com/31/bogdan_krim_ba88c12f38.webp)\n_Public comment regarding the individual’s presence in Crimea in 2024_\n\nAircraft commander (2nd class) **S.S. Golubnichy**. Sergey Sergeyevich Golubnichy (born 18 April 1991) worked for the Russian Ministry of Emergency Situations (EMERCOM) for several years, including involvement in forest firefighting operations. In 2014, he graduated from the Saint Petersburg State University of Civil Aviation. \n\nNotably, records indicate he crossed the Ukrainian border in 2016. According to leaked datasets, the following movements are recorded:\n\n2016-12-02: Ukraine, Luhansk to Russia, Donetsk (Izyvarino)\n2016-11-28: Russia, Donetsk (Izyvarino) to Ukraine, Luhansk\n\n![голубничий_вк_капитан](https://cdn.osintflow.com/31/golubnichij_vk_c68bcde145.webp)\n_Source:VKontakte_\n\n![голубничий_капитан](https://cdn.osintflow.com/31/golubnichij_0c1d59ce2b.webp)\n_Source:VKontakte_",[629,630,631],{"id":357,"documentId":358,"name":359,"slug":359,"createdAt":360,"updatedAt":360,"publishedAt":361},{"id":233,"documentId":234,"name":235,"slug":235,"createdAt":236,"updatedAt":237,"publishedAt":238},{"id":351,"documentId":352,"name":205,"slug":205,"createdAt":353,"updatedAt":354,"publishedAt":355},{"id":633,"metaTitle":634,"metaDescription":576,"keywords":635,"metaRobots":39,"metaViewport":40,"canonicalURL":636,"structuredData":637},261,"Russian aviation incidents: engine failures, bomb drops","Russian aviation, Russian aviation report, aircraft engine failures, helicopter accidents, Crimea incidents, accidental bomb drops, FAB bombs, Russian military aviation, aviation safety issues, aviation sanctions, aircraft maintenance problems, OSINT, military incidents Russia, technical failures aircraft, Russian air force operations","https://osintflow.com/en/news/russian-aviation-report-engine-failures-fab-crimea/",{"@type":260,"image":638,"author":640,"@context":48,"headline":576,"keywords":642,"publisher":652,"inLanguage":15,"description":655,"dateModified":656,"datePublished":656,"articleSection":657,"mainEntityOfPage":658,"isAccessibleForFree":659},{"url":639,"@type":262,"width":94,"height":263},"https://osintflow.com/path-to-image.jpg",{"url":52,"name":641,"@type":47},"OSINT Flow",[643,644,645,646,647,648,649,650,57,651],"Russian aviation","aircraft engine failures","helicopter accidents","Crimea incidents","accidental bomb drops","FAB bombs","Russian military aviation","aviation safety","military aviation Russia",{"url":52,"logo":653,"name":641,"@type":47},{"url":654,"@type":262,"width":230,"height":230},"https://osintflow.com/path-to-logo.png","An analysis of an internal Russian aviation report highlighting engine failures, accidental bomb drops, and helicopter incidents in Crimea, reflecting systemic issues in Russian military aviation.","2026-03-21","Defense",{"@id":636,"@type":59},true,[661],{"id":662,"documentId":575,"title":663,"description":664,"slug":665,"publicationDate":666,"createdAt":667,"updatedAt":668,"publishedAt":669,"locale":29},760,"Відмови двигунів, сход ФАБ та пошкодження вертольота в Криму: що показав внутрішній звіт авіації РФ","В процесі роботи команда OsintFlow добула цікавий документ – «Информация по безопасности полетов» за період з 29 грудня 2025 по 18 січня 2026 року, у якому чітко списком зазначені деталі авіаційних подій у воєнно-транспортній та державній авіації Росії","zvit-rf-aviatsiia-vidmovy-dvyhuniv-fab-krym","2026-03-20T09:00:00.000Z","2026-03-18T19:04:38.720Z","2026-03-28T13:49:13.759Z","2026-03-21T21:13:24.245Z",{"pagination":671},{"page":672,"pageSize":537,"pageCount":203,"total":673},1,29,{"data":675,"meta":773},[676,705,728,756],{"id":159,"documentId":160,"title":161,"description":162,"slug":163,"publicationDate":164,"createdAt":165,"updatedAt":166,"publishedAt":167,"locale":15,"cover":677,"authors":681,"category":683,"blocks":684,"tags":692,"seo":696,"localizations":703},{"id":169,"documentId":170,"name":171,"alternativeText":172,"caption":172,"width":173,"height":174,"formats":678,"hash":190,"ext":88,"mime":91,"size":191,"url":192,"previewUrl":9,"provider":116,"provider_metadata":9,"createdAt":193,"updatedAt":193,"publishedAt":194},{"medium":679,"thumbnail":680},{"ext":88,"url":177,"hash":178,"mime":91,"name":179,"path":9,"size":180,"width":102,"height":181,"sizeInBytes":182},{"ext":88,"url":184,"hash":185,"mime":91,"name":186,"path":9,"size":187,"width":110,"height":188,"sizeInBytes":189},[682],{"id":197,"documentId":198,"name":199,"email":9,"createdAt":200,"updatedAt":200,"publishedAt":201},{"id":203,"documentId":204,"name":205,"slug":206,"description":9,"createdAt":207,"updatedAt":208,"publishedAt":209,"locale":15},[685,686,687,688,689,690,691],{"__component":18,"id":212,"body":213},{"__component":215,"id":216,"content":217},{"__component":219,"id":220},{"__component":215,"id":222,"content":223},{"__component":219,"id":225},{"__component":215,"id":227,"content":228},{"__component":219,"id":230},[693,694,695],{"id":233,"documentId":234,"name":235,"slug":235,"createdAt":236,"updatedAt":237,"publishedAt":238},{"id":240,"documentId":241,"name":242,"slug":243,"createdAt":244,"updatedAt":245,"publishedAt":246},{"id":248,"documentId":249,"name":250,"slug":250,"createdAt":251,"updatedAt":252,"publishedAt":253},{"id":255,"metaTitle":256,"metaDescription":161,"keywords":257,"metaRobots":39,"metaViewport":40,"canonicalURL":258,"structuredData":697},{"@type":260,"image":698,"author":699,"@context":48,"headline":266,"keywords":700,"publisher":701,"inLanguage":15,"description":161,"dateModified":276,"datePublished":276,"articleSection":277,"mainEntityOfPage":702,"alternativeHeadline":279},{"url":192,"@type":262,"width":94,"height":263},{"name":199,"@type":265},[57,268,269,270,271,272,273,274],{"url":52,"name":46,"@type":47},{"@id":258,"@type":59},[704],{"id":282,"documentId":160,"title":283,"description":284,"slug":285,"publicationDate":286,"createdAt":287,"updatedAt":288,"publishedAt":289,"locale":29},{"id":291,"documentId":292,"title":293,"description":294,"slug":295,"publicationDate":296,"createdAt":297,"updatedAt":298,"publishedAt":299,"locale":15,"cover":706,"authors":711,"category":713,"blocks":714,"tags":716,"seo":720,"localizations":726},{"id":301,"documentId":302,"name":303,"alternativeText":304,"caption":304,"width":305,"height":306,"formats":707,"hash":329,"ext":88,"mime":91,"size":330,"url":331,"previewUrl":9,"provider":116,"provider_metadata":9,"createdAt":332,"updatedAt":333,"publishedAt":334},{"large":708,"medium":709,"thumbnail":710},{"ext":88,"url":309,"hash":310,"mime":91,"name":311,"path":9,"size":312,"width":94,"height":173,"sizeInBytes":313},{"ext":88,"url":315,"hash":316,"mime":91,"name":317,"path":9,"size":318,"width":102,"height":319,"sizeInBytes":320},{"ext":88,"url":322,"hash":323,"mime":91,"name":324,"path":9,"size":325,"width":326,"height":327,"sizeInBytes":328},[712],{"id":337,"documentId":338,"name":339,"email":340,"createdAt":341,"updatedAt":342,"publishedAt":343},{"id":203,"documentId":204,"name":205,"slug":206,"description":9,"createdAt":207,"updatedAt":208,"publishedAt":209,"locale":15},[715],{"__component":18,"id":347,"body":348},[717,718,719],{"id":351,"documentId":352,"name":205,"slug":205,"createdAt":353,"updatedAt":354,"publishedAt":355},{"id":357,"documentId":358,"name":359,"slug":359,"createdAt":360,"updatedAt":360,"publishedAt":361},{"id":233,"documentId":234,"name":235,"slug":235,"createdAt":236,"updatedAt":237,"publishedAt":238},{"id":364,"metaTitle":365,"metaDescription":366,"keywords":367,"metaRobots":368,"metaViewport":40,"canonicalURL":369,"structuredData":721},{"url":371,"@type":260,"image":309,"author":722,"@context":48,"headline":373,"keywords":723,"publisher":724,"inLanguage":380,"description":381,"dateModified":382,"datePublished":382,"mainEntityOfPage":725,"alternativeHeadline":384},{"name":46,"@type":47},[57,375,376,377,46,378],{"name":46,"@type":47},{"@id":371,"@type":59},[727],{"id":387,"documentId":292,"title":388,"description":389,"slug":390,"publicationDate":296,"createdAt":391,"updatedAt":392,"publishedAt":393,"locale":29},{"id":395,"documentId":396,"title":397,"description":398,"slug":399,"publicationDate":400,"createdAt":401,"updatedAt":402,"publishedAt":403,"locale":15,"cover":729,"authors":734,"category":736,"blocks":737,"tags":745,"seo":749,"localizations":754},{"id":405,"documentId":406,"name":407,"alternativeText":408,"caption":408,"width":84,"height":409,"formats":730,"hash":432,"ext":88,"mime":91,"size":433,"url":434,"previewUrl":9,"provider":116,"provider_metadata":9,"createdAt":435,"updatedAt":435,"publishedAt":436},{"large":731,"medium":732,"thumbnail":733},{"ext":88,"url":412,"hash":413,"mime":91,"name":414,"path":9,"size":415,"width":94,"height":416,"sizeInBytes":417},{"ext":88,"url":419,"hash":420,"mime":91,"name":421,"path":9,"size":422,"width":102,"height":423,"sizeInBytes":424},{"ext":88,"url":426,"hash":427,"mime":91,"name":428,"path":9,"size":429,"width":110,"height":430,"sizeInBytes":431},[735],{"id":197,"documentId":198,"name":199,"email":9,"createdAt":200,"updatedAt":200,"publishedAt":201},{"id":203,"documentId":204,"name":205,"slug":206,"description":9,"createdAt":207,"updatedAt":208,"publishedAt":209,"locale":15},[738,739,740,741,742,743,744],{"__component":18,"id":442,"body":443},{"__component":219,"id":445},{"__component":447,"id":448,"description":449},{"__component":215,"id":451,"content":452},{"__component":215,"id":454,"content":455},{"__component":215,"id":457,"content":458},{"__component":215,"id":460,"content":461},[746,747,748],{"id":248,"documentId":249,"name":250,"slug":250,"createdAt":251,"updatedAt":252,"publishedAt":253},{"id":233,"documentId":234,"name":235,"slug":235,"createdAt":236,"updatedAt":237,"publishedAt":238},{"id":240,"documentId":241,"name":242,"slug":243,"createdAt":244,"updatedAt":245,"publishedAt":246},{"id":467,"metaTitle":468,"metaDescription":397,"keywords":469,"metaRobots":39,"metaViewport":40,"canonicalURL":470,"structuredData":750},{"@type":260,"image":412,"author":751,"@context":48,"headline":474,"keywords":475,"publisher":752,"inLanguage":15,"description":477,"dateModified":478,"datePublished":478,"articleSection":57,"mainEntityOfPage":753},{"name":473,"@type":47},{"name":473,"@type":47},{"@id":480,"@type":59},[755],{"id":483,"documentId":396,"title":484,"description":485,"slug":486,"publicationDate":487,"createdAt":488,"updatedAt":489,"publishedAt":490,"locale":29},{"id":492,"documentId":493,"title":494,"description":495,"slug":496,"publicationDate":497,"createdAt":498,"updatedAt":499,"publishedAt":500,"locale":15,"cover":757,"authors":762,"category":763,"blocks":764,"tags":767,"seo":770,"localizations":771},{"id":502,"documentId":503,"name":504,"alternativeText":505,"caption":505,"width":84,"height":506,"formats":758,"hash":529,"ext":88,"mime":91,"size":530,"url":531,"previewUrl":9,"provider":116,"provider_metadata":9,"createdAt":532,"updatedAt":533,"publishedAt":534},{"large":759,"medium":760,"thumbnail":761},{"ext":88,"url":509,"hash":510,"mime":91,"name":511,"path":9,"size":512,"width":94,"height":513,"sizeInBytes":514},{"ext":88,"url":516,"hash":517,"mime":91,"name":518,"path":9,"size":519,"width":102,"height":520,"sizeInBytes":521},{"ext":88,"url":523,"hash":524,"mime":91,"name":525,"path":9,"size":526,"width":110,"height":527,"sizeInBytes":528},[],{"id":537,"documentId":538,"name":539,"slug":540,"description":9,"createdAt":541,"updatedAt":541,"publishedAt":542,"locale":15},[765,766],{"__component":18,"id":545,"body":546},{"__component":447,"id":548,"description":549},[768,769],{"id":357,"documentId":358,"name":359,"slug":359,"createdAt":360,"updatedAt":360,"publishedAt":361},{"id":553,"documentId":554,"name":555,"slug":555,"createdAt":556,"updatedAt":557,"publishedAt":558},{"id":560,"metaTitle":494,"metaDescription":561,"keywords":562,"metaRobots":39,"metaViewport":40,"canonicalURL":563,"structuredData":9},[772],{"id":566,"documentId":493,"title":567,"description":568,"slug":496,"publicationDate":569,"createdAt":570,"updatedAt":571,"publishedAt":572,"locale":29},{"pagination":774},{"page":672,"pageSize":775,"pageCount":776,"total":673},4,8,{"data":778},[779,885,1305,1393,1407,1418,1469,1478,1503,1518,1546,1559,1597],{"id":780,"documentId":781,"name":782,"slug":782,"createdAt":783,"updatedAt":784,"publishedAt":785,"articles":786,"seo":9},30,"ysf3fi2en1rizj77yszd4i0h","osintflow","2025-07-12T11:05:25.809Z","2026-01-13T20:39:31.460Z","2026-01-13T20:39:31.408Z",[787,797,805,814,823,828,837,846,854,864,874,875],{"id":788,"documentId":789,"title":790,"description":791,"slug":792,"publicationDate":793,"createdAt":794,"updatedAt":795,"publishedAt":796,"locale":15},197,"sxgm8r0qdpaa1b0o8h8kkuxf","How to use OSINT tools effectively? OsintFlow team shares its experience","","2024-07-10","2024-07-10T05:07:11.000Z","2025-07-12T11:05:32.682Z","2025-07-12T11:13:12.131Z","2025-07-12T11:05:32.705Z",{"id":798,"documentId":799,"title":800,"description":791,"slug":801,"publicationDate":802,"createdAt":803,"updatedAt":803,"publishedAt":804,"locale":29},253,"y2sccsnopt47zkahjdieqo3k","Команда OsintFlow знову готова ділитися досвідом!","2024-04-11","2024-04-11T05:07:11.000Z","2025-07-12T11:11:26.008Z","2025-07-12T11:11:26.027Z",{"id":806,"documentId":807,"title":808,"description":791,"slug":809,"publicationDate":810,"createdAt":811,"updatedAt":812,"publishedAt":813,"locale":29},344,"xlw6fi68s6w7vnh3qwba5iuy","ССО ГУ ГШ ЗС РФ. ВЧ 00317. Севастополь. Частина 2.","2024-05-27-02","2024-05-27T05:07:11.000Z","2025-07-12T11:12:48.193Z","2025-10-09T22:48:22.153Z","2025-10-09T22:48:22.284Z",{"id":815,"documentId":816,"title":817,"description":791,"slug":818,"publicationDate":819,"createdAt":820,"updatedAt":821,"publishedAt":822,"locale":29},679,"m9aq9ogdqvl88l04xo46wbgm","ССО ГУ ГШ ЗС РФ. ВЧ 00317. Севастополь","2024-05-27","2024-05-27T04:08:11.000Z","2025-07-12T11:12:58.514Z","2026-02-05T13:01:38.445Z","2026-02-05T13:01:38.510Z",{"id":824,"documentId":789,"title":825,"description":791,"slug":792,"publicationDate":793,"createdAt":826,"updatedAt":826,"publishedAt":827,"locale":29},265,"Як ефективно використовувати OSINT інструментарій? Команда «OsintFlow» ділиться досвідом ","2025-07-12T11:13:12.070Z","2025-07-12T11:13:12.090Z",{"id":829,"documentId":830,"title":831,"description":791,"slug":832,"publicationDate":833,"createdAt":834,"updatedAt":835,"publishedAt":836,"locale":29},341,"l03tg3prlk48xe0ezd8fbnjt","«Гостомельські десантники». 45 окрема бригада спеціального призначення ПДВ (45 ОБрСпП ПДВ) РФ","2024-07-29","2024-07-29T05:07:11.000Z","2025-07-12T11:14:08.896Z","2025-10-09T22:47:19.596Z","2025-10-09T22:47:19.685Z",{"id":838,"documentId":839,"title":840,"description":791,"slug":841,"publicationDate":842,"createdAt":843,"updatedAt":844,"publishedAt":845,"locale":29},339,"pwghj0j16jwh60c0t512ncg1","Поєднання GEO та OSINT. Севастопольський Спецзагін ГРУ та «Уссурійські воїни»","2024-09-26","2024-09-26T05:07:11.000Z","2025-07-12T11:14:34.168Z","2025-10-09T19:07:24.985Z","2025-10-09T19:07:25.037Z",{"id":847,"documentId":848,"title":849,"description":791,"slug":850,"publicationDate":851,"createdAt":852,"updatedAt":852,"publishedAt":853,"locale":29},273,"zhrsvkebtszg5bhve869vcg0","\"Позивний Армян\"","2024-10-31","2024-10-31T05:07:11.000Z","2025-07-12T11:15:38.539Z","2025-07-12T11:15:38.571Z",{"id":855,"documentId":856,"title":857,"description":858,"slug":859,"publicationDate":860,"createdAt":861,"updatedAt":862,"publishedAt":863,"locale":29},484,"ih1hjtl45tcjkwiuihi2wh9w","Мороз Сергей Владимирович","Осінт досьє. Підполковник РОВ, командир групи зенітних ракетних дивізіонів 24-ої Зенітно ракетної бригади (в/ч 79222). Командир в/ч 79222-2","moroz-sergej-vladimirovich","2026-01-13T21:02:00.000Z","2026-01-13T19:33:46.847Z","2026-01-15T11:38:22.415Z","2026-01-14T15:15:42.994Z",{"id":865,"documentId":866,"title":867,"description":868,"slug":869,"publicationDate":870,"createdAt":871,"updatedAt":872,"publishedAt":873,"locale":29},485,"rly9pymg0icozm01wy9pfit7","Винский Марат Валерьевич","Осінт досьє. Ветеран війни в Україні. Єфрейтор, 35 ОМСБр, в/ч 41659","vinskij-marat-valerevich","2026-01-07T15:16:00.000Z","2026-01-07T17:00:50.326Z","2026-01-15T11:15:48.796Z","2026-01-14T15:17:00.401Z",{"id":566,"documentId":493,"title":567,"description":568,"slug":496,"publicationDate":569,"createdAt":570,"updatedAt":571,"publishedAt":572,"locale":29},{"id":876,"documentId":877,"title":878,"description":879,"slug":880,"publicationDate":881,"createdAt":882,"updatedAt":883,"publishedAt":884,"locale":29},814,"tlhdf5w3aizpe2h0f6hc9bu7","Вивчаємо тактику противника","До команди OsintFlow потрапила лекція РОВ «Застосування розрахунків з FPV-дронами в інтересах батальйону», якою ми ділимось із вами.","fpv-drone-tactics-rov","2026-05-06T16:00:00.000Z","2026-05-06T16:31:26.088Z","2026-05-06T17:08:17.701Z","2026-05-06T17:08:17.805Z",{"id":248,"documentId":249,"name":250,"slug":250,"createdAt":251,"updatedAt":252,"publishedAt":253,"articles":886,"seo":9},[887,896,905,914,923,932,941,950,959,968,977,986,995,1004,1012,1020,1028,1036,1046,1054,1062,1070,1079,1087,1096,1104,1110,1116,1122,1128,1133,1139,1146,1153,1159,1167,1176,1186,1195,1205,1213,1222,1232,1242,1252,1261,1271,1281,1291,1292,1293,1303,1304],{"id":263,"documentId":888,"title":889,"description":890,"slug":891,"publicationDate":892,"createdAt":893,"updatedAt":894,"publishedAt":895,"locale":15},"v8ol1os52c9yb1oca2xqr9c2","The family of the chief designer of the Lancet and Orlan UAVs, Director of ZALA Aero Group - Oleksandr Zakharov","The family of Zakharov, the chief designer behind the Lancet and Orlan UAVs and director of ZALA Aero Group","zakharov-family-zala-aero-uav-en","2023-11-03T05:08:10.000Z","2025-07-12T11:02:53.196Z","2026-01-29T04:31:56.803Z","2026-01-29T04:25:12.301Z",{"id":897,"documentId":898,"title":899,"description":791,"slug":900,"publicationDate":901,"createdAt":902,"updatedAt":903,"publishedAt":904,"locale":15},605,"kpuj5g9mhsdv6fx6wjjkw6b7","OsintFlow has identified the names of \"Kalashnikov\" Group employees","kalashnikov-employees-en","2023-11-16T05:08:10.000Z","2025-07-12T11:02:55.276Z","2026-01-29T02:35:53.078Z","2026-01-29T02:35:53.172Z",{"id":906,"documentId":907,"title":908,"description":791,"slug":909,"publicationDate":910,"createdAt":911,"updatedAt":912,"publishedAt":913,"locale":15},610,"nlbbnco4958j1m9065iemzqf","List of employees of the \"Kalashnikov\" Group of Companies, 2nd part","2023-11-18","2023-11-18T05:07:10.000Z","2025-07-12T11:02:57.413Z","2026-01-29T02:37:34.719Z","2026-01-29T02:37:34.782Z",{"id":915,"documentId":916,"title":917,"description":791,"slug":918,"publicationDate":919,"createdAt":920,"updatedAt":921,"publishedAt":922,"locale":15},179,"senjada99xvfqw1y7ogb6irv","On 22 November 2023, the occupation authorities held a meeting with farmers in Novotroitsk, Kherson region.","2023-11-27","2023-11-27T05:07:10.000Z","2025-07-12T11:03:33.664Z","2025-08-22T05:41:15.696Z","2025-07-12T11:03:33.699Z",{"id":924,"documentId":925,"title":926,"description":791,"slug":927,"publicationDate":928,"createdAt":929,"updatedAt":930,"publishedAt":931,"locale":15},631,"wj3eu73br9ggrhesluh7ep0j","OsintFlow gained access to the mail of the acting director of the \"Department of Education and Science of Sevastopol\" - Kryvonos Maksym Yuriyovych.","2023-11-29","2023-11-29T05:07:10.000Z","2025-07-12T11:03:36.380Z","2026-01-29T04:27:51.648Z","2026-01-29T04:27:51.696Z",{"id":933,"documentId":934,"title":935,"description":791,"slug":936,"publicationDate":937,"createdAt":938,"updatedAt":939,"publishedAt":940,"locale":15},612,"d6vgn839xkrpkv780dn5ftfw","OsintFlow volunteers have collected a list of employees of \"SPECIAL TECHNOLOGICAL CENTRE\" LLC.","2023-12-12","2023-12-12T05:07:10.000Z","2025-07-12T11:03:38.519Z","2026-01-29T02:38:24.270Z","2026-01-29T02:38:24.344Z",{"id":942,"documentId":943,"title":944,"description":791,"slug":945,"publicationDate":946,"createdAt":947,"updatedAt":948,"publishedAt":949,"locale":15},609,"i16ad8rmkxeb1mbid36bxion","OsintFlow volunteers have compiled a list of employees of SPECIAL TECHNOLOGICAL CENTRE LLC. Part 2","2023-12-13","2023-12-13T05:07:11.000Z","2025-07-12T11:03:39.666Z","2026-01-29T02:37:12.689Z","2026-01-29T02:37:12.765Z",{"id":951,"documentId":952,"title":953,"description":791,"slug":954,"publicationDate":955,"createdAt":956,"updatedAt":957,"publishedAt":958,"locale":15},288,"he9v1ovpmdm6x8fxgnqtxd0y","OsintFlow identified a part of the board of directors and employees of Novator Design Bureau, which manufactures Kalibr missiles","2024-01-08","2024-01-08T05:07:10.000Z","2025-07-12T11:03:41.747Z","2025-08-05T12:25:16.033Z","2025-08-05T12:25:17.631Z",{"id":960,"documentId":961,"title":962,"description":791,"slug":963,"publicationDate":964,"createdAt":965,"updatedAt":966,"publishedAt":967,"locale":15},608,"w1qvaoj0ie2a39xz0b9thf9u","OsintFlow installed a part of the board of directors and employees of JSC Concern VKO Almaz-Antey","2024-01-13","2024-01-13T05:07:10.000Z","2025-07-12T11:03:43.565Z","2026-01-29T02:36:53.532Z","2026-01-29T02:36:53.608Z",{"id":969,"documentId":970,"title":971,"description":791,"slug":972,"publicationDate":973,"createdAt":974,"updatedAt":975,"publishedAt":976,"locale":15},606,"s99y6h6k0xhz17tddnrfork3","Putin's cousin and nephews","2024-01-15","2024-01-15T05:07:10.000Z","2025-07-12T11:04:07.061Z","2026-02-04T16:58:16.420Z","2026-01-29T02:36:14.271Z",{"id":978,"documentId":979,"title":980,"description":791,"slug":981,"publicationDate":982,"createdAt":983,"updatedAt":984,"publishedAt":985,"locale":15},193,"d3fyb6n3oh75ytd6wcfc5yo5","How OSINT saves lives. OsintFlow team helps prevent sabotage in eastern Ukraine","2024-01-25","2024-01-25T05:07:11.000Z","2025-07-12T11:04:27.464Z","2025-10-10T16:26:19.391Z","2025-07-12T11:04:27.493Z",{"id":987,"documentId":988,"title":989,"description":791,"slug":990,"publicationDate":991,"createdAt":992,"updatedAt":993,"publishedAt":994,"locale":15},607,"rf5teybb9at7nn491hw5bxgu","Identification of key war criminals of BARS-35 «Skif»","2024-02-14","2024-02-13T05:07:11.000Z","2025-07-12T11:05:25.453Z","2026-01-29T02:36:26.219Z","2026-01-29T02:36:26.327Z",{"id":996,"documentId":997,"title":998,"description":791,"slug":999,"publicationDate":1000,"createdAt":1001,"updatedAt":1002,"publishedAt":1003,"locale":29},596,"mhsp2g5om80zjqf1g2se2fgs","Генерал-полковник Кузовлев Сергій Юрійович, командувач Південного військового округу зс рф, воєнний злочинець","Kuzovlev-Sergey-Yurievich","2023-01-25T05:07:10.000Z","2025-07-12T11:06:09.281Z","2026-01-29T02:22:32.573Z","2026-01-29T02:22:33.616Z",{"id":1005,"documentId":1006,"title":1007,"description":791,"slug":1008,"publicationDate":1009,"createdAt":1010,"updatedAt":1010,"publishedAt":1011,"locale":29},203,"jhwlzkv32dz2r8wjdvql28hq","Керівник операції по захопленню Гостомеля і Київської області","2023-02-23","2023-02-23T05:07:10.000Z","2025-07-12T11:06:31.497Z","2025-07-12T11:06:31.522Z",{"id":1013,"documentId":1014,"title":1015,"description":791,"slug":1016,"publicationDate":1017,"createdAt":1018,"updatedAt":1018,"publishedAt":1019,"locale":29},205,"up7ej5s9cwra937wb6smvbnm","Колишній адвокат “беркутівців”, Шарія та російської агентури в Україні який використовував в українському суді свою переписку з ватажками терористів “ДНР” змінив зовнішність та прислуговує окупантам у якості “міністра інформполітики” Херсонської області","2023-03-24","2023-03-24T05:07:10.000Z","2025-07-12T11:06:46.381Z","2025-07-12T11:06:46.406Z",{"id":1021,"documentId":1022,"title":1023,"description":791,"slug":1024,"publicationDate":1025,"createdAt":1026,"updatedAt":1026,"publishedAt":1027,"locale":29},207,"nojgc88acf38ydbvuownaafn","Студентка-колаборантка, працівниця “ТРК Таврія”","2023-05-04","2023-05-04T05:07:10.000Z","2025-07-12T11:06:54.530Z","2025-07-12T11:06:54.560Z",{"id":1029,"documentId":1030,"title":1031,"description":791,"slug":1032,"publicationDate":1033,"createdAt":1034,"updatedAt":1034,"publishedAt":1035,"locale":29},211,"i0y32frfr86en0h764cz9ztm","Позивний “Ваха”. Рекрутер до БАРС 11","2023-05-19","2023-05-19T05:07:10.000Z","2025-07-12T11:07:36.111Z","2025-07-12T11:07:36.137Z",{"id":1037,"documentId":1038,"title":1039,"description":1040,"slug":1041,"publicationDate":1042,"createdAt":1043,"updatedAt":1044,"publishedAt":1045,"locale":29},635,"f43pdgpl3lrz2u5omejo3rh8","Родина Пєскова з актуальними даними","Персональні дані родини Пескова, прес-секретаря президента рф Владіміра Путіна","peskovs-family-ua","2023-08-24T06:12:00.000Z","2025-07-12T11:07:49.202Z","2026-01-29T04:35:15.215Z","2026-01-29T04:33:26.016Z",{"id":1047,"documentId":1048,"title":1049,"description":791,"slug":1050,"publicationDate":1051,"createdAt":1052,"updatedAt":1052,"publishedAt":1053,"locale":29},215,"bj1b0qo4i6lvw1vzv9r86b1m","Керівник  Академії ФСБ РФ генерал-майор Николай Владимирович Плотников","2023-08-25","2023-08-25T05:07:11.000Z","2025-07-12T11:07:51.064Z","2025-07-12T11:07:51.092Z",{"id":1055,"documentId":1056,"title":1057,"description":791,"slug":1058,"publicationDate":1059,"createdAt":1060,"updatedAt":1060,"publishedAt":1061,"locale":29},217,"mvf5eog0iqlyyr3t01h7rkx1","Орки Московского государственного университета.","2023-08-26","2023-08-26T05:07:11.000Z","2025-07-12T11:08:16.098Z","2025-07-12T11:08:16.126Z",{"id":1063,"documentId":1064,"title":1065,"description":791,"slug":1066,"publicationDate":1067,"createdAt":1068,"updatedAt":1068,"publishedAt":1069,"locale":29},219,"a7jauij9jbye4pnop9s75uhq","Сімейка Євгена Пригожина.","2023-08-28","2023-08-28T05:07:11.000Z","2025-07-12T11:08:21.388Z","2025-07-12T11:08:21.414Z",{"id":1071,"documentId":1072,"title":1073,"description":791,"slug":1074,"publicationDate":1075,"createdAt":1076,"updatedAt":1077,"publishedAt":1078,"locale":29},613,"y9vlxvcxvv9562su8h276qjr","Сім’я прем’єр-міністра Російської Федерації.","2023-08-29","2023-08-29T05:07:10.000Z","2025-07-12T11:08:27.309Z","2026-01-29T02:39:22.339Z","2026-01-29T02:39:22.444Z",{"id":1080,"documentId":1081,"title":1082,"description":791,"slug":1083,"publicationDate":1084,"createdAt":1085,"updatedAt":1085,"publishedAt":1086,"locale":29},223,"ubb943itgn6fqm96ot16b2b7","Патріарх Кирило - невідома сім’я КГБшніка.","2023-09-02","2023-09-02T05:07:11.000Z","2025-07-12T11:08:36.525Z","2025-07-12T11:08:36.943Z",{"id":1088,"documentId":888,"title":1089,"description":1090,"slug":1091,"publicationDate":1092,"createdAt":1093,"updatedAt":1094,"publishedAt":1095,"locale":29},634,"Сім’я головного конструктора БПЛА Ланцет та Орлан, директора ZALA Aero Group – ЗАХАРОВА Олександра Вячеславовича","Сім’я головного конструктора БПЛА Ланцет та Орлан, директора ZALA Aero Group – ЗАХАРОВА","zakharov-family-zala-aero-uav-ua","2023-11-03T05:08:00.000Z","2025-07-12T11:08:41.267Z","2026-01-29T04:31:56.595Z","2026-01-29T04:31:56.704Z",{"id":1097,"documentId":898,"title":1098,"description":791,"slug":1099,"publicationDate":1100,"createdAt":1101,"updatedAt":1102,"publishedAt":1103,"locale":29},603,"OsintFlow встановили імена співробітників групи компаній Калашніков","kalashnikov-employees-ua","2023-11-16T05:07:10.000Z","2025-07-12T11:08:42.197Z","2026-01-29T02:35:54.085Z","2026-01-29T02:35:11.111Z",{"id":1105,"documentId":907,"title":1106,"description":791,"slug":909,"publicationDate":910,"createdAt":1107,"updatedAt":1108,"publishedAt":1109,"locale":29},371,"Список співробітників групи компаній «Калашніков» 2-га частина","2025-07-12T11:08:43.297Z","2026-01-29T02:37:34.835Z","2025-10-10T16:23:29.344Z",{"id":1111,"documentId":916,"title":1112,"description":791,"slug":918,"publicationDate":919,"createdAt":1113,"updatedAt":1114,"publishedAt":1115,"locale":29},300,"22 листопада 2023 року, в Новотроїцьку Херсонської області окупаційна влада влаштувала зустріч з фермерами.","2025-07-12T11:08:45.464Z","2025-08-22T05:41:15.524Z","2025-08-22T05:41:15.611Z",{"id":1117,"documentId":925,"title":1118,"description":791,"slug":927,"publicationDate":928,"createdAt":1119,"updatedAt":1120,"publishedAt":1121,"locale":29},233,"OsintFlow отримали доступ до пошти виконуючого обовʼязки директора «департамента образования и науки города Севастополя». Кривоноса Максима Юрійовича.","2025-07-12T11:08:46.876Z","2026-01-29T04:27:51.741Z","2025-07-12T11:08:46.899Z",{"id":1123,"documentId":934,"title":1124,"description":791,"slug":936,"publicationDate":937,"createdAt":1125,"updatedAt":1126,"publishedAt":1127,"locale":29},235,"Волонтери OsintFlow зібрали список співробітників ООО «СПЕЦИАЛЬНЫЙ ТЕХНОЛОГИЧЕСКИЙ ЦЕНТР».","2025-07-12T11:08:47.967Z","2026-01-29T02:38:24.417Z","2025-07-12T11:08:47.985Z",{"id":136,"documentId":943,"title":1129,"description":791,"slug":945,"publicationDate":946,"createdAt":1130,"updatedAt":1131,"publishedAt":1132,"locale":29},"Волонтери OsintFlow зібрали список співробітників ООО «СПЕЦИАЛЬНЫЙ ТЕХНОЛОГИЧЕСКИЙ ЦЕНТР». Частина 2","2025-07-12T11:08:48.857Z","2026-01-29T02:37:12.836Z","2025-07-12T11:08:48.878Z",{"id":1134,"documentId":952,"title":1135,"description":791,"slug":954,"publicationDate":955,"createdAt":1136,"updatedAt":1137,"publishedAt":1138,"locale":29},287,"OsintFlow встановили частину ради директорів та співробітників АО “ОКБ “Новатор”, який виготовляє крилаті ракети “Калібри”","2025-07-12T11:08:49.867Z","2025-08-05T12:25:18.783Z","2025-08-05T12:23:57.786Z",{"id":1140,"documentId":970,"title":1141,"description":791,"slug":1142,"publicationDate":973,"createdAt":1143,"updatedAt":1144,"publishedAt":1145,"locale":29},663,"Двоюрідний брат та племінники Путіна","putin-family-network","2025-07-12T11:08:52.564Z","2026-02-04T16:58:16.283Z","2026-02-04T16:58:16.360Z",{"id":1147,"documentId":979,"title":1148,"description":791,"slug":1149,"publicationDate":982,"createdAt":1150,"updatedAt":1151,"publishedAt":1152,"locale":29},372,"Як OSINT рятує життя. Команда OsintFlow допомогла попередити диверсію на сході України","2024-01-26","2025-07-12T11:08:54.197Z","2025-10-10T16:26:19.285Z","2025-10-10T16:26:19.337Z",{"id":1154,"documentId":988,"title":1155,"description":791,"slug":990,"publicationDate":991,"createdAt":1156,"updatedAt":1157,"publishedAt":1158,"locale":29},353,"Ідентифікація ключових воєнних злочинців БАРС-35 «Скіф»","2025-07-12T11:09:00.235Z","2026-01-29T02:36:26.406Z","2025-10-09T22:51:54.625Z",{"id":1160,"documentId":1161,"title":1162,"description":791,"slug":1163,"publicationDate":1164,"createdAt":1165,"updatedAt":1165,"publishedAt":1166,"locale":29},249,"bdzoe9welmh16ycip0vxpxjp","Встановлено відповідальних за розстріл українських воїнів при здачі в полон 24 лютого 2024 року","2024-02-27","2024-02-27T05:07:11.000Z","2025-07-12T11:09:18.046Z","2025-07-12T11:09:18.075Z",{"id":1168,"documentId":856,"title":1169,"description":1170,"slug":1171,"publicationDate":1172,"createdAt":1173,"updatedAt":1174,"publishedAt":1175,"locale":15},495,"Moroz Sergey Vladimirovich","OSINT Profile. A Lieutenant Colonel, Commander of the Group of Anti-Aircraft Missile Divisions of the 24th Anti-Aircraft Missile Brigade","moroz-sergej-vladimirovich-en","2026-01-13T22:14:00.000Z","2026-01-15T10:10:14.571Z","2026-01-15T11:38:22.088Z","2026-01-15T11:38:22.264Z",{"id":1177,"documentId":1178,"title":1179,"description":1180,"slug":1181,"publicationDate":1182,"createdAt":1183,"updatedAt":1184,"publishedAt":1185,"locale":29},551,"gqlfrw6s03utms6wyd49eqjz","Фунтиков Олег Валентинович","Колишній замполіт бригади «Днепр» ДШК та начальник штабу бригади «Дон». Чемпіон світу з карате. Крім участі у бойових діях займався мілітаризацією українських дітей","Funtikov-Oleg-Valentinovich-ua","2026-01-20T13:24:00.000Z","2026-01-20T11:45:48.898Z","2026-01-24T13:25:41.479Z","2026-01-24T13:25:41.660Z",{"id":1187,"documentId":1178,"title":1188,"description":1189,"slug":1190,"publicationDate":1191,"createdAt":1192,"updatedAt":1193,"publishedAt":1194,"locale":15},545,"Funtikov Oleg Valentinovich","Osint Profile. Former political officer of the Dnepr Brigade (Volunteer Assault Corps) and chief of staff of the Don Brigade. WKC World Karate Champion. In addition to participating in combat operations, he was involved in the militarization of Ukrainian children","Funtikov-Oleg-Valentinovich-en","2026-01-20T19:16:00.000Z","2026-01-20T18:22:26.632Z","2026-01-24T13:25:41.824Z","2026-01-20T21:26:04.490Z",{"id":1196,"documentId":1197,"title":1198,"description":1199,"slug":1200,"publicationDate":1201,"createdAt":1202,"updatedAt":1203,"publishedAt":1204,"locale":29},718,"d9x41db9qmnphzoeb2ub7lz8","Николаев Артём Михайлович ","Гвардії капітан, штурман бойового вертольота Ка-52. Учасник повномасштабного вторгнення РФ в Україну та війни в Сирії. З травня 2024 - заступник голови уряду Пензенської області РФ","Nikolaev-Artyom-Mikhailovich-ua","2026-01-23T17:48:00.000Z","2026-01-23T12:47:45.153Z","2026-02-06T04:16:22.493Z","2026-02-06T04:12:31.878Z",{"id":85,"documentId":1197,"title":1206,"description":1207,"slug":1208,"publicationDate":1209,"createdAt":1210,"updatedAt":1211,"publishedAt":1212,"locale":15}," Nikolaev Artem Mikhailovich","Osint Profile. Captain of the Russian Army, navigator of a Ka-52 combat helicopter. Participant in Russia’s full-scale invasion of Ukraine and the war in Syria. Since May 2024 — Deputy Chairman of the Government of Penza Oblast, Russian Federation","Nikolaev-Artyom-Mikhailovich-en","2026-01-24T12:32:00.000Z","2026-01-24T13:39:26.755Z","2026-02-06T04:16:22.125Z","2026-02-06T04:16:22.308Z",{"id":1214,"documentId":1038,"title":1215,"description":1216,"slug":1217,"publicationDate":1218,"createdAt":1219,"updatedAt":1220,"publishedAt":1221,"locale":15},636,"Current personal data of the Peskovs family","Personal data of the family of Peskov, press secretary to Russian President Vladimir Putin","peskovs-family-en","2023-08-23T06:10:00.000Z","2025-10-27T16:07:00.389Z","2026-01-29T04:35:15.008Z","2026-01-29T04:35:15.113Z",{"id":1223,"documentId":1224,"title":1225,"description":1226,"slug":1227,"publicationDate":1228,"createdAt":1229,"updatedAt":1230,"publishedAt":1231,"locale":29},591,"uad6bbyn2a4b7qal1w577ibw","Слюсар, банкрот та 2 стволи – як рекрутить БАРС-11","Як працює система рекрутингу підрозділу БАРС-11 та хто ці рекрутери","recruitment-system-BARS-11","2023-05-19T06:12:00.000Z","2025-07-12T11:07:28.721Z","2026-01-29T02:12:25.127Z","2026-01-29T02:12:25.270Z",{"id":1233,"documentId":1234,"title":1235,"description":1236,"slug":1237,"publicationDate":1238,"createdAt":1239,"updatedAt":1240,"publishedAt":1241,"locale":29},643,"whch04fyi76cggpj5z9prxxl","ШБ «Крим» | Корпус Редут","Дослідження команди OsintFlow, яке дозволило встановити підрозділ зрадників та окупантів, що воюють під керівництвом Головного управління Генерального штабу ЗС РФ (колишнє ГРУ).","krym-redut-ua","2025-02-17T06:02:45.000Z","2025-07-12T11:22:28.822Z","2026-02-03T07:55:52.858Z","2026-02-03T04:58:40.576Z",{"id":1243,"documentId":1244,"title":1245,"description":1246,"slug":1247,"publicationDate":1248,"createdAt":1249,"updatedAt":1250,"publishedAt":1251,"locale":29},716,"e60ybahuili90ena98ug1qvo","Як РФ намагається заповнити прогалину «офіцерських втрат» і набирає у виші учасників війни в Україні","Російські військові академії активно набирають офіцерів із бойовим досвідом. Дослідження показує, хто може стати майбутньою офіцерською елітою РФ","russia-recruits-ukraine-veterans-for-officer-gap","2024-11-17T06:04:00.000Z","2025-07-12T11:18:08.696Z","2026-02-06T04:06:16.887Z","2026-02-06T04:06:17.010Z",{"id":1253,"documentId":1244,"title":1254,"description":1255,"slug":1256,"publicationDate":1257,"createdAt":1258,"updatedAt":1259,"publishedAt":1260,"locale":15},715,"How Russia Fills Officer Losses by Recruiting War Veterans","Russian military academies recruit combat-experienced soldiers to fill officer losses in Ukraine, creating a “new blood” for the future officer elite","russia-recruits-ukraine-veterans-for-officer-gap-en","2024-11-17T08:03:00.000Z","2025-07-12T11:05:34.693Z","2026-02-06T04:06:17.133Z","2026-02-06T04:03:11.502Z",{"id":1262,"documentId":1263,"title":1264,"description":1265,"slug":1266,"publicationDate":1267,"createdAt":1268,"updatedAt":1269,"publishedAt":1270,"locale":29},750,"j3v4f6b2z0uvz4bttvpxl2ft","«Універсальний солдат» або як РОВ готує «майбутніх піхотинців» на т.о.т Луганщини","Росія створила численні молодіжні рухи на окупованих територіях України, спрямовані на індоктринацію та мілітаризацію дітей. У статті розглядається відкриття табору «Академія дружби Ахмат», його ідеологічні цілі, джерела фінансування та ключові фігури, пов’язані з індоктринацією та подальшою мілітаризацією дітей на території Луганщини.","luhansk-child-militarization","2024-11-03T05:08:11.000Z","2025-07-12T11:17:38.322Z","2026-03-11T15:16:01.639Z","2026-03-11T15:16:01.954Z",{"id":1272,"documentId":1273,"title":1274,"description":1275,"slug":1276,"publicationDate":1277,"createdAt":1278,"updatedAt":1279,"publishedAt":1280,"locale":29},741,"vpl1uyy2rpok83668gr8kyzh"," Егорцев Александр Юрьевич ","Осінт досьє. Спеціальний кореспондент телеканалу «СПАС». У своїх публічних виступах та матеріалах відкрито підтримує військові дії Росії проти України та регулярно перебуває на тимчасово окупованих територіях.","egortsev-alexander-yuryevich","2026-03-03T01:17:00.000Z","2026-03-03T01:39:37.410Z","2026-03-09T10:32:38.802Z","2026-03-09T10:32:38.949Z",{"id":1282,"documentId":1283,"title":1284,"description":1285,"slug":1286,"publicationDate":1287,"createdAt":1288,"updatedAt":1289,"publishedAt":1290,"locale":29},749,"ekmt8i1xyc14z2g99b7av2jp","Рахимов Денис Рушанович ","Осінт досьє. Заступник начальника розрахунку, оператор зенітного комплексу ППО «Панцир-С1», сержант. Брав участь у боях у тимчасово окупованих Лисичанську, Іловайську та Криму.","Rakhimov-Deni-Rushanovich","2026-03-10T05:30:00.000Z","2026-03-10T08:14:41.121Z","2026-03-11T13:18:20.913Z","2026-03-11T13:18:21.060Z",{"id":483,"documentId":396,"title":484,"description":485,"slug":486,"publicationDate":487,"createdAt":488,"updatedAt":489,"publishedAt":490,"locale":29},{"id":395,"documentId":396,"title":397,"description":398,"slug":399,"publicationDate":400,"createdAt":401,"updatedAt":402,"publishedAt":403,"locale":15},{"id":1294,"documentId":1295,"title":1296,"description":1297,"slug":1298,"publicationDate":1299,"createdAt":1300,"updatedAt":1301,"publishedAt":1302,"locale":29},826,"cdlqfudcb347axce4bh0eb06","«Пчела» — заступник командира роти «Барс-23» «Орел»","Учасник повномасштабного вторгнення. Згідно з інтерв'ю російським ЗМІ та сторінок «Барс-23» воює з 2023 року. Був помічений на Вугледарському напрямку","kudria-bars-23","2026-05-13T09:02:00.000Z","2026-05-13T11:25:50.656Z","2026-05-13T13:34:51.840Z","2026-05-13T13:34:52.085Z",{"id":282,"documentId":160,"title":283,"description":284,"slug":285,"publicationDate":286,"createdAt":287,"updatedAt":288,"publishedAt":289,"locale":29},{"id":159,"documentId":160,"title":161,"description":162,"slug":163,"publicationDate":164,"createdAt":165,"updatedAt":166,"publishedAt":167,"locale":15},{"id":357,"documentId":358,"name":359,"slug":359,"createdAt":360,"updatedAt":360,"publishedAt":361,"articles":1306,"seo":9},[1307,1316,1324,1325,1326,1327,1328,1329,1330,1340,1350,1351,1352,1353,1354,1355,1364,1365,1366,1367,1368,1369,1378,1387,1388,1389,1390,1391,1392],{"id":1308,"documentId":1309,"title":1310,"description":791,"slug":1311,"publicationDate":1312,"createdAt":1313,"updatedAt":1314,"publishedAt":1315,"locale":29},351,"xxcj14o6xvunnrylh54nzby5","Хто виробляє Supercam S350? Структура ГК «Беспилотные Системы»","2024-04-15","2024-04-15T05:07:11.000Z","2025-07-12T11:11:58.668Z","2025-10-09T22:50:39.303Z","2025-10-09T22:50:39.383Z",{"id":1317,"documentId":1318,"title":1319,"description":791,"slug":1320,"publicationDate":1321,"createdAt":1322,"updatedAt":1322,"publishedAt":1323,"locale":29},257,"va56rf2tyr584yth7a0wwclz","Співпраця з RMRF Group","2024-05-03","2024-05-03T05:07:11.000Z","2025-07-12T11:12:07.605Z","2025-07-12T11:12:07.626Z",{"id":806,"documentId":807,"title":808,"description":791,"slug":809,"publicationDate":810,"createdAt":811,"updatedAt":812,"publishedAt":813,"locale":29},{"id":815,"documentId":816,"title":817,"description":791,"slug":818,"publicationDate":819,"createdAt":820,"updatedAt":821,"publishedAt":822,"locale":29},{"id":838,"documentId":839,"title":840,"description":791,"slug":841,"publicationDate":842,"createdAt":843,"updatedAt":844,"publishedAt":845,"locale":29},{"id":847,"documentId":848,"title":849,"description":791,"slug":850,"publicationDate":851,"createdAt":852,"updatedAt":852,"publishedAt":853,"locale":29},{"id":1262,"documentId":1263,"title":1264,"description":1265,"slug":1266,"publicationDate":1267,"createdAt":1268,"updatedAt":1269,"publishedAt":1270,"locale":29},{"id":1243,"documentId":1244,"title":1245,"description":1246,"slug":1247,"publicationDate":1248,"createdAt":1249,"updatedAt":1250,"publishedAt":1251,"locale":29},{"id":1331,"documentId":1332,"title":1333,"description":1334,"slug":1335,"publicationDate":1336,"createdAt":1337,"updatedAt":1338,"publishedAt":1339,"locale":29},689,"vn1s1m60dhvi2sc1emfcrahn","Персональні дані працівників БелТПП від C.A.S [ Cyber.Anarchy.Squad ]","Частина зливу персональних даних працівників «Беларусская торгово-промышленная палата» від  кіберугруповання від C.A.S [Cyber.Anarchy.Squad ]","beltpp-leak","2024-11-23T05:08:00.000Z","2025-07-12T11:18:16.887Z","2026-02-05T22:39:24.554Z","2026-02-05T22:39:24.658Z",{"id":1341,"documentId":1342,"title":1343,"description":1344,"slug":1345,"publicationDate":1346,"createdAt":1347,"updatedAt":1348,"publishedAt":1349,"locale":29},701,"aijyhx8jyjcbwp4ucu8k0nof","Демілітаризовані зони - «ефективне заморожування» конфліктів","Дослідження демілітаризованих зон (ДМЗ): історія, сучасні виклики та уроки для України","demilitarized-zones-conflict","2024-11-17T06:03:45.000Z","2025-07-12T11:18:42.046Z","2026-02-06T02:21:32.972Z","2026-02-06T02:21:33.077Z",{"id":1233,"documentId":1234,"title":1235,"description":1236,"slug":1237,"publicationDate":1238,"createdAt":1239,"updatedAt":1240,"publishedAt":1241,"locale":29},{"id":855,"documentId":856,"title":857,"description":858,"slug":859,"publicationDate":860,"createdAt":861,"updatedAt":862,"publishedAt":863,"locale":29},{"id":865,"documentId":866,"title":867,"description":868,"slug":869,"publicationDate":870,"createdAt":871,"updatedAt":872,"publishedAt":873,"locale":29},{"id":1037,"documentId":1038,"title":1039,"description":1040,"slug":1041,"publicationDate":1042,"createdAt":1043,"updatedAt":1044,"publishedAt":1045,"locale":29},{"id":1214,"documentId":1038,"title":1215,"description":1216,"slug":1217,"publicationDate":1218,"createdAt":1219,"updatedAt":1220,"publishedAt":1221,"locale":15},{"id":1356,"documentId":1224,"title":1357,"description":1358,"slug":1359,"publicationDate":1360,"createdAt":1361,"updatedAt":1362,"publishedAt":1363,"locale":15},577,"A Mechanic, a Bankrupt and Two Smoking Barrels: How the BARS-11 Unit Recruits","Inside the BARS‑11 Recruitment System: Who the Recruiters Are and How It Works","recruitment-system-BARS-11-en","2023-05-19T08:30:00.000Z","2025-10-24T10:41:31.148Z","2026-01-29T02:12:25.440Z","2026-01-27T14:38:18.614Z",{"id":1088,"documentId":888,"title":1089,"description":1090,"slug":1091,"publicationDate":1092,"createdAt":1093,"updatedAt":1094,"publishedAt":1095,"locale":29},{"id":1223,"documentId":1224,"title":1225,"description":1226,"slug":1227,"publicationDate":1228,"createdAt":1229,"updatedAt":1230,"publishedAt":1231,"locale":29},{"id":263,"documentId":888,"title":889,"description":890,"slug":891,"publicationDate":892,"createdAt":893,"updatedAt":894,"publishedAt":895,"locale":15},{"id":1097,"documentId":898,"title":1098,"description":791,"slug":1099,"publicationDate":1100,"createdAt":1101,"updatedAt":1102,"publishedAt":1103,"locale":29},{"id":897,"documentId":898,"title":899,"description":791,"slug":900,"publicationDate":901,"createdAt":902,"updatedAt":903,"publishedAt":904,"locale":15},{"id":1370,"documentId":1332,"title":1371,"description":1372,"slug":1373,"publicationDate":1374,"createdAt":1375,"updatedAt":1376,"publishedAt":1377,"locale":15},688,"Personal data of BelCCI employees by C.A.S [Cyber.Anarchy.Squad]","Personal data of employees at the Belarusian Chamber of Commerce and Industry has been exposed by the cyber group C.A.S [Cyber.Anarchy.Squad]","beltpp-leak-en","2024-11-23T05:10:00.000Z","2026-02-05T22:27:21.177Z","2026-02-05T22:39:24.742Z","2026-02-05T22:39:14.586Z",{"id":1379,"documentId":1342,"title":1380,"description":1381,"slug":1382,"publicationDate":1383,"createdAt":1384,"updatedAt":1385,"publishedAt":1386,"locale":15},700,"Demilitarized Zones: A Tool for “Freezing” Conflicts","“Lessons from Demilitarized Zones: What Ukraine Can Learn","demilitarized-zones-conflict-en","2024-12-02T06:15:00.000Z","2026-02-05T23:00:30.857Z","2026-02-06T02:21:33.170Z","2026-02-06T02:21:21.927Z",{"id":574,"documentId":575,"title":576,"description":577,"slug":578,"publicationDate":579,"createdAt":580,"updatedAt":581,"publishedAt":582,"locale":15},{"id":492,"documentId":493,"title":494,"description":495,"slug":496,"publicationDate":497,"createdAt":498,"updatedAt":499,"publishedAt":500,"locale":15},{"id":876,"documentId":877,"title":878,"description":879,"slug":880,"publicationDate":881,"createdAt":882,"updatedAt":883,"publishedAt":884,"locale":29},{"id":1294,"documentId":1295,"title":1296,"description":1297,"slug":1298,"publicationDate":1299,"createdAt":1300,"updatedAt":1301,"publishedAt":1302,"locale":29},{"id":387,"documentId":292,"title":388,"description":389,"slug":390,"publicationDate":296,"createdAt":391,"updatedAt":392,"publishedAt":393,"locale":29},{"id":291,"documentId":292,"title":293,"description":294,"slug":295,"publicationDate":296,"createdAt":297,"updatedAt":298,"publishedAt":299,"locale":15},{"id":553,"documentId":554,"name":555,"slug":555,"createdAt":556,"updatedAt":557,"publishedAt":558,"articles":1394,"seo":9},[1395,1405,1406],{"id":1396,"documentId":1397,"title":1398,"description":1399,"slug":1400,"publicationDate":1401,"createdAt":1402,"updatedAt":1403,"publishedAt":1404,"locale":29},781,"pcm6ncgrwe7m9vfg2tg81q9h","«Пухнасті гвинтики» системи: фурі-працівники ВПК РФ","«Маленькі гвинтики» працюють на російську оборонну промисловість та опосередковано є співучасниками злочинів путінського режиму. Від скромного прихильника «ФБК» та «умного голосования», пов’язаного з Навальним, до «ведмедя-росгвардійця» — організатора Furrburg","furi-praczivniki-vpk-rf","2026-04-08T19:00:00.000Z","2026-04-08T11:06:54.462Z","2026-04-16T10:58:36.887Z","2026-04-16T10:58:37.116Z",{"id":566,"documentId":493,"title":567,"description":568,"slug":496,"publicationDate":569,"createdAt":570,"updatedAt":571,"publishedAt":572,"locale":29},{"id":492,"documentId":493,"title":494,"description":495,"slug":496,"publicationDate":497,"createdAt":498,"updatedAt":499,"publishedAt":500,"locale":15},{"id":1408,"documentId":1409,"name":1410,"slug":1411,"createdAt":1412,"updatedAt":1413,"publishedAt":1414,"articles":1415,"seo":9},52,"uqlqibbcjdfu4izjikn5mu7d","CAS","cas","2025-07-12T11:18:09.505Z","2026-01-13T20:42:23.897Z","2026-01-13T20:42:23.841Z",[1416,1417],{"id":1331,"documentId":1332,"title":1333,"description":1334,"slug":1335,"publicationDate":1336,"createdAt":1337,"updatedAt":1338,"publishedAt":1339,"locale":29},{"id":1370,"documentId":1332,"title":1371,"description":1372,"slug":1373,"publicationDate":1374,"createdAt":1375,"updatedAt":1376,"publishedAt":1377,"locale":15},{"id":351,"documentId":352,"name":205,"slug":205,"createdAt":353,"updatedAt":354,"publishedAt":355,"articles":1419,"seo":9},[1420,1421,1431,1432,1433,1434,1435,1436,1437,1438,1439,1440,1441,1442,1443,1452,1461,1462,1463,1464,1465,1466,1467,1468],{"id":855,"documentId":856,"title":857,"description":858,"slug":859,"publicationDate":860,"createdAt":861,"updatedAt":862,"publishedAt":863,"locale":29},{"id":1422,"documentId":1423,"title":1424,"description":1425,"slug":1426,"publicationDate":1427,"createdAt":1428,"updatedAt":1429,"publishedAt":1430,"locale":29},751,"qe7wuw8g3fxwl54s6nm3s2dn","ШБ «Крим» | Корпус Редут Частина II - «Помічники» підрозділу","Представляємо вашій увазі продовження дослідження команди OsintFlow. У другій частині дослідження ми дослідили зв’язки батальйону з різним організаціями і з'ясувати хто очолює ці структури. ","krym-redut-part-2-ua","2025-03-17T06:05:00.000Z","2025-07-12T11:23:56.424Z","2026-03-11T15:17:08.040Z","2026-03-11T15:17:08.156Z",{"id":865,"documentId":866,"title":867,"description":868,"slug":869,"publicationDate":870,"createdAt":871,"updatedAt":872,"publishedAt":873,"locale":29},{"id":1168,"documentId":856,"title":1169,"description":1170,"slug":1171,"publicationDate":1172,"createdAt":1173,"updatedAt":1174,"publishedAt":1175,"locale":15},{"id":1187,"documentId":1178,"title":1188,"description":1189,"slug":1190,"publicationDate":1191,"createdAt":1192,"updatedAt":1193,"publishedAt":1194,"locale":15},{"id":1196,"documentId":1197,"title":1198,"description":1199,"slug":1200,"publicationDate":1201,"createdAt":1202,"updatedAt":1203,"publishedAt":1204,"locale":29},{"id":85,"documentId":1197,"title":1206,"description":1207,"slug":1208,"publicationDate":1209,"createdAt":1210,"updatedAt":1211,"publishedAt":1212,"locale":15},{"id":1356,"documentId":1224,"title":1357,"description":1358,"slug":1359,"publicationDate":1360,"createdAt":1361,"updatedAt":1362,"publishedAt":1363,"locale":15},{"id":1088,"documentId":888,"title":1089,"description":1090,"slug":1091,"publicationDate":1092,"createdAt":1093,"updatedAt":1094,"publishedAt":1095,"locale":29},{"id":1223,"documentId":1224,"title":1225,"description":1226,"slug":1227,"publicationDate":1228,"createdAt":1229,"updatedAt":1230,"publishedAt":1231,"locale":29},{"id":1097,"documentId":898,"title":1098,"description":791,"slug":1099,"publicationDate":1100,"createdAt":1101,"updatedAt":1102,"publishedAt":1103,"locale":29},{"id":1233,"documentId":1234,"title":1235,"description":1236,"slug":1237,"publicationDate":1238,"createdAt":1239,"updatedAt":1240,"publishedAt":1241,"locale":29},{"id":263,"documentId":888,"title":889,"description":890,"slug":891,"publicationDate":892,"createdAt":893,"updatedAt":894,"publishedAt":895,"locale":15},{"id":924,"documentId":925,"title":926,"description":791,"slug":927,"publicationDate":928,"createdAt":929,"updatedAt":930,"publishedAt":931,"locale":15},{"id":1444,"documentId":1234,"title":1445,"description":1446,"slug":1447,"publicationDate":1448,"createdAt":1449,"updatedAt":1450,"publishedAt":1451,"locale":15},648,"Assault Battalion \"Krym\" | Redut Corps","An OsintFlow investigation that uncovered a unit of collaborators and occupiers operating under the command of the General Staff of the Armed Forces of the Russian Federation (formerly the GRU).","krym-redut-en","2025-02-17T06:03:00.000Z","2025-10-08T10:53:11.438Z","2026-02-03T07:55:52.616Z","2026-02-03T07:55:52.755Z",{"id":1453,"documentId":1423,"title":1454,"description":1455,"slug":1456,"publicationDate":1457,"createdAt":1458,"updatedAt":1459,"publishedAt":1460,"locale":15},654,"Krym Assault Battalion | Redut Corps Part II – ‘Unit Assistants’","The OsintFlow team continues its in-depth investigation. In the second part, we trace the battalion’s connections to various organizations and reveal the individuals leading these structures.","krym-redut-part-2-en","2025-02-19T05:00:00.000Z","2026-02-03T05:01:29.107Z","2026-03-11T15:17:08.258Z","2026-02-04T11:16:00.995Z",{"id":1243,"documentId":1244,"title":1245,"description":1246,"slug":1247,"publicationDate":1248,"createdAt":1249,"updatedAt":1250,"publishedAt":1251,"locale":29},{"id":1253,"documentId":1244,"title":1254,"description":1255,"slug":1256,"publicationDate":1257,"createdAt":1258,"updatedAt":1259,"publishedAt":1260,"locale":15},{"id":1262,"documentId":1263,"title":1264,"description":1265,"slug":1266,"publicationDate":1267,"createdAt":1268,"updatedAt":1269,"publishedAt":1270,"locale":29},{"id":662,"documentId":575,"title":663,"description":664,"slug":665,"publicationDate":666,"createdAt":667,"updatedAt":668,"publishedAt":669,"locale":29},{"id":574,"documentId":575,"title":576,"description":577,"slug":578,"publicationDate":579,"createdAt":580,"updatedAt":581,"publishedAt":582,"locale":15},{"id":1396,"documentId":1397,"title":1398,"description":1399,"slug":1400,"publicationDate":1401,"createdAt":1402,"updatedAt":1403,"publishedAt":1404,"locale":29},{"id":387,"documentId":292,"title":388,"description":389,"slug":390,"publicationDate":296,"createdAt":391,"updatedAt":392,"publishedAt":393,"locale":29},{"id":291,"documentId":292,"title":293,"description":294,"slug":295,"publicationDate":296,"createdAt":297,"updatedAt":298,"publishedAt":299,"locale":15},{"id":673,"documentId":1470,"name":1471,"slug":1472,"createdAt":1473,"updatedAt":1474,"publishedAt":1475,"articles":1476,"seo":9},"gvvuovyllyvl3bpsu06rt8al","Ukraine","ukraine","2025-07-12T11:02:57.994Z","2026-01-13T20:43:19.676Z","2026-01-13T20:43:19.632Z",[1477],{"id":1379,"documentId":1342,"title":1380,"description":1381,"slug":1382,"publicationDate":1383,"createdAt":1384,"updatedAt":1385,"publishedAt":1386,"locale":15},{"id":1479,"documentId":1480,"name":1481,"slug":1482,"createdAt":1483,"updatedAt":1483,"publishedAt":1484,"articles":1485,"seo":9},57,"azlfkpt8ypzfearghb1z9vzw","dossier ","dossier","2026-01-20T11:11:03.892Z","2026-01-20T11:11:03.865Z",[1486,1487,1488,1489,1497,1498,1499,1500,1501,1502],{"id":855,"documentId":856,"title":857,"description":858,"slug":859,"publicationDate":860,"createdAt":861,"updatedAt":862,"publishedAt":863,"locale":29},{"id":1168,"documentId":856,"title":1169,"description":1170,"slug":1171,"publicationDate":1172,"createdAt":1173,"updatedAt":1174,"publishedAt":1175,"locale":15},{"id":865,"documentId":866,"title":867,"description":868,"slug":869,"publicationDate":870,"createdAt":871,"updatedAt":872,"publishedAt":873,"locale":29},{"id":1490,"documentId":866,"title":1491,"description":1492,"slug":869,"publicationDate":1493,"createdAt":1494,"updatedAt":1495,"publishedAt":1496,"locale":15},489,"Vinsky Marat Valerievich","OSINT Profile. Veteran of the War in Ukraine.  Lance Corporal, 35th Separate Motorized Rifle Brigade, Central MD, Russian Armed Forces. Military unit 41659 ","2026-01-07T15:21:00.000Z","2026-01-07T19:06:59.137Z","2026-01-15T11:15:48.576Z","2026-01-15T11:15:48.698Z",{"id":1177,"documentId":1178,"title":1179,"description":1180,"slug":1181,"publicationDate":1182,"createdAt":1183,"updatedAt":1184,"publishedAt":1185,"locale":29},{"id":1187,"documentId":1178,"title":1188,"description":1189,"slug":1190,"publicationDate":1191,"createdAt":1192,"updatedAt":1193,"publishedAt":1194,"locale":15},{"id":85,"documentId":1197,"title":1206,"description":1207,"slug":1208,"publicationDate":1209,"createdAt":1210,"updatedAt":1211,"publishedAt":1212,"locale":15},{"id":1097,"documentId":898,"title":1098,"description":791,"slug":1099,"publicationDate":1100,"createdAt":1101,"updatedAt":1102,"publishedAt":1103,"locale":29},{"id":897,"documentId":898,"title":899,"description":791,"slug":900,"publicationDate":901,"createdAt":902,"updatedAt":903,"publishedAt":904,"locale":15},{"id":1262,"documentId":1263,"title":1264,"description":1265,"slug":1266,"publicationDate":1267,"createdAt":1268,"updatedAt":1269,"publishedAt":1270,"locale":29},{"id":1504,"documentId":1505,"name":1506,"slug":1506,"createdAt":1507,"updatedAt":1508,"publishedAt":1509,"articles":1510,"seo":1513},58,"hbips61mwchb00ntib0hvrjl","BARS","2026-01-27T11:28:22.396Z","2026-01-27T14:25:16.870Z","2026-01-27T14:25:16.755Z",[1511,1512],{"id":1356,"documentId":1224,"title":1357,"description":1358,"slug":1359,"publicationDate":1360,"createdAt":1361,"updatedAt":1362,"publishedAt":1363,"locale":15},{"id":1223,"documentId":1224,"title":1225,"description":1226,"slug":1227,"publicationDate":1228,"createdAt":1229,"updatedAt":1230,"publishedAt":1231,"locale":29},{"id":1514,"metaTitle":1515,"metaDescription":1516,"keywords":1517,"metaRobots":9,"metaViewport":9,"canonicalURL":9,"structuredData":9},123,"БАРС - Боевой армейский резерв страны ","БАРС — система добровільних штурмових загонів РФ, сформована з 2021-2022 років, що діє як мобілізаційний резерв у складі армії РФ","БАРС, добровільні штурмові загони РФ, Збройні сили РФ,війна в Україні, мобілізаційний резерв, російська армія, парамілітарні формування",{"id":240,"documentId":241,"name":242,"slug":243,"createdAt":244,"updatedAt":245,"publishedAt":246,"articles":1519,"seo":9},[1520,1521,1522,1523,1524,1525,1526,1527,1528,1529,1530,1531,1532,1533,1534,1535,1536,1537,1538,1539,1540,1541,1542,1543,1544,1545],{"id":855,"documentId":856,"title":857,"description":858,"slug":859,"publicationDate":860,"createdAt":861,"updatedAt":862,"publishedAt":863,"locale":29},{"id":865,"documentId":866,"title":867,"description":868,"slug":869,"publicationDate":870,"createdAt":871,"updatedAt":872,"publishedAt":873,"locale":29},{"id":1168,"documentId":856,"title":1169,"description":1170,"slug":1171,"publicationDate":1172,"createdAt":1173,"updatedAt":1174,"publishedAt":1175,"locale":15},{"id":1490,"documentId":866,"title":1491,"description":1492,"slug":869,"publicationDate":1493,"createdAt":1494,"updatedAt":1495,"publishedAt":1496,"locale":15},{"id":1177,"documentId":1178,"title":1179,"description":1180,"slug":1181,"publicationDate":1182,"createdAt":1183,"updatedAt":1184,"publishedAt":1185,"locale":29},{"id":1187,"documentId":1178,"title":1188,"description":1189,"slug":1190,"publicationDate":1191,"createdAt":1192,"updatedAt":1193,"publishedAt":1194,"locale":15},{"id":1196,"documentId":1197,"title":1198,"description":1199,"slug":1200,"publicationDate":1201,"createdAt":1202,"updatedAt":1203,"publishedAt":1204,"locale":29},{"id":85,"documentId":1197,"title":1206,"description":1207,"slug":1208,"publicationDate":1209,"createdAt":1210,"updatedAt":1211,"publishedAt":1212,"locale":15},{"id":1037,"documentId":1038,"title":1039,"description":1040,"slug":1041,"publicationDate":1042,"createdAt":1043,"updatedAt":1044,"publishedAt":1045,"locale":29},{"id":1214,"documentId":1038,"title":1215,"description":1216,"slug":1217,"publicationDate":1218,"createdAt":1219,"updatedAt":1220,"publishedAt":1221,"locale":15},{"id":1356,"documentId":1224,"title":1357,"description":1358,"slug":1359,"publicationDate":1360,"createdAt":1361,"updatedAt":1362,"publishedAt":1363,"locale":15},{"id":1223,"documentId":1224,"title":1225,"description":1226,"slug":1227,"publicationDate":1228,"createdAt":1229,"updatedAt":1230,"publishedAt":1231,"locale":29},{"id":1422,"documentId":1423,"title":1424,"description":1425,"slug":1426,"publicationDate":1427,"createdAt":1428,"updatedAt":1429,"publishedAt":1430,"locale":29},{"id":1233,"documentId":1234,"title":1235,"description":1236,"slug":1237,"publicationDate":1238,"createdAt":1239,"updatedAt":1240,"publishedAt":1241,"locale":29},{"id":1444,"documentId":1234,"title":1445,"description":1446,"slug":1447,"publicationDate":1448,"createdAt":1449,"updatedAt":1450,"publishedAt":1451,"locale":15},{"id":1453,"documentId":1423,"title":1454,"description":1455,"slug":1456,"publicationDate":1457,"createdAt":1458,"updatedAt":1459,"publishedAt":1460,"locale":15},{"id":1243,"documentId":1244,"title":1245,"description":1246,"slug":1247,"publicationDate":1248,"createdAt":1249,"updatedAt":1250,"publishedAt":1251,"locale":29},{"id":1253,"documentId":1244,"title":1254,"description":1255,"slug":1256,"publicationDate":1257,"createdAt":1258,"updatedAt":1259,"publishedAt":1260,"locale":15},{"id":1272,"documentId":1273,"title":1274,"description":1275,"slug":1276,"publicationDate":1277,"createdAt":1278,"updatedAt":1279,"publishedAt":1280,"locale":29},{"id":1282,"documentId":1283,"title":1284,"description":1285,"slug":1286,"publicationDate":1287,"createdAt":1288,"updatedAt":1289,"publishedAt":1290,"locale":29},{"id":1396,"documentId":1397,"title":1398,"description":1399,"slug":1400,"publicationDate":1401,"createdAt":1402,"updatedAt":1403,"publishedAt":1404,"locale":29},{"id":483,"documentId":396,"title":484,"description":485,"slug":486,"publicationDate":487,"createdAt":488,"updatedAt":489,"publishedAt":490,"locale":29},{"id":395,"documentId":396,"title":397,"description":398,"slug":399,"publicationDate":400,"createdAt":401,"updatedAt":402,"publishedAt":403,"locale":15},{"id":1294,"documentId":1295,"title":1296,"description":1297,"slug":1298,"publicationDate":1299,"createdAt":1300,"updatedAt":1301,"publishedAt":1302,"locale":29},{"id":282,"documentId":160,"title":283,"description":284,"slug":285,"publicationDate":286,"createdAt":287,"updatedAt":288,"publishedAt":289,"locale":29},{"id":159,"documentId":160,"title":161,"description":162,"slug":163,"publicationDate":164,"createdAt":165,"updatedAt":166,"publishedAt":167,"locale":15},{"id":1547,"documentId":1548,"name":1549,"slug":1550,"createdAt":1551,"updatedAt":1552,"publishedAt":1553,"articles":1554,"seo":9},53,"yomrsywagangq0drr9d2hshe","редут","tag","2025-09-29T15:47:18.235Z","2026-01-13T21:15:50.646Z","2026-01-13T21:15:50.570Z",[1555,1556,1557,1558],{"id":1233,"documentId":1234,"title":1235,"description":1236,"slug":1237,"publicationDate":1238,"createdAt":1239,"updatedAt":1240,"publishedAt":1241,"locale":29},{"id":1444,"documentId":1234,"title":1445,"description":1446,"slug":1447,"publicationDate":1448,"createdAt":1449,"updatedAt":1450,"publishedAt":1451,"locale":15},{"id":1422,"documentId":1423,"title":1424,"description":1425,"slug":1426,"publicationDate":1427,"createdAt":1428,"updatedAt":1429,"publishedAt":1430,"locale":29},{"id":1453,"documentId":1423,"title":1454,"description":1455,"slug":1456,"publicationDate":1457,"createdAt":1458,"updatedAt":1459,"publishedAt":1460,"locale":15},{"id":233,"documentId":234,"name":235,"slug":235,"createdAt":236,"updatedAt":237,"publishedAt":238,"articles":1560,"seo":9},[1561,1562,1563,1564,1565,1566,1567,1568,1569,1570,1571,1572,1573,1574,1575,1576,1577,1578,1579,1580,1581,1582,1583,1584,1585,1586,1587,1588,1589,1590,1591,1592,1593,1594,1595,1596],{"id":263,"documentId":888,"title":889,"description":890,"slug":891,"publicationDate":892,"createdAt":893,"updatedAt":894,"publishedAt":895,"locale":15},{"id":897,"documentId":898,"title":899,"description":791,"slug":900,"publicationDate":901,"createdAt":902,"updatedAt":903,"publishedAt":904,"locale":15},{"id":906,"documentId":907,"title":908,"description":791,"slug":909,"publicationDate":910,"createdAt":911,"updatedAt":912,"publishedAt":913,"locale":15},{"id":933,"documentId":934,"title":935,"description":791,"slug":936,"publicationDate":937,"createdAt":938,"updatedAt":939,"publishedAt":940,"locale":15},{"id":942,"documentId":943,"title":944,"description":791,"slug":945,"publicationDate":946,"createdAt":947,"updatedAt":948,"publishedAt":949,"locale":15},{"id":951,"documentId":952,"title":953,"description":791,"slug":954,"publicationDate":955,"createdAt":956,"updatedAt":957,"publishedAt":958,"locale":15},{"id":960,"documentId":961,"title":962,"description":791,"slug":963,"publicationDate":964,"createdAt":965,"updatedAt":966,"publishedAt":967,"locale":15},{"id":969,"documentId":970,"title":971,"description":791,"slug":972,"publicationDate":973,"createdAt":974,"updatedAt":975,"publishedAt":976,"locale":15},{"id":1356,"documentId":1224,"title":1357,"description":1358,"slug":1359,"publicationDate":1360,"createdAt":1361,"updatedAt":1362,"publishedAt":1363,"locale":15},{"id":865,"documentId":866,"title":867,"description":868,"slug":869,"publicationDate":870,"createdAt":871,"updatedAt":872,"publishedAt":873,"locale":29},{"id":1168,"documentId":856,"title":1169,"description":1170,"slug":1171,"publicationDate":1172,"createdAt":1173,"updatedAt":1174,"publishedAt":1175,"locale":15},{"id":855,"documentId":856,"title":857,"description":858,"slug":859,"publicationDate":860,"createdAt":861,"updatedAt":862,"publishedAt":863,"locale":29},{"id":1177,"documentId":1178,"title":1179,"description":1180,"slug":1181,"publicationDate":1182,"createdAt":1183,"updatedAt":1184,"publishedAt":1185,"locale":29},{"id":1187,"documentId":1178,"title":1188,"description":1189,"slug":1190,"publicationDate":1191,"createdAt":1192,"updatedAt":1193,"publishedAt":1194,"locale":15},{"id":1196,"documentId":1197,"title":1198,"description":1199,"slug":1200,"publicationDate":1201,"createdAt":1202,"updatedAt":1203,"publishedAt":1204,"locale":29},{"id":85,"documentId":1197,"title":1206,"description":1207,"slug":1208,"publicationDate":1209,"createdAt":1210,"updatedAt":1211,"publishedAt":1212,"locale":15},{"id":1037,"documentId":1038,"title":1039,"description":1040,"slug":1041,"publicationDate":1042,"createdAt":1043,"updatedAt":1044,"publishedAt":1045,"locale":29},{"id":1214,"documentId":1038,"title":1215,"description":1216,"slug":1217,"publicationDate":1218,"createdAt":1219,"updatedAt":1220,"publishedAt":1221,"locale":15},{"id":1088,"documentId":888,"title":1089,"description":1090,"slug":1091,"publicationDate":1092,"createdAt":1093,"updatedAt":1094,"publishedAt":1095,"locale":29},{"id":1097,"documentId":898,"title":1098,"description":791,"slug":1099,"publicationDate":1100,"createdAt":1101,"updatedAt":1102,"publishedAt":1103,"locale":29},{"id":1444,"documentId":1234,"title":1445,"description":1446,"slug":1447,"publicationDate":1448,"createdAt":1449,"updatedAt":1450,"publishedAt":1451,"locale":15},{"id":1453,"documentId":1423,"title":1454,"description":1455,"slug":1456,"publicationDate":1457,"createdAt":1458,"updatedAt":1459,"publishedAt":1460,"locale":15},{"id":1243,"documentId":1244,"title":1245,"description":1246,"slug":1247,"publicationDate":1248,"createdAt":1249,"updatedAt":1250,"publishedAt":1251,"locale":29},{"id":1253,"documentId":1244,"title":1254,"description":1255,"slug":1256,"publicationDate":1257,"createdAt":1258,"updatedAt":1259,"publishedAt":1260,"locale":15},{"id":1272,"documentId":1273,"title":1274,"description":1275,"slug":1276,"publicationDate":1277,"createdAt":1278,"updatedAt":1279,"publishedAt":1280,"locale":29},{"id":1282,"documentId":1283,"title":1284,"description":1285,"slug":1286,"publicationDate":1287,"createdAt":1288,"updatedAt":1289,"publishedAt":1290,"locale":29},{"id":662,"documentId":575,"title":663,"description":664,"slug":665,"publicationDate":666,"createdAt":667,"updatedAt":668,"publishedAt":669,"locale":29},{"id":574,"documentId":575,"title":576,"description":577,"slug":578,"publicationDate":579,"createdAt":580,"updatedAt":581,"publishedAt":582,"locale":15},{"id":1396,"documentId":1397,"title":1398,"description":1399,"slug":1400,"publicationDate":1401,"createdAt":1402,"updatedAt":1403,"publishedAt":1404,"locale":29},{"id":483,"documentId":396,"title":484,"description":485,"slug":486,"publicationDate":487,"createdAt":488,"updatedAt":489,"publishedAt":490,"locale":29},{"id":395,"documentId":396,"title":397,"description":398,"slug":399,"publicationDate":400,"createdAt":401,"updatedAt":402,"publishedAt":403,"locale":15},{"id":1294,"documentId":1295,"title":1296,"description":1297,"slug":1298,"publicationDate":1299,"createdAt":1300,"updatedAt":1301,"publishedAt":1302,"locale":29},{"id":387,"documentId":292,"title":388,"description":389,"slug":390,"publicationDate":296,"createdAt":391,"updatedAt":392,"publishedAt":393,"locale":29},{"id":291,"documentId":292,"title":293,"description":294,"slug":295,"publicationDate":296,"createdAt":297,"updatedAt":298,"publishedAt":299,"locale":15},{"id":282,"documentId":160,"title":283,"description":284,"slug":285,"publicationDate":286,"createdAt":287,"updatedAt":288,"publishedAt":289,"locale":29},{"id":159,"documentId":160,"title":161,"description":162,"slug":163,"publicationDate":164,"createdAt":165,"updatedAt":166,"publishedAt":167,"locale":15},{"id":1598,"documentId":1599,"name":1600,"slug":1601,"createdAt":1602,"updatedAt":1603,"publishedAt":1604,"articles":1605,"seo":9},45,"pmzg80ynk26vyqqyt94be9je","Крим","krim","2025-07-12T11:14:18.821Z","2026-01-13T20:43:07.136Z","2026-01-13T20:43:07.101Z",[1606,1607,1608,1609],{"id":1422,"documentId":1423,"title":1424,"description":1425,"slug":1426,"publicationDate":1427,"createdAt":1428,"updatedAt":1429,"publishedAt":1430,"locale":29},{"id":1444,"documentId":1234,"title":1445,"description":1446,"slug":1447,"publicationDate":1448,"createdAt":1449,"updatedAt":1450,"publishedAt":1451,"locale":15},{"id":1453,"documentId":1423,"title":1454,"description":1455,"slug":1456,"publicationDate":1457,"createdAt":1458,"updatedAt":1459,"publishedAt":1460,"locale":15},{"id":662,"documentId":575,"title":663,"description":664,"slug":665,"publicationDate":666,"createdAt":667,"updatedAt":668,"publishedAt":669,"locale":29},1780925243247]