TgDB News (TelegramDB)
Open in Telegram
TgDB official channel TgDB Search Plus: tgdb.org/bot TgDB Search Lite: @tgdb_search_bot
Show more📈 Analytical overview of Telegram channel TgDB News (TelegramDB)
Channel TgDB News (TelegramDB) (@tgdatabase) in the English language segment is an active participant. Currently, the community unites 24 264 subscribers, ranking 4 672 in the Cryptocurrencies category and 846 in the International region.
📊 Audience metrics and dynamics
Since its creation on невідомо, the project has demonstrated rapid growth, gathering an audience of 24 264 subscribers.
According to the latest data from 07 September, 2026, the channel demonstrates stable activity. Although there has been a change in the number of participants by -579 over the last 30 days and by -3 over the last 24 hours, overall reach remains high.
- Verification status: Not verified
- Engagement rate (ER): The average audience engagement rate is 34.97%. Within the first 24 hours after publication, content typically collects N/A% reactions from the total number of subscribers.
- Post reach: On average, each post receives 0 views. Within the first day, a publication typically gains 0 views.
- Reactions and interaction: The audience actively supports content: the average number of reactions per post is 0.
- Thematic interests: Content is focused on key topics such as telegramdb, command, algorithm, webmaster, /network.
📝 Description and content policy
The author describes the resource as a platform for expressing subjective opinions:
“TgDB official channel
TgDB Search Plus: tgdb.org/bot
TgDB Search Lite: @tgdb_search_bot”
Thanks to the high frequency of updates (latest data received on 08 September, 2026), the channel maintains relevance and a high level of publication reach. Analytics show that the audience actively interacts with content, making it an important point of influence in the Cryptocurrencies category.
24 264
Subscribers
-324 hours
-1277 days
-57930 days
Data loading in progress...
Similar Channels
Tags Cloud
Incoming and Outgoing Mentions
---
---
---
---
---
---
Attracting Subscribers
September '26
September '26
+34
in 0 channels
August '26
+185
in 0 channels
Get PRO
July '26
+29
in 0 channels
Get PRO
June '26
+58
in 0 channels
Get PRO
May '26
+71
in 0 channels
Get PRO
April '26
+123
in 5 channels
Get PRO
March '26
+180
in 0 channels
Get PRO
February '26
+263
in 0 channels
Get PRO
January '26
+182
in 0 channels
Get PRO
December '25
+179
in 0 channels
Get PRO
November '25
+191
in 1 channels
Get PRO
October '25
+278
in 0 channels
Get PRO
September '25
+157
in 0 channels
Get PRO
August '25
+202
in 1 channels
Get PRO
July '25
+61
in 0 channels
Get PRO
June '25
+1 183
in 0 channels
Get PRO
May '25
+1 785
in 0 channels
Get PRO
April '25
+505
in 0 channels
Get PRO
March '25
+1 906
in 0 channels
Get PRO
February '25
+1 141
in 0 channels
Get PRO
January '25
+561
in 0 channels
Get PRO
December '24
+2 559
in 0 channels
Get PRO
November '24
+3 570
in 0 channels
Get PRO
October '24
+1 330
in 0 channels
Get PRO
September '24
+1 101
in 0 channels
Get PRO
August '24
+979
in 0 channels
Get PRO
July '24
+877
in 1 channels
Get PRO
June '24
+693
in 0 channels
Get PRO
May '24
+1 222
in 0 channels
Get PRO
April '24
+1 258
in 0 channels
Get PRO
March '24
+817
in 0 channels
Get PRO
February '24
+803
in 0 channels
Get PRO
January '24
+872
in 0 channels
Get PRO
December '23
+1 406
in 0 channels
Get PRO
November '23
+1 500
in 0 channels
Get PRO
October '23
+1 501
in 0 channels
Get PRO
September '23
+1 687
in 0 channels
Get PRO
August '23
+575
in 0 channels
Get PRO
July '23
+651
in 0 channels
Get PRO
June '23
+3 181
in 0 channels
Get PRO
May '23
+2 909
in 0 channels
Get PRO
April '23
+276
in 0 channels
Get PRO
March '23
+334
in 0 channels
Get PRO
February '23
+338
in 0 channels
Get PRO
January '23
+53
in 0 channels
Get PRO
December '22
+73
in 0 channels
Get PRO
November '22
+68
in 0 channels
Get PRO
October '22
+230
in 0 channels
Get PRO
September '22
+910
in 0 channels
| Date | Subscriber Growth | Mentions | Channels | |
| 07 September | +28 | |||
| 06 September | 0 | |||
| 05 September | +1 | |||
| 04 September | +2 | |||
| 03 September | 0 | |||
| 02 September | 0 | |||
| 01 September | +3 |
Channel Posts
🎉 TgDB is back online!
📱 TgDB Search Lite: @tgdb_search_bot
🖥 TgDB Search Plus: tgdb.org/bot
| 2 | 🎉 TgDB is back online!
📱 TgDB Search Lite: @tgdb_search_bot
🖥 TgDB Search Plus: tgdb.org/bot | 7 262 |
| 3 | TgDB Search webchat will be down for maintenance for about ~8h | 8 157 |
| 4 | All known bugs related to the TgDB Search Plus webchat have finally been fixed.
The webchat now supports notifications and read receipts for messages sent to the bot.
Infinite scrolling and search functionality within the chat history will also be implemented shortly.
📱 TgDB Search Lite: @tgdb_search_bot
🖥 TgDB Search Plus: tgdb.org/bot | 0 |
| 5 | The webchat is currently experiencing some technical issues; we are working to resolve them. The issues will be resolved shortly. | 0 |
| 6 | We've eased the restrictions on the /search command, so regular searches are back to normal!
Unfortunately, we’ve had to limit the 'search by ID' feature for certain users for now. Thanks for your patience!
📱 TgDB Search Lite: @tgdb_search_bot
🖥 TgDB Search Plus: tgdb.org/bot | 0 |
| 7 | Technical context
It is important to understand that @tgdb_search_bot is a public service. For a long time, various third-party Telegram client developers have exploited our bot's functionality to resolve Telegram internal ids into usernames or to provide lookup features within their apps—all without our knowledge, consent, or approval.
The presence of our username in a codebase does not imply any partnership or malicious intent on our part; it is simply proof that our public service has been abused by third-party developers who integrate it into their own software behind our backs.
You can see for yourself how widespread this unauthorized integration is by checking the sheer number of results for our bot on GitHub:
https://github.com/search?q=tgdb_search_bot&type=code | 0 |
| 8 | Public Statement regarding the Nekogram incident
We are aware of the recent controversy surrounding the Nekogram application and the claims regarding the unauthorized transmission of user phone numbers.
Following the public disclosure (GitHub Issue #336), many users have noticed the username @tgdb_search_bot mentioned within Nekogram's source code. We want to address this directly to clear up any misinformation and protect our community’s reputation.
To be crystal clear:
- TgDB is completely independent. We have no relationship, partnership, or communication with the Nekogram team. We were never consulted, and we did not authorize them to use or include our bot in their codebase.
- The allegations that Nekogram phone numbers were transmitted to our bot are factually incorrect. Our bot has never received, processed, or stored any user phone numbers related to this incident.
- The inclusion of our bot's username in their source code was a unilateral decision by the Nekogram developers, likely for their own internal app features, done entirely without our knowledge. We have been unfairly dragged into this scandal solely because our project was mentioned in their code, causing our users and the public to draw false conclusions about our involvement.
We are currently in contact with the Telegram Team to provide all necessary clarifications and to prove that TgDB has played no part in these activities..
Thank you for your continued support and understanding.
TgDB Team
@tgdb_search_bot
www.tgdb.org | 0 |
| 9 | Public Statement regarding the Nekogram Incident
We are aware of the recent controversy surrounding the Nekogram application and the claims regarding the unauthorized transmission of user phone numbers.
Following the public disclosure (GitHub Issue #336), many users have noticed the username @tgdb_search_bot mentioned within Nekogram's source code. We want to address this directly to clear up any misinformation and protect our community’s reputation.
To be crystal clear:
No Affiliation: TgDB is completely independent. We have no relationship, partnership, or communication with the Nekogram team. We were never consulted, and we did not authorize them to use or include our bot in their codebase.
No Data Collection: The allegations that phone numbers were transmitted to our bot are factually incorrect. Our bot has never received, processed, or stored any user phone numbers related to this incident.
We are a Victim: The inclusion of our bot's username in their source code was a unilateral decision by the Nekogram developers, likely for their own internal app features, done entirely without our knowledge. We have been unfairly dragged into this scandal solely because our project was mentioned in their code, causing our users and the public to draw false conclusions about our involvement.
We strongly condemn any actions that violate user privacy or the integrity of the Telegram ecosystem. We are currently in contact with the Telegram Team to provide all necessary clarifications and to prove that TgDB has played no part in these activities.
We value the trust you place in our services and we are committed to maintaining the highest standards of security and transparency.
Thank you for your continued support and understanding.
TgDB Team
@tgdb_search_bot | 0 |
| 10 | ℹ️ TgDB Update
🇬🇧 The issue causing slow response times for Chinese language queries on the TelegramDB Search Bot has been resolved.
System indexing has been optimized, and Chinese search results now load instantly.
🇨🇳 TelegramDB Search Bot 中文搜索响应缓慢的问题现已修复。系统已完成优化，中文搜索结果现可实现即时加载。 | 0 |
| 11 | The service is currently offline due to a server malfunction. We are working to resolve the issue. | 0 |
| 12 | 🎉 TgDB is back online!
📱 TgDB Search Lite: @tgdb_search_bot
🖥 TgDB Search Plus: tgdb.org/bot | 0 |
| 13 | TgDB Search will be down for maintenance for about ~1.5h | 0 |
| 14 | ⚡️ TgDB: 50% OFF IS NOW LIVE!
The wait is over! To push toward our 1 Million Users milestone, we are cutting all prices in half for the next 7 days.
Starting today, all commands are 50% OFF exclusively via our Web App.
The Web interface is the only place to purchase credits and access our full suite of premium features. If you’ve only been using the bot on Telegram, now is the best time to try the new version:
Premium Commands: Get full access to /where, /members, /near, and /network.
Exclusive Savings: 50% discount applied to all credit purchases.
Full Experience: Manage your account and features with a seamless interface.
⏳ 7 Days Only
This flash sale lasts for one week. Don't miss your chance to get the full feature set at the lowest price possible.
Access the Web App here:
👉 https://www.tgdb.org/bot | 0 |
| 15 | ℹ️ Google login restored
We are pleased to announce that Google login is fully back online on our website.
You can now sign up or log in to your account seamlessly using your Google account.
🔗 https://www.tgdb.org | 0 |
| 16 | ⚡️ TgDB: 50% OFF Starts This Saturday
We are pushing to reach 1 Million Users, so we’re cutting prices in half for one week.
Starting this Saturday, all commands are 50% OFF exclusively via our Web App.
The Web interface is the only place to buy credits and access all premium features like /where, /members, /near, and /network. If you’ve only been using the bot in the chat, this is the best time to switch and get the full feature set for half the price.
Access the Web App here:
👉 https://www.tgdb.org/bot | 0 |
| 17 | 🎉 TgDB is back online!
📱 TgDB Search Lite: @tgdb_search_bot
🖥 TgDB Search Plus: tgdb.org/bot | 0 |
| 18 | The service is currently down due to a general blackout in the main data center area | 0 |
| 19 | Merry Christmas! 🎄 | 0 |
| 20 | TgDB is under maintenance | 0 |
