3 measurements spanning 6 days, net +73. 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 872–968 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
13 Aug 2026, 12:28
957
+74
7 Aug 2026, 06:53
883
-1
7 Aug 2026, 01:02
884
first reading
Engagement
12 posts held, back to 13 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
11.6%
avg views ÷ 957 subscribers
Avg views / post
111
8 posts measured
Reaction rate
4.49%
reactions ÷ views · ER floor
Posts in window
8
of 12 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 6 August 2026
Posts held
12 (13 July 2026 – 6 August 2026)
Views total
890
Reactions total
40
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
7 Aug 2026, 01:02 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
62 reactions across 12 posts, in 3 distinct kinds. The most used accounts for 79.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
49
79.0%
🔥
9
14.5%
👍
4
6.45%
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 12 of the 12 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 62reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 13 July 2026 to 6 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.
😎 온체인코리아 Night LIVE
Metaplex AMA Session
최근 한국 시장에 혜성처럼 등장한 Metaplex!
알고 보니 이전부터 엄청난 내공을 쌓아온 프로젝트였다?
자그마치 1,400만 유저, 10억 개의 온체인 자산을 만든 독보적 스케일.
Metaplex Foundation U.S.A. President인 맥과 함께 지금의 Metaplex가 그리고 있는 솔라나 온체인 자산의 미래를 짚어봅니다.
📅 8월 13일(목) 오후 9시
📍 온체인코리아 X Space(링크는 아래)
🎙 게스트: 맥(Mackenzie Hom)
- 메타플렉스 재단 미국 대표
🎤 호스트: 유리 × 메도
🎁 푸짐한 이벤트도 함께 진행됩니다.
💎 질문 선정자 보상
🟢사전질문 선정자: 1,500 $MPLX × 6명
🟢현장질문 선정자: 1,500 $MP…
😎 메타플렉스 런치풀
모든 프로젝트가 각기 다른데,
토큰 런칭 방식이 똑같을 필요가 있을까요?
이것이 바로 저희가 팀들이 각자의 런칭을 맞춤 설정할 수 있도록 더 많은 옵션들을 출시한 이유입니다
🔘TGE 일정 지연
🔘런치 풀 캡 설정
🔘직관적인 요약 툴
솔라나 생태계 내 ICM의 미래를 이끌어갈 발행자들을 위해 필수적인 툴들을 제공합니다
🔘TGE 일정 지연
발행자는 풀이 성공적으로 마무리되고 실제 거래가 시작되는 시점을 정확히 선택할 수 있습니다
세일이 끝나는 즉시 거래를 시작하려면 "즉시"를 선택하고, 세일 종료 후 1시간에서 최대 30일 사이로 TGE 일정을 잡으려면 "지연"을 선택하세요
🔘런치 풀 캡
팀이 모든 참여자에게 사전에 정의된 가격으로 진입할 수 있도록 보장해 줍니다
만약 런치 풀 캡에 도달할 경우, 초과된 예치금은 비…
😎 메타플렉스 KBW 2026 공식 스폰서
메타플렉스가 오는 KBW에 공식 스폰서로 참여하게 되었습니다!
이번 행사에서 메타플렉스의 파운더인 스티븐 헤스님께서 IMPACT 무대에 올라
"표준 토큰을 너머:기관 도입을 위한 규제 준수형 RWA 아키텍처 설계"
를 주제로 발표할 예정입니다
행사 기간 글로벌 기관 관계자나 국내 파트너,
개발자 커뮤니티와 함께 솔라나 기반 온체인 경제 확장 방향과 협력 방안을 논의할 계획입니다
올해 RWA와 스테이블코인을 중심으로 한 전통 금융의 온체인 전환이 주요 화두였던 만큼 솔라나 생태계의 주요 인프라를 담당한 메타플렉스에 많은 기대 부탁드립니다
➡️관련기사
Metaplex 한국 공지방 ㅣMetaplex 한국 채팅방
메타플렉스 커뮤니티 어워드 공지
메타플렉스 커뮤니티 어워드에 참여해주셔서 대단히 감사합니다!
많은분들이 콘텐츠를 작성해주셨는데
전부 확인해보고 직접 셀렉하였습니다!
🔘당첨자 [ 치킨 ]
@onnozea
@darksaverclosea
@soosung2
@Soeolinyoung
@asjsj0
🔘열성유저 [ 1,000 MPLX ]
@sixfour46
@Mineda2
@liberator09
치킨은 전부 발송되었습니다!
열성유저 세 분은 DM 확인 부탁드립니다!
앞으로도 메타플렉스에 많은 관심부탁드립니다!
Create, Launch, Grow
Metaplex 한국 공지방 ㅣMetaplex 한국 채팅방
😎 커뮤니티 어워드 이벤트 종료 임박!
업빗썸 상장 기념 이벤트가
금일 오후 9시 종료됩니다!
아직 참여하지 않으신분들은
공지사항 참고하시길 바랍니다!
Create, Launch, Grow
메타플렉스 코리아 커뮤니티에서 함께 배우고, 연결되고, 온체인에서 다음 기회를 만들어가요 🇰🇷
Metaplex 한국 공지방 ㅣMetaplex 한국 채팅방
😎 메타플렉스 6월 요약
🔘$MPLX가 업비트와 빗썸에 상장되며 한국 시장으로 확장했습니다
🔘CoreNFT 민팅 수는 전월 대비 142% 증가한 66만 개를 기록하며, 출시 이후 역대 최고 월간 수치를 달성했습니다
🔘월간 프로토콜 매출은 전월 대비 17% 증가한 $201K로, 26년 3월 이후 가장 높은 수준을 기록했습니다
구성
토큰 메타데이터: $117K ( 58% )
Core : $69K ( 34% )
제네시스 및 기타 : $15K ( 8% )
5월 프로토콜 매출 중 $100K는 DAO를 위한 3.6M $MPLX 바이백에 사용되었습니다
이는 총 공급량의 0.4% 유통 공급량의 0.7%에 해당됩니다
매달 전월 프로토콜 매출의 50%가 DAO를 위한 $MPLX 바이백에 배정됩니다
➖
에이전트 프로필 출시
6월 10일, 메타플렉스는 에이전…
😎 메타플렉스 6월 요약
🔘5월 프로토콜 수익 중 $100K 가 DAO를 위한 3.6M $MPLX 바이백에 사용
총 곱급량의 0.4% / 유통 공급량의 0.7%에 해당
🔘6월 프로토콜 수익은 $201K 기록
매달 프로토콜 수익의 50%는 DAO를 위한 $MPLX 바이백에 배정됩니다
따라서 6월 수익의 50%는 7월 $MPLX 바이백 재원으로 사용될 예정입니다
메타플렉스 DAO는 탈중앙화 거버넌스, 프로토콜 개발, 생태계 확장의 허브로 계속 성장하고 있습니다
앞으로도 프로토콜 활동과 생태계 소식에 대한 월간 업데이트를 기대해 주세요
➡️ 실시간 지표
➡️원글
Metaplex 한국 공지방 ㅣMetaplex 한국 채팅방
😎 메타플렉스 알아보기
메타플렉스에 대해 코백남님께서
유튜브영상을 만들어주셨습니다!
아직 메타플렉스가 어떤 프로젝트인지 모르시다면
꼭 한 번 시청해보시는걸 추천드립니다!
➡️영상보기
Create, Launch, Grow
메타플렉스 코리아 커뮤니티에서 함께 배우고, 연결되고, 온체인에서 다음 기회를 만들어가요 🇰🇷
Metaplex 한국 공지방 ㅣMetaplex 한국 채팅방
❤5
Showing the 12 most recent of 12 posts we hold for @Metaplexkorea. 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 — 942,390 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 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.
Handles this channel named that no longer answer
Dead references
1
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
1
vacant every time we have ever looked
@Metaplexkorea named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@asjsj0 named in 1 post, 8 August 2026 – 8 August 2026
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.
“Metaplex 한국 공지방” (@Metaplexkorea), 957 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/Metaplexkorea.
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.