미친거같습니다.. 그냥 보유하고 있는 물량으로 일단 수익내야겠네요 ㅋㅋㅋㅋ아무것도 안하겠습니다
❤60

Channel
@BIT_DTR
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
14,599subscribers
-47 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001864874268 |
|---|---|
| Type | Channel |
| Username | @BIT_DTR |
| Description | 차트 공부가 목적으로써 거래대상·시점·가액에 대한 추천이나 권유가 아닌 개인적인 의견이니 "참고"만 해주시기 바랍니다. 모든 선택과 책임은 “본인”에게 있습니다. |
| Created | Between 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 21 August 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 21 August 2026 |
| On Telegram | t.me/BIT_DTR |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 21 Aug 2026, 10:44 | 14,599 | +25 |
| 20 Aug 2026, 13:43 | 14,574 | +14 |
| 19 Aug 2026, 10:57 | 14,560 | +5 |
| 18 Aug 2026, 10:34 | 14,555 | -6 |
| 17 Aug 2026, 14:07 | 14,561 | -11 |
| 16 Aug 2026, 05:38 | 14,572 | -8 |
| 14 Aug 2026, 17:17 | 14,580 | -16 |
| 13 Aug 2026, 07:14 | 14,596 | -4 |
| 12 Aug 2026, 06:22 | 14,600 | -13 |
| 11 Aug 2026, 04:48 | 14,613 | -7 |
| 10 Aug 2026, 04:11 | 14,620 | -11 |
| 9 Aug 2026, 03:54 | 14,631 | -8 |
| 8 Aug 2026, 04:53 | 14,639 | -7 |
| 7 Aug 2026, 09:45 | 14,646 | first reading |
31 posts held, back to 28 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 30 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.
| Window | Rolling 30 days · latest post in window 21 August 2026 |
|---|---|
| Posts held | 31 (28 July 2026 – 21 August 2026) |
| Views total | 143,780 |
| Reactions total | 5,810 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 22 Aug 2026, 12: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.
Lifetime counters from Telegram’s own channel header, read 22 August 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.
5,810 reactions across 31 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 5,810 | 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 31 of the 31 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 5,810reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 31 most recent posts we hold, published 28 July 2026 to 21 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.
미친거같습니다.. 그냥 보유하고 있는 물량으로 일단 수익내야겠네요 ㅋㅋㅋㅋ아무것도 안하겠습니다
❤60
#비트코인 지금은 추세가 이어지고있기때문에 여기서 롱포지션이나 현물을 추격으로 매매할수는 없을거같고 조정 및 횡보하는 기간을 기다려야 새로운 타점이 나올거같습니다. 현재 구간이 C인지 3인지 알수없지만 추세기반 되돌림 비율상 연장으로 흘러간다면 1:1.618 = 77.3K 정도로 체크되고있습니다. 해당 자리에서 한번 쉬는구간이 있지않을까..생각하고있습니다
❤223
#비트코인 어제 영상에서 말씀드렸던것처럼 가장 중요한 저항구간들을 그냥 뿌셔버리면서 올라오고있습니다. 뭔가 비트코인이 이런식으로 장대양봉을 뽑은게 얼마만인지... 설레기도 하네요 현재 58k 가 최저점이 될 수 있는 상황에서 보유하고있는 소량의 물량은 좀 더 가져가야할거같고 기존에 보고있던 메인관점은 폐기처분 할 생각입니다. 새로운 시나리오를 짜야하는데 다행인건 롱포지션이랑 현물을 들고있어서 포모가 오지않는다는점... 이게 젤 큰거같습니다.
❤202
영상 업로드했습니다. 지금 상승이 공격적으로 나오고있는데 주의해서 나쁠건 없다고 생각합니다. 내용 정말 중요하니 꼭 끝까지 시청하시길 바랍니다. 좋아요와 선플은 사랑입니다..! https://youtu.be/3BD5jSl_uY0?si=OFd1uIIavbTV9EGC
❤194
#비트코인 저번 영상에서 말씀드렸던 직전고점은 넘어갈거고 저항으로 유추되는 구간이 67~68k 70~71k 해당 두 구간이였는데 첫번째 저항구간은 순식간에 밀어버렸네요 오늘 영상으로 제작해서 올리겠습니다
❤217
58k 롱 적중 62.3k롱 적중 62.4k 롱 또 적중 70k 저항 적중 갓미남
❤204
빅롱~.~
❤179
#비트코인 어제 영상에서 말씀드렸던 구간인 하락채널의 상단부에서 저항으로 작용한모습입니다. 67k든 70k든 상승이 진행되려면 해당 자리 돌파가 나와야하는데 아직은 하락채널안에서 추세를 이어가고있으니 추가로 매매를 할 이유는 없어보입니다. 우선 단타 타점도 장기타점도 잘 잡아놨으니 계속 지켜보도록 하겠습니다.
❤201
멤버십 모집 - 투자의정석 혜택 ✔️ 시장 흐름에 대한 멤버십 전용 브리핑 ✔️ 차트 관점과 주요 구간 분석 ✔️ 멤버 전용 라이브 및 Q&A (멤버들이 궁금한 코인 질의응답) ✔️ 코미남 단타 현물,선물 모두 포지션 공개 (업비트 기준) *긴말 안하겠습니다. 7월 1일부터 현재까지 승률 100% 유지중 근거있는 자리에서만 제대로 매매하실 팀원을 원합니다. 입장문의 📱https://t.me/LUMINOUSKOR
❤161
영상 업로드했습니다 다음 저항구간과 작도 및 주요구간 영상으로 설명드렸습니다 꼭 시청하시길 바랍니다...!! 오늘 하루도 고생하셨습니다 *좋아요랑 선플은 사랑입니다... https://youtu.be/IiMyhw8xUw0
❤176
#비트코인 멤버십에서 오픈한 타점입니다. 62.6k~62.3k -피보나치 0.5되돌림 -추세기반 1:0.618구간 해당 두 구간에서 반등에 성공한 모습입니다. 이번에도 저점을 잡을 수 있어서 기분은 좋네요 ㅋㅋㅋ.. 채널상단을 돌파한다면 아마 꽤 크게 상승하지않을까 싶습니다. 금일 영상에서 브리핑 제대로 드려보겠습니다!!
❤194
#비트코인 지루하네요.. 여전히 같은 그림을 보고있습니다. 지금 잘 떨어지고있긴한데.. 아마 다음주 안으로는 타점이 체결되지않을까 생각하고있습니다. 특별한 자리가 아니면 굳이 매매할 필요성을 못느끼는고있어서 좋은 자리 올때까지 기다리려고 합니다.
❤223
Showing the 12 most recent of 31 posts we hold for @BIT_DTR. 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 — 1,115,195 of 1,581,209entries 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.
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.
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 21 August 2026 — this entry's latest reading, not the date you are reading this.
“코인에 미친남자(비트코인)” (@BIT_DTR), 14,599 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/BIT_DTR.
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.