Channel
@feilis530
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
502subscribers
+11 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003764623028 |
|---|---|
| Type | Channel |
| Username | @feilis530 |
| Created | Between 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/feilis530 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 05:29 | 502 | +11 |
| 8 Aug 2026, 08:50 | 491 | no change |
| 8 Aug 2026, 08:01 | 491 | first reading |
20 posts held, back to 6 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 1 pageof Telegram’s post history, 20 posts per page.
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 5 of 12 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 20 (6 July 2026 – 6 August 2026) |
| Views total | 9,374 |
| Reactions total | 5 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 08:01 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.
7 reactions across 6 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 7 | 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 9 of the 20 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 7reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 6 July 2026 to 6 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.
杭州开课小助理分享： 颜值：9 身材：9 服务：9.5 时间：8.5 联系方式：@feilis531 细节：复刷，隔了两月有余，果断预约前往。推开门，她正在化妆，许久未见，却像从未分开过。我刚在沙发坐下，她的腿就很自然地搁到我膝上，像女友一般开始闲聊。然后开始洗漱，很贴心的帮忙调水温，洗完帮忙擦拭，递上撕开的漱口水。进入房间开始第一次，嫩妹起手，下面一柱擎天，带伞女上开始，老师直接坐了上来，全程骚话不断，奈何第一次状态不佳，体力不支。歇息时间，抱着老师温存，一边刷抖音，老师还唱起来小曲儿，第二次cjs起手，先在外面蹭蹭，老师一直催插进去，直接猛插进去，瞬间感觉下面被温暖包裹，还能听见水声，然后疯狂啪啪啪，老师一直喊用力，再深一点，最后鏖战15分钟，在老师的娇喘中出货，床单都湿了一块。看来得回去得锻炼一下，不然都满足不了老师。 该报告使用 @hzkaikebot 生成，如有任何疑问请联系 @fugezhiyou
杭州御女阁出击报告模板: https://t.me/hangzhou_777 评分标准： 6分-差 7分-及格 8分-良好 9分-优秀 10分-极品 【老师艺名】：#菲丽丝 【联系方式】：@feilis531 【老师芳邻】：29左右 【验证留名】：半闲 【出击时间】：8月5日 【大概位置】：滨江 【出击水费】：工兵p 【高端服务】：有的打✅ ① 舌吻 ✅️ ② 69舔逼 ✅️ ③ 情绪价值 ✅️ ④ 毒龙 ✅️毒龙一绝 【人照相似】：人照相似8.5，气质姐 【身高身材】：身高165，屁股和身上有，皮肤白 【凶器罩杯】：胸型b略微下催，乳头颜色黑， 【湿度紧度】：比比户型一线天鲍🐠，湿度很多水，周围少量毛 【环境细节】：交通/出入方便，房间整洁 【个人卫生】：抽烟，有漱口水/牙刷/浴巾，事前事后有清洗 【时间管理】：开课准时，排课宽松，课时做完 【服务总结】：服务到位，无少…
❤1
如果真心换不了真心，那就速度换声音
❤2
开课，可约
还有位置可约
❤1
开课了
【私聊】 @feilis531 【位置】#滨江区 【课费】800/p-45分钟，1500/pp-90分钟 【分类】#御姐 【高级服务】 #舌吻 #69互舔 #毒龙 #陪浴 #AB面 #深喉.过水 Tips：
❤1
还有位置，可以预约
开课了，可以预约了
谢谢哥哥肯定
开课预约了
开课了，可以预约了
Showing the 12 most recent of 20 posts we hold for @feilis530. 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 — 1,390,767 of 1,480,944entries 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.
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.
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.
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.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“菲丽丝学院” (@feilis530), 502 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/feilis530.
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.