3 measurements spanning 3 days, net +2. 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 102–104 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
9 Aug 2026, 09:31
104
no change
7 Aug 2026, 19:26
104
+2
6 Aug 2026, 21:04
102
first reading
Engagement
4 posts held, back to 15 July 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 · 30 days
255.1%
avg views ÷ 104 subscribers
Avg views / post
265
3 posts measured
Reaction rate
6.41%
reactions ÷ views · ER floor
Posts in window
3
of 4 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
Window
Rolling 30 days · latest post in window 5 August 2026
Posts held
4 (15 July 2026 – 5 August 2026)
Views total
796
Reactions total
51
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
9 Aug 2026, 09:31 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
3
Links
3
Lifetime counters from Telegram’s own channel header, read 9 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Reaction mix
51 reactions across 3 posts, in 3 distinct kinds. The most used accounts for 76.5% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
39
76.5%
custom 6246855307251688495
11
21.6%
👍
1
1.96%
Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it isTelegram’s.
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 3 of the 4 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 51reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 4 most recent posts we hold, published 15 July 2026 to 5 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.
🫥 BAY 블록체인 weekly｜7/26~8/1
한 주간의 블록체인 주요 흐름을 BAY가 선별해 전해드립니다.
🔜 BAY 뉴스트래킹 사이트에서 전체 내용 확인하기
1⃣ AI 또 탈출했다… 오픈AI GPT 이어 앤트로픽 ‘클로드’도 실제 기업 해킹
• 요약: 보안 평가 환경의 설정 오류로 클로드 모델 3종이 실제 인터넷에 접속해 기업 3곳의 시스템에 무단으로 접근한 사실이 확인됐음.
• 인사이트: 고성능 AI의 보안 평가는 모델 자체뿐 아니라 샌드박스 격리, 네트워크 차단, 실시간 로그 감시까지 함께 검증해야 함.
2⃣ 콜드카드 지갑 취약점 악용…비트코인 546억 원 25분 만에 유출
• 요약: 콜드카드 펌웨어가 하드웨어 난수 생성기를 건너뛰어 예측 가능한 값으로 개인키를 생성한 취약점이 악용되면서 약 594 BTC가 25분 만에 유출됐음…
🫥 BAY 블록체인 weekly｜7/19~7/25
한 주간의 블록체인 주요 흐름을 BAY가 선별해 전해드립니다.
➡️ BAY 뉴스트래킹 사이트에서 전체 내용 확인하기
1️⃣ 6시간 새 3건 뚫린 브리지…3500만달러 유출, 신뢰 위기 커졌다
• 요약: 6시간 동안 3개 브리지·프로토콜에서 3,500만달러 이상이 유출됐으며, 관리자 키 탈취와 권한 관리 실패가 공통 원인으로 지목되었음.
• 인사이트: 스마트계약 코드뿐 아니라 관리자 권한과 업그레이드 키 관리도 핵심 보안 영역으로 다뤄야 함.
2️⃣ [네이버·두나무 M&A①] 공정위 현미경 심사 들어가나…‘시장지배력 전이’ 집중 추적
• 요약: 공정위가 네이버의 검색·포털·페이 영향력이 업비트의 이용자 확보와 시장점유율 확대로 이어질 가능성을 검토 중인 것으로 알려졌음.
• 인사이트: 플랫…
🎉 BAY(Blockchain at Yonsei)가 공식 텔레그램 채널을 오픈했습니다.
2017년부터 이어져 온 연세대학교 기반 국내 최초 블록체인 학회 BAY의 연구와 인사이트를 이제 공식 텔레그램 채널에서 만나보실 수 있습니다.
BAY 텔레그램에서는 다음과 같은 콘텐츠를 정기적으로 공유합니다.
🔹학회 연구 및 프로젝트 성과
🔹블록체인·Web3 생태계를 심층 분석한 리서치 아티클
🔹국내외 주요 업계 뉴스 및 핵심 이슈 큐레이션
🔹BAY의 활동 소식과 행사·협업 업데이트
단순한 뉴스 전달을 넘어, 빠르게 변화하는 블록체인 산업을 이해하는 데 필요한 관점과 맥락을 함께 제공하겠습니다. BAY의 연구와 네트워크가 학회 내부를 넘어 더 넓은 생태계와 연결될 수 있도록, 공식 텔레그램 채널에 함께해 주세요!❤️
🔗 TG | X | Linked…
Showing the 4 most recent of 4 posts we hold for @blockchain_at_yonsei. 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 — 191,788 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 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.
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 August 2026 — this
entry's latest reading, not the date you are reading this.
“BAY(Blockchain at Yonsei)” (@blockchain_at_yonsei), 104 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/blockchain_at_yonsei.
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.
