Channel
@cryptowangbei
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
7,382subscribers
-18 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002175162477 |
|---|---|
| Type | Channel |
| Username | @cryptowangbei |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/cryptowangbei |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 01:15 | 7,382 | -8 |
| 9 Aug 2026, 20:37 | 7,390 | -7 |
| 6 Aug 2026, 23:42 | 7,397 | -3 |
| 6 Aug 2026, 03:07 | 7,400 | no change |
| 6 Aug 2026, 02:03 | 7,400 | first reading |
45 posts held, back to 4 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 11 pagesof 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. It is computed over the 21 of 45 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 12 August 2026 |
|---|---|
| Posts held | 45 (4 August 2026 – 12 August 2026) |
| Views total | 12,712 |
| Reactions total | 25 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 17: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.
20 reactions across 16 posts, in 3 distinct kinds. The most used accounts for 90.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 18 | 90.0% | |
| ⚡ | 1 | 5.00% | |
| 🐳 | 1 | 5.00% |
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 21 of the 45 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 25reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 45 most recent posts we hold, published 4 August 2026 to 12 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.
📈 삼성·SK하이닉스, ‘200조+α’ 주주환원 가능성 반도체 슈퍼사이클로 현금이 크게 늘면서 양사 모두 대규모 주주환원책 검토 중 - 삼성전자: 100~125조원 수준 거론 - SK하이닉스: 수십조~최대 100조원 가능성 - 특별배당 + 자사주 매입·소각 방식 유력 - 이르면 3분기 내 구체적인 방향 발표 전망 참고) 아직 규모와 일정은 확정 전 출처
❤1
업비트(Upbit) 공지 [거래] 프롬(PROM) KRW, USDT 마켓 디지털 자산 추가 2026-08-12 11:11:41
🚨 업계인 대상 Linkedin 면접 해킹 주의 1. 업계 경력자에게 링크드인으로 스카웃, 면접 제안 2. Slack 같은 앱이라며 Obsidian 으로 위장한 피싱 링크를 줌 3. 링크 클릭만으로도 설치, Mac 비밀번호 입력하게 됨 4. 새벽에 자는 시간에 지갑 4개 털림, 총 58.4만불 손실 5. 해킹자금은 쿠코인으로 송금됨 6. 해킹 자금은 3일간 동결되나 경찰 요청 없으면 3일 뒤 동결이 풀릴 예정 7. 수사 협조가 신속히 안되면 그대로 놓치는 상황 ✍️ 왜 당하냐 싶겠지만 오히려 코인을 잘 아는 사람들도 당한 사례가 많습니다. Mac 사용하더라도 주의하시길
❤1
업비트(Upbit) 공지 [거래] 댑오에스(DOS) 신규 거래지원 안내 (KRW, BTC, USDT 마켓) 2026-08-11 11:30:38
❤1
빗썸(Bithumb) 공지 [마켓 추가] 댑오에스(DOS) 원화 마켓 추가 2026-08-11 10:17:41
🌍 프리랜서 원천징수 3.3% → 2.2%로 인하 - 2027년 1월 1일 이후 지급되는 소득부터 적용 - 인적용역 프리랜서 원천징수 세율 3.3% → 2.2% - 디자이너, IT 개발자, 미용사 등 대상 - 매달 미리 떼는 세금 부담이 약 1/3 감소 - 최종 세금 자체를 깎아주는 개념보다는 선납하는 세금을 줄이는 방식 - 종합소득세 신고 때 실제 납부세액에 따라 추가 납부 또는 환급 프리랜서 입장에서는 당장 매달 받는 실수령액이 늘어나는 효과 출처
❤1
🌟 크립토 카드 결제, 누적 73억 달러 돌파 - 2023년 10월 이후 크립토 카드 결제 누적 결제액 약 73억 달러 - 총 결제 건수 약 1.31억 건 - 시장 평균 1회 결제액 약 56달러 🔘카드별 평균 결제액 - Tria $180 - Avici $170 - Plasma One $143 - Avalanche Card $99 - ether.fi $80 - MetaMask $55 - RedotPay $55 - Gnosis Pay $54 - SafePal $16 - Bitget Wallet $11 출처
❤1
🌟 Base, 메인넷 출시 3주년 맞이 주요 지표 공개 - TVL 약 50억 달러 - 누적 스테이블코인 거래량 46조 달러 - 전체 x402 트랜잭션의 90%가 Base에서 발생 출처
🌟 지난주 아시아 크립토 주요 이슈 정리 - 러시아, 디지털화폐 관련 법안 서명 - 모스크바 거래소, 크립토 커스터디 사업 준비 - 일본 금융청, 크립토·스테이블코인 전담 부서 신설 - 도쿄증권거래소, 크립토 트레저리 기업 심사 강화 움직임 - 대만, 가상자산 이전 관련 규정 도입 - 인도, 크립토 세금 신고 범위 확대 - 빗썸, 2028년 IPO 목표 - 두나무, 경찰청 압수 가상자산 수탁 사업자 선정 아시아 전반적으로 크립토 제도권 편입과 규제 정비가 동시에 빨라지는 흐름
🌟 비트코인 ETF, 지난주 8.5억 달러 순유입 8/3~8/7 미국 현물 ETF 자금 흐름 - BTC 현물 ETF +8.54억 달러 - ETH 현물 ETF +2.45억 달러 - ETH는 5주 연속 순유입 비트코인 ETF에만 한 주간 약 1.2조원 유입 최근 주춤했던 ETF 자금이 다시 들어오면서 기관 수요도 회복되는 모습
❤1
🌟 가상자산 과세, 2030년까지 3년 유예안 발의 - 현재 예정대로라면 2027년 1월부터 가상자산 과세 시작 - 국민의힘 정성국 의원, 시행 시점을 2030년 1월로 3년 연기하는 법안 발의 - 연 250만원 공제 후 초과 소득에 20% 과세 - 지방소득세 포함 실질 세율 22% - 국민의힘은 별도로 가상자산 과세 완전 폐지안도 추진 중 - 반면 정부는 추가 유예 없이 2027년부터 시행한다는 입장 유지 결국 유예안이 국회를 통과하느냐가 핵심 아직 확정된 건 아니고 현재는 ‘법안 발의’ 단계 출처
❤1
🌍 청년 월세 30% 공제·프리랜서 원천징수 절반 인하 법안 발의 국민의힘 박수영 의원, ‘청년 지원 3법’ 발의 - 15~34세 청년 월세 세액공제율 30%로 확대 - 공제 대상 월세액 한도 최대 1,500만원으로 확대 - 비수도권 중소기업 취업 청년 근로소득세 감면 한도 200만원 → 300만원 - 중소기업 취업 청년 세금 감면 제도 10년 연장 - 배달라이더·프리랜서 등 인적용역 사업자 원천징수율 3% → 1.5% 청년 주거비부터 프리랜서 세금 부담까지 낮추는 내용 아직 확정된 건 아니고 현재는 ‘법안 발의’ 단계 출처
Showing the 12 most recent of 45 posts we hold for @cryptowangbei. 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 — 444,044 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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“왕베이” (@cryptowangbei), 7,382 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/cryptowangbei.
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.