Telegram RegisterThe public register of Telegram
Telegram profile photo for Find Blog👁发现博客

Channel

Find Blog👁发现博客

@FindBlog

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

13,943subscribers

-23 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-1001170164385
TypeChannel
Username@FindBlog
CreatedBetween 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live22 August 2026
Measurements held12
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/FindBlog

Growth

13,94313,97213,957.57 August 2026 — 13,966 subscribers7 August 2026 — 13,966 subscribers8 August 2026 — 13,963 subscribers8 August 2026 — 13,969 subscribers9 August 2026 — 13,972 subscribers11 August 2026 — 13,965 subscribers14 August 2026 — 13,961 subscribers15 August 2026 — 13,960 subscribers17 August 2026 — 13,955 subscribers20 August 2026 — 13,953 subscribers21 August 2026 — 13,952 subscribers22 August 2026 — 13,943 subscribers7 August 202622 August 2026
12 measurements spanning 16 days, net -23. 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 13,939–13,976 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 20:3313,943-9
21 Aug 2026, 10:1313,952-1
20 Aug 2026, 10:5813,953-2
17 Aug 2026, 10:3813,955-5
15 Aug 2026, 20:5113,960-1
14 Aug 2026, 13:5413,961-4
11 Aug 2026, 22:4213,965-7
9 Aug 2026, 23:3113,972+3
8 Aug 2026, 21:0013,969+6
8 Aug 2026, 00:0713,963-3
7 Aug 2026, 01:0013,966no change
7 Aug 2026, 00:5813,966first reading

Engagement

21 posts held, back to 10 February 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 29 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
18.0%
avg views ÷ 13,943 subscribers
Avg views / post
2,520
2 posts measured
Reaction rate
0.537%
reactions ÷ views · ER floor
Posts in window
2
of 21 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 14 August 2026
Posts held21 (10 February 202614 August 2026)
Views total5,030
Reactions total27
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken22 Aug 2026, 13:05 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.

Reaction mix

135 reactions across 18 posts, in 14 distinct kinds. The most used accounts for 48.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
6548.1%
😁2417.8%
🎉118.15%
😢96.67%
🥰85.93%
💔42.96%
🙈42.96%
🏆32.22%
😈21.48%
10.741%
🔥10.741%
🙏10.741%
🤩10.741%
🤬10.741%

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

Measured over the 21 most recent posts we hold, published 10 February 2026 to 14 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

14 Aug 2026, 10:43 UTC≈1,410 views11 reactionsread 22 August 2026
Forwarded from @c_res

许久没有见过这样力透纸背的文字了。 2006年8月2日上午,我在母亲房中无忧无虑的玩着45度俯视角射击游戏孤单枪手2,母亲穿上衣服和鞋子,站在门口对我说要去北京办点事情,我随意应承了一句,瞟了一眼门口,然后继续打击异形保护地球。四天后,我亲手给她拔下管子。 终于二十年了。 让我想起了《项脊轩志》: 庭有枇杷树,吾妻死之年所手植也,今已亭亭如盖矣 https://t.me/SteamVents/455

😢9😁1🙏1

29 Jul 2026, 09:20 UTC≈3,620 views16 reactionsread 22 August 2026
Photo

🇳🇿 新西兰保号神卡:One NZ giff giff 卡应该已经寄了,赶快换成新西兰 one卡体验! ✅ 0 月租:国内免费收短信,10 NZD/年低成本保号 ✅ 免实名:原生 +64 实体卡,隐私安全 ✅ 支持漫游:国内收发短信/接打电话,享原生 IP ✅ 海外必备:轻松注册 ChatGPT、TG、TikTok、X 🔗 购买:https://kaka-shops.com/r/seluki

8🙈4😁2😈2

16 Jul 2026, 14:03 UTC≈4,270 viewsread 22 August 2026

求推荐 Telegram 群组机器人,主要用于拦截广告。

12 Jul 2026, 04:10 UTC≈4,740 views8 reactionsread 22 August 2026

时雨: 博客聚合站已经多到可以给博客聚合站开一个博客聚合站聚合站。 谁有想法?搞一个。 频道:@FindBlog 群组:@FindBlog_Group

😁71

12 Jul 2026, 04:03 UTC≈4,350 views3 reactionsread 22 August 2026
Photo

Bo.ke 发现值得反复阅读的独立博客 博客大联盟由写作者自发组成。这里没有算法推荐,您可以认识每一个博客,读到他们最新的文章。 维护者: u.sb https://bo.ke/ 频道:@FindBlog 群组:@FindBlog_Group

21

24 May 2026, 09:58 UTC≈5,310 views5 reactionsread 22 August 2026

独立博客收录站的一些建议 频道:@FindBlog 群组:@FindBlog_Group

5

8 May 2026, 14:44 UTC≈5,130 views8 reactionsread 22 August 2026
Forwarded from @geeksharePhoto

#阅读 #网站 #博客 🌟 Blogosphere - 一个极简主义的博客内容聚合平台 网站将散落在世界各地、不受算法控制的个人博客、数字花园等汇聚于此。 内容则主要是科技向,细分了数字花园、个人生活、社会经济等十几个频道,有点类似 HN 📮投稿 📢频道 💬群聊 🔎索引

5😁2🔥1

2 May 2026, 00:29 UTC≈5,070 views2 reactionsread 22 August 2026

当一个人不再向外寻求认同,不再被那种「必须产出精品」的虚荣心所绑架时,博客就不再是一项任务,而是一种生活方式。 https://blog.solazy.me/20260429/ 频道:@FindBlog 群组:@FindBlog_Group

1🤬1

30 Apr 2026, 13:56 UTC≈4,570 views8 reactionsread 22 August 2026
Photo

如果你想发现更多的网站,可以看看这个,它收录了 4366 个个人网站,非常精美。 https://personalwebsites.org/ #website 频道:@FindBlog 群组:@FindBlog_Group

8

30 Apr 2026, 13:39 UTC≈3,780 views1 reactionsread 22 August 2026

有群友在评论区问:这些文章是怎么被发现的? 我觉得,博客圈是个圈,兜兜转转总会看到。 分享你发现博客、发现文章的方法吧。 #讨论 频道:@FindBlog 群组:@FindBlog_Group

1

17 Apr 2026, 07:39 UTC≈4,340 views10 reactionsread 22 August 2026

这个朋友文章写的太好了,原来医生的工作是这样的,对国内的一些医生多了几分敬佩。 https://blog.drpika.com/posts/2024-06-04/

10

17 Apr 2026, 07:35 UTC≈4,320 views6 reactionsread 22 August 2026
Photo

Monolith——高质感无服务器边缘博客系统 Monolith 是一套运行在 Cloudflare 全球边缘网络上的现代化无服务器博客系统。前后端完全解耦,通过适配器模式支持多种数据库与对象存储后端,无需运维,全球延迟 < 50ms。 📚 文档 · 🐛 Issue · ☁️ 在线预览 项目地址:https://monolith-client.pages.dev/ #Blog #Platform 频道:@FindBlog 群组:@FindBlog_Group

6

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

Citation-graph rank — 329,333 of 1,584,142entries 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.

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

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.

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

“Find Blog👁发现博客” (@FindBlog), 13,943 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/FindBlog.

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.