Telegram RegisterThe public register of Telegram

Channel

수스의 비밀 메모장

@SUS_secretnote

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

3,776subscribers

-10 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-1001631164900
TypeChannel
Username@SUS_secretnote
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/SUS_secretnote

Growth

3,7763,7863,7816 August 2026 — 3,786 subscribers6 August 2026 — 3,786 subscribers6 August 2026 — 3,784 subscribers9 August 2026 — 3,781 subscribers12 August 2026 — 3,776 subscribers6 August 202612 August 2026
5 measurements spanning 6 days, net -10. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 3,775–3,788 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 11:243,776-5
9 Aug 2026, 12:383,781-3
6 Aug 2026, 19:253,784-2
6 Aug 2026, 04:313,786no change
6 Aug 2026, 02:033,786first reading

Engagement

20 posts held, back to 10 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 4 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
19.5%
avg views ÷ 3,776 subscribers
Avg views / post
736
16 posts measured
Reaction rate
0.305%
reactions ÷ views · ER floor
Posts in window
16
of 20 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 7 of 16 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held20 (10 July 20266 August 2026)
Views total11,779
Reactions total16
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 06:13 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.

Reaction mix

16 reactions across 7 posts, in 4 distinct kinds. The most used accounts for 56.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
956.3%
🔥318.8%
👍212.5%
😢212.5%

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 9 of the 20 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 20reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 10 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.

Recent posts

6 Aug 2026, 13:50 UTC139 viewsread 8 August 2026
Forwarded from @yeouidobi

정말 도움을 요청드리고 싶어 이렇게 올립니다. 정말 무거운 마음으로 이 글을 올리게됩니다. 저희 아버지는 대형회사에서 IT담당 임원으로 계십니다. 메모리가격 인상에 따라 계약을 재체결하는 과정에서 높은가격으로 재 계약을 진행하는 과정에서 제대로 이전 계약 마무리가 제대로 되지 못하고 진행이됨과 함께 최종 결재자가 되시면서 감사에서 계속해서 회사에 수백억에 가까운 손해를 입혔다고 압박을 받으시는것 같습니다. 결론이 나지 않았지만 수백억을 추징을 당할 수 있다는 압박감에… 좋지못한 선택을 시도하셨습니다. 혹시 이와관련하여 상담을 할 수 있거나 관련 전문가를 알고 계신분이 있다면 지나치치지마시고 한번만이라도 조언을 주시면 너무나도 감사하겠습니다. 제가 지금 당장 못하더라도 꼭 평생에 걸쳐서라도 보은하겠습니다 @netdebtzer0 로 연

6 Aug 2026, 04:56 UTC277 viewsread 8 August 2026
Forwarded from @WeCryptoTogetherPhoto

🇰🇷 조세형평성을 상실한 징벌적 가상자산 과세 유예 및 재검토 요청에 관한 청원 동의하러 가기 소귀에 경을 읽으면 소가 열반에 들 수도 있어.

1 Aug 2026, 01:21 UTC639 views2 reactionsread 8 August 2026
Forwarded from @BChoSNPhoto

Bitmart 직원이 폭로하는 뱅크런 과정 출처 1. 4월 카피 트레이딩 사기 사건으로 대거 손실 2. 6월 첫번째 해고 물결, 고액 자산가들 인출 시작 3. 대규모 출금이 승인 안되기 시작 4. 399일 연이율 12% 원금 보장 상품 출시 5. 7월 이율 18.88%로 상승, 10일로 기한 축소 6. 이율 상승한 날 거래소 토큰 폭락 시작 7. 7월 24일 투자상품 환매 버튼 제거, 1만달러 이상 출금 거절 8. 7월 25일 공지사항 게시판 폐쇄, 직원 권한 전부 회수 9. 7월 31일 출금 최소 금액 100불, 수수료 10%로 상향 10. 고위 임원들은 Wooxpro 거래소로 이동 중

1👍1

30 Jul 2026, 06:39 UTC594 views4 reactionsread 8 August 2026
Photo

🚨빗썸 고객확인 서류를 모두 제출했지만 서비스 이용제한(영구정지) 예정 통보를 받았습니다. ✍️한 줄 요약 반복적인 코인 출금으로 고객확인 요청 및 출금정지 조치를 받은 후 요청받은 모든 서류를 제출했지만, 추가 소명 기회 없이 '자금출처 확인 불충분'을 이유로 1개월 후 빗썸 서비스 이용제한(영구정지) 예정 통보를 받았습니다. 📅진행 경과 6월 30일: 반복적인 코인 출금 관련 1차 주의 안내 문자 수신 7월 1일: 반복적인 코인 출금 관련 2차 주의 안내 문자 수신 7월 3일: 고객확인 요청 및 출금정지 안내 문자 및 메일 수신 7월 6일: 추가 서류 제출 요청 안내 메일 수신 7월 7일: 모든 서류 제출 완료 7월 24일: 자금출처 확인 불충분을 이유로 1개월 후 빗썸 서비스 이용제한(영구정지) 예정 안내 메일 수신 💰거래 방식 및

🔥2😢2

28 Jul 2026, 09:37 UTC≈1,020 views3 reactionsread 8 August 2026

✍️ - 업비트는 소명 될때까지 자료 요청하고 최대한 정지 안시키려고 하는 반면에 - 빗썸은 출금 좀 치는 사람들한테 무차별 경고 문자와 칼 정지 사례가 많은거 같네요 ㄷㄷ - 빗썸에 경고 문자(출금, 정지 등등) 받거나 궁금하신분들 아래 링크로 가셔서 정보 얻으시면 좋으거 같네요 👉https://t.me/+OY9jiRUN_B80NzA9

2🔥1

28 Jul 2026, 05:29 UTC533 viewsread 8 August 2026
Forwarded from @emperorcoinPhoto

향후 5년 폐쇄 가능성이 높은 거래소 어느 중국인이 만든 건데 한국어로 번역했습니다. 높은 위험은 일단 빼시는게.. #거래소

27 Jul 2026, 13:36 UTC476 views1 reactionsread 8 August 2026
Forwarded from @allpointsareminePhoto

출금하려던 코인의 스테이킹 이율은 연 15%가 넘음. 정상적으로 출금해 두 달간 스테이킹했다면 약 3%의 수익을 얻을 수 있었던 셈. 솔직히 그냥 출금해서 메울까 수도 없이 고민했지만, 텔그에 글을 올린 것도 있고 ‘내가 왜 손해를 봐야 하지?’라는 생각에 꾹 참고 버팀. 금감원에서도 해결되지 않으면 민사소송까지 가야 하니 1~2년 정도는 각오하고 있었는데, 다행히 원만하게 처리되어 출금액에서 단 한 푼도 손해 보지 않고 출금할 수 있게 됨. 물론 이것이 정말 ‘잘 처리된 것’인지는 의문임. 두 달간 발생한 손해는 결국 온전히 내 몫이었기 때문. 부당한 대우에 침묵하면, 부당함은 결국 관행이 됨. 조금이나마 횡포에 제동을 걸었다는 데 의미를 두려 함. 민원을 넣는 과정도 참 번거로웠는데… 함께하신 분들 모두 수고하셨습니다. (참고로

1

26 Jul 2026, 15:52 UTC754 views2 reactionsread 8 August 2026
Forwarded from @qtrealm

그나저나 빗썸은 진짜 호되게 혼 좀 났으면..

2

26 Jul 2026, 02:17 UTC862 viewsread 8 August 2026

✍️ - 출금 문제로 이슈가 있었던 비트마트가 결국.. - 하락장이라 그런지 거래소들이 하나 둘씩 사라지네요 ㅠㅠ

26 Jul 2026, 00:06 UTC≈1,220 viewsread 8 August 2026
Photo

✅ 업비트 스테이블 코인 거래 수수료 무료 ✍️ - 작년 11월에 0.01% 이후로 다시 수수료 이벤트 하네요 - 이제 빗썸도 비슷하게 나오겠군요 - 근데 빗썸 출금 수수료 1%는 언제 없어지려나 ㄷㄷ 🗓 기한 ~ 8/2일 23시 59분

23 Jul 2026, 12:59 UTC633 viewsread 8 August 2026
Forwarded from @yobeullyANNPhoto

✈️ 설정 -> 고급 -> 미디어 자동 다운로드 개인 대화 & 그룹 & 채널 (자동으로 다운로드 끄기)

22 Jul 2026, 15:26 UTC864 views3 reactionsread 8 August 2026
Forwarded from @ksoon77Photo

https://x.com/ksssoon/status/2079834083589587012?s=20 시간나실때 한번 읽어주시면 감사하겠습니다.

2👍1

Showing the 12 most recent of 20 posts we hold for @SUS_secretnote. 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 — 303,468 of 1,151,006entries 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

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.

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.

“수스의 비밀 메모장” (@SUS_secretnote), 3,776 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/SUS_secretnote.

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.