Channel
@sannsaku
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
608subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001585551640 |
|---|---|
| Type | Channel |
| Username | @sannsaku |
| Created | Between 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/sannsaku |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 20:43 | 608 | -1 |
| 8 Aug 2026, 03:04 | 609 | no change |
| 7 Aug 2026, 23:23 | 609 | first reading |
16 posts held, back to 11 March 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 1 pageof Telegram’s post history, 20 posts per page.
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 17 July 2026 |
|---|---|
| Posts held | 16 (11 March 2026 – 17 July 2026) |
| Views total | 244 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 03:04 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.
22 reactions across 7 posts, in 5 distinct kinds. The most used accounts for 54.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 12 | 54.5% | |
| 🎉 | 3 | 13.6% | |
| 👍 | 3 | 13.6% | |
| 🤯 | 3 | 13.6% | |
| 🤔 | 1 | 4.55% |
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 8 of the 16 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 22reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 11 March 2026 to 17 July 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.
美国2020年7月起实施的《香港正常化总统行政令》（第13936号）已到期终止。中国商务部发言人7月17日表示，在中美马德里经贸会谈期间，美方作出了今年不延续该行政令、使之在2026年7月14日自然失效等承诺。中方对美方终止行政令表示赞赏。 该行政令曾使得香港适用与对中国大陆相同的出口管制，要求香港产品标识原产地为中国，授权制裁起草实施《香港国安法》破坏香港民主自治与侵害人权的官员等。 （路透社）
各类有氧运动的利弊 跑步习惯养成了之后感觉应该把划船机习惯重新加回来，没必要全是跑步。 #wellness #youtube
https://www.xiaoyuzhoufm.com/episode/6a37b1bb75ba9e0c5336bc8a
https://youtu.be/tAMNPeo7AG0?si=Zm5PaHJupCD_RY17
13 years ago: https://www.youtube.com/watch?v=3kke7qAGWFQ
https://www.reddit.com/r/LAMetro/s/TGpWtHdvAI
美国空军两架 C-17 （08-8204、05-5140）在 5 月 1 日和 5 月 2 日分别降落北京国际机场，为特朗普访华运送先遣物资，后续将还会有两架。
🤔1
大家可能还记得几年在欧洲被抓在美国受审的国安局官员，Bloomberg最近出了一个播客系列详细讲这件事，毕竟他可能是美国抓住的最高级别国安局官员。 没想到作为一个国安局员工，他竟然每天记日记，工作生活内容全混在一起，还有南京爬山、参加音乐节、扫墓、赌钱、外遇的细节，工作上则有开了什么会见了什么人。这保密工作也实在是太草台了…… https://podcasts.apple.com/us/podcast/2-the-spys-diary/id1802010242?i=1000749917256
🤯3
I gave every train in New York an instrument https://www.trainjazz.com/
谷歌之前在 Pixel 10 系列上使用 Quick Share 兼容了 AirDrop 双向互传文件，但当时很多人并没有搞清楚谷歌是如何破解苹果 AirDrop 协议的。 现在谷歌直接自己发了一篇技术 blog，解释了其中使用的哪些小技巧以及未来的发展计划。 整个技术栈使用 Rust 编写，从编译期就消除了内存破坏漏洞。同时，谷歌自己做了第三方渗透测试报告，确保这个漏洞不会被其他有心之人利用。 但目前 Quick Share 与 AirDrop 互传目前只支持 AirDrop 的十分钟内对所有人开放模式，也就是 iPhone 用户在 iOS 16.2 之后被苹果"降级"过的那个临时开放窗口。仅联系人模式没有打通。 Dan Boneh （斯坦福密码学教授，业界最有公信力的安全学者之一）的结论是："鼓励 Google 和 Apple 在这方面更多合作"。 这算是把球踢回给苹果：现在如果苹果继续拒绝合作（比如不开放 Con…
👍3
https://worksinprogress.co/issue/why-japan-has-such-good-railways/
🎉1
Google Store JP 上线了日本地区限定的异彩蓝。 「異彩（Isai）」一词寄托了“每个人可以不同、彼此尊重”的温柔世界的祈愿。这是 Google Pixel 史上首次采用源自日语的配色名称。 https://store.google.com/jp/magazine/google-pixel-10a-isai-blue
❤1🎉1
Showing the 12 most recent of 16 posts we hold for @sannsaku. 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 — 1,135,049 of 1,480,688entries 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.
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.
Named by 1 registered channel — 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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“散步中” (@sannsaku), 608 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/sannsaku.
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.