Channel
@dunstearth
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
249subscribers
+195 since we began measuring on 25 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004347532191 |
|---|---|
| Type | Channel |
| Username | @dunstearth |
| Created | 18 August 2026 — measured — dated from the channel’s first post |
| First recorded | 25 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/dunstearth |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 05:59 | 249 | +3 |
| 10 Sept 2026, 18:19 | 246 | +167 |
| 1 Sept 2026, 22:27 | 79 | +8 |
| 26 Aug 2026, 20:54 | 71 | +17 |
| 25 Aug 2026, 22:15 | 54 | first reading |
7 posts held, back to 18 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 1 page 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 1 of 4 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 25 August 2026 |
|---|---|
| Posts held | 7 (18 August 2026 – 25 August 2026) |
| Views total | 1,433 |
| Reactions total | 0 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 25 Aug 2026, 22:15 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.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 1 | 100.0% |
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 2 of the 7 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 18 August 2026 to 25 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.
스토리지 플레이북 시나리오 hft와는 다르게 입금이 막혀있기 때문에 숏플레이의 느낌이 나는 현선을 잡게 되는데 리스크로는 바낸 상폐이후에도 계속해서 가격이 상승하며 역프가 무한대로 커지면서 청산가 위협이 있으나 출금이 가능하기때문에(정기실사와 다른점. IN은 이점을 이용해서 스퀴징을 유도함) 비벼볼 여지가 존재함. 별다른이벤트를 예상하지 않는다면 상황을 보고 해도 나쁘지않고 가격하락을 예상한다면 미리 현선을 잡는게 나은방법일 수 있을듯.
느낀점 소위 무지성 매수가 사라지고 유동성이 마른 시장에서 가격으로 하입을 이끌어내기 위해 크라임코인들이 여럿 등장하고 거의 대부분의 기회가 여기에서 나오기도하고 마른 오징어 엑기스 장인줄 알았는데? 비트가 상승하고 테더가 1300원대까지 박으며 감이 안오는 장세인듯. 흐름이 너무 빨라서 쉽지는 않은거 같음
08.15 — CAP 03:00 핫한 크라임코인 CAP 현물이 하니급으로 위아래를 추던 과정에서 업비트는 현기증이 났는지 갑자기 가격을 못따라가는 현상 발생 03:12 업비트에 고점15%가 넘는 김프가 발생했고, 바이빗에서 CAP 약 4천만 개가 업비트로 들어감 ~03:34 김프는 생각보다 꽤 오래 유지됐고, 바낸선물이 현물하락을 못따라가는 상황이 나오며 콘탱고 발생. 정프에 털어도 남는 상황 이후 소강상태에 들어가면서 1% 안팎을 잔잔하게 주길래 슬슬 끝났나 싶었는데… 03:35~04:00 여지없이 크라임코인다운 무빙으로 단 몇 분 만에 약 40%를 쏴버리면서 상황이 반전되고 업비트가 순식간에 역프로 전환. 처음 생각했던 해외 쪽 상승 시나리오가 현실화되면서, 바이빗에서는 괴리가 30% 넘게 벌어지는 구간이 나옴. 이날 CAP은…
08.07 HFT 바낸 선물 상폐를 앞두고 이전부터 쭉 상폐 당일까지 호로말XX스양봉을 무한으로 띄우고 있었음. 상폐당일 국내에서 상당히 큰 역프가 나오지만 핫채우는 속도와 양,펀비를 고려해봤을때 잡을수가 없는상황. 상폐5분전까지도 이렇다 할 하락없이 신규 포지션 생성이 중단됨. 바이낸스 선물은 마지막까지 포지션을 청산시키지 않고 들고있으면 거래중지와 함께 자동으로 거래소에서 마지막 30분 중간값으로 청산해줌. 지난몇년간 코인시장에서 굴러먹은 개미들도 상당히 똑똑해졌기때문에 크라임 코인을 운전하는 세력입장에서 정직한 운전으로는 손익비가 나오지않고, 상폐타이밍 맞춰서 숏을치기때문에 근1년간 가격을 내리지 않고 그대로 끝내버리는 패턴이 꽤 나옴. 이러한 패턴이 나올수도 있는걸 알기 때문에 주변 고수들도 건들지 않고 쳐다보기만 한듯. …
으하하
🔥1
Channel name was changed to «퍼렁별침략소대»
Channel created
Showing the 7 most recent of 7 posts we hold for @dunstearth. 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.
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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“퍼렁별침략소대” (@dunstearth), 249 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/dunstearth.
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.