지금 로빈후드가 가스비로 하루에 50억 씩 버는데 이렇게 1년 벌면 약 1.8조를 범. (50*365) 근데 로빈후드 2025년 영업 이익이 2.64조임. 이거 너무 노다지 사업인데 ㅋㅋㅋ
🍓2❤1

Channel
@cryptopandann
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
16,244subscribers
-175 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001266542207 |
|---|---|
| Type | Channel |
| Username | @cryptopandann |
| Created | 10 August 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/cryptopandann |
Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 99% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Sept 2026, 06:00 | 16,244 | -111 |
| 18 Sept 2026, 19:00 | 16,355 | -40 |
| 16 Sept 2026, 10:39 | 16,395 | -39 |
| 14 Sept 2026, 17:19 | 16,434 | -34 |
| 13 Sept 2026, 03:36 | 16,468 | -34 |
| 11 Sept 2026, 06:56 | 16,502 | +117 |
| 8 Sept 2026, 09:55 | 16,385 | -15 |
| 5 Sept 2026, 05:02 | 16,400 | -5 |
| 3 Sept 2026, 10:44 | 16,405 | -5 |
| 2 Sept 2026, 07:24 | 16,410 | -15 |
| 1 Sept 2026, 03:59 | 16,425 | -8 |
| 31 Aug 2026, 05:53 | 16,433 | -16 |
| 30 Aug 2026, 04:38 | 16,449 | -3 |
| 29 Aug 2026, 03:14 | 16,452 | -5 |
| 27 Aug 2026, 03:07 | 16,457 | -12 |
| 26 Aug 2026, 05:45 | 16,469 | -6 |
| 25 Aug 2026, 07:12 | 16,475 | -18 |
| 24 Aug 2026, 03:44 | 16,493 | -14 |
| 22 Aug 2026, 09:37 | 16,507 | -10 |
| 21 Aug 2026, 02:34 | 16,517 | first reading |
63 posts held, back to 30 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 55 pages of 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.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 63 (30 July 2026 – 2 September 2026) |
| Views total | 4,973 |
| Reactions total | 22 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 09:54 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.
Measured directly from 3 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
321 reactions across 62 posts, in 14 distinct kinds. The most used accounts for 84.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 270 | 84.1% | |
| ⚡ | 9 | 2.80% | |
| 👍 | 8 | 2.49% | |
| 😁 | 5 | 1.56% | |
| 🤣 | 5 | 1.56% | |
| 🤡 | 4 | 1.25% | |
| 🥰 | 4 | 1.25% | |
| 🌚 | 3 | 0.935% | |
| 🍌 | 3 | 0.935% | |
| 👎 | 3 | 0.935% | |
| 👏 | 3 | 0.935% | |
| 🍓 | 2 | 0.623% | |
| 💯 | 1 | 0.312% | |
| 🔥 | 1 | 0.312% |
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 62 of the 63 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 321 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 63 most recent posts we hold, published 30 July 2026 to 2 September 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.
지금 로빈후드가 가스비로 하루에 50억 씩 버는데 이렇게 1년 벌면 약 1.8조를 범. (50*365) 근데 로빈후드 2025년 영업 이익이 2.64조임. 이거 너무 노다지 사업인데 ㅋㅋㅋ
🍓2❤1
골드만 등 21개 글로벌 금융사, 스테이블코인 공동 발행 📂 핵심 내용 참여사: 골드만삭스, BOA, 시티그룹, 도이체방크, 산탄데르, 피델리티, 미쓰비시UFJ, 스탠더드뱅크 등 (작년 10월 10개 은행→21개로 확대) 하반기 공동회사 설립, 내년 상반기 달러 스테이블코인 출시, 이후 유로 등 G7 통화로 확대 계획 지니어스법(美)·MiCA(EU) 요건 충족 목표 전 세계 스테이블코인 시총 약 3030억달러(작년 초 약 2000억달러에서 증가), 테더 USDT 약 60%·서클 USDC 20%+ 점유 경쟁 구도: 37개 금융기관 유로화 코인 '키발리스' 연내 출시 예정, 스트라이프·코인베이스·비자 등 140개+ 기업 '오픈 USD' 추진 중 이번 발표 여파로 서클 주가 당일 약 6% 하락 로이터 "은행 스테이블코인 실수요 신호는 아직 부족"…
❤4
📰 DAXA, 미신고 해외 거래소 4곳 수사 의뢰 📂 핵심 내용 특금법상 국내 이용자 대상 영업시 FIU 신고 의무, 미신고시 5년 이하 징역·5000만원 이하 벌금 확인된 불법 영업 정황: 한국어 서비스 지원, 거래가격 원화 표시, 리워드센터(입금·거래량별 USDT·포인트 지급)로 국내 이용자 모집 미신고 거래소는 AML·이용자보호 체계 취약, 출금중단·해킹 등 사고시 국내 제도로 피해구제 어려움 DAXA, 지난 6월에도 불법 장외거래소 8곳·미신고 해외거래소 4곳 등 총 12곳 수사의뢰 이력 ✍️ 바이낸스처럼 규제권 안에 있는 대형 거래소와 달리 이번 4곳은 아예 신고 자체를 안 한 곳들이라 리스크 등급이 다릅니다. 원화 표시·리워드센터로 국내 유저 모으는 곳은 사고 나면 구제 경로가 없다는 점, 이용 전 FIU 신고 여부부터 확인하는…
❤4
[기타] Upbit, $INJ 거래 유의 종목 지정
❤4
지금 로빈후드 TradFI Defi 리스크는 "로빈후드 주식 토큰화 무한 발행되어서 LP에 해커가 가치 0 만드는거" 정도가 직관적인 것 같은데 이게 피해가 크면 로빈후드에서 복구 안해줄거 같긴 함. 왜냐면 현재 로빈후드 기반 주식 토큰들이 LP 수요 + 폰지 기반 바이백때문에 프리미엄이 자주 생기는데 로빈후드측 MM에서 토큰 발행해서 덤핑해서 프리미엄 쳐먹기만 하고 LP는 안 댐. (= 양아치) 하지만, 현재 이 전략들을 익혀놓으면 좋은점이 앞으로 Arc건 Tempo건 이 체인들의 주류 유동성에 "주식 토큰화"가 크게 차지할 것 같고 장기 트렌드로 자리잡힐 수 있는데 그때마다 LP 공급을 해보면서 안정적 APR 파밍을 해볼 수 있다는 것.
❤2
🇰🇷🔥 코인과세유예하라! 코인과세 2년 유예에 관한 청원 약 20일 남았고, 절반정도 동의 찼습니다. 이거 제가쓴건데, 이렇게 메인 청원으로 올라갈줄 알았으면 더 신중하게 쓸걸 그랬네요. 다들 꼭 꼭 꼭 유예청원 동의 부탁드립니다!
❤5
업비트(Upbit) 공지 [거래] 이유알코인(EURC) 신규 거래지원 안내 (KRW, BTC, USDT 마켓) 2026-08-28 10:49:49
❤6
후오비 입출금 중단 사유 폭력적이네요 당사는 범죄자금의 유입·유출로 인한 자금세탁 위험을 예방하고, 회원님의 자산을 안전하게 보호하기 위해 HTX 관련 주소에 대한 입출금 및 출금주소 등록을 제한합니다. ※ 기존 HTX는 '26.05.27 영국 통합 제재리스트(The UK Sanctions List)에 HTX(HUOBI GLOBAL S.A.)가 제재 대상으로 등재됨에 따라 출금 제한 등의 조치가 적용된 바 있습니다. 잘하면 표적당해서 넥스트 샘뱅크런이 될수도?
❤4
4대 코인거래소, 상반기 5000억 손실 - 이중고 빠진 가상자산 시장 - 두나무, 포괄손실 3623억 - 빗썸, 1087억 순손실 전환 - 거래량 급감·코인값 하락 여파 https://n.news.naver.com/mnews/article/015/0005325601
👍1
✅ 한은, 기준금리 연 3%로 인상…두차례 연속 https://biz.sbs.co.kr/article_hub/20000331060
❤3
개인적으로 퍼프덱스가 실제로 만들어낸 결과값에 비해 부정적인 인식이 너무 과한 것 같음. 이전 세대만 봐도 dYdX, Drift, HYPE가 있었고 그다음 Aster, Lighter, Avantis, Based, Backpack까지 계속 큰 승자가 나왔음. HYPE는 제네시스 에어드롭으로 초기 물량 31%를 커뮤니티에 뿌렸고, Lighter도 초기 사용자에게 공급량 25%를 배분했음. 토큰을 받고 바로 팔았는지, 계속 들고 갔는지에 따라 최종 수익은 천차만별이겠지만 매년 에드작 전체를 놓고 봐도 가장 큰 수익을 만들어준 작업 중 하나가 퍼프였음. 선셋하고, 토큰 채단가 밑으로 가고, 잘못하면 전손인데 왜 하냐고 생각할 수 있는데 그 논리로 섹터 자체를 피하면 앞으로 HYPE 같은 기회도 영영 못 가져감. 지금은 작업 방식도 많이 달라졌…
❤7
본 콘텐츠는 KBW2026 티켓과 할인코드를 협찬받는 Community Program의 일환으로 작성됐습니다. ☑️ KBW2026: 조셉 루빈 합류 및 메인 스폰서 공개 KBW2026에 이더리움 공동창립자이자 Consensys CEO인 조셉 루빈이 연사로 합류했습니다. 한국 방문은 2019년 이후 7년 만이라고 합니다. • Joseph Lubin: 이더리움 공동창립자 / Consensys 공동창립자 & CEO • MetaMask, Infura, Linea 등 이더리움 주요 인프라 구축을 이끌어온 인물 • 이번 KBW에서는 RWA·스테이블코인 등 전통 금융의 온체인 전환과 Web3의 다음 단계에 대해 이야기할 예정 이번에 함께 공개된 메인 스폰서는, • Upbit • 0G • Stable • Tria 연사 라인업에는 조셉 루빈 외에도 H…
❤6
Showing the 12 most recent of 63 posts we hold for @cryptopandann. 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.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“Crypto 팬더 공지방🦅” (@cryptopandann), 16,244 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/cryptopandann.
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.