한국의 천만 개미들은 다 알고있는데 왜... 어째서지?

Channel
도랏맨
@doratman18
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
9,496subscribers
+61 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001864238560 |
|---|---|
| Type | Channel |
| Username | @doratman18 |
| 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 | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/doratman18 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 10:07 | 9,496 | -7 |
| 9 Aug 2026, 20:22 | 9,503 | +10 |
| 6 Aug 2026, 18:56 | 9,493 | +58 |
| 6 Aug 2026, 02:50 | 9,435 | no change |
| 6 Aug 2026, 02:03 | 9,435 | first reading |
Engagement
51 posts held, back to 3 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 15 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 23.9%
- avg views ÷ 9,496 subscribers
- Avg views / post
- 2,270
- 51 posts measured
- Reaction rate
- 0.508%
- reactions ÷ views · ER floor
- Posts in window
- 51
- of 51 held
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 33 of 51 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 15 August 2026 |
|---|---|
| Posts held | 51 (3 August 2026 – 15 August 2026) |
| Views total | 115,642 |
| Reactions total | 442 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Aug 2026, 08:33 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.
What this channel posts
- Photos
- ≈1,680
- Videos
- ≈17
- Links
- ≈598
Lifetime counters from Telegram’s own channel header, read 15 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.
- Video runtime
- 13s
- Average length
- 13s
Measured directly from 1 video 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.
Reaction mix
431 reactions across 30 posts, in 9 distinct kinds. The most used accounts for 75.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 326 | 75.6% | |
| 👏 | 45 | 10.4% | |
| 👍 | 31 | 7.19% | |
| 🙏 | 9 | 2.09% | |
| 🥰 | 7 | 1.62% | |
| 😁 | 6 | 1.39% | |
| 🤬 | 3 | 0.696% | |
| 🕊 | 2 | 0.464% | |
| 😱 | 2 | 0.464% |
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 33 of the 51 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 442reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 51 most recent posts we hold, published 3 August 2026 to 15 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.
Recent posts
✖️머스크가 지목한 핵심 병목, 메모리 source 1. 지금까지 AI 투자의 중심은 GPU와 컴퓨팅 파워였음. 하지만 에이전트 AI로 넘어가면 병목은 메모리 용량과 대역폭으로 이동함 2. 모델 가중치와 연산 중간값이 메모리에 저장됨. 긴 컨텍스트일수록 KV 캐시가 급증 3. 여러 에이전트가 동시에 장시간 작업할수록 필요한 메모리도 누적. 메모리가 부족하면 좋은 GPU도 제대로 활용할 수 없음 4. 메모리는 단순 부품이 아님. AI가 얼마나 많이 기억하고, 오래 추론하며, 저렴하게 지능을 생산할 수 있는지 결정하는 핵심 요소 5. 물론 메모리는 여전히 공급과 가격에 따라 움직이는 사이클 산업이지만 이번에는 디바이스 수요 위에 AI라는 구조적 수요가 추가 6. AI 1차전이 GPU 확보 경쟁이었다면, 에이전트 시대의 2차전은 메모리 …
저도 조금이지만 기부해보았습니다 다들 어렵지만 조금씩 돕는 마음이 기부의 시작아닐까요
👏35❤15
https://youtu.be/aY8TPIaw4t8?si=mVKLvjCCJ6By4lEl 대한독립만세🇰🇷
❤11
https://n.news.naver.com/mnews/article/014/0005561908?sid=101 허허 조강지처가 좋더라~♬ 썬연료가 좋더라~♪ 국민연료 썬연료♩
주식은 비싸도 주도주를 사라 퀄리티 주식을 사라 부동산은 서울을 사라 싸다고 지방사면 안된다 코인은 비트코인/이더리움을 사지마라 쓰레기알트코인을 사서 100배를 노려라
👍26❤8
테더의 금 트레이딩 인력 해고의 진실? 1) 테더는 2025년 11월 11일 HSBC에서 귀금속 인력 2명을 채용 2) 한 명은 HSBC의 글로벌 금속 트레이딩 책임자 Vincent Domien, 다른 한 명은 EMEA 지역 귀금속 오리저네이션 책임자 Mathew O’Neill 3) Bloomberg는 테더가 대규모 금 보유고를 활용해 본격적인 금 트레이딩 사업을 구축하려고한다고 발표 4) 이후 금은 2026년 1월 1온스당 5595달러라는 사상 최고가를 찍고, 3월에만 13%이상 급락 5) 2026년 3월, 테더는 두 사람의 자리를 없앰 6) 이후 발표된 해고 이유는 테더의 감독구조 때문에, 금 트레이딩 사업을 할 수 없었다고 발표 과연 진짜 테더의 구조 때문에 그런 것일까? 아니면 골드를 최고점에 처물려서 짤린 것일까? 궁금하긴함
테더는 좋은 결함발견
🐛 테더 역사상 가장 큰 재무 감사 완료 항상 불투명성에 휘말리고 있는 테더가 이번에 2025년 12월 기준의 자산을 세계 최대 감사사인 KPMG 와 함께 완료했다고 합니다. 재미있는 점은 테더가 가지고 있는 모든 실물 자산을 실제로 눈으로 보고 세었으며, 실제 모든 금괴에 데이터 라벨링을 했고 여기서 결함이 하나 발견되었다고 하는데 해당 결함은 "보고서와 다르게 68억 1400만달러가 더 많음" 이라고 하네요. 공지원문 #USDT #Tether
❤6👍5
최근에 수백억대 부자친구랑 같이 드라이브를 했습니다 그 친구가 튼 노래가, 제 최애곡이랑 똑같더군요. 이 노래를 듣다보면 나도 수백억 벌 수 있겠지? 노래는 댓글로 공개합니다
❤16
투기 2행시 투자 기회
❤12
투기하라고 말씀드린바있습니다 감사할 필요는 없습니다 여러분의 용기 덕분에 수익을 내신겁니다
❤17🕊2
Showing the 12 most recent of 51 posts we hold for @doratman18. 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
Citation-graph rank — 25,322 of 1,478,351entries 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
@cryptodino_dino · 5,8562 posts디젠의 트레이딩 일지
@degen2468 · 11,8442 posts인생코인
@lnsanecoin · 7,6202 posts알랑이 정보교류소
@AlanInfoExchange · 3,2771 post바밀이야 bamilirya
@Bananamilkrich · 8,9451 post에어드랍ATM
@Bounty_ATM · 25,9571 post육아현물왕 개인관점방
@coin500Bking · 3,0781 post보노의 야수매매
@cryptobonobobo · 7821 post돌곰배와 매직 코인일기 🦅
@dolgommagic · 11,8501 postZi존파워잼민
@jammin0720 · 3,5631 post쿠쿠쿱 koob 6.0
@kookookoob · 17,1501 post뉴스 및 정보싸개
@npynews · 6891 post사랑방🍬(CRYPTO ALPHA)
@Sarangbang_Crypto · 7,8581 postSOJANG COIN NEWS
@SOJANG_signal · 3571 post빚쟁이는 여의도로
@yeouidobi · 1,9601 post안녕
@z01028 · 3421 post
Republishes
Channels on the register whose posts this channel has forwarded.
@insidertracking · 69,4582 posts백두남 (백억 두 번 잃은 남자)
@baekdoo_ch · 7381 postSteve’s Catallaxy
@catallactic · 5,2221 postAWAKE - 실시간 주식 공시 정리채널
@darthacking · 64,7501 post돌비콩의 투자정복
@dolbikong · 9,4721 post취미생활방📮
@enjoymyhobby · 50,5771 post새우잡이어선 공지방
@shrimp_notice · 29,2391 post[ IT는 SK ]
@skitteam · 17,7651 post빚쟁이는 여의도로
@yeouidobi · 1,9601 post
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.
Mentions
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.
Cite this entry
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“도랏맨” (@doratman18), 9,496 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/doratman18.
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.