4 measurements spanning 6 days, net -17. 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 5,553–5,576 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
12 Aug 2026, 10:15
5,556
-10
9 Aug 2026, 05:05
5,566
-7
6 Aug 2026, 13:00
5,573
no change
6 Aug 2026, 11:19
5,573
first reading
Engagement
19 posts held, back to 4 November 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 8 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
6.86%
avg views ÷ 5,556 subscribers
Avg views / post
381
1 post measured
Reaction rate
0.525%
reactions ÷ views · ER floor
Posts in window
1
of 19 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
19 (4 November 2025 – 5 August 2026)
Views total
381
Reactions total
2
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
12 Aug 2026, 04:07 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
80 reactions across 17 posts, in 3 distinct kinds. The most used accounts for 52.5% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
42
52.5%
👍
27
33.8%
🔥
11
13.8%
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 17 of the 19 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 80reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 4 November 2025 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.
🟢 개인적으로 생각하는 업비트의 원화상장 빈도 증가
✅ 왜 자주 상장하나?
1️⃣ 네이버 합병
-두나무와 네이버의 주식교환 일정은 연말로 연기(주총 11월 19일, 효력발생일 12월 31일)
-두나무는 3분기~4분기 중 주식교환 일정에 앞서 업비트의 주요 지표를 최대한 끌어올려 체급을 올릴 필요가 있음
2️⃣ 디지털자산 기본법 시행
-최근 정부부처는 디지털자산기본법 시행에 대해 강경한 기조로 움직이고 있음
-디지털자산기본법에서 주로 언급 되는 내용 중 상장심사강화가 손에 꼽히고 있음
-규제 불확실성 + 상장절차 강화 전 거래량 안나오는 올드페어 종목을 대신할 신규페어 상장 노리기
3️⃣ 과세 시행
-마찬가지로 정부는 세제개편안을 통해 27년 1월부 가상자산 과세 시행을 거의 못박은 상태
-이미 거래량이 크게 줄어든 상황이지…
😆빗썸 출금 수수료 정책 개악
- 시행일: 2026. 05. 11(월) 오전 10:00 ~
- 대상 종목 : 전일 종가 원화 환산액 기준 거래소 내 예치 잔고 100억원 미만 종목과 이용자 보호 및 거래 안정화를 위해 필요하다고 판단되는 종목
- 출금 한도 : 예치 잔고의 0.1% (수량 기준, 가상자산 1인 1일 출금한도)
- 출금 수수료: 출금 금액의 1% (상대적으로 유동성이 부족하여 관리가 필요한 종목에 한해)
제대로 안 읽어봤었는데, 사실상 빗썸에 상장되어 있는 거의 모든 알트 대상 출금 수수료 1% 적용, 일일한도 0.1% 적용이네요
빗썸 똥갭따리는 이제 안녕😒
- 일부 가상자산 출금 정책 변경 안내
- 출금 수수료 정률 적용 종목
❗️[AllRound X 채용공고]❗️
2026년 과세 전까지, 시장의 기회를 함께 잡을 동료를 찾습니다.
형식적인 자소서는 보지 않습니다.
오직 당신의 '투자 인사이트'만 봅니다.
1️⃣주요 업무 :
- 국내외 크립토 트렌드/메타 심층 분석
- 자체 투자 전략 수립 및 매매 아이디어 제안
- 해외 리서치 번역 및 요약
2️⃣근무 환경 :
- 서울 강남구 도곡동 근무
- 10:00~17:00
- 수요일 재택
- 주차 가능
- 트레이딩/리서치 몰입을 위한 장비 지원
3️⃣기간 :
- 1/31까지 모집, 12/31까지 근무
- 이후 근무 기간 연장 가능 (AllRound 합류)
4️⃣상세링크 : 모집요강
직전 포워딩 글은 지우도록 하겠습니다.
약간 이슈가 있는 분이셨네요 . . .
좀 더 디테일하게 살펴보지 않고 가벼운 마음으로 포워딩한 점 죄송합니다.
👍4❤1
Signed 카일
Showing the 12 most recent of 19 posts we hold for @Info_Arbitrage. 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 — 756,975 of 1,160,990entries 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.
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 12 August 2026 — this
entry's latest reading, not the date you are reading this.
“카일의 아비트라지 정보공유방” (@Info_Arbitrage), 5,556 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Info_Arbitrage.
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.
