Telegram RegisterThe public register of Telegram
Telegram profile photo for LIHAI 分享

Channel

LIHAI 分享

@lihaiba

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Cite this entry

39,135subscribers

+540 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001351552963
TypeChannel
Username@lihaiba
Description一个分享频道,进频道先看置顶,不定时不定量更新,希望推送内容对你能有帮助 有问题或投稿找资源私聊 bot @lihaibaBot 助力: https://t.me/boost/lihaiba LIHAI的收藏夹 @lihai GitHub的存档 @iGitHub 优质网盘资源分享存档 @lihaiCloud 转载原档请注明出处 @lihaiba 频道资源均收集于网上各大博客论坛资源网站等,对资源源以及真实性一概不知,如不慎对您的权利造成了伤害,请立即与我们 BOT 联系进行处理
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live18 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/lihaiba

Topic

Software piracy — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 September 2026 and assigned it the closest of 31 fixed categories, at 85% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

38,59539,13538,8656 August 2026 — 38,595 subscribers6 August 2026 — 38,596 subscribers7 August 2026 — 38,602 subscribers8 August 2026 — 38,636 subscribers9 August 2026 — 38,659 subscribers10 August 2026 — 38,702 subscribers11 August 2026 — 38,729 subscribers12 August 2026 — 38,751 subscribers14 August 2026 — 38,770 subscribers15 August 2026 — 38,801 subscribers16 August 2026 — 38,821 subscribers17 August 2026 — 38,823 subscribers18 August 2026 — 38,830 subscribers19 August 2026 — 38,845 subscribers20 August 2026 — 38,861 subscribers21 August 2026 — 38,868 subscribers23 August 2026 — 38,873 subscribers24 August 2026 — 38,895 subscribers25 August 2026 — 38,901 subscribers27 August 2026 — 38,913 subscribers28 August 2026 — 38,924 subscribers29 August 2026 — 38,929 subscribers30 August 2026 — 38,949 subscribers31 August 2026 — 38,963 subscribers1 September 2026 — 38,964 subscribers2 September 2026 — 38,971 subscribers3 September 2026 — 38,980 subscribers5 September 2026 — 38,993 subscribers8 September 2026 — 39,032 subscribers11 September 2026 — 39,048 subscribers13 September 2026 — 39,060 subscribers14 September 2026 — 39,102 subscribers16 September 2026 — 39,124 subscribers18 September 2026 — 39,135 subscribers6 August 202618 September 2026
34 measurements spanning 44 days, net +540. 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 38,514–39,216 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
18 Sept 2026, 22:1739,135+11
16 Sept 2026, 17:0139,124+22
14 Sept 2026, 16:5739,102+42
13 Sept 2026, 03:4139,060+12
11 Sept 2026, 05:5739,048+16
8 Sept 2026, 11:1739,032+39
5 Sept 2026, 05:1838,993+13
3 Sept 2026, 10:0238,980+9
2 Sept 2026, 03:5438,971+7
1 Sept 2026, 04:3738,964+1
31 Aug 2026, 05:4738,963+14
30 Aug 2026, 02:2438,949+20
29 Aug 2026, 04:4338,929+5
28 Aug 2026, 02:3438,924+11
27 Aug 2026, 00:3738,913+12
25 Aug 2026, 21:1538,901+6
24 Aug 2026, 21:0438,895+22
23 Aug 2026, 07:4638,873+5
21 Aug 2026, 16:4538,868+7
20 Aug 2026, 17:0738,861first reading

Engagement

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

ERR · 30 days
19.2%
avg views ÷ 39,135 subscribers
Avg views / post
7,510
7 posts measured
Reaction rate
0.099%
reactions ÷ views · ER floor
Posts in window
7
of 32 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 15 September 2026
Posts held32 (26 May 202615 September 2026)
Views total52,570
Reactions total52
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken23 Sept 2026, 12: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.

What this channel posts

Photos
1,640
Videos
114
Links
2,210

Lifetime counters from Telegram’s own channel header, read 23 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
12s
Average length
12s

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

326 reactions across 30 posts, in 8 distinct kinds. The most used accounts for 54.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
17654.0%
👍7021.5%
💩4614.1%
🤔133.99%
😁72.15%
😱61.84%
🫡61.84%
💊20.613%

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

Measured over the 32 most recent posts we hold, published 26 May 2026 to 15 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.

Telegram Stars

Stars received
3
across the posts below
Posts paid on
1
of 32 we hold a reading for · 3%
Most on one post
3
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @lihaiba. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 32 most recent posts we hold for this entry, published 26 May 2026 to 15 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

15 Sept 2026, 06:11 UTC≈4,570 views15 reactionsread 23 September 2026
Video

27.0 这扩图有意思啊 标签:#AI #Apple

👍64💩3😁2

14 Sept 2026, 06:27 UTC≈5,230 views5 reactionsread 23 September 2026
Photo

哪版 — iPhone 地区版本比较 该网站可以详细比较iPhone不同地区的版本的 价格、双卡与功能差异 https://naban.barrybarrywu.cn/ 标签:#网站 #Apple

4😁1

9 Sept 2026, 18:44 UTC≈7,540 views1 reactionsread 23 September 2026
Photo

iPhone 18 Pro 系列官网 SIM 卡介绍显示 国行版本:双卡 两个 nano-SIM 卡,或一个 nano-SIM 卡和一个 eSIM,或激活两个 eSIM 港澳版本:双卡 可同时使用两张 eSIM;或一张 nano-SIM 及一张 eSIM 标签:#Apple

1

7 Sept 2026, 11:00 UTC≈7,640 views1 reactionsread 23 September 2026

#互推 【小说分享】日更100 刺猬猫菠萝包起点飞卢小说有声书txt分享 【苹果限免】 App Store 限免应用 & ... 【资源分享】小声逼逼 【网络分享】书墨资源 【影视分享】douView × 银幕🐷🐷🍿 【软件资讯】iOS限免&降价 【软件分享】大聪明 破解软件分享频道 【影视分享】观影视界[GyWEB] 【网络分享】LIHAI 分享 Powered by @Summer_Clear_Sky_Bot

1

7 Sept 2026, 08:56 UTC≈7,010 views2 reactionsread 23 September 2026
Photo

▎👨‍💻 折叠隐藏Mac菜单栏图标:Thaw Bartender 平替,开源、支持中文界面 GitHub 标签:#Mac #开源 #软件 ✈️合作/投稿 频道群组 频道标签

💊2

2 Sept 2026, 09:45 UTC≈8,880 views13 reactionsread 23 September 2026
Photo

▎🎵 Fastpotify:轻量 Spotify 客户端 开源、跨 Windows/macOS/Linux,通常占用约 100~250MB 内存,支持本地播放、Spotify Connect、播客和歌单管理,最有趣的是还能套用 Winamp 皮肤和 MilkDrop 音乐可视化 另外,Spotify 除了低价区合租外可以去海鲜市场🐟,有印度区UPI一次性年费支付自己账号的 Standard 套餐售卖,成本₹799约合人民币57,售卖价格大约为 ¥98-108 之间,商家靠谱程度自行分辨 官网 GitHub 标签:#音乐 #开源 #软件 ✈️合作/投稿 频道群组 频道标签

13

27 Aug 2026, 14:25 UTC≈11,700 views15 reactionsread 23 September 2026
File

我的女友景甜 疑似 Claude code 暗广 https://x.com/justinsuntron/status/2092932777612390850 标签:#瓜 #PDF

🤔114

20 Aug 2026, 10:55 UTC≈14,400 views13 reactionsread 23 September 2026

▎🙁 活动继续,通过学生认证后免费领一年 Google One AI(Gemini) 高级计划 美国学生:送一年 19.99 美元/月的 Google AI Pro 其他学生:送一年 4.99 美元/月的 Google AI Plus(未验证) https://one.google.com/ai-student 标签:#AI #羊毛

👍8😁32

13 Aug 2026, 14:50 UTC≈15,900 views11 reactionsread 23 September 2026
Photo

微信小程序搜索:影厅指南 CINEMA GUIDE 可以更加直观查询全国IMAX,杜比音效等特效影厅,以及查看银幕尺寸、放映技术、影院地址 标签:#科普 #影视 #安利 ✈️合作/投稿 频道群组 频道标签

11

10 Aug 2026, 11:00 UTC≈13,600 views5 reactionsread 23 September 2026

#互推 【转存&引流】媒体托管机器人 【网络分享】纸鸢分享社-破解软件|游戏分享 【资源分享】小声逼逼 【网络分享】互联网研习社(破解软件/游戏 | 实测) 【网络分享】LIHAI 分享 【科技分享】Fᴜғᴜ の Cʜᴀɴɴᴇʟ 【视频分享】B站充电视频分享 【小说分享】Lemaned的宝藏书屋(轻小说书库) 【软件分享】TK集库 Powered by @Summer_Clear_Sky_Bot

4💩1

6 Aug 2026, 11:16 UTC≈14,700 views7 reactionsread 23 September 2026
Photo

迁移网易云/汽水/QQ音乐歌单 至 Apple/Youtube/Spotify Music 1. 粘贴原歌单链接 2. 获取并复制歌曲列表 3. 粘贴列表文本导入目标平台:Spotify官方/TuneMyMusic 官网:https://music.unmeta.cn/ 标签:#开源 #音乐 #网站 #GitHub ✈️合作/投稿 频道群组 频道标签

7

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

Posts edited after publishing

@lihaiba edited 4 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.

First edit seen
14 August 2026
Most recent edit
2 September 2026

Forward network

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

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

“LIHAI 分享” (@lihaiba), 39,135 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/lihaiba.

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.