10 Aug 2026, 01:41 UTC6 viewsread 10 August 2026
Photo
⭐️单月会员走一个
Channel
雨季の副频道
@yujinb0906
On this record: Growth · Engagement · Posts · Citations · Cite this entry
1,173subscribers
+29 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1003922341393 |
|---|---|
| Type | Channel |
| Username | @yujinb0906 |
| Created | Between 1 April 2026 and 31 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/yujinb0906 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 17:37 | 1,173 | +36 |
| 10 Aug 2026, 10:20 | 1,137 | -7 |
| 10 Aug 2026, 02:32 | 1,144 | first reading |
Engagement
6 posts held, back to 9 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 1 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.654%
- avg views ÷ 1,173 subscribers
- Avg views / post
- 7.7
- 6 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 6
- of 6 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.
| Window | Rolling 30 days · latest post in window 10 August 2026 |
|---|---|
| Posts held | 6 (9 August 2026 – 10 August 2026) |
| Views total | 46 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Aug 2026, 02:32 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.
Recent posts
10 Aug 2026, 01:01 UTC7 viewsread 10 August 2026
‼️‼️TG万能搜索群‼️‼️ ☄️全网最牛逼的万能搜索群☄️ ☄️各种爆火资源都可以搜索☄️ 🧸都是独一无二的搜索结果🧒 🤡频道主都推荐这个☄️ 🤯超多不限量火爆资源应有尽有🤝 🌈无延迟 无重复 无卡顿 无没结果🤙 https://t.me/sosoaqu https://t.me/sosoaqu https://t.me/sosoaqu
9 Aug 2026, 22:54 UTC6 viewsread 10 August 2026
Forwarded from @fhyj0906Photo
🎰 雨季 📮 抽奖条件: 🎫 加入-雨季の窝 🎫 加入-雨季思路库and反馈 🎫 加入-雨季の副频道 🎁 奖品内容: 雨季 × 88 vx同群百分百 vx群隔百分百 快手wwg QQwwg 抖音概率禁言 抖音高概率禁止关注 小红书秒疑似 小红书秒笔记 小红书批量封禁 定制思路 低价🥬徒 侵权隔空高概 美v 美快 美q 港v 电话轰炸 支付宝口令反 支付宝码反 支付宝一体py ks人工定制 ks邮箱定制 38.88🧧 × 88 💡 活动说明: 雨季 😊 参与人数: 开奖需要参与人数到达 188
9 Aug 2026, 20:03 UTC3 viewsread 10 August 2026
Forwarded from @iianhon
📱你还在担心你的频道没时间管理吗 只需要一个管理位我就可以帮你管理频道 想找公益封号思路的频道？想找可以开户查档的频道？想找优质号商的频道？想找经常送福利可以白嫖各种账号 靓号 nft 红包的频道？ ✅脸红集团专业互推/团队运营 🔼高效上人速度/免费引流 各平台账号源头卡网😃 https://new.cayfpay.cn/shop/UZXDL3NC 点击下方链接一键加入高质量频道合集 互推交流群 @douqie 😃😃😃😃😃😃😃😃😃
9 Aug 2026, 17:06 UTC9 viewsread 10 August 2026
Forwarded from @Solacevow
月会员代开 3.7u无限开 联系 @penghuajian
9 Aug 2026, 12:41 UTC15 viewsread 10 August 2026
Forwarded from @NiHaoXioDi
收款码代收『暑假零风险项目』 😀😃😀😃😀😃年底提A6 新手小白看过来 ☺️😃😃😃😃😃😃😃😃😃😃 做单流程：接单→结账😳😳【一单一结】 （白资换赌资，仅需两步👇轻松兑换秒到账） 做单详情： ⚠️2️⃣5️⃣回款5️⃣8️⃣（教学单） 😙5️⃣8️⃣回款8️⃣8️⃣（尝试单） 😙1️⃣2️⃣8️⃣回款2️⃣8️⃣8️⃣（老人单） 👋3️⃣2️⃣8️⃣回款4️⃣8️⃣8️⃣（老人单） 👍5️⃣8️⃣8️⃣回款1️⃣2️⃣8️⃣8️⃣ 😄😃😄😃：📏📖 小白极速上车，0️⃣风险，账户冻结3️⃣倍赔付 😀全网只有【晚安】能做到秒结账！！！ ☺️☺️☺️☺️☺️☺️☺️☺️☺️☺️😊😊😊 ✅已上押公群，诚信保障！！！！！！ 🥰 在线客服 @WAKOUI 🔠双向联系 @WAKFHBOT 📱业务频道 https://t.me/NiHaoXioDi
Showing the 6 most recent of 6 posts we hold for @yujinb0906. 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.
Citation-graph rank
Citation-graph rank — 1,052,419 of 1,478,351entries 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.
Forward network
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 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.
Names
Channels on the register whose handles appear in this channel's posts.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“雨季の副频道” (@yujinb0906), 1,173 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/yujinb0906.
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.