Telegram RegisterThe public register of Telegram
Telegram profile photo for Дисс заботится о вас!

Channel

Дисс заботится о вас!

@ImDisss

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Telegram's recommendations · Cite this entry

11,206subscribers

+22 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001646115749
TypeChannel
Username@ImDisss
Created24 July 2022measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live28 August 2026
Measurements held21
Confirmed unchanged1 time, most recently 28 August 2026
On Telegramt.me/ImDisss

Growth

11,12411,22211,1736 August 2026 — 11,184 subscribers6 August 2026 — 11,189 subscribers7 August 2026 — 11,177 subscribers8 August 2026 — 11,170 subscribers10 August 2026 — 11,167 subscribers11 August 2026 — 11,162 subscribers12 August 2026 — 11,165 subscribers13 August 2026 — 11,156 subscribers14 August 2026 — 11,146 subscribers16 August 2026 — 11,153 subscribers17 August 2026 — 11,146 subscribers18 August 2026 — 11,141 subscribers19 August 2026 — 11,136 subscribers20 August 2026 — 11,131 subscribers21 August 2026 — 11,124 subscribers23 August 2026 — 11,150 subscribers24 August 2026 — 11,222 subscribers25 August 2026 — 11,221 subscribers26 August 2026 — 11,218 subscribers27 August 2026 — 11,221 subscribers28 August 2026 — 11,206 subscribers11,2066 August 202628 August 2026
21 measurements spanning 22 days, net +22. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 11,109–11,237 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 21
Measured (UTC)SubscribersChange
28 Aug 2026, 17:0711,206-15
27 Aug 2026, 13:5611,221+3
26 Aug 2026, 16:2311,218-3
25 Aug 2026, 14:4511,221-1
24 Aug 2026, 18:1611,222+72
23 Aug 2026, 04:0311,150+26
21 Aug 2026, 13:0211,124-7
20 Aug 2026, 11:5211,131-5
19 Aug 2026, 14:1911,136-5
18 Aug 2026, 12:5911,141-5
17 Aug 2026, 13:4811,146-7
16 Aug 2026, 03:0711,153+7
14 Aug 2026, 16:0811,146-10
13 Aug 2026, 04:2411,156-9
12 Aug 2026, 02:4411,165+3
11 Aug 2026, 02:1411,162-5
10 Aug 2026, 00:0211,167-3
8 Aug 2026, 21:2711,170-7
7 Aug 2026, 22:0811,177-12
6 Aug 2026, 19:1011,189first reading

Engagement

40 posts held, back to 17 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 40 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
45.8%
avg views ÷ 11,206 subscribers
Avg views / post
5,130
24 posts measured
Reaction rate
11.7%
reactions ÷ views · ER floor
Posts in window
24
of 40 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 27 August 2026
Posts held40 (17 July 202627 August 2026)
Views total123,130
Reactions total14,465
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 10:01 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

Video runtime
1m 47s
Average length
36s

Measured directly from 3 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

28,039 reactions across 40 posts, in 4 distinct kinds. The most used accounts for 75.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🍓21,26875.9%
🎃2,3458.36%
🎄2,3448.36%
🤝2,0827.43%

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 40 of the 40 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 28,039reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 40 most recent posts we hold, published 17 July 2026 to 27 August 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
41
across the posts below
Posts paid on
9
of 40 we hold a reading for · 23%
Most on one post
27
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @ImDisss. 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 40 most recent posts we hold for this entry, published 17 July 2026 to 27 August 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

27 Aug 2026, 05:54 UTC≈2,260 views808 reactionsread 28 August 2026
Photo

Хэппи бездэй

🍓640🤝102🎄66

23 Aug 2026, 18:54 UTC≈3,910 views377 reactionsread 28 August 2026
Forwarded from @mimi_xd27Photo

С днем рождения дисс!! ❤️❤️🥥🥥

🍓304🤝44🎄29

23 Aug 2026, 17:49 UTC≈12,300 views668 reactions3 Starsread 28 August 2026
Photo

Photo, posted without a caption

🍓520🎃89🎄59

23 Aug 2026, 15:51 UTC≈3,460 views207 reactionsread 28 August 2026
Photo

💬 У тебя новое анонимное сообщение! Дисс вы очень крутая художница!! Поздравляю вас с вашим дррр! Ваши работы вдохновляют многих, спасибо вам за это!!。⁠◕⁠‿⁠◕⁠。 @anonaskbot

🍓188🎃13🎄6

23 Aug 2026, 15:44 UTC≈3,460 views257 reactionsread 28 August 2026
Photo

здравствуйте, с днем рождения вас !! 👀🦦

🍓219🎃26🎄12

23 Aug 2026, 14:17 UTC≈3,590 views231 reactionsread 28 August 2026
Photo

💬 У тебя новое анонимное сообщение! Клубнично-ванильного дня рождения! @anonaskbot

🍓207🎄19🎃5

23 Aug 2026, 12:19 UTC≈2,980 views266 reactionsread 28 August 2026
Forwarded from @kluqwashhPhoto

С др именниничков 😊

🍓227🎃32🎄7

23 Aug 2026, 12:19 UTC≈3,140 views262 reactionsread 28 August 2026
Forwarded from @MiddayDeathPhoto

С днём клубничного варенья Дисс!!

🍓254🎃6🎄2

23 Aug 2026, 08:38 UTC≈3,600 views366 reactionsread 28 August 2026
Forwarded from @kto_to_tamovPhoto

С днё рождения Дисс клубничко 🍓

🍓292🎄45🎃29

23 Aug 2026, 04:40 UTC≈3,890 views362 reactionsread 28 August 2026
Photo

💬 У тебя новое анонимное сообщение! еее с днём рождения Дисс🥺 @anonaskbot

🍓301🎄38🤝23

Showing the 12 most recent of 40 posts we hold for @ImDisss. 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.

Citation-graph rank

Citation-graph rank — 17,295 of 1,623,166entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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 42 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. The 23 listed below are the most frequent namers; the rest are counted above but not each listed.

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Фикс
@fixplaygg · 53,168
Telegram ranks this channel #23 of 51 here — alongside 50 others — read 24 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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 28 August 2026 — this entry's latest reading, not the date you are reading this.

“Дисс заботится о вас!” (@ImDisss), 11,206 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/ImDisss.

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.