21 measurements spanning 27 days, net +501. 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 9,951–11,249 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 21
Measured (UTC)
Subscribers
Change
8 Sept 2026, 09:59
10,772
+52
5 Sept 2026, 06:20
10,720
-19
3 Sept 2026, 07:54
10,739
-34
2 Sept 2026, 01:47
10,773
-9
1 Sept 2026, 00:45
10,782
-73
31 Aug 2026, 01:44
10,855
-31
30 Aug 2026, 01:45
10,886
-29
29 Aug 2026, 02:37
10,915
-63
27 Aug 2026, 23:54
10,978
-10
27 Aug 2026, 00:16
10,988
-17
26 Aug 2026, 02:52
11,005
-32
25 Aug 2026, 01:43
11,037
-62
23 Aug 2026, 14:28
11,099
+998
22 Aug 2026, 02:38
10,101
-23
20 Aug 2026, 17:54
10,124
+4
19 Aug 2026, 14:42
10,120
+15
18 Aug 2026, 12:27
10,105
-31
17 Aug 2026, 12:46
10,136
-56
16 Aug 2026, 05:06
10,192
-26
13 Aug 2026, 11:18
10,218
first reading
Engagement
43 posts held, back to 26 May 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 24 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
9.44%
avg views ÷ 10,772 subscribers
Avg views / post
1,020
24 posts measured
Reaction rate
2.71%
reactions ÷ views · ER floor
Posts in window
24
of 43 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 6 of 24 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 1 September 2026
Posts held
43 (26 May 2026 – 1 September 2026)
Views total
24,396
Reactions total
204
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
1 Sept 2026, 20:11 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
42s
Average length
21s
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
682 reactions across 16 posts, in 7 distinct kinds. The most used accounts for 23.5% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
160
23.5%
🎉
133
19.5%
🔥
133
19.5%
😁
132
19.4%
❤
120
17.6%
👏
2
0.293%
🥰
2
0.293%
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 17 of the 43 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 682 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 43 most recent posts we hold, published 26 May 2026 to 1 September 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.
Showing the 12 most recent of 43 posts we hold for @dbddc. 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.
Forward network
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 1 registered channel — 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.
Handles this channel named that no longer answer
Dead references
7
handles named in this channel’s posts, vacant today
Evidenced gone
4
we ourselves saw one of these resolve, at some point
Never seen alive
3
vacant every time we have ever looked
@dbddc named 7 handles 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.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
@qzngx named in 6 posts, 13 August 2026 – 24 August 2026 · confirmed gone 16 August 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@qzcgx named in 6 posts, 13 August 2026 – 24 August 2026 · confirmed gone 17 August 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@qzzgx named in 6 posts, 13 August 2026 – 24 August 2026 · confirmed gone 17 August 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@tfnftq named in 3 posts, 24 August 2026 – 29 August 2026 · confirmed gone 2 September 2026 (two independent sightings — see how we confirm a dead handle)evidenced
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@lvdb333 named in 5 posts, 16 August 2026 – 24 August 2026
@lvhses named in 5 posts, 16 August 2026 – 24 August 2026
@rc168 named in 5 posts, 16 August 2026 – 24 August 2026
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 8 September 2026 — this
entry's latest reading, not the date you are reading this.
“【七仔 】搭建机器人/机器人开发/电报引流 @ccdb9” (@dbddc), 10,772 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/dbddc.
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.
