드디어 하리가 가는구나
❤1🎉1

Channel
@moneygrid
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
10,753subscribers
-534 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001733283934 |
|---|---|
| Type | Channel |
| Username | @moneygrid |
| Description | 과욕은 돈을 부른다 |
| Created | 13 December 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 64 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/moneygrid |
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 11 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Nov 2026, 11:49 | 10,753 | -17 |
| 8 Nov 2026, 20:39 | 10,770 | -10 |
| 7 Nov 2026, 15:01 | 10,780 | -2 |
| 6 Nov 2026, 16:46 | 10,782 | -5 |
| 5 Nov 2026, 18:58 | 10,787 | -6 |
| 4 Nov 2026, 17:08 | 10,793 | -5 |
| 3 Nov 2026, 14:48 | 10,798 | -8 |
| 2 Nov 2026, 15:35 | 10,806 | -7 |
| 1 Nov 2026, 13:46 | 10,813 | -5 |
| 31 Oct 2026, 13:46 | 10,818 | -3 |
| 30 Oct 2026, 16:11 | 10,821 | -9 |
| 29 Oct 2026, 15:09 | 10,830 | -5 |
| 28 Oct 2026, 16:48 | 10,835 | -10 |
| 27 Oct 2026, 15:20 | 10,845 | -5 |
| 25 Oct 2026, 13:16 | 10,850 | -3 |
| 24 Oct 2026, 14:36 | 10,853 | -3 |
| 23 Oct 2026, 11:27 | 10,856 | -6 |
| 22 Oct 2026, 12:46 | 10,862 | -3 |
| 21 Oct 2026, 09:09 | 10,865 | -10 |
| 20 Oct 2026, 10:16 | 10,875 | first reading |
50 posts held, back to 20 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 58 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. It is computed over the 11 of 12 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 10 November 2026 |
|---|---|
| Posts held | 50 (20 July 2026 – 10 November 2026) |
| Views total | 7,109 |
| Reactions total | 15 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Nov 2026, 21:19 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.
Lifetime counters from Telegram’s own channel header, read 10 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
99 reactions across 45 posts, in 6 distinct kinds. The most used accounts for 77.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 77 | 77.8% | |
| 👍 | 8 | 8.08% | |
| 🔥 | 6 | 6.06% | |
| 😢 | 6 | 6.06% | |
| 🎉 | 1 | 1.01% | |
| 😁 | 1 | 1.01% |
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 45 of the 50 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 99 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 50 most recent posts we hold, published 20 July 2026 to 10 November 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.
Telegram’s own ‘edited’ marker: 0 of 12 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
드디어 하리가 가는구나
❤1🎉1
$HYPE listed on Upbit spot (KRW)・
🤪바이낸스 해킹 피해 자산 90% 복구 완료 발표 한줄요약 : 출금 내일 재개가 목표 / 주요코인은 전부 충당했고 잡코들은 계속 매입해서 보충 중 ✔️피해 자산 90% 충당 완료 - BTC·ETH·USDT·BNB·SOL·USDC·XRP·USD1·RLUSD·ZEC 등 주요 10개 자산은 100% 충당 - 나머지 10%는 유동성이 낮은 알트코인으로, 시장 및 OTC를 통해 계속 매입 예정 - 해킹 손실은 이용자가 아닌 바이낸스가 전액 부담 ✔️자산 복구에 동원한 자금 - SAFU 이용자 보호기금 일부 (향후 24시간 내 집행 예정) - 선물 보험기금의 초과 적립분 일부 - 바이낸스 자체 기업 자금 - SAFU는 향후 약 10억 달러 규모로 재충당 계획 ✔️준비금 및 출금 재개 - 10월 31일 00:00 UTC 기준 PoR 스냅샷 업데이트 -…
❤1
바이낸스의 초기 조사에 따르면, 이번 보안 사고는 데브옵스 엔지니어의 노트북이 해킹당해 공격자가 서비스 컨테이너에 접근하여 무단 출금 거래를 실행한 것으로 추정됩니다. 현재까지 지갑 개인 키 유출 증거는 발견되지 않았습니다. 조사가 완료되고 사실 관계가 완전히 확인되는 대로 자세한 기술적 사후 분석 보고서를 공유할 예정입니다. 바이낸스는 SAFU 기금과 회사 자금에서 발생하는 모든 손실을 보전할 것입니다. 사용자 자금은 안전합니다. 또한 복구 작업이 완료되면 업데이트된 준비금 증명(Proof of Reserves)을 공개할 예정입니다.
❤1
$STABLE listed on Coinbase spot・
❤1
업비트(Upbit) 공지 [거래] 닐리온(NIL) KRW 마켓 디지털 자산 추가 2026-10-27 16:30:00
❤1
백팩에서 일한지 1년이 되었어요. 시간이 정말 빨리 흐르는것 같습니다. 만난 소중한 동료들과, 언제나 지지해주는 친구들에게 큰 감사함을 느껴요. 제가 백팩에 처음 들어왔을때 저는 백팩이 이렇게 완벽한 길을 걸을 줄 몰랐어요. 바보같을 정도로 규제를 준수하는것, 그리고 라이센스를 집착하다싶이 따는것들이 현재 이렇게 큰 자산을 만들어냈어요. 천천히, 가랑비에 옷 젖듯 저는 백팩에 비전에 스며들어갔고, 아르마니를 완전히 존경하게 되었어요. 그는 좋은 창업자이지만, 인간적으로도 참 따듯하고 좋은 사람이기도 해요. 사람들은 팀을 온전히 토큰의 가격으로만 평가하곤 하죠. 인위적인 펌프 앤 덤프로 물들은 TGE속에서 백팩은 오가닉하게 최저점 대비 10배를 만들어냈어요. 하지만 토큰 가격을 차치하고도, 팀은 정말 밤낮없이 일하며 올바른 길을 가고 있어…
❤4
靑, 가상자산 과세 재유예 결론…청년 여론·美 카프 등 고려
❤1
업비트(Upbit) 공지 [거래] 콘크리트(CT) 신규 거래지원 안내 (KRW, BTC, USDT 마켓) 2026-10-19 16:40:00
❤1
영상 재밌어잉 https://youtu.be/SF1SLHOlcC0?si=ii6U-eUPf8u22HKo
❤1
업비트(Upbit) 공지 [거래] 퍼퍼(PUFFER) KRW 마켓 디지털 자산 추가 2026-10-15 13:40:00
❤1
업비트(Upbit) 공지 [거래] 깃코인(GTC) KRW, USDT 마켓 디지털 자산 추가 2026-10-12 19:00:00
❤1
Showing the 12 most recent of 50 posts we hold for @moneygrid. 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 2 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.
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 31 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 10 November 2026 — this entry's latest reading, not the date you are reading this.
“머니그리드” (@moneygrid), 10,753 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/moneygrid.
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.