Telegram RegisterThe public register of Telegram
Telegram profile photo for 凉心の小窝

Channel

凉心の小窝

@Lx_hub

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

7,142subscribers

+308 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002067871539
TypeChannel
Username@Lx_hub
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live6 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 6 September 2026
On Telegramt.me/Lx_hub

Growth

6,8347,1426,9887 August 2026 — 6,834 subscribers7 August 2026 — 6,834 subscribers8 August 2026 — 6,837 subscribers10 August 2026 — 6,834 subscribers14 August 2026 — 6,855 subscribers17 August 2026 — 6,912 subscribers21 August 2026 — 6,946 subscribers24 August 2026 — 7,094 subscribers27 August 2026 — 7,103 subscribers30 August 2026 — 7,114 subscribers2 September 2026 — 7,129 subscribers6 September 2026 — 7,142 subscribers7 August 20266 September 2026
12 measurements spanning 30 days, net +308. 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”. The vertical axis spans 6,788–7,188 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Sept 2026, 22:157,142+13
2 Sept 2026, 05:037,129+15
30 Aug 2026, 15:347,114+11
27 Aug 2026, 16:467,103+9
24 Aug 2026, 18:447,094+148
21 Aug 2026, 01:376,946+34
17 Aug 2026, 18:456,912+57
14 Aug 2026, 09:586,855+21
10 Aug 2026, 23:336,834-3
8 Aug 2026, 06:026,837+3
7 Aug 2026, 15:306,834no change
7 Aug 2026, 15:226,834first reading

Engagement

18 posts held, back to 14 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 12 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
38.3%
avg views ÷ 7,142 subscribers
Avg views / post
2,740
6 posts measured
Reaction rate
0.189%
reactions ÷ views · ER floor
Posts in window
6
of 18 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 19 August 2026
Posts held18 (14 July 202619 August 2026)
Views total16,424
Reactions total31
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken20 Aug 2026, 03:47 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
11s
Average length
11s

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.

Reaction mix

114 reactions across 15 posts, in 6 distinct kinds. The most used accounts for 43.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
5043.9%
👍2320.2%
😁1614.0%
🤯1311.4%
🤡119.65%
🔥10.877%

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 16 of the 18 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 114 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 14 July 2026 to 19 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.

Recent posts

19 Aug 2026, 12:15 UTC861 views8 reactionsread 20 August 2026
Photo

下午没事想起来还有个软件 设计之初只是为了方便管理qB 重构了一下整体底层设计 把原来的结构重新拆成了可扩展的模块 以方便后续接入Tr/Aria2 TrackLuxe 2.0 敬请期待吧~

👍7🤡1

17 Aug 2026, 08:44 UTC883 views0 reactionsread 20 August 2026
Forwarded from @qiqipluginsharesFile

复制作品链接 无水印保存图片/视频 隐藏右侧元素 纯净全屏模式 基于快手版本14.7.20

17 Aug 2026, 00:46 UTC≈1,860 views14 reactionsread 20 August 2026

到底要上多少年的班,才能平静的面对周一

🤯131

16 Aug 2026, 13:24 UTC≈7,020 views2 reactionsread 20 August 2026
File

复制视频链接 无水印下载视频/图片 调整右侧布局 基于14.7.20版本 Via: @QiQi777iii

2

13 Aug 2026, 03:16 UTC≈3,080 views2 reactionsread 20 August 2026

https://b23.tv/lOPuHev 那没事了,整半天原来是老偷家了 阿西西的日常 => 偷东西的日常

2

11 Aug 2026, 06:03 UTC≈2,720 views5 reactionsread 20 August 2026
File

▎桌隐 v1.0.0 顾名思义 隐藏Windows桌面图标用的 原Windows自带的功能 在右键菜单点击隐藏比较繁琐 于是桌隐就诞生了 启用后双击桌面空白区域 切换桌面图标显示/隐藏

5

4 Aug 2026, 00:51 UTC≈4,390 viewsread 20 August 2026
Video

一个“国民”级别的软件为什么能有这么多Bug🤷‍♂️

30 Jul 2026, 11:23 UTC≈4,890 views6 reactionsread 20 August 2026
Photo

GG: 拿着吧,俺从中国人那里抢来的

4😁2

27 Jul 2026, 06:32 UTC≈17,400 views13 reactionsread 20 August 2026
File

▎NetSpeed v2.1.0 ▎新增功能 重启作用域 文字颜色自定义 预设色板 / RGB 调节 / 色值输入 ▎优化 整体配色跟随系统动态取色 设置项图标统一配色风格 使用提示按模块状态动态显示 部分UI交互逻辑优化 ▎修复 横屏下自定义位置乱跑 ▎要求 支持 API 102 的 LSPosed 102只用到了热重载 向下兼容了101但是我没设备测试 有需要的可以自行测试 仅在Pixel10ProXL/Android17测试

13

25 Jul 2026, 10:57 UTC≈3,490 views5 reactionsread 20 August 2026
Photo

晚点再发个版本 不出意外的话这个版本后就可以告一段落了🤔

👍5

24 Jul 2026, 14:46 UTC≈3,290 views12 reactionsread 20 August 2026
Photo

当你负重前行时 总有狗东西拿着你的成果在享福😂 欢迎点点举报 https://m.tb.cn/h.8WZEZlb 钱多的没地方花的也可以去下几单

🤡102

Showing the 12 most recent of 18 posts we hold for @Lx_hub. 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 2 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.

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

“凉心の小窝” (@Lx_hub), 7,142 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/Lx_hub.

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.