最新爆款推荐: 😀微信号,ai微信,不死微信,华为备份包 😀原设备实名微信+国网,包加人带支付 📱地推国卡私人小红书,可解封,可复接 📱企业微信标绿主体,上真机/云机,企业微信三合一,企业独苗,稳如老狗 📱体育,股票,融媒体,微信企业公众号,服务号,H5小程序日租,抖音来客 📱私人地推QQ号 单太双太三太皇冠月卡0违规 📱国卡私人地推抖音号,抖音蓝v号,企业抖音号,抖音实名号,抖音千粉号,抖音等级号,抖音万粉号 ✔️国卡三条实名号,闲鱼三认证鱼号,😇陌陌私人号,千天soul云机。 📱三网快手号实名包激活,快手实名老号,快手备份包 😀国内支付宝v3,,境外支付宝,原设备私人支付宝可加工余额宝,可解封,全网最牛逼的支付宝! 😀三网手机卡,拆机卡,国内流量卡,香港流量卡,国内注册卡,实名厅卡,国内注册卡,国内电话卡,移动电话卡,联通电话卡 🙃韩国kakao,band,蓝标ws,台湾日本line接码,苹果id,tg会员,飞机会员, 😃…

Channel
翠兰(Cui Lan)-频道付费广告30U/条
@cuilan1
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
26,299subscribers
+4,050 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1003956343252 |
|---|---|
| Type | Channel |
| Username | @cuilan1 |
| Created | Between 1 April 2026 and 21 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 14 October 2026 |
| Measurements held | 32 |
| Confirmed unchanged | 1 time, most recently 14 October 2026 |
| On Telegram | t.me/cuilan1 |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Oct 2026, 19:25 | 26,299 | -119 |
| 13 Oct 2026, 08:39 | 26,418 | +41 |
| 9 Oct 2026, 05:37 | 26,377 | -504 |
| 4 Oct 2026, 17:20 | 26,881 | -1,666 |
| 26 Sept 2026, 17:15 | 28,547 | -1,246 |
| 19 Sept 2026, 12:16 | 29,793 | -11 |
| 17 Sept 2026, 00:20 | 29,804 | +13 |
| 15 Sept 2026, 02:39 | 29,791 | +258 |
| 13 Sept 2026, 14:36 | 29,533 | +6,958 |
| 11 Sept 2026, 21:16 | 22,575 | -8 |
| 9 Sept 2026, 07:21 | 22,583 | -36 |
| 6 Sept 2026, 01:55 | 22,619 | -30 |
| 3 Sept 2026, 23:38 | 22,649 | -2 |
| 2 Sept 2026, 15:39 | 22,651 | -21 |
| 1 Sept 2026, 14:05 | 22,672 | -17 |
| 31 Aug 2026, 11:28 | 22,689 | +6 |
| 30 Aug 2026, 11:04 | 22,683 | -12 |
| 29 Aug 2026, 12:38 | 22,695 | -19 |
| 28 Aug 2026, 13:08 | 22,714 | -8 |
| 27 Aug 2026, 16:17 | 22,722 | first reading |
Engagement
68 posts held, back to 21 July 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 88 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 15.2%
- avg views ÷ 26,299 subscribers
- Avg views / post
- 4,010
- 21 posts measured
- Reaction rate
- 0.026%
- reactions ÷ views · ER floor
- Posts in window
- 21
- of 68 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 2 of 21 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 14 October 2026 |
|---|---|
| Posts held | 68 (21 July 2026 – 14 October 2026) |
| Views total | 84,119 |
| Reactions total | 2 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Oct 2026, 15:00 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
- 16s
- Average length
- 16s
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.
Reaction mix
4 reactions across 4 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 4 | 100.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 6 of the 68 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 4 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 68 most recent posts we hold, published 21 July 2026 to 14 October 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
01公群已退押 停止交易
👊👊👊👊 (天马 )(Q裙 ) 无限吃全网平台产值粉 带产值图来 在别家稳定打的想挑战更高单价的欢迎来试试宝贝们 同等待遇的前提下单价+1+2+3 满足一切要求 零过滤 零暗扣 卡密丝滑、 ✈️联系 @kk25850501 女汉子 ✈️联系 @kkkk25850501 小助理
👊👊👊👊 😀😀😀😀😀😀😀😀😀😀😀😀😀😀😀😀😀😀 抖音全系列 热评只要同城 点赞只要粉丝群 快手全系列 快手语音厅 陌陌私信 飞车 soul全系 三国杀 英雄联盟 小红书自热 SLG策略游戏 三国志战略版 三国志王道天下 Q附近人 Q站街 地下城 率土之滨 😃😃😃😃⚡️⚡️⚡️⚡️ 以上姿势均可测试 欢迎中介各大小工作室来聊,价格你开,条件你定,只要真粉可扶持。⚡️⚡️⚡️ 本人 @txbjyr 助理 @cl57575 助理 @mmen81 已发布供需次数5
👊👊👊👊 实力集团😀😀😀 不管你是做SEO、劫持、影视、小说、下载还是灰色站群,只要有真实用户流量,我们都能收。 ✅ 收seo 量,劫持,站点,地推 网推影视小说等,一切真量! ✅ 支持测试,量好支持预付!资金无上限! 结算稳,短期转变长期合作量老板都懂,稳定比什么都重要😀😀😀 联系人 @pn136258 @ALL159357 频道 https://t.me/Cz668888
Photo, posted without a caption
👊👊👊👊 ☁️一手工作室跳槽 单价加2-5可预付 ☁️陌陌聊天室单价起步33-40 ☁️陌陌所有姿势价格20-28 ☁️抖音V转姿势起步23 ☁️抖音其他中转姿势起步20 ☁️小红书V转 浏览器转起步17 ☁️王者微转22 浏览器私聊 ☁️地推量 盖章 贴纸浏览器 ☁️探探除私信以外任何姿势 ☁️微信站街 朋友圈 公众号 浏览器 ☁️Q验证Q采集Q附近人Q扫 浏览器扫 ☁️以上姿势跳槽找我 浏览器➕1 微转➕2 公众号起步2-5 价格多少 卡密过滤开多少 被炸多少 你说了算 当天打完当天放款 !!!!!!!! ☁️联系粉圈 风尘:@FL_20_25
👊👊👊👊 (天马 )(Q裙 ) 无限吃全网平台产值粉 带产值图来 在别家稳定打的想挑战更高单价的欢迎来试试宝贝们 同等待遇的前提下单价+1+2+3 满足一切要求 零过滤 零暗扣 卡密丝滑、 ✈️联系 @kk25850501 女汉子 ✈️联系 @kkkk25850501 小助理
亚太实体赌场和钱庄联合双担保 凡所应有,无所不有!公平公正公开,诚信千秋万代,人走钱还在。 无人扶你凌云志,我司送你万两金! ⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️ ⚡️⚡️挑战全网最高首存赠送比例!首存多少就送多少!不为赚钱只为交朋友!真实有效无套路!注:体育不参与此活动! ⚡️存款天天送,每日前三笔存款大派送2888 ⚡️亏损不担心,通赔转运金 天天 9888 ⚡️捕鱼大亨 一发入魂 存款入住星级大酒店 ⚡️月福利每月3号全站发放88888 ⚡️庄、闲一念间,好彩天天送 18888 😆😆😆😆 🤝🥰 😗 💵 😂泰铢 更多精彩活动,请联系客服咨询 爱拼才😂😂 : hy883.me 😂😂RMB投注: www.hy883.me 详情联系⚡️ :@hyyl887 官方网址 ↘️ R: www.hy883.me 即点即玩 U ➡️ hy883.me 😘 说得再好也是吹牛,真金白银送送送才是实力象征…
苹果机 安卓下载充值 扫码可指定地区 全国ip,不同手机型号 一机一图 真人真机精聊, 每个下载都聊到充值,价格实惠 下载和充值都返图 关注频道下单送下载 ✈️: @SAH1204
再次强调一下,对接让公群老板拉专群,不收费,避免纠纷,全额赔付 为什么要拉专群才能赔付?答:因为担保很多家,只认拉翠兰专群
(天马 )(Q裙 ) 无限吃全网平台产值粉 带产值图来 在别家稳定打的想挑战更高单价的欢迎来试试宝贝们 同等待遇的前提下单价+1+2+3 满足一切要求 零过滤 零暗扣 卡密丝滑、 ✈️联系 @kk25850501 女汉子 ✈️联系 @kkkk25850501 小助理
Showing the 12 most recent of 68 posts we hold for @cuilan1. 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
Names
Channels on the register whose handles appear in this channel's posts.
@DB12311223344 · 2173 posts翠兰(Cui Lan)互利互赢 携手共进
@cuilan7 · 31,9902 posts共赢-收各渠道贷款粉
@GY889518 · 542 posts麦芽 工作室
@maiya1688888 · 3762 posts七七哈
@qiqiqiqi777777777777 · 2692 posts橙子
@Cz668888 · 4521 post鸿河集团 长期收一切色粉
@HongHeJT · 7,9481 post怀盈频道通知
@shanhai11223344 · 2,4401 post天富娱乐官方频道🧧
@tianfuhb · 2,0431 posttk959595
@tk959595 · 111 post666公群 腾博会娱乐综合盘已押100万U
@vip28 · 7,9271 post字节跳动团队通知频道
@ZJTD6688888 · 4,1401 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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 1
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 0
- vacant every time we have ever looked
@cuilan1 named 1 handle 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.
named in 3 posts, 29 August 2026 – 28 September 2026 · confirmed gone 4 October 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 14 October 2026 — this entry's latest reading, not the date you are reading this.
“翠兰(Cui Lan)-频道付费广告30U/条” (@cuilan1), 26,299 subscribers as measured 14 October 2026. Telegram Register, tgregister.com/channel/cuilan1.
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.