@NocturneSound one of his other accounts dont purchase anything from there either
๐16โค6๐2๐2โก1๐คฉ1

Channel
@drumkitleaks
On this record: Growth ยท Engagement ยท What this channel posts ยท Reactions ยท Posts ยท Citations ยท Handles named that no longer answer ยท Cite this entry
13,493subscribers
-51 since we began measuring on 7 August 2026
Risers and fallers across the register ยท movement among entries of 10,000โ31,623.
| Telegram ID | -1001199475789 |
|---|---|
| Type | Channel |
| Username | @drumkitleaks |
| Created | Between 1 March 2018 and 31 July 2021โ estimated from Telegramโs id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 26 August 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 26 August 2026 |
| On Telegram | t.me/drumkitleaks |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Aug 2026, 02:12 | 13,493 | -3 |
| 25 Aug 2026, 04:34 | 13,496 | +2 |
| 24 Aug 2026, 03:06 | 13,494 | -7 |
| 22 Aug 2026, 11:55 | 13,501 | -3 |
| 20 Aug 2026, 23:29 | 13,504 | +3 |
| 19 Aug 2026, 23:33 | 13,501 | -4 |
| 18 Aug 2026, 23:58 | 13,505 | -1 |
| 17 Aug 2026, 20:38 | 13,506 | -4 |
| 16 Aug 2026, 18:35 | 13,510 | -6 |
| 15 Aug 2026, 04:04 | 13,516 | -3 |
| 14 Aug 2026, 00:27 | 13,519 | -7 |
| 12 Aug 2026, 17:23 | 13,526 | -5 |
| 10 Aug 2026, 17:44 | 13,531 | -5 |
| 9 Aug 2026, 19:03 | 13,536 | -6 |
| 8 Aug 2026, 16:53 | 13,542 | -4 |
| 7 Aug 2026, 19:11 | 13,546 | +2 |
| 7 Aug 2026, 15:00 | 13,544 | no change |
| 7 Aug 2026, 14:59 | 13,544 | first reading |
17 posts held, back to 25 November 2025 โ the reader has not yet reached the start of this channelโs public history, so older posts may sit further back, unread. Read across 35 pagesof Telegramโs post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute โ we hold 17 posts for this entry, the most recent from 25 November 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegramโs own channel header, read 26 August 2026 โ not the date at the top of this page, which is when the subscriber count was last read. A count marked โ was rounded by Telegram before we ever saw it โ t.me prints these counters in full below 1,000 and to three significant figures above, so โ142,000 means somewhere between 141,500 and 142,499.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel โ not this channelโs whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegramโs own rounded chrome, so it carries no โ mark.
215 reactions across 13 posts, in 11 distinct kinds. The most used accounts for 35.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| โค | 76 | 35.3% | |
| ๐ | 48 | 22.3% | |
| ๐ | 29 | 13.5% | |
| ๐ | 19 | 8.84% | |
| ๐ | 16 | 7.44% | |
| ๐ | 12 | 5.58% | |
| ๐ฅ | 8 | 3.72% | |
| ๐ | 3 | 1.40% | |
| โก | 2 | 0.93% | |
| โคโ๐ฅ | 1 | 0.465% | |
| ๐คฉ | 1 | 0.465% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities โ ๐ is thanks in one channel and mourning in another โ so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one โ 4.34K, 1.2M โ so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 15 of the 17 sampled posts in this sample. Summed by Telegramโs own count on each post โ not by adding up the per-emoji breakdown above โ those same posts carry 215reactions in total: the kind of figure the paragraph above means by โa reaction total printed elsewhere on the pageโ.
Measured over the 17 most recent posts we hold, published 25 November 2025 to 25 November 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
@NocturneSound one of his other accounts dont purchase anything from there either
๐16โค6๐2๐2โก1๐คฉ1
Dont purchase anything from any of these groups or you'll get scammed ๐
๐31โค15๐7๐2๐1
Pure i tuoi gruppi e canali del cazzo sono stati etichettati come truffa coglione ๐๐๐
๐15โค12๐2โคโ๐ฅ1๐1
https://t.me/coccotheplug https://t.me/producerslab https://t.me/leaksalliancefiles https://t.me/ProducersRiot These are some of his other channels/groups so stay away from these channels too he's just been scamming people for years now but he fucked with the wrong guy this time ๐คฃ๐คฃ
โค23๐2
Pussy ass ninja il karma gira ricordatelo
๐12
Keep deleting all messages ๐คฃ๐คฃ
๐7โค1
Never purchase any offer from any of this guy's groups he's a fucking scammer help us take down all of his groups he even changed his tag pussy ass ๐คฃ๐คฃ๐คฃ๐คฃ @Nowrriesusdt
๐ฅ7๐3
Togli pure i commenti stupido coglione vali meno di zero come uomo e come persona
โค11
Channel name was changed to ยซ๐คก๐คก๐คกยป
Con questo canale ha finito all love ๐ค
โค1
Segnalatelo e tirategli giรน l account
๐9
Mi spiace per tutte le persone che ha scammato non ho potuto fare altro che toglierli questo canale che era di proprietร mia @AnthesArche รจ una puttana appena scammato 150โฌ ad un mio amico vali meno di zero figlio di puttana
โค3
Showing the 12 most recent of 17 posts we hold for @drumkitleaks. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked โ was rounded by Telegram before we ever saw it โ t.me prints views in full below 1,000 and to three significant figures above, so โ1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason โ naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides โ the โNamed by N registered channelsโ figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
@drumkitleaks named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handleโs history โ see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today โ not that anything โdiedโ. How this is measured.
References a handle that is not a live channel โ we have no record it ever was one.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 26 August 2026 โ this entry's latest reading, not the date you are reading this.
โ๐คก๐คก๐คกโ (@drumkitleaks), 13,493 subscribers as measured 26 August 2026. Telegram Register, tgregister.com/channel/drumkitleaks.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV ยท JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.