🤖初见选妃、搜索机器人 ·告别繁琐|资源分散、查找耗时? ·全网秒搜|全国资源实时匹配。 ·一步到位|搜完即得,效率翻倍! 🔍[立即开始搜索]
Channel
【初见 】全国包养中转站
@chujian901
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
11,122subscribers
+1,052 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1003621136466 |
|---|---|
| Type | Channel |
| Username | @chujian901 |
| Created | 30 December 2025 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 5 September 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 5 September 2026 |
| On Telegram | t.me/chujian901 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Sept 2026, 08:42 | 11,122 | +40 |
| 3 Sept 2026, 11:42 | 11,082 | +2 |
| 1 Sept 2026, 05:55 | 11,080 | +39 |
| 31 Aug 2026, 05:02 | 11,041 | +19 |
| 30 Aug 2026, 08:07 | 11,022 | +26 |
| 29 Aug 2026, 09:27 | 10,996 | +40 |
| 28 Aug 2026, 11:57 | 10,956 | +23 |
| 27 Aug 2026, 11:33 | 10,933 | +38 |
| 26 Aug 2026, 08:42 | 10,895 | +25 |
| 25 Aug 2026, 05:07 | 10,870 | +48 |
| 24 Aug 2026, 04:45 | 10,822 | +81 |
| 22 Aug 2026, 09:44 | 10,741 | +54 |
| 20 Aug 2026, 21:55 | 10,687 | +43 |
| 19 Aug 2026, 19:12 | 10,644 | +39 |
| 18 Aug 2026, 21:55 | 10,605 | +16 |
| 17 Aug 2026, 19:26 | 10,589 | +67 |
| 16 Aug 2026, 14:12 | 10,522 | +49 |
| 14 Aug 2026, 18:57 | 10,473 | +101 |
| 13 Aug 2026, 06:06 | 10,372 | +72 |
| 12 Aug 2026, 07:17 | 10,300 | first reading |
Engagement
64 posts held, back to 30 December 2025 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 43 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 6.29%
- avg views ÷ 11,122 subscribers
- Avg views / post
- 700
- 44 posts measured
- Reaction rate
- 0.055%
- reactions ÷ views · ER floor
- Posts in window
- 44
- of 64 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 7 of 44 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 3 September 2026 |
|---|---|
| Posts held | 64 (30 December 2025 – 3 September 2026) |
| Views total | 30,783 |
| Reactions total | 8 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 02:06 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
- 18s
- Average length
- 9s
Measured directly from 2 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.
Reaction mix
73 reactions across 19 posts, in 4 distinct kinds. The most used accounts for 94.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 69 | 94.5% | |
| 👍 | 2 | 2.74% | |
| 😁 | 1 | 1.37% | |
| 🥰 | 1 | 1.37% |
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 22 of the 64 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 73 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 64 most recent posts we hold, published 30 December 2025 to 3 September 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
🎟️ 抽奖标题:初见萝莉包养周活跃福利0902 抽奖编号:TL178833265917 🎁 奖品内容: - VIP会员资格*1 - 188积分*2 - 52现金红包*4 - 下次一定*3 🪧 抽奖说明:参与需扣除165积分, 会员资格已入会的中奖抵扣介绍费288 陪跑设立为了平衡抽奖重复度, 中奖者在开奖24小时内找 神の随波逐流 登记领取,炸号恕不兑奖 禁止乱水,违者禁言24h 🎫 参与条件: - 必须有用户名 - 从2026-09-02 00:00:00起发言数量不少于50 - 加入频道:【初见】全国萝莉包养 - 加入频道:【初见 】全国包养中转站 🕒 开奖时间:2026-09-06 22:00自动开奖 🎰已参与人(0):
😂新手交易流程 请耐心看完 初见给大家介绍一下常见问题 😀😃😃😃😃😃😃😃 😳妹子想要上架必看 😳点击此处查看大概保养流程 😳点击此处整体见面满意或者不满意 😳妹妹资料为什么会重复上架 😳与妹妹的见面细节必须看 😳点击此处整体讲解会员的好处 😳点击购买usdt交易所币安流程 😳关于介绍费 看一 😳包养干净吗 看二 😳包养不等于外围 看三 😳零花钱费用 看四、五、六 😳售后规则 看七 😳关于chu单 看八 😳关于联系方式 看九 ➗➗➗➗➗➗➗➗➗➗➗➗➗➗ 😳点击此处历史交易下单反馈 😳点击导航全部资源进入频道 😳点击进入公开聊天群大家可以交流 💯新手玩包养必看流程 一定要看
🤖初见选妃、搜索机器人 ·告别繁琐|资源分散、查找耗时? ·全网秒搜|全国资源实时匹配。 ·一步到位|搜完即得,效率翻倍! 🔍[立即开始搜索]
🎉🎉🎉 开奖通知 🎉🎉🎉 🔖 防伪编号:H178782740455 🎰 合肥观察 @kk3737373 ×【初见】全国包养 @chujian90 联名抽奖 ⚠️ 抽奖说明: 🌊 炎夏繁杂,佳人难遇。2026年6月18日 - 9月1日,凭其他任意包养平台历史消费凭证,经核实,永久入会费直接减半(仅需 333 RMB)。 🍃老客引荐新友入席,新客完成首单后,新老双方各赠 1888 元抵扣券(直接抵扣下一单,不可叠加其他活动优惠)! 🛎中奖者请在48h内兑奖,折扣券可转让,现金红包请找 @palworld137 兑换 🛎中奖后退出群组和频道,炸号,不予兑奖 🛎一切解释权归兑奖人所有 💁 参与情况:102达标 / 139报名 🔋 人品加成:98票 ⚡️⚡️⚡️ 🎅 联系领奖:初见Bao养【查档】 1. 西雅图⚡️ 奖品:52现金红包 2. 波·比⚡️⚡️⚡️ 奖品:52现金红包 3. 彼特 奖品:52现金红包 4. …
🤖初见选妃、搜索机器人 ·告别繁琐|资源分散、查找耗时? ·全网秒搜|全国资源实时匹配。 ·一步到位|搜完即得,效率翻倍! 🔍[立即开始搜索]
🤖初见选妃、搜索机器人 ·告别繁琐|资源分散、查找耗时? ·全网秒搜|全国资源实时匹配。 ·一步到位|搜完即得,效率翻倍! 🔍[立即开始搜索]
🤖初见选妃、搜索机器人 ·告别繁琐|资源分散、查找耗时? ·全网秒搜|全国资源实时匹配。 ·一步到位|搜完即得,效率翻倍! 🔍[立即开始搜索]
🤖初见选妃、搜索机器人 ·告别繁琐|资源分散、查找耗时? ·全网秒搜|全国资源实时匹配。 ·一步到位|搜完即得,效率翻倍! 🔍[立即开始搜索]
🎰 合肥观察 @kk3737373 ×【初见】全国包养 @chujian90 联名抽奖 📮 参与条件: 🪪 必须设置用户名 🎫 加入-合肥观察👀🥇-聊天推荐群 🎫 加入-合肥观察👀🥇-b哥朋友圈 🎫 加入-【初见 】全国包养中转站 🎫 加入-【初见】萝莉包养交流群 └ 🎟️ 发言数大于 30 条 🎁 奖品内容: 💰️ 52现金红包 × 6 💰️ 8折介绍费 × 4 💰️ 初见VIP会员 × 1 ⚠️ 抽奖说明: 🌊 炎夏繁杂,佳人难遇。2026年6月18日 - 9月1日,凭其他任意包养平台历史消费凭证,经核实,永久入会费直接减半(仅需 333 RMB)。 🍃老客引荐新友入席,新客完成首单后,新老双方各赠 1888 元抵扣券(直接抵扣下一单,不可叠加其他活动优惠)! 🛎中奖者请在48h内兑奖,折扣券可转让,现金红包请找 @palworld137 兑换 🛎中奖后退出群组和频道,炸号,不予兑奖 🛎一切解释权归兑奖人所有 …
❤1
🎉🎉🎉 开奖通知 🎉🎉🎉 🔖 防伪编号:H178712786909 🎰 猫少 @onehundredtravel ×【初见】全国包养 @chujian90 联名抽奖 ⚠️ 抽奖说明: 🌊 炎夏繁杂,佳人难遇。2026年6月18日 - 9月1日,凭其他任意包养平台历史消费凭证,经核实,永久入会费直接减半(仅需 333 RMB)。 🍃老客引荐新友入席,新客完成首单后,新老双方各赠 1888 元抵扣券(直接抵扣下一单,不可叠加其他活动优惠)! 🛎中奖者请在48h内兑奖,折扣券可转让,现金红包请找 @palworld137 兑换 🛎中奖后退出群组和频道,炸号,不予兑奖 🛎一切解释权归兑奖人所有 💁 参与情况:121达标 / 179报名 🔋 人品加成:117票 ⚡️⚡️⚡️ 🎅 联系领奖:初见Bao养【查档】 1. T 外套⚡️ 奖品:52现金红包 2. 给 特为⚡️⚡️⚡️ 奖品:52现金红包 3. 凌乘风⚡️ 奖品…
🤖初见选妃、搜索机器人 ·告别繁琐|资源分散、查找耗时? ·全网秒搜|全国资源实时匹配。 ·一步到位|搜完即得,效率翻倍! 🔍[立即开始搜索]
Showing the 12 most recent of 64 posts we hold for @chujian901. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Named by 8 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.
@YueLu_1 · 8,7495 postsLotteryBest精选推荐
@lotterybestnav · 143,4123 posts少萝/萝莉学园(中转站)
@lolischool1 · 7,2792 posts铲屎官的100次出击之旅
@onehundredtravel · 38,0672 postsTT的嫩妹档案
@taxiai5200 · 14,6942 postsLotteryBest抽奖导航
@lotterynav · 170,4731 post苏州硬了么认证老师榜
@SZnewls · 55,8531 post岳麓山·飨膳坊
@ylsxxxh0_0 · 12,6511 post
Names
Channels on the register whose handles appear in this channel's posts.
@chujianbaoyang9 · 21,0919 postsLotteryBest Bot
@LotteryBestBot · 97,7895 posts【初见】全国萝莉包养
@zhiboaishangheisi · 10,7055 postsLotteryBest抽奖导航
@lotterynav · 170,4734 posts合肥观察👀🥇-b哥朋友圈
@kk3737373 · 14,9062 posts铲屎官的100次出击之旅
@onehundredtravel · 38,0672 posts岳麓山·飨膳坊
@ylsxxxh0_0 · 12,6512 posts枫林晚🍁-「长沙」美食品鉴社
@CSC_Fenglinwan · 4,6361 post猫之国群聊
@csg100cj · 31,1571 post《西安狼友出击指南》
@Faiz_LoveGirls · 19,9351 post西安狼友出击情报站OvO
@FaizLove_Girls · 7,3661 post合肥观察👀🥇-聊天推荐群
@kk37373737 · 13,6971 post少萝/萝莉学园(中转站)
@lolischool1 · 7,2791 postTT的嫩妹档案
@taxiai5200 · 14,6941 post上海艺术展览会榜单
@yishuzanlanhui · 62,6721 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 5 September 2026 — this entry's latest reading, not the date you are reading this.
“【初见 】全国包养中转站” (@chujian901), 11,122 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/chujian901.
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.