Channel
@yangfan1112
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
51subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001803689442 |
|---|---|
| Type | Channel |
| Username | @yangfan1112 |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/yangfan1112 |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 29 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Oct 2026, 18:38 | 51 | -2 |
| 2 Oct 2026, 07:19 | 53 | -1 |
| 16 Sept 2026, 23:56 | 54 | +1 |
| 10 Aug 2026, 09:31 | 53 | no change |
| 7 Aug 2026, 13:14 | 53 | first reading |
17 posts held, back to 7 June 2024 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 17 posts for this entry, the most recent from 2 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
48 reactions across 11 posts, in 9 distinct kinds. The most used accounts for 37.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 💩 | 18 | 37.5% | |
| ❤ | 15 | 31.3% | |
| 👎 | 6 | 12.5% | |
| 👍 | 3 | 6.25% | |
| 🤬 | 2 | 4.17% | |
| ❤🔥 | 1 | 2.08% | |
| 😁 | 1 | 2.08% | |
| 😎 | 1 | 2.08% | |
| 🥱 | 1 | 2.08% |
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 11 of the 17 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 48 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 7 June 2024 to 2 July 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.
The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 10 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 20 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
15598332424 👈客户手机号 小李 👈推的客服
通过后话术【点击自动复制】 1.您好，我是圆梦大业扶贫基金会的，给您通知一下，这边有你的名额，最多可以领取98万扶贫金 2.添加我们老师领取一下，领取全程是不收费的，请您放心 3.发客服码 4.加了跟我说一下，我这边帮你登记 5.客户有顾虑可以说 大业扶贫基金领取的全程是不收费的，您添加老师了解一下对您也没什么坏处 6.交单拉黑删除前结束语 好的，这边看到您添加我们老师了，我就暂时不打扰您了，因为需要通知的群众较多，微信添加人数有上限，这边先把您删了，后续您直接联系老师办理直到领取。
💩2❤1
建议换一下头像昵称 成功率更高 昵称xx老师 或者xx专员
招短信大团 引流团队来 日发几百组
🥱1
有没有在深圳福田的 给你地址帮我找一个人 天价
❤2💩2
Q推180收团
💩2❤1
Q推来团
💩3
日隔15天日收入已超妖精 近我者富 来人谈业务 大量招下手
💩3👍1🤬1😎1
视频色聊女拖来两个，每天粉不多，不露脸，不露私密。明天上班， 做过的联系我，直接弹语音
群呼电销有吗
❤3
Showing the 12 most recent of 17 posts we hold for @yangfan1112. 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.
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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“扬帆彩信教程” (@yangfan1112), 51 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/yangfan1112.
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.