File, posted without a caption

Channel
懒猫的频道
@lanmaoshare
On this record: Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
19,176subscribers
+203 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001238881646 |
|---|---|
| Type | Channel |
| Username | @lanmaoshare |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 9 September 2026 |
| On Telegram | t.me/lanmaoshare |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 07:57 | 19,176 | +8 |
| 6 Sept 2026, 01:41 | 19,168 | +9 |
| 3 Sept 2026, 21:58 | 19,159 | +32 |
| 2 Sept 2026, 09:52 | 19,127 | +37 |
| 1 Sept 2026, 08:29 | 19,090 | -5 |
| 31 Aug 2026, 07:35 | 19,095 | +3 |
| 30 Aug 2026, 07:06 | 19,092 | -2 |
| 29 Aug 2026, 08:17 | 19,094 | -3 |
| 28 Aug 2026, 11:34 | 19,097 | +5 |
| 27 Aug 2026, 09:42 | 19,092 | +4 |
| 25 Aug 2026, 12:02 | 19,088 | +13 |
| 24 Aug 2026, 09:19 | 19,075 | -3 |
| 22 Aug 2026, 19:52 | 19,078 | -1 |
| 21 Aug 2026, 12:28 | 19,079 | +4 |
| 20 Aug 2026, 12:06 | 19,075 | +4 |
| 19 Aug 2026, 10:03 | 19,071 | +2 |
| 18 Aug 2026, 11:37 | 19,069 | +9 |
| 17 Aug 2026, 10:17 | 19,060 | +14 |
| 15 Aug 2026, 20:44 | 19,046 | +14 |
| 14 Aug 2026, 08:37 | 19,032 | first reading |
Engagement
15 posts held, back to 29 May 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 55 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 22.9%
- avg views ÷ 19,176 subscribers
- Avg views / post
- 4,390
- 2 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 2
- of 15 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.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 15 (29 May 2026 – 2 September 2026) |
| Views total | 8,770 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 01:27 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.
Recent posts
修复8.0.78进入其它插件页面不隐藏底栏问题 由于修改了包,越狱用户需要先写在旧版重新安装。
无根
修复应用程序列表不显示应用问题
隐根版本新增了关闭弹出层和返回桌面
【主题盒子】3.0.3更新公告 修复低于8.0.60版本闪退问题 修复顶栏图标不变色问题 映射问小微图标为xiaowei_filled
File, posted without a caption
【主题盒子】3.0.2更新公告 修复几处细节问题 修复主题配置无暗黑模式失效问题 对模拟液态玻璃进行了一定的优化
File, posted without a caption
【主题盒子】上新的主题只能在主题盒子3.0以上版本显示,旧版本无法下载最新的主题。插件能发布说明经过测试已经没有问题了,如果出现闪退大概率是插件冲突了,希望可以说一下是和哪个插件冲突,开了什么功能冲突,不要丢下一句更新之后闪退就没有下文了。
Relaxin 公测版现已发布 https://owngoal.dev/relaxin/ 如果你需要证书: https://pay.ldxp.cn/shop/huami 首次使用: 给联网权限后重新打开软件越狱
【主题盒子】3.0.1更新公告 重构大量代码 优化主题加载速度 新增毛玻璃和液态玻璃渲染 *由于重构了代码,当前版本可能会存在少量bug。 *首次安装启动不显示主题请前往更换主题更换一下。 *降级回2.x版本需要重新下载一次主题。 *液态玻璃功能存在一些Bug。
Showing the 12 most recent of 15 posts we hold for @lanmaoshare. 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 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.
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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@iosrxwy · 99,252
Telegram ranks this channel #20 of 28 here — alongside 27 others — read 31 August 2026
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“懒猫的频道” (@lanmaoshare), 19,176 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/lanmaoshare.
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.