5 measurements spanning 7 days, net +71. 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,372–2,465 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
13 Aug 2026, 04:15
2,454
+48
9 Aug 2026, 18:13
2,406
+21
6 Aug 2026, 19:21
2,385
+2
6 Aug 2026, 05:47
2,383
no change
6 Aug 2026, 02:08
2,383
first reading
Engagement
29 posts held, back to 3 August 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 2 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
15.2%
avg views ÷ 2,454 subscribers
Avg views / post
373
29 posts measured
Reaction rate
0.456%
reactions ÷ views · ER floor
Posts in window
29
of 29 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 9 of 29 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 7 August 2026
Posts held
29 (3 August 2026 – 7 August 2026)
Views total
10,806
Reactions total
14
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
7 Aug 2026, 16:36 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
6 reactions across 5 posts, in 4 distinct kinds. The most used accounts for 33.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👌
2
33.3%
😘
2
33.3%
❤
1
16.7%
👍
1
16.7%
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 9 of the 29 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 14reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 29 most recent posts we hold, published 3 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.
MANCER 출시 이후 2배 이상 상승
StonkBroker가 인큐베이팅한 스폐셜 프로젝트 MANCER가 출시이후 2배이상 상승했습니다.
Mancer는 로빈후드체인의 주피터가 되기위한 야망을 가진 비수탁형 DEX로, StonkBroker와 함께 온체인 금융 생태계를 확장해 나가는 핵심 파트너 입니다.
향후 NFT 보유자는 활성화를 통해 플랫폼에서 발생하는 수수료의 일부를 분배받으며,
활성화에 사용 된 $MANCER의 50%는 소각됩니다.
이 출시로 $MANCER 는 $DERP에 이어 두번째로 $STONKBROKER 유동성페어를 구성하게 되었습니다.
오늘 Unvault AMA에서 Mancer와 같은 스폐셜 프로젝트를 추가로 인큐베이팅하고있으며,
3~4개의 프로젝트가 파이프라인에 올라와 있다는 소식도 공개 되었습니다.
앞으로 생태계에 …
Unvault AMA 리캡
오늘 AMA는 거의 2시간동안 진행돼서 너무 길어서 진짜 짧게 압축했습니다.
- 파트너 컬렉션에 Claynosaurz 추가 되었습니다.
- 페이즈 1 민팅은 컬렉션마다 정해진 할당내에서 경쟁으로 민팅
- 페이즈 1 에서 솔드아웃되면 페이즈 2 가 안올수도 있음
- 기존 NFT들도 자체 AMM을 구현할 수 있음
- Mancer 처럼 StonkBrokers 가 인큐베이팅하는 스폐셜 프로젝트 파이프라인에 이미 다른 프로젝트들도 추가되고 있음
- Bulls on the Block 시리즈 컬렉션들을 하나의 바스켓처럼 묶는 Indexed AMM 을 준비중
- 민팅일은 현재 비공개지만, 최종 감사 및 테스트가 진행중인 상태로 곧 민팅 날짜가 발표될 수도 있음
Mancer 민팅이 1시간 연기 됐는데 조금 지연되고 있다고 합니다.
CA 랑 NFT 민팅 같이 되는데 OTC에서 화리가 최고 $1,000 거래된 점과 Stonk Broker 가 인큐베이팅하는 프로젝트이기 때문에
기대가 되네요.
아래 트윗에서 올라오는 공식 링크만 신뢰 하세요!
https://x.com/MichaelHirsch
Momo 토큰이 나왔네요.
🔘CA : 0x664E9D73db2A3514F6B437137dE4779977a06E8
작동방식은 StonkBroker 와 Unvault 작동방식과 매우 유사합니다.
각 NFT = 117,000 $MOMO 의 가치로 움직이며 스왑이 가능합니다.
이에따라 발생하는 수수료는 홀더들에게 제공되는 보상으로 지급됩니다.
- 포켓몬, 원피스 팩
- 디지털 콜렉터블
- $MOMO 또는 스테이블 토큰 등
해당 소식이 나오고 순간 0.1 eth 까지 올랐네요.
자세한 건 아티클을 참고하시고 보유하고 계셨던 분들은 축하드립니다!
🌐 아티클 링크
😀 Fuego, 민팅 페이지
오후10시부터 PWL (GTD) 민팅이 시작됩니다.
민팅비도 비싸고, 그걸 아는지 지갑당 5개씩 민팅하게끔 해뒀는데, 민팅되는 속도 보면서 진행하면 될 것 같습니다.
추가로 시즌1 트레이딩 대회(총 10eth+@ 상금)에서 fuego 홀더는 직접 트레이딩을 하지 않고, 다른 트레이더에게 위임해서 그 실적을 나에게 가져와서 대회에 참여하는 것도 가능하네요. (nft당 1명 선택 가능)
자세한건 관련 글의 이미지참고하세요!
✖️ 트윗
🌐 민팅 페이지
Signed Nimdal
Showing the 12 most recent of 29 posts we hold for @alpha_duo. 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 — 53,908 of 1,336,469entries 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 3 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.
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 13 August 2026 — this
entry's latest reading, not the date you are reading this.
“알파를 듀오 공지방” (@alpha_duo), 2,454 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/alpha_duo.
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.