麻烦各位教职工多吹点水,少刷点开课表情,删了一天表情包了🥱😴😂
🤡3🌚2🤣2
Signed TGBot

Channel
@glgkb
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry
21,194subscribers
+5,025 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002136182077 |
|---|---|
| Type | Channel |
| Usernames | @gl_qHF @glgkb |
| Description | 桂林花间坊 @gl_HJF 桂林报告榜 @gl_bgb 上榜及报告 @glhwq_bot |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 3 September 2026 |
| Measurements held | 37 |
| Confirmed unchanged | 1 time, most recently 3 September 2026 |
| On Telegram | t.me/glgkb |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Sept 2026, 10:26 | 21,194 | +100 |
| 2 Sept 2026, 20:16 | 21,094 | +81 |
| 2 Sept 2026, 07:04 | 21,013 | -11 |
| 1 Sept 2026, 21:14 | 21,024 | +146 |
| 1 Sept 2026, 05:45 | 20,878 | +6 |
| 1 Sept 2026, 00:14 | 20,872 | +27 |
| 31 Aug 2026, 04:07 | 20,845 | -16 |
| 30 Aug 2026, 20:14 | 20,861 | +95 |
| 30 Aug 2026, 03:16 | 20,766 | +10 |
| 29 Aug 2026, 18:58 | 20,756 | +2 |
| 29 Aug 2026, 06:13 | 20,754 | +10 |
| 28 Aug 2026, 17:17 | 20,744 | +35 |
| 28 Aug 2026, 05:52 | 20,709 | +11 |
| 27 Aug 2026, 15:39 | 20,698 | +9 |
| 27 Aug 2026, 07:58 | 20,689 | +109 |
| 26 Aug 2026, 16:23 | 20,580 | +167 |
| 26 Aug 2026, 05:42 | 20,413 | +426 |
| 25 Aug 2026, 15:56 | 19,987 | -13 |
| 25 Aug 2026, 03:47 | 20,000 | +8 |
| 24 Aug 2026, 13:35 | 19,992 | first reading |
25 posts held, back to 7 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 42 pages of 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 21 of 25 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 | 25 (7 August 2026 – 3 September 2026) |
| Views total | 68,810 |
| Reactions total | 54 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 16:59 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 3 September 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 3 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.
54 reactions across 17 posts, in 8 distinct kinds. The most used accounts for 64.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 35 | 64.8% | |
| 💩 | 7 | 13.0% | |
| 🤡 | 3 | 5.56% | |
| 🥰 | 3 | 5.56% | |
| 🌚 | 2 | 3.70% | |
| 🤣 | 2 | 3.70% | |
| 👏 | 1 | 1.85% | |
| 🔥 | 1 | 1.85% |
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 21 of the 25 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 54 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 25 most recent posts we hold, published 7 August 2026 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.
麻烦各位教职工多吹点水,少刷点开课表情,删了一天表情包了🥱😴😂
🤡3🌚2🤣2
Signed TGBot
🙋♀ 昵称: #甜甜 📍 坐标: #秀峰区 🎟 银两: 5p 10pp ☎️ 连系: @Dw98jiayou 📮 报告: 戳一戳投稿 💌 提示: 戳一戳不失恋 该老师不得收取客户订金 正常收取外出外卖配送费 🔎 课表报告查看评论区
❤1
Signed 花无缺
台风天的到来,使得9月初的桂林倒有些入秋感。 我想,还是发条信息提醒大伙儿穿好衣服吧。 一千块的长袖、外套脱下来,难免不会着凉。保护好自己,别感冒。这也是对别人的一种保护。
Signed TGBot
✨ 命运揭晓时刻 ✨ 小可回归有礼 开奖了 抽奖人数:34,抽奖号数:130 1. 楚天阔【祝福18次】 中得:约会折扣券🎟¥100 2. 飞一样的感觉【祝福1次】 中得:约会折扣券🎟¥100 3. 牛汉三(吃喝嫖赌)【祝福1次】 中得:约会折扣券🎟¥100 有效期:周日 9/6 23.59 小可妹妹:@sooi10
❤2
Signed Saber
🙋♀ 昵称: #小琪 📍 坐标: #秀峰区 🎟 银两: 6p 12pp ☎️ 连系: @xiaoqibb1 📮 报告: 戳一戳投稿 💌 提示: 戳一戳不失恋 🔎 课表报告查看评论区 📝 给 TA 留下评价
❤1
Signed 花无缺
全国同城导航(持续更新) 华北: 天津|石家庄|唐山|邯郸|邢台|保定|沧州|廊坊|衡水|任丘河间 华东: 常州|扬州|临沂 华中: 郑州|开封|新乡|安阳|鹤壁 华南: 佛山|福州|厦门|桂林 | 东莞 | 深圳 | 海南 西南: 贵阳|遵义|绵阳|乐山|眉山|昆明 西北: 西安|兰州|内蒙古|西宁 东北: 沈阳|大连|长春 工具: TG创作者中心 中文修车助手 点击申请加入
❤4
Signed 末日制裁
✨ 命运揭晓时刻 ✨ 珊珊工兵 开奖了 抽奖人数:23,抽奖号数:71 1. Shgolf7777【祝福1次】 中得:400P 2. 风雨【祝福15次】 中得:400P 3. 欧尼克雷斯【祝福5次】 中得:400P 因老师开学,剩余2位工兵空置。
❤2
Signed Saber
🙋♀ 昵称: #珊珊 📍 坐标: #秀峰区 🎟 银两: 6p 12pp ☎️ 连系: @aa6588888 📮 报告: 戳一戳投稿 💌 提示: 戳一戳不失恋 该老师不得收取客户订金 正常收取外出外卖配送费 已对该老师年龄核实满18 🔎 课表报告查看评论区
❤1
Signed 桂林广播台
Photo, posted without a caption
Signed Saber
🙋♀ 昵称: #妍可 📍 坐标: #秀峰区 🎟 银两: 6p 12pp ☎️ 连系: @yanke8866 📮 报告: 戳一戳投稿 💌 提示: 戳一戳不失恋 花语:兜兜转转又回桂 身材颜值不错,熊小点 🔎 课表报告查看评论区
❤5
Signed 花无缺
若某些老师频道发有盲盒类消息,请退频拉黑🥵
❤1
Signed TGBot
Photo, posted without a caption
❤2
Signed Saber
Showing the 12 most recent of 25 posts we hold for @glgkb. 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.
@glgkb edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Named by 3 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.
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.
@glgkb named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 3 September 2026 — this entry's latest reading, not the date you are reading this.
“桂林群花坊” (@glgkb), 21,194 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/glgkb.
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.