🚀 CrossWall (克洛斯) 高速大流量机场 💰超级实惠 60元/年→ 每月285GB 120元/年→ 每月857GB ⚡️闪电速度 国际高速优质线路 高清视频/下载,告别卡顿 ⚙️智能调度 独家DNS算法平衡负载 人多不卡顿! 🌐全球畅行 13地域30+节点 解锁Netflix/Tiktok/Disney+等平台 📍 特殊区域支持 新疆/河南/江苏/福建等地稳定可用! 📱多端支持 手机、电脑、平板,一键搞定 解锁全球精彩,丝滑高速网络! 🎯 CrossWall,注册开飙🔗 官网💬 群组🚀 测速💰定价

Channel
山茶花の频道
@schpd
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
18,657subscribers
+415 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1002629851735 |
|---|---|
| Type | Channel |
| Username | @schpd |
| Description | 欢迎机场主投稿 私聊/反馈联系: @schpd_bot 投稿/商务联系:https://t.me/schpd?direct 备用频道: @schpd1 公益订阅: @schgy_bot |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 25 August 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 25 August 2026 |
| On Telegram | t.me/schpd |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Aug 2026, 11:52 | 18,657 | +34 |
| 24 Aug 2026, 10:58 | 18,623 | +41 |
| 22 Aug 2026, 16:33 | 18,582 | +41 |
| 21 Aug 2026, 09:37 | 18,541 | +28 |
| 20 Aug 2026, 12:52 | 18,513 | +40 |
| 19 Aug 2026, 15:23 | 18,473 | +27 |
| 18 Aug 2026, 17:58 | 18,446 | +31 |
| 17 Aug 2026, 19:28 | 18,415 | +14 |
| 16 Aug 2026, 18:23 | 18,401 | +34 |
| 15 Aug 2026, 04:36 | 18,367 | +77 |
| 13 Aug 2026, 23:38 | 18,290 | +41 |
| 12 Aug 2026, 16:37 | 18,249 | +7 |
| 12 Aug 2026, 11:16 | 18,242 | first reading |
Engagement
37 posts held, back to 3 August 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 27 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 9.89%
- avg views ÷ 18,657 subscribers
- Avg views / post
- 1,850
- 37 posts measured
- Reaction rate
- 0.21%
- reactions ÷ views · ER floor
- Posts in window
- 37
- of 37 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 29 of 37 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 25 August 2026 |
|---|---|
| Posts held | 37 (3 August 2026 – 25 August 2026) |
| Views total | 68,280 |
| Reactions total | 119 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 25 Aug 2026, 11:53 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
- Photos
- 555
- Videos
- 4
- Links
- 685
Lifetime counters from Telegram’s own channel header, read 25 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
- Video runtime
- 7s
- Average length
- 7s
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
119 reactions across 25 posts, in 5 distinct kinds. The most used accounts for 57.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 68 | 57.1% | |
| ❤ | 46 | 38.7% | |
| 💯 | 2 | 1.68% | |
| 🕊 | 2 | 1.68% | |
| 😁 | 1 | 0.84% |
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 29 of the 37 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 119reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 37 most recent posts we hold, published 3 August 2026 to 25 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
https://t.me/schpd_chat/302747
✅山茶花发卡网|正式上线 优质货源持续更新,稳定靠谱,欢迎进店查看选购! 🛒 自助下单: https://fak.de5.net 💬 缺货补货 / 售后咨询: https://t.me/schhydk?direct 📌 货源持续新增,缺货随时联系补货~
GGB加速服务,您的备用首选 月度计费5.9元/月 年付最低24元/年 aff返佣高达百分之五十,注册即送24小时试用 套餐含ipv4与ipv6节点 下方进入频道防失联 官方频道 |立即注册 | 永久官网
#频道互推 #群组推荐 利器软件工具与开源项目 健身组(健身小姐姐集合) 安卓破解软件大全 二次元轻小说书屋 二手机场流转中心 电子书图书馆 今日有羊毛 深度 好文 (付费文章共享) VPSXB|主机|羊毛|资讯 电报频道&群组索引
✅山茶花の频道 ✈️机场名称: #白嫖云 🌐注册地址: 立即注册 💰优惠券码: FreeF0801 🎁套餐详情:Free计划/80GB/30天套餐 📍节点位置 :香港, 日本 ⚙协议类型 :AnyTLS, TUIC ❗️机场跑路风险难以预估,求稳建议选月付! #白嫖机场 #免费机场
👍3❤2
Neko Cloud-连接世界保护您的隐私。 喵~欢迎加入Neko Cloud🎉 那就让我们先成为朋友吧🥰 🖥官网 💬群组 📣频道 全球线路随心选隐私守护喵~ 🇭🇰香港AWS✔️和 GCP☁️优化线路中转 🇭🇰香港Hytron🔗& 聪明的☁️优质落地 ¥2元/月128G大流量📦 流媒体AI平台支持🤖️ 不限设备不限速无倍率套路🤨 VLESS高速协议TLS支持❌ 喵~可爱又可靠的云服务 就在Neko Cloud💃 ⏲测速图 🔒解锁图 💳拓扑图 ——猫云
比特冲刺 DASHBIT|¥5/月 100GB 🆕首单7折优惠码: dashbit ,100GB 年付仅3️⃣9️⃣元 📱支持流媒体和AI解锁,另有每月1T免费流量的公益节点🤖 🚀“还在担心机场踩雷还不能退款?选择比特冲刺,注册即送48小时免费试用!速度稳定性一试便知” 🚀 购买地址: https://web.dashbit.top 机场频道: https://t.me/dashbitTel 机场群组: https://t.me/dashbitWWW
👍4❤2
端起碗吃肉,放下碗骂娘 有意思,发言也全是为了抽奖而来 tg://user?id=8355018927 tg://openmessage?user_id=8355018927 https://t.me/schpd_chat/299838
👍10❤2
开奖时间今天23:59分 https://t.me/schpd_chat/297407
👍1
✅山茶花の频道 ✈️机场名称: #PandaNetwork #熊猫网络 🌐注册地址: 立即注册 💰优惠券码: 山茶花频道 🎁套餐详情:中号竹笋/88GB/30天套餐 📍节点位置 :香港, 日本, 美国,台湾 ⚙协议类型 :VLESS, AnyTLS 📢机场频道 :https://t.me/pandanetwork_group 💬机场群组 : https://t.me/panda_natwork ⚡️测速报告 : 点击查看 ❗️机场跑路风险难以预估,求稳建议选月付! #白嫖机场 #免费机场
❤2👍2
✅山茶花の频道 ✈️机场名称: #云帆 🌐注册地址: 立即注册 💰优惠券码:RXqTyoUO 🎁套餐详情:试用/30GB/30天套餐 📍节点位置 :香港, 新加坡, 中国, 台湾, 越南, 日本, 美国, 德国, 英国, 阿根廷, 巴西, 加拿大, 瑞士, 智利, 哥斯达黎加, 捷克, 丹麦, 西班牙, 法国, 克罗地亚, 匈牙利, 意大利, 墨西哥, 荷兰, 波兰, 葡萄牙, 罗马尼亚, 塞尔维亚, 斯洛文尼亚, 泰国, 乌克兰, 南非 ⚙协议类型 :VLESS, Hysteria2 ❗️机场跑路风险难以预估,求稳建议选月付! #白嫖机场 #免费机场
👍4❤2🕊1
Showing the 12 most recent of 37 posts we hold for @schpd. 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.
Posts edited after publishing
@schpd edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
- First edit seen
- 13 August 2026
- Most recent edit
- 13 August 2026
Citation-graph rank
Citation-graph rank — 1,494,332 of 1,602,822entries 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 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.
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.
@dashbitTel · 2244 posts山茶花发卡网
@schhydk · 14 postsGGB
@ggbjc0 · 3903 postsNeko Cloud
@NekoCloud2 · 3,8193 posts频道索引&推荐
@recommend3 · 105,9153 postsCrossWall (克洛斯)知识库
@crosswall_knowledge · 2,9672 postsCrossWall 官方交流群| 诚招affman
@crosswall_official · 10,6442 posts影子传话筒
@yingziyyds · 1,1502 postsBeckyNetworkCannel
@BeckyNetworkChannel · 1961 postPanda Natwork
@pandanetwork_group · 271 post7Jia通知
@qijiavpn · 1,2261 postQi 【启】频道
@qijsqyes · 7031 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 25 August 2026 — this entry's latest reading, not the date you are reading this.
“山茶花の频道” (@schpd), 18,657 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/schpd.
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.