【妹子花名】:#睡不醒 【所在位置】:#济南 【修车费用】:#800p 【备 注】:#教室需要自备 必须带套,自己做自己聊 不要定金 不要车费 见面满意给钱 【凶器罩杯】:C 【身高体重】:166/103斤 【大概年纪】:22 【服务内容】:#蛇吻 #嫩妹 #大雷 #上门 #包夜 【联系方式】: @shuibuxing04 双向联系: @shuibuxing_bot 个人频道: https://t.me/shuibuxing040
❤2🔥1

Channel
@orzfc
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
25,749subscribers
-328 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002317397812 |
|---|---|
| Type | Channel |
| Username | @orzfc |
| Description | 交流群 @JNXSH 上榜联系: @chengcheng588 Hello @Telegram My channel has not violated the rules and policy of using Telegram. Please pay attention. @rove |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/orzfc |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 01:24 | 25,749 | -23 |
| 29 Aug 2026, 04:24 | 25,772 | +16 |
| 28 Aug 2026, 02:46 | 25,756 | +3 |
| 27 Aug 2026, 00:47 | 25,753 | -25 |
| 26 Aug 2026, 00:03 | 25,778 | -20 |
| 25 Aug 2026, 01:05 | 25,798 | -57 |
| 23 Aug 2026, 14:48 | 25,855 | -44 |
| 22 Aug 2026, 00:07 | 25,899 | +1 |
| 20 Aug 2026, 15:02 | 25,898 | -26 |
| 19 Aug 2026, 15:17 | 25,924 | -24 |
| 18 Aug 2026, 12:22 | 25,948 | -1 |
| 17 Aug 2026, 09:38 | 25,949 | -37 |
| 15 Aug 2026, 17:56 | 25,986 | +40 |
| 14 Aug 2026, 04:48 | 25,946 | -11 |
| 13 Aug 2026, 00:45 | 25,957 | -48 |
| 11 Aug 2026, 21:32 | 26,005 | -11 |
| 10 Aug 2026, 21:38 | 26,016 | +2 |
| 10 Aug 2026, 00:30 | 26,014 | -16 |
| 9 Aug 2026, 01:51 | 26,030 | -47 |
| 7 Aug 2026, 15:45 | 26,077 | first reading |
6 posts held, back to 4 June 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 50 pagesof 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.
| Window | Rolling 30 days · latest post in window 26 August 2026 |
|---|---|
| Posts held | 6 (4 June 2026 – 26 August 2026) |
| Views total | 1,140 |
| Reactions total | 3 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 30 Aug 2026, 20:42 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.
Lifetime counters from Telegram’s own channel header, read 30 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.
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.
45 reactions across 6 posts, in 5 distinct kinds. The most used accounts for 84.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 38 | 84.4% | |
| 🔥 | 3 | 6.67% | |
| 💯 | 2 | 4.44% | |
| 👍 | 1 | 2.22% | |
| 🥰 | 1 | 2.22% |
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 6 of the 6 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 45reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 4 June 2026 to 26 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.
【妹子花名】:#睡不醒 【所在位置】:#济南 【修车费用】:#800p 【备 注】:#教室需要自备 必须带套,自己做自己聊 不要定金 不要车费 见面满意给钱 【凶器罩杯】:C 【身高体重】:166/103斤 【大概年纪】:22 【服务内容】:#蛇吻 #嫩妹 #大雷 #上门 #包夜 【联系方式】: @shuibuxing04 双向联系: @shuibuxing_bot 个人频道: https://t.me/shuibuxing040
❤2🔥1
【妹子花名】:#优优 【所在位置】:#济南 【修车费用】:#800p 【备 注】:#教室需要自备 必须带套,自己做自己聊 不要定金 不要车费 见面满意给钱 【凶器罩杯】:C 【身高体重】:167/105斤 【大概年纪】:22 【服务内容】:#蛇吻 #嫩妹 #大雷 #上门 #包夜 【联系方式】: @youyou542 双向联系: @youyou555_bot 个人频道: https://t.me/youyou69690
❤7💯2
昵称: #屁桃 📊位置:💫济南💫 📣一节课: 600p 💫两节课:1200pp ✈️联系老师: @luluooio 🌐老师频道:https://t.me/luluxiaohuayuan1 🔈尽量注:#现金上课 📩联系老师说(艺术学院) 上榜·报告联系“@zhurenjqrbot” 📱📱📱📱📱📱📱 🏠聊天群
❤10🔥2
柒柒个人抓龙筋‼️ 营业时间:中午12.30-凌晨01.00 预约联系: @qiqizlj 双向联系: @qiqizlj001_bot 频道信息: https://t.me/qiqizlj01 服务项目: 泰国皇室抓龙筋、前列腺保养、宗筋护理、腰背臀SPA、龟责前高、延时脱敏、固本扶阳、前高开发、极致潮喷、柔氏丝足SM剧情演绎 #济南抓龙筋 #历下区 #脱敏延时 #sm调教
❤6
艺名:懒懒 年龄:21岁 胸器:36C 课室:历城区 有无教室:有 课时:600/p/40分钟 (口➕做) 800/p/60分钟(全套服务) 1400/pp/100分钟 全套服务,陪浴 无套口 调情 亲蛋蛋 亲咪咪 制服诱惑(自带) 激情爱爱 配合度高 听指挥 联系 @lanlandexiao 双向机器人 @lanlanxi_bot 频道链接: https://t.me/lanlanxiaowoo
❤9
💎💎工作室诚招代聊💎💎 来键盘、代聊 🙌小白可教学,简单易上手🙌 💖 无押金,无需垫资💖 🤑单成结算,一单一结i🤑 @SZBB_Only3
❤4👍1🥰1
Showing the 6 most recent of 6 posts we hold for @orzfc. 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 — 503,210 of 1,627,445entries 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.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“济南学生会公开榜🅢” (@orzfc), 25,749 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/orzfc.
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.