Channel
@channel_dms
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
2,064subscribers
+1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001577805179 |
|---|---|
| Type | Channel |
| Username | @channel_dms |
| Created | 22 July 2023 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 10 August 2026 |
| On Telegram | t.me/channel_dms |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 01:27 | 2,064 | +1 |
| 6 Aug 2026, 11:22 | 2,063 | no change |
| 6 Aug 2026, 10:45 | 2,063 | first reading |
18 posts held, back to 18 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 2 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. It is computed over the 3 of 18 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 18 (18 July 2026 – 6 August 2026) |
| Views total | 8,204 |
| Reactions total | 3 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 17:01 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.
3 reactions across 2 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3 | 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 3 of the 18 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 3reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 18 July 2026 to 6 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.
이란, 호르무즈 통과 규정 강화 검토 이란 의회는 호르무즈 해협과 페르시아만을 통한 통과 규정을 강화하는 법안 초안을 검토 중이다. 주요 제안 내용은 다음과 같다: • 미국, 이스라엘 및 기타 적대 국가와 연계된 선박 금지 • 이스라엘과 관련된 군사 및 민간 화물 차단 • "저항의 축"에 대한 행동과 연계된 선박 제한 • 이란에 배상금을 지불해야 할 당사자의 통과 거부 • 위반 시 화물 가치의 최대 20% 벌금 부과 이 제안은 현재 검토 중이며 아직 승인되지 않았다. https://x.com/DeItaone/status/2085394030586728631?s=20
Signed Pe Pe .dms
[속보] 스트래티지, 비트코인 1,637개 매도, 보유량 842,138개로 감소 📰원문/번역 📊시장 현황 📲앱 다운로드 $MSTR
Signed Pe Pe .dms
코스피 코스닥 사이드카 사이드카는 매일… https://n.news.naver.com/article/003/0014100185?sid=101
Signed Pe Pe .dms
오늘 같은 날 코인은 안 오르는 이유.. 코인 관련 회사는 실적 진짜 …
Signed Pe Pe .dms
연준 결정 요약 (2026/7/29): 1. 연준, 5회 연속 회의에서 금리를 동결 2. 연준, 기준금리를 3.50%-3.75% 구간으로 유지하기로 9-3 표결 3. 해맥, 카슈카리, 로건, 금리 인상 지지하며 반대표 4. 연준, 불확실성에도 불구하고 경제 활동이 "건실한 속도"로 확대되고 있다고 밝혀 5. 연준, 일자리 증가가 "노동력과 보조를 맞추고 있다"고 언급 6. 연준, 2% 인플레이션 목표에 여전히 전념하고 있다고 밝혀 https://x.com/KobeissiLetter/status/2082527378312745188?s=20
Signed Pe Pe .dms
[CNBC] 연방준비제도, 금리 동결… 그러나 3명은 인상 찬성 • 연방공개시장위원회(FOMC)는 연방기금금리를 3.5%에서 3.75% 사이로 유지하기로 9대 3으로 표결했다. • 반대표를 던진 3명의 지역 연준 총재는 클리블랜드 연준의 베스 해맥, 미니애폴리스 연준의 닐 카슈카리, 댈러스 연준의 로리 로건으로, 이들은 이번 회의에서 연방기금금리 목표범위를 0.25%포인트 인상하는 방안을 선호했다. 🔗자세히 보기 🏦연준 관찰 📲앱 다운로드
Signed Pe Pe .dms
시타델은 이번 주 FOMC 깜짝 금리 인상 예상. https://x.com/Barchart/status/2081894358647812250?s=20
Signed Pe Pe .dms
미국 금리 인상 예상 확률 7월 36.3% 9월 80.4%
Signed Pe Pe .dms
이번 주 주요 이벤트: 1. 시장, 미국/이란 공습 중단 2. 7월 소비자 신뢰 지수 데이터 - 화요일 3. 7월 연준 금리 결정 - 수요일 4. 마이크로소프트, $MSFT, 메타, $META, 실적 발표 - 수요일 5. 7월 PCE 인플레이션 데이터 - 목요일 6. 애플, $AAPL, 아마존, $AMZN, 실적 발표 - 목요일 7. 7월 MI 소비자 심리 지수 데이터 - 금요일 8. 7월 MI 인플레이션 기대치 데이터 - 금요일 https://x.com/KobeissiLetter/status/2081376483705069752?s=20
Signed Pe Pe .dms
BitMEX 11년 이상의 운영 끝에 9월 23일 거래소를 폐쇄 예전엔 모두 비트맥스 썼지만 바이낸스와 다른 거래소들 많이 생기면서 경쟁력이.. https://x.com/CoinDesk/status/2080207059430129805?s=20
Signed Pe Pe .dms
오늘 새벽엔 구글 발표했고.. 내일은 인텔.. 담주에 큰거 온다.. https://www.instagram.com/p/DbFan_PICb6/
Signed Pe Pe .dms
상원 공화당이 암호화폐 시장 구조 법안의 새로운 초안을 발표 주요 포인트: 1. 대통령과 연방 관리들이 암호화폐 발행 또는 후원을 금지당합니다. 2. 자체 보관 보호 조항이 법안에 유지됩니다. 3. 개발자들이 송금인으로 취급되지 않습니다. 4. 거래소가 파산하더라도 당신의 암호화폐는 보호됩니다. 5. 스테이블코인 수익 규칙은 변경되지 않습니다. 발표 후 법안 통과 확률 48% -> 37% https://x.com/AshCrypto/status/2079967778610786713?s=20
Signed Pe Pe .dms
Showing the 12 most recent of 18 posts we hold for @channel_dms. 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 — 419,915 of 1,160,990entries 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.
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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“.dms” (@channel_dms), 2,064 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/channel_dms.
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.