Telegram RegisterThe public register of Telegram

Channel

HAT's Public Channel | 🫪

@hatschannel

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

2,471subscribers

+141 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002673733731
TypeChannel
Username@hatschannel
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/hatschannel

Growth

2,3302,4712,400.56 August 2026 — 2,330 subscribers6 August 2026 — 2,330 subscribers6 August 2026 — 2,345 subscribers10 August 2026 — 2,423 subscribers13 August 2026 — 2,471 subscribers6 August 202613 August 2026
5 measurements spanning 7 days, net +141. 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 2,309–2,492 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 01:042,471+48
10 Aug 2026, 00:022,423+78
6 Aug 2026, 15:302,345+15
6 Aug 2026, 05:502,330no change
6 Aug 2026, 04:182,330first reading

Engagement

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

ERR · 30 days
28.3%
avg views ÷ 2,471 subscribers
Avg views / post
700
36 posts measured
Reaction rate
1.15%
reactions ÷ views · ER floor
Posts in window
37
of 37 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. It is computed over the 24 of 36 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held37 (5 August 20267 August 2026)
Views total25,204
Reactions total220
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 16:39 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

136 reactions across 13 posts, in 12 distinct kinds. The most used accounts for 27.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤯3727.2%
💩1712.5%
🥰1410.3%
🤬139.56%
118.09%
🔥107.35%
👻96.62%
👍75.15%
🤡75.15%
🤓64.41%
🤨32.21%
🐳21.47%

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

Measured over the 37 most recent posts we hold, published 5 August 2026 to 7 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

7 Aug 2026, 11:40 UTC408 views15 reactionsread 7 August 2026
Forwarded from @NekoMirraPhoto

截胡这一块 神人gitee还不修 https://gitee.com/organizations/new

10🤡5

7 Aug 2026, 11:22 UTC471 views9 reactionsread 7 August 2026
Forwarded from @limisayPhoto

害我笑了一下。

👻9

7 Aug 2026, 08:19 UTC≈1,890 views14 reactionsread 7 August 2026
Photo

牛逼!OpenCode Go 里的 V4 Flash 限时 2x usage https://t.me/hatschannel/5565 全部x2! 意味着你呼哧呼哧蹬了 6B 发现还没用完 $5 Plan 的 5h limit (

🤯14

7 Aug 2026, 07:46 UTC678 viewsread 7 August 2026
Photo

ds 用的 statuspage 服务商甚至用的还是 dnspod 免费版??

7 Aug 2026, 07:32 UTC613 views2 reactionsread 7 August 2026
Photo

应该是把上游服务商的整个阿里云北京 NLB IP 到外网全给 d 到黑洞了,什么仇什么怨 现在整个 ds statuspage 只有阿里云内网是通的

🤯2

7 Aug 2026, 07:29 UTC764 views15 reactionsread 7 August 2026
Photo

速报: DeepSeek Statuspage 爆炸了,甚至把整个 flashcat 服务商托管的所有 statuspage 都给炸穿了 https://status.deepseek.com/ 15:38 Update: 换了个新 IP, 开始恢复 https://t.me/hatschannel/5588

🤯13🐳2

7 Aug 2026, 06:50 UTC515 viewsread 7 August 2026
Forwarded from @Laoself

https://notashelf.dev/posts/taste-is-all-thats-left

7 Aug 2026, 06:49 UTC600 views7 reactionsread 7 August 2026
Photo

帮分享一下群友写的 Kimi Code 小插件, 支持在 statusline 中展示当前会话实时的 TTFT / TPS / cache hit rate / Kimi For Coding 用量信息 确实想要这个功能很久了 https://github.com/arsfy/kimi-code-statusbar-plugin

👍7

7 Aug 2026, 06:43 UTC710 views11 reactionsread 7 August 2026

我看不懂,但我大受震撼.gif https://fixupx.com/noa_onlyonly/status/2085363886317072410

🤯8🤨3

7 Aug 2026, 06:15 UTC520 views8 reactionsread 7 August 2026
Forwarded from @limisayPhoto

https://x.com/Andr3jH/status/2085368832403587542

🤓6🤡2

Showing the 12 most recent of 37 posts we hold for @hatschannel. 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 — 11,150 of 1,350,102entries 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.

2.5次元日常 🍉
@acgdaily · 16,200
10 posts
Puddin在TG上看到了啥
@puddin_share · 936
5 posts
重力倒转
@i365je94e4ixc56a · 53
4 posts
Laoself 🫈
@Laoself · 2,982
4 posts
厘米碎碎念
@limisay · 3,281
4 posts
今天abc看了啥🤔
@abcthoughts · 6,789
3 posts
Cherr panic
@cherr_panic · 122
3 posts
tg生态观察 ٭✡️⚝✹✸✶✷✴️✧⊛🔯❂⍣≛✨🇻🇳
@tgsucks · 2,023
3 posts
是芙莉莲
@iReallyHateTheWorld · 67
2 posts
Steven’s Diary | 为0700.hk卖命中
@stv_diary · 448
2 posts
未題名の四月と海
@acherkrau · 2,512
1 post
Ac-Wiki | 真·青年大学习
@AcWiki · 3,513
1 post
アキラの小冊子
@ak1ra_ch · 147
1 post
Akasha Terminal: dev🍃
@AkashaTerminal · 914
1 post
某小学生的破事水日常
@anankkew · 871
1 post
安结Tech
@AncheysTechTips · 11
1 post
Ayame no Negoto
@ayame_no_negoto · 6
1 post
三向月的日常
@bakamarch7th · 416
1 post
我喜欢你
@bakaPD · 9,754
1 post
酷安 ℂ𝕠𝕠𝕝𝕒𝕡𝕜 ℂ𝕙𝕒𝕟𝕟𝕖𝕝
@CoolapkChannel · 3,194
1 post
DoriyaNetwork Log
@DoriyaNetStatus · 443
1 post
逃逸极限
@gc00_escapingzone · 141
1 post
红星中学
@Hong_Xing_High_School · 60
1 post
mhmrdd
@mhm72dd · 6,095
1 post
布告栏上的贴纸
@noticeboardthings · 2,324
1 post
<NullPointerException> 二周目
@NullPointerA · 890
1 post
NY 的实况转播器
@ny_ceiver · 74
1 post
柒柒的鱼罐头
@nya_qiqi · 227
1 post
💊🌿🥟(
@pill_grass_dumpling_brac · 416
1 post
QRZ 的摸鱼日常
@qrzbing · 64
1 post
Sky of Beginning
@raspberry_stories · 67
1 post
kaze channel
@rclogs · 86
1 post
Re: Daily of Jin
@re_dailyofjin · 68
1 post
生蚝的浅海漂流站
@shenghuo2_news · 13
1 post
Channel of ssr
@ssrdaily · 509
1 post
​::1
@subss62 · 755
1 post
733 Tech Tips (Public)
@tech_tips_733 · 304
1 post
碎碎念的 Thregren
@Thregren_daily · 13
1 post
TimeAxis
@TimeAxis · 784
1 post
娱乐迷因
@yulemiyin42 · 4
1 post
zrj766的频道
@zrj96 · 16,768
1 post

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

“HAT's Public Channel | 🫪” (@hatschannel), 2,471 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/hatschannel.

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.