Hello @Telegram My channel has not violated the rules and policy of using Telegram.
🐲广告、投稿爆料、求助删帖 狗群主@dogdc
新闻专注海外华人资讯，求助，避免踩坑，真假自辩理性吃瓜，讨论群 @dcfff666
🐲专注社群运营DC广告联盟 @dogdc8 👉新闻 @dcaaa777 @dcbbb777 @dcccc777 @dcddd777 @dceee888 @dcfff888 @dcggg888
Created
Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
Gambling & betting — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 79% 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 why it has no browse page of its own yet.
Growth
65 measurements spanning 49 days, net +17,954. 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 56,918–111,351 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)
Subscribers
Change
26 Sept 2026, 00:20
85,999
-1,180
19 Sept 2026, 06:20
87,179
-476
17 Sept 2026, 21:18
87,655
-279
16 Sept 2026, 22:21
87,934
-219
15 Sept 2026, 15:56
88,153
-451
15 Sept 2026, 00:20
88,604
-1,219
14 Sept 2026, 02:00
89,823
-1,588
13 Sept 2026, 12:58
91,411
-647
12 Sept 2026, 08:58
92,058
-517
11 Sept 2026, 20:00
92,575
-441
10 Sept 2026, 07:38
93,016
-514
9 Sept 2026, 10:37
93,530
-763
6 Sept 2026, 23:57
94,293
-312
6 Sept 2026, 03:18
94,605
-682
4 Sept 2026, 10:18
95,287
-116
3 Sept 2026, 21:57
95,403
-334
2 Sept 2026, 20:29
95,737
-57
2 Sept 2026, 14:06
95,794
-517
1 Sept 2026, 21:25
96,311
-47
1 Sept 2026, 17:08
96,358
first reading
Engagement
1,271 posts held, back to 7 August 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 104 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
5.28%
avg views ÷ 85,999 subscribers
Avg views / post
4,540
723 posts measured
Reaction rate
1.48%
reactions ÷ views · ER floor
Posts in window
723
of 1,271 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 663 of 723 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 26 September 2026
Posts held
1,271 (7 August 2026 – 26 September 2026)
Views total
3,284,069
Reactions total
45,771
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
27 Sept 2026, 00:06 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
≈19,000
Videos
≈5,600
Links
≈13,800
Lifetime counters from Telegram’s own channel header, read 27 September 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
2h 18m
Average length
19s
Measured directly from 445 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
61,912 reactions across 900 posts, in 8 distinct kinds. The most used accounts for 20.2% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🎉
12,493
20.2%
👍
12,478
20.2%
🔥
12,380
20.0%
❤
12,307
19.9%
😁
12,249
19.8%
👏
2
0.003%
🤩
2
0.003%
⚡
1
0.002%
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 900 of the 1,000 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 61,912 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 18 August 2026 to 26 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.
Advertising
Ad load
5.40%
54 of 1,000 posts carry an ad marker
Regulatory tokens
0
none — marked by hashtag only
Median views · ads
4,870
over 54 measured posts
Median views · rest
4,350
over 946 measured posts
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 18 August 2026 to 26 September 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Showing the 12 most recent of 1,271 posts we hold for @dcfff888. 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 22 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.
Handles this channel named that no longer answer
Dead references
7
handles named in this channel’s posts, vacant today
Evidenced gone
7
we ourselves saw one of these resolve, at some point
Never seen alive
0
vacant every time we have ever looked
@dcfff888 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.
@topnewsdc named in 23 posts, 8 August 2026 – 28 August 2026 · confirmed gone 12 September 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@huarendashijiandc named in 23 posts, 8 August 2026 – 28 August 2026 · confirmed gone 11 September 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@ribaonews named in 13 posts, 8 August 2026 – 28 August 2026 · confirmed gone 11 September 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@wuxiaoshinews named in 13 posts, 8 August 2026 – 28 August 2026 · confirmed gone 11 September 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@picturedc named in 10 posts, 8 August 2026 – 28 August 2026 · confirmed gone 11 September 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@videodc named in 10 posts, 8 August 2026 – 28 August 2026 · confirmed gone 11 September 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@djmusicdc named in 10 posts, 8 August 2026 – 28 August 2026 · confirmed gone 11 September 2026 (two independent sightings — see how we confirm a dead handle)evidenced
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 26 September 2026 — this
entry's latest reading, not the date you are reading this.
“东南亚热点话题🐲” (@dcfff888), 85,999 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/dcfff888.
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.
