Telegram RegisterThe public register of Telegram
Telegram profile photo for 冬霖信誉频道

Channel

冬霖信誉频道

@Donglin666

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

71subscribers

-1 since we began measuring on 10 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001779288664
TypeChannel
Username@Donglin666
CreatedBetween 1 December 2021 and 27 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live24 August 2026
Measurements held3
Confirmed unchanged2 times, most recently 24 August 2026
On Telegramt.me/Donglin666

Growth

717271.510 August 2026 — 72 subscribers10 August 2026 — 72 subscribers17 August 2026 — 71 subscribers10 August 202617 August 2026
3 measurements spanning 7 days, net -1. 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 71–72 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Aug 2026, 14:3971-1
10 Aug 2026, 11:3072no change
10 Aug 2026, 11:1672first reading

Engagement

10 posts held, back to 27 February 2023the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 10 posts for this entry, the most recent from 10 October 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
1m 37s
Average length
24s

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

25 reactions across 6 posts, in 5 distinct kinds. The most used accounts for 36.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👎936.0%
👍624.0%
💩416.0%
312.0%
🔥312.0%

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

Measured over the 10 most recent posts we hold, published 27 February 2023 to 10 October 2023, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

10 Oct 2023, 03:16 UTC≈1,490 views3 reactionsread 10 August 2026
Video

饿死胆小的 撑死胆大的

👍3

Signed 冬霖

3 Aug 2023, 12:55 UTC≈1,090 views3 reactionsread 10 August 2026

冬霖已经改名 喜羊羊

👍2👎1

Signed 喜羊羊

26 Jul 2023, 02:34 UTC≈1,470 views9 reactionsread 10 August 2026
Video

做大做强,重回巅峰!

👎5🔥3💩1

Signed 冬霖 山东童锦程

24 Jul 2023, 23:25 UTC≈1,450 views1 reactionsread 10 August 2026
Photo

那个风控死号的时代早就过去了,加人方法用对,事半功倍

💩1

Signed 冬霖 山东童锦程

24 Jul 2023, 14:52 UTC≈1,350 views7 reactionsread 10 August 2026

支付宝拉手风控已解除,强势回归!!! 需求商品:无限招收支拉独码团队纯男数据1w出10群 加粉规则: 除了自动通过是我的数据都要 对接群: https://t.me/+GgY27DiguQ4wZWU1 百单大团单线联系: @Donglin6 信誉频道: https://t.me/Donglin666 单价:50+42,100+43,500+44,1000+45,你有量我有价! 拉群时间:晚上12点-凌晨2点 结账时间:下午7-10点 结算: 只结u 要求:带交单记录来,只要独码团队和机房

3👎3👍1

Signed 冬霖 山东童锦程

11 Apr 2023, 13:48 UTC≈1,900 views2 reactionsread 10 August 2026
Photo

你们也想抽天下的破独码都有扶持,主打分逼不挣,就是扶持

💩2

Signed 冬霖 山东童锦程

11 Apr 2023, 13:40 UTC≈1,550 views0 reactionsread 10 August 2026
Photo

4.11账清,支拉体系以完整稳定半年多,不发动态的日子都是在好好赚钱

Signed 冬霖 山东童锦程

9 Mar 2023, 04:01 UTC≈1,330 viewsread 10 August 2026
Video

Video, posted without a caption

Signed 冬霖 山东童锦程

7 Mar 2023, 04:26 UTC≈1,270 viewsread 10 August 2026

通知:现在我留的这些团队,都是我看着跟的久的支拉团,我麻烦各位我的要求控制好了,数据杜绝浪费,给我做到1万出5个群以上,当然现在这个阶段风控那么严重不允许发展团队扩大数据,稳定住你们也清楚为什么我这盘能坚持那么久从一开始钉拉到转型这个支,到现在外面99%盘口倒闭,我们还在坚持,没有规矩,就没有出金,没有出金我们就不需要这个东西

Signed 冬霖 山东童锦程

27 Feb 2023, 13:33 UTC≈1,480 views0 reactionsread 10 August 2026
Photo

2.27账清

Signed 冬霖 山东童锦程

Showing the 10 most recent of 10 posts we hold for @Donglin666. 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.

Citation-graph rank

Citation-graph rank — 1,419,660 of 1,620,105entries 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.

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.

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

“冬霖信誉频道” (@Donglin666), 71 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/Donglin666.

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.