Telegram RegisterThe public register of Telegram
Telegram profile photo for 安好😘一手源头业务通知

Channel

安好😘一手源头业务通知

@douff888

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

48subscribers

+16 since we began measuring on 5 November 2026

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

Register entry

Telegram ID-1003522898088
TypeChannel
Username@douff888
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded5 November 2026
Last confirmed live13 November 2026
Measurements held3
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/douff888

Growth

3248405 November 2026 — 32 subscribers5 November 2026 — 35 subscribers13 November 2026 — 48 subscribers5 November 202613 November 2026
3 measurements spanning 8 days, net +16. 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 30–50 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Nov 2026, 22:5048+13
5 Nov 2026, 20:4835+3
5 Nov 2026, 14:2232first reading

Engagement

16 posts held, back to 30 October 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 1 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
57.0%
avg views ÷ 48 subscribers
Avg views / post
27.4
16 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
16
of 16 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 5 November 2026
Posts held16 (30 October 2026 – 5 November 2026)
Views total438
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken5 Nov 2026, 14:22 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
43s
Average length
9s

Measured directly from 5 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.

Recent posts

Telegram’s own ‘edited’ marker: 2 of 16 posts held from the last 30 days (12.5%) 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).

5 Nov 2026, 12:12 UTC16 viewsread 5 November 2026
Photo

扫PC 、提前设置好IP、 牛逼大哥 一次性拿5台 爆粉爆的嘎嘎叫 还是大哥会玩 😘🥰🥰😘😘😎😎🥰 🐉🐉😀🐉🐉🐉🐉🐉 👍👍👍👍👍👍👍

Signed 安好Anic

5 Nov 2026, 11:11 UTC19 viewsread 5 November 2026

🔈🔈🔈 😃三合一绿标,子号Sm 😄经营码 💥💥💥 地球不爆炸我们不放假 💥💥💥 🟢接预定🟢 😘🥰🥰😘😘😎😎🥰

Signed 安好Anic

5 Nov 2026, 03:22 UTC26 viewsread 5 November 2026
Video

😃😀😃😀😃 😃企业三合一绿标 、获客已开、超管码、微信客服、独家独码、原机一机一IP 🉑定制子号一拖5 、价格小贵 🉑挂靠、🉑PC(建议平板调好IP) (代加工子号SM,一条龙服务) ⚡⚡⚡⚡⚡⚡ 😶😶😶😶😶😶 🧐 @kyfaqq

Signed 安好Anic

4 Nov 2026, 12:21 UTC27 viewsread 5 November 2026
Photo

😃大量出三合一企业微信绿标主体目前比较稳妥的主体挂载方式 🫠模式(挂靠、PC (提前设置Ip) 可以给你设置独家管理【最稳妥】 可设管理,可邮寄价格不一可问价 🫠单独设备 + 一台企业微信绿标主体 + 一个微信法人实名账号质量有保障【邮寄硬性指标需设置管理或者拉号】防止后续人脸及其他意外 ⚡售后服务: 主体邮寄的用死主体不补, 主体出二次人脸,可以售后 😄😃😃😃😃😃😃😃 专业的事交给专业的人 😃😃😄😃😃 @kyfaqq

Signed 安好Anic

4 Nov 2026, 02:27 UTC28 viewsread 5 November 2026
Photo

最后3台 三合一绿标主体 获客已开 可定制一超管五子号 提前预约预定 包含主体设备+子号设备

Signed 安好Anic

4 Nov 2026, 01:38 UTC27 viewsread 5 November 2026
Video

😃好不好用,大哥们知道,稳的一批 😄😃😃😃😃😃😃😃 ⚡⚡⚡⚡⚡⚡

Signed 安好Anic

3 Nov 2026, 17:53 UTC28 viewsread 5 November 2026

🔈🔈🔈 企业入职避开人脸最新方案 企业主体打开内部群,用群码邀请员工入群,后10-20分钟后再去实名认证,目前还未发现出现过人脸问题。好方案分享给大家🤝

Signed 安好Anic

3 Nov 2026, 17:47 UTC27 viewsread 5 November 2026
Video

接企业微信代 实名 可二次 来量大老板 各种代实名 成品号直出 出大量零钱通

Signed 安好Anic

2 Nov 2026, 16:55 UTC29 viewsread 5 November 2026
Photo

三合一绿标主体、接预定 可做子号 大批量接

Signed 安好Anic

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

Mentions

Named by 2 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.

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

“安好😘一手源头业务通知” (@douff888), 48 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/douff888.

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.