Telegram RegisterThe public register of Telegram
Telegram profile photo for 精聊话术|海外素材|成功话术|话术大全

Channel

精聊话术|海外素材|成功话术|话术大全

@huashu_sucaili

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

1,402subscribers

-8 since we began measuring on 30 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002063100404
TypeChannel
Username@huashu_sucaili
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded30 August 2026
Last confirmed live19 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/huashu_sucaili

Topic

Marketing & affiliate — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 63% 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

1,4021,4101,40630 August 2026 — 1,410 subscribers30 August 2026 — 1,408 subscribers2 September 2026 — 1,407 subscribers7 September 2026 — 1,406 subscribers11 September 2026 — 1,404 subscribers15 September 2026 — 1,403 subscribers19 September 2026 — 1,402 subscribers30 August 202619 September 2026
7 measurements spanning 21 days, net -8. 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 1,401–1,411 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 15:391,402-1
15 Sept 2026, 09:191,403-1
11 Sept 2026, 13:211,404-2
7 Sept 2026, 01:001,406-1
2 Sept 2026, 07:441,407-1
30 Aug 2026, 17:041,408-2
30 Aug 2026, 03:301,410first reading

Engagement

4 posts held, back to 19 November 2025the 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 4 posts for this entry, the most recent from 14 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1100.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 1 of the 4 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 4 most recent posts we hold, published 19 November 2025 to 14 August 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.

Recent posts

19 Nov 2025, 15:47 UTC917 views1 reactionsread 30 August 2026

😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂 🇼🇫【旺财作图生成器】🇼🇫 ➡️ @wangcai18168 ⭐️请大家持续关注 频道 以免上架 错过更好的人设套图 需要哪方面需求 , 点击进入那方面的频道,可以选择性使用! 套图频道如下⬇️⬇️⬇️⬇️⬇️⬇️ ⭐️购买人设⭐️诚信为本⭐️素材分类⭐️国家明细 1️⃣套图 【亚洲女】:https://t.me/taotu_z6 2️⃣套图 【亚洲男】:https://t.me/taotu_z7 3️⃣套图 【欧洲女】:https://t.me/taotu_z8 4️⃣套图 【欧洲男】:https://t.me/taotu_z9 5️⃣套图 【私密照】:https://t.me/simi_taotu2 6️⃣免费 【话术区】:https://t.me/SuCai_A6 7️⃣免费 【男私密】:https://t.me/simi_taotu3 8️⃣精选 【素材区】:https://t.

1

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

Names

Channels on the register whose handles appear in this channel's posts.

精品话术素材馆
@huashu_sucai_taotu2 · 693
1 post
可可 素材馆♥️
@huashu_sucai_taotu3 · 445
1 post
【韩国素材】狗推素材|旅游|生活|美食|风景|购物|高清大图|taotu renshe hanguo
@sucais01 · 15,621
1 post
【日本素材】狗推素材|旅游|生活|美食|风景|购物|高清大图|taotu renshe riben
@sucais02 · 16,978
1 post
【美国素材】狗推素材|旅游|生活|美食|风景|购物|高清大图|taotu renshe meiguo
@sucais03 · 16,255
1 post
【台湾素材】狗推素材|旅游|生活|美食|风景|购物|高清大图|taotu renshe taiwan
@sucais04 · 15,812
1 post
【香港素材】狗推素材|旅游|生活|美食|风景|购物|高清大图|taotu renshe xianggang
@sucais05 · 15,921
1 post
【中国素材】国内素材|狗推素材|旅游|生活|美食|风景|购物|高清大图|taotu renshe zhongguo
@sucais06 · 16,521
1 post
【印度素材】印度尼西亚素材|狗推素材|旅游|生活|美食|风景|购物|高清大图|taotu renshe yindu
@sucais07 · 15,586
1 post
【英国素材】狗推素材|旅游|生活|美食|风景|购物|高清大图|taotu renshe yingguo
@sucais08 · 15,395
1 post
【新加坡素材】狗推素材|旅游|生活|美食|风景|购物|高清大图|taotu renshe xinjiapo
@sucais09 · 15,504
1 post
【马来西亚素材】狗推素材|旅游|生活|美食|风景|购物|高清大图|taotu renshe malaixiya
@sucais10 · 14,785
1 post
【海外素材总库】taotu renshe huashu
@sucaizk · 86,379
1 post
旺财作图官方频道-作图选旺财,专业包发财💰
@wangcai18168 · 15,930
1 post

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

“精聊话术|海外素材|成功话术|话术大全” (@huashu_sucaili), 1,402 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/huashu_sucaili.

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.