DIRTY EVENTS pinned «МОСКВА! GONE.FLUDD YANIX BUSHIDO ZHO LOVV66 SCALLY MILANO AARNE VOSKRESENSKII ELYAPLUGG! BABY CUTE STOPBAN МОЛОДОЙ ПЛАТОН CARDINPARIS 2000 реакции и мы анонсируем CHRISTMAS FEST!»

Channel
DIRTY EVENTS
@dirtyevents
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry
7,459subscribers
-14 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002112626442 |
|---|---|
| Type | Channel |
| Username | @dirtyevents |
| Description | Москва | Вечеринки и концерты Гостевой чат – t.me/dirtyeventschat Ночные ивенты – https://t.me/dirtynightevents Рассылка – https://vk.cc/cPdczN Сотрудничество & реклама - @sbdhiro7 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 3 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 3 November 2026 |
| On Telegram | t.me/dirtyevents |
Topic
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 12 September 2026 and assigned it the closest of 31 fixed categories, at 75% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Nov 2026, 07:51 | 7,459 | +169 |
| 31 Oct 2026, 13:46 | 7,290 | -13 |
| 28 Oct 2026, 15:56 | 7,303 | -10 |
| 22 Oct 2026, 08:26 | 7,313 | -16 |
| 18 Oct 2026, 23:07 | 7,329 | +12 |
| 16 Oct 2026, 04:09 | 7,317 | -38 |
| 13 Oct 2026, 11:37 | 7,355 | +34 |
| 7 Oct 2026, 06:18 | 7,321 | +39 |
| 30 Sept 2026, 03:40 | 7,282 | +68 |
| 19 Sept 2026, 17:39 | 7,214 | -12 |
| 15 Sept 2026, 12:17 | 7,226 | -9 |
| 12 Sept 2026, 00:57 | 7,235 | -38 |
| 7 Sept 2026, 21:59 | 7,273 | -45 |
| 2 Sept 2026, 21:45 | 7,318 | -39 |
| 31 Aug 2026, 04:57 | 7,357 | -6 |
| 28 Aug 2026, 10:15 | 7,363 | -44 |
| 25 Aug 2026, 00:15 | 7,407 | -30 |
| 21 Aug 2026, 10:23 | 7,437 | -5 |
| 18 Aug 2026, 11:39 | 7,442 | -1 |
| 15 Aug 2026, 10:17 | 7,443 | first reading |
Engagement
82 posts held, back to 31 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 22 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 16.1%
- avg views ÷ 7,459 subscribers
- Avg views / post
- 1,200
- 22 posts measured
- Reaction rate
- 6.09%
- reactions ÷ views · ER floor
- Posts in window
- 23
- of 82 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 21 of 22 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 4 November 2026 |
|---|---|
| Posts held | 82 (31 July 2026 – 4 November 2026) |
| Views total | 26,416 |
| Reactions total | 1,543 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 4 Nov 2026, 13:33 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
- Photos
- ≈1,480
- Videos
- ≈96
- Links
- ≈1,410
Lifetime counters from Telegram’s own channel header, read 4 November 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.
- Video runtime
- 32s
- Average length
- 16s
Measured directly from 2 videos 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.
Reaction mix
2,702 reactions across 77 posts, in 35 distinct kinds. The most used accounts for 22.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5271604904484429816 | 618 | 22.9% | |
| custom 5418085373999858225 | 437 | 16.2% | |
| custom 5271482832923942376 | 372 | 13.8% | |
| custom 5283275949830338520 | 105 | 3.89% | |
| 🍓 | 94 | 3.48% | |
| custom 5283097949205721775 | 76 | 2.81% | |
| custom 5409057284024199515 | 73 | 2.70% | |
| custom 6104890025185385445 | 72 | 2.66% | |
| custom 5363838691510873846 | 64 | 2.37% | |
| custom 5283058671729803109 | 62 | 2.29% | |
| custom 5337173743535934206 | 62 | 2.29% | |
| custom 5285297440612712457 | 61 | 2.26% | |
| custom 5309888224326329043 | 61 | 2.26% | |
| custom 5301008383736827835 | 59 | 2.18% | |
| custom 5301041884481735933 | 55 | 2.04% | |
| custom 5316997365863828351 | 51 | 1.89% | |
| custom 5334598893462113260 | 41 | 1.52% | |
| custom 5283061622372329867 | 37 | 1.37% | |
| custom 5301156186446387878 | 35 | 1.30% | |
| custom 5336970007467281749 | 34 | 1.26% | |
| 15 further kinds | 233 | 8.62% |
Custom emoji. 19 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 77 of the 82 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 2,702 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 82 most recent posts we hold, published 31 July 2026 to 4 November 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Telegram Stars
- Stars received
- 6
- across the posts below
- Posts paid on
- 1
- of 81 we hold a reading for · 1%
- Most on one post
- 6
- single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @dirtyevents. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 82 most recent posts we hold for this entry, published 31 July 2026 to 4 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Recent posts
Telegram’s own ‘edited’ marker: 3 of 23 posts held from the last 30 days (13.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Таинственный LOVV66 ворвался в топ так же стремительно, как продаются билеты на наш фестиваль🎤 Промокод на скидку : DIRTY
custom 54180853739998582255custom 52714828329239423763custom 52716049044844298163
Мы подготовили для вас 3 фестиваля, и 1 сольный концерт 🎶 От вас ждём максимальной поддержки,будут все артисты которых вы ждете и не ждете
custom 541808537399985822551custom 527148283292394237633custom 527160490448442981628
Перед основным фестивалем, хотите фестиваль 27 декабря? SECRET GUEST + HUZZY B + 3GOTH2002 + CARDINPARIS + CLOUT
custom 541808537399985822530custom 527148283292394237623custom 527160490448442981617
МОСКВА! GONE.FLUDD YANIX BUSHIDO ZHO LOVV66 SCALLY MILANO AARNE VOSKRESENSKII ELYAPLUGG! BABY CUTE STOPBAN МОЛОДОЙ ПЛАТОН CARDINPARIS 2000 реакции и мы анонсируем CHRISTMAS FEST!
custom 5271604904484429816550custom 5418085373999858225313custom 5271482832923942376286
С кем сольный концерт провести Elya Plugg или Шайни ? Ваши мнение под комментариями 👇
custom 541808537399985822520custom 52716049044844298168custom 52714828329239423767
Думаем сделать сольный концерт , посоветуйте артиста С кем сделать ? Читаем все ваши комментарии
custom 541808537399985822510custom 52714828329239423764custom 52716049044844298163
Розыгрыш билетов на фестиваль 25 артистов ❤️ Условия : 1. Сделать репост истории к себе в историю/тгк 2. Скинуть скрин под комментарием Сама история : https://t.me/dirtyevents/s/926
custom 527148283292394237613custom 52716049044844298167custom 54180853739998582256
Остались последние 500 билетов Такими темпами SOLD OUT скоро Успей купить билет до повышение цен,ведь цены будут только расти 🔼 Промокод на скидку : DIRTY Купить билеты 🎫
custom 53371737435359342068custom 53011561864463878786custom 53369700074672817494💘1
Posted without readable text
custom 52714828329239423763custom 52716049044844298162custom 54180853739998582252
Блогеры/инста блогеры/тиктокеры-тиктокерши Отпишите нам в лс - @sbdhiro7 Для вас есть хорошее предложение
custom 53369700074672817494custom 53011561864463878782custom 53371737435359342062
Ребята все сегодняшние выступление артистов выложили к себе в инстаграм https://www.instagram.com/dirty_eventsmsk?xtok=MTNmMndnNGs1cjlybg%3D%3D&utm_source=qr Приятного просмотра ❤️
Showing the 12 most recent of 82 posts we hold for @dirtyevents. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Posts edited after publishing
@dirtyevents edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
- First edit seen
- 28 August 2026
- Most recent edit
- 4 November 2026
Posts recorded as deleted after publishing
We recorded 4 posts on @dirtyevents as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
- First seen missing
- 7 August 2026
- Most recent seen missing
- 4 November 2026
- Median time before seen missing
- 38 hours
- Seen missing in the last 30 days
- 1
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Named by 5 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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.
Cite this entry
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 3 November 2026 — this entry's latest reading, not the date you are reading this.
“DIRTY EVENTS” (@dirtyevents), 7,459 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/dirtyevents.
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.