https://x.com/wakuangdashen/status/2094176431031087304?s=20 여자들이 비키니 사진을 ㅈㄴ 보낸다는 것을 믿을 수 가 없네.... 400만 위안 = 8억 1억 위안 = 200억
❤9🤩4

Channel
@dontak00
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
14,271subscribers
+55 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001749096540 |
|---|---|
| Type | Channel |
| Username | @dontak00 |
| Created | 14 April 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/dontak00 |
Technology — 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 63% 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 |
|---|---|---|
| 18 Sept 2026, 12:40 | 14,271 | +21 |
| 16 Sept 2026, 05:38 | 14,250 | -11 |
| 14 Sept 2026, 09:17 | 14,261 | +2 |
| 12 Sept 2026, 17:40 | 14,259 | -16 |
| 10 Sept 2026, 19:21 | 14,275 | +19 |
| 7 Sept 2026, 19:17 | 14,256 | -17 |
| 4 Sept 2026, 17:17 | 14,273 | -11 |
| 3 Sept 2026, 00:37 | 14,284 | -5 |
| 1 Sept 2026, 21:44 | 14,289 | -2 |
| 1 Sept 2026, 00:37 | 14,291 | -12 |
| 31 Aug 2026, 01:16 | 14,303 | -3 |
| 30 Aug 2026, 00:47 | 14,306 | +19 |
| 28 Aug 2026, 21:35 | 14,287 | -7 |
| 27 Aug 2026, 21:04 | 14,294 | +3 |
| 26 Aug 2026, 18:43 | 14,291 | +5 |
| 25 Aug 2026, 20:47 | 14,286 | +25 |
| 24 Aug 2026, 17:15 | 14,261 | +9 |
| 22 Aug 2026, 23:24 | 14,252 | +5 |
| 21 Aug 2026, 16:08 | 14,247 | +43 |
| 20 Aug 2026, 12:03 | 14,204 | first reading |
48 posts held, back to 29 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 51 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 1 September 2026 |
|---|---|
| Posts held | 48 (29 July 2026 – 1 September 2026) |
| Views total | 89,270 |
| Reactions total | 914 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Sept 2026, 18: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.
2,745 reactions across 47 posts, in 9 distinct kinds. The most used accounts for 74.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2,040 | 74.3% | |
| 👍 | 211 | 7.69% | |
| 😱 | 148 | 5.39% | |
| 😁 | 110 | 4.01% | |
| 🔥 | 105 | 3.83% | |
| 👏 | 63 | 2.30% | |
| 🥰 | 53 | 1.93% | |
| 🤔 | 10 | 0.364% | |
| 🤩 | 5 | 0.182% |
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 47 of the 48 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 2,745 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 48 most recent posts we hold, published 29 July 2026 to 1 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.
https://x.com/wakuangdashen/status/2094176431031087304?s=20 여자들이 비키니 사진을 ㅈㄴ 보낸다는 것을 믿을 수 가 없네.... 400만 위안 = 8억 1억 위안 = 200억
❤9🤩4
일론 머스크 합의된 추정치에 따르면, 2027년에 생산될 약 15GW 규모의 AI 컴퓨팅 설비가 2027년 안에 실제로 가동되지 못할 것으로 예상됩니다. 문제는 단순히 전력을 확보하는 것보다 더 어렵습니다. 전력뿐 아니라 변압기, 배선, 액체 냉각 시스템, 대형 칠러, 복잡한 네트워킹 인프라까지 모두 구축해야 하기 때문입니다.
❤18
나는 연내 미국 금리 인상이 있을 것이라고 생각하는데... 나같은 무지렁이가 매크로에 대해 뭘 알겠음.. 그냥 오건영 선생님이 올릴 것 같다고 하니 그렇지않을까 생각중임. 저번에 프라이빗하게 오건영 선생님 강연을 들을 기회가 있었데 거기서도 꽤나 강하게 미국의 금리 인상 가능성을 말씀 해 주심. 미국의 금리 인상 가능성이 없다고 생각하는 사람이라면 읽고 생각 해 볼 글.
❤55👍6
아직까지는 코인이 디베이스먼트 트레이드 논리에 굉장히 충실하게 움직이고 있음. 어제 금리인상 가능성이 대두되니 금이랑 같이 쭈욱 빠지는 모양을 보임. 나는 미국이 연내 금리 인상을 할 가능성을 높게 보고 있음. 그러다보니 디베이스먼트 트레이드 논리에 따라 충실히 움직이는 모습이 그렇게 달갑지는 않음. 또한 차트적으로는 이더리움 등이 굉장히 좋은 돌파 셋업을 만들어 놨다가 깨졌고 초반에 장을 주도하던 리플같은 애들 숏만 쥐어 짜내고 구더기 되버림. 솔라나도 이벤트 셀온으로 매도가 많이 나오고 구려짐. 그리고 자주보던 현물 호가창으로 이야기하자면.. 비트코인에 계속 매도 대기 물량이 늘고 8k 저항이 거센데 이걸 못 이기는 흐름. 다른 주요 코인들도 좋은 돌파 셋업 자리에서 계속 매도가 쌓이다가 결국 망가진 모습. 이런 것들이 종…
❤72👍9
개인적으로는 코인은 익절 다 했습니당... 쉽게 안주고 어렵게 가고 개인적으로 좀 안좋게 보는 단기 시그널들이 뜨길래 .. 주말 해피 육아를 위해 다들 주말 행복한 시간 되십숑
🥰49👍13🤔10❤1
어제 치킨을 먹음. 와이프가 치킨을 먹었으니 운동을 하라며 호들갑을 떰. 맨몸 스쿼트 20개 했음. 근데 그날 걷는데 가끔씩 다리에 힘이 풀림. 오늘 허벅지 근육통 옴. 변기에 앉거나 할 때 아픔. 이정도면 몸상태 얼마나 심각한건가요
😁35❤14😱6🥰1
3줄 요약 : 1. 지금 왜 오르는지 사람들이 떠드는 그 이상을 잘 모르겠음. 2. 근데 차트상으로 내 기준 매우 좋아보임. 흡사 상승장 초입. 3. 그래서 롱치고 있긴한디 쎄하면 바로 튈 근본 DNA 숏충이인 것은 변함없음.
👍69❤19
이번에 코인이 오른 이유로 많이 지목되는 것이 디베이스먼트 트레이드 입니다. 쉽게 말하면 달러가치 훼손에 따른 금/비트 상승 논리 입니다. 실제로 저 또한 위 이슈로 금과 비트가 강세를 나타내고 이더가 돌파를 하는 모습을 보이는 것을 보면서 매수를 했기 때문에... 어느정도 타당한 이야기라는 생각도 듭니다만 한편으로는 정말 이게 맞아? 하는 생각이 드는 것도 사실입니다. 언제부터 지가 금이랑 그렇게 묶여서 잘 움직였다고..... 비슷하지만 또 다른 상승논리로는 "미국은 스테이블을 키울 수 밖에 없어~" 가 있겠습니다. 다들 익숙한 이야기겠지요... 현재 단기채를 찍어내서 장기채를 사주는 행위를 하고 있는데.. 이를 위해서는 단기채를 집어 삼켜줄 수요처가 필요하고... 그것으로 미국이 보고 있는 것이 스테이블 코인이다... 따라서 …
❤88👍9
코인은 숏이 가치투자라는 제 신념에는 변함이 없습니다.
❤56
코인은 확실히 좋은 모습을 계속해서 보여주고 있네요 상승각도에 비해 아주 건강한 조정만을 보여주고 있습니다. 오랜기간 유동성이 말라붙고 변동성이 죽어있다가 분출되었기에 이정도에서 끝이라고는 생각이 잘 안들고 있습니다. 일반적인 스퀴징이라면... 피뢰침을 꽂고 상승폭을 상당부분 토해내야 하는데.. 이번에는 대량 청산을 시켜도 계속 물량을 소화하면서 옆으로 빼고 자리를 지키고 재차 상승하는 모습을 보여주네요. 개인적으로 굉장히 긍정적인 모양이라고 보는데... 그 이유는 제가 숏을 치면서 가장 경계하는 그림이 바로 이런 그림이기 때문입니다. 보통 숏을 칠때 꿀 자리 중 하나가 거래량이 터지는 양봉 (스퀴징 빔) 같은 것인데... 이런 장대양봉이 나온 이후 되돌림이 얼마없이 옆으로 빼기 시작하면 저는 무조건 숏을 접습니다. 너무 많이 …
❤68
업비트 형님.... 벌써부터 무한상장을 해 버리면... 코인 시장은 우째 살아납니까
😱25❤5👍5
최근 자신의 강점과 약점을 검사하는 테스트를 받았음. 유료로 몇십만원짜리 테스트 였던 것 같음. 기회가 있어서 무료로 테스트를 받고 상담사(?)와 이야기 할 기회도 있었음. 검사 결과지를 보면... 인간의 여러 덕목 중 자신이 강한점과 모자란 점이 순서대로 나열되어 있음. 나에게 1등 강점은 커뮤니케이션이었고... 꼴찌는 계획수립 같은 것이었음. 인상깊었던 점은 바로 나의 약점은 계획수립이 아니라는 것임. 나의 가장 큰 약점 또한... 커뮤니케이션임. 인간의 강점이라 함은,,, 모름지기 양면성이 있고... 장점이 있으면... 그부분에서 파생되는 단점이 있다는 것. 말을 잘 하는 사람은.. 말로서 많은 이점을 누리지만... 어쩌면 다른 사람들이 말 할 기회를 자신도 모르게 뺏고 있으며... 그로인해 많은 미움을 받고 있을지도 …
❤78🤩1
Showing the 12 most recent of 48 posts we hold for @dontak00. 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.
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 12 seed channels' Telegram-generated recommendation lists 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“돈타쿠” (@dontak00), 14,271 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/dontak00.
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.