Telegram RegisterThe public register of Telegram
Telegram profile photo for 若兮🌸 频道

Channel

若兮🌸 频道

@xiqina520

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

427subscribers

-1,044 since we began measuring on 24 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004298995102
TypeChannel
Username@xiqina520
Created7 June 2026measured — dated from the channel’s first post
First recorded24 August 2026
Last confirmed live18 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/xiqina520

Growth

4278,1444,285.524 August 2026 — 1,471 subscribers25 August 2026 — 1,567 subscribers27 August 2026 — 2,525 subscribers31 August 2026 — 8,144 subscribers4 September 2026 — 6,404 subscribers9 September 2026 — 532 subscribers18 September 2026 — 427 subscribers24 August 202618 September 2026
7 measurements spanning 24 days, net -1,044. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 04:37427-105
9 Sept 2026, 18:20532-5,872
4 Sept 2026, 01:216,404-1,740
31 Aug 2026, 06:468,144+5,619
27 Aug 2026, 21:322,525+958
25 Aug 2026, 05:191,567+96
24 Aug 2026, 17:151,471first reading

Engagement

9 posts held, back to 7 June 2026the 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.

ERR · 30 days
48.7%
avg views ÷ 427 subscribers
Avg views / post
208
7 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
8
of 9 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 24 August 2026
Posts held9 (7 June 202624 August 2026)
Views total1,457
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken24 Aug 2026, 17:15 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
13s
Average length
13s

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.

Recent posts

24 Aug 2026, 13:52 UTC52 viewsread 24 August 2026

杭州颜值嫩妹报告 https://t.me/hzyanzhi 【综合评价】:‼️下面只留一个 #超级好评 【妹子花名】:若兮 【联系方式】:@ruoxi4522 【妹子年龄】:26 【验证留名】:yyds @hyybbbb (需加分请留姓名及id) 【验证时间】:8月23日 【大概位置】:拱墅 【修车水费】:600p 【高端服务】:有的打✅ ① 舌吻 ✅ ② 69舔逼 ③ 情绪价值 ✅ ④ 毒龙 【人照相似】:人照相似9分,颜值气质 【身材皮肤】:身高腿长,纹身大小,皮肤观感手感 【凶器罩杯】:胸型大小,乳头颜色 大小,手感 【湿度紧度】:户型颜色,水量紧度,周围毛量 【环境细节】:交通 停车是否方便,房间环境是否整洁 【个人卫生】:是否抽烟,有无漱口水 浴巾,事前事后有无清洗 【时间管理】:开课是否准时,排课是否宽松,课时是否做完 【服务总结】:服务是否到位,有无少做,过程有无机车 【流程小

24 Aug 2026, 10:17 UTC124 viewsread 24 August 2026
Photo

🎰 【杭州大学】认证教师·若兮 @ruoxi4522 上榜福利 📮 抽奖条件: 🎫 加入-若兮🌸 频道 🎫 加入-若兮群组 🎫 加入-【杭州大学】新人老师榜单 🎫 加入-杭州大学 🎟️ 要求活动期间群内发言数 1 🎁 奖品内容: 若兮 @ruoxi4522 1p半价优惠券 × 1 若兮 @ruoxi4522 100优惠券 × 3 若兮 @ruoxi4522 赞助·52红包 × 1 💡 活动说明: 开奖前请勿退出频道与群组,以免机器人开奖时无法统计。 开奖后,口令红包找老师兑奖。优惠券不可转让,有效期五天。 📅 开奖日期:(UTC+8) 2026年08月29日 18时00分00秒

24 Aug 2026, 04:30 UTC152 viewsread 24 August 2026
Photo

开课了、宝宝们可以提前预约、莞式服务,胸推毒龙、温柔听话、

23 Aug 2026, 12:13 UTC288 viewsread 24 August 2026

【杭州修车协会】 群里大量现金红包、白嫖福利、水群奖励等你来拿! 协会: https://t.me/hzxc666666 收录杭州优质老师,高质量狼友 每月现金出击补贴!白嫖应有尽有!

23 Aug 2026, 12:12 UTC274 viewsread 24 August 2026
Photo

🎰 杭州修车协会福利【若兮】 📮 参与条件: 🪪 必须设置用户名 🎫 加入-若兮🌸 频道 🎫 加入-若兮群组 🎫 加入-杭州修车协会抽奖公告 🎫 加入-杭州修车协会 └ 🎟️ 发言数大于 10 条 🎁 奖品内容: 💰️ 单P6折优惠券 × 1 ⚠️ 抽奖说明: 刷屏、灌水、纯表情、复制粘贴、无意义对话、撤回内容等,一律视为无效发言,不计入统计!请用心交流。 开奖如果不在群内,一律视为自动放弃,奖品将会回到奖池继续抽奖活动最终解释权归本群管理团队所有。 中奖的人员核实元宝数量,开奖即查,达到200扣除后再联系老师约定约时间(在抽奖期间提交过本群老师原价出击报告可以不扣除直接兑奖),元宝不够奖品作废回到兑换区供其他狼友兑换 24小时内预约时间,3天内出击,过时自动作废 中奖需本人出击,转让需经过老师同意并与管理协商,不得私下买卖,出现买卖双方都将被踢出群里!出击完成后提交报告(提交报告额外奖励元宝)如若不提交,将永久拉黑!

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

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

“若兮🌸 频道” (@xiqina520), 427 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/xiqina520.

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.