Channel
@STRONGBETCRYPTO
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
3,412subscribers
+97 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002091223576 |
|---|---|
| Type | Channel |
| Username | @STRONGBETCRYPTO |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/STRONGBETCRYPTO |
Crypto & trading — 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 14 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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 |
|---|---|---|
| 17 Sept 2026, 06:16 | 3,412 | +8 |
| 13 Sept 2026, 12:56 | 3,404 | +10 |
| 9 Sept 2026, 16:36 | 3,394 | +66 |
| 4 Sept 2026, 05:36 | 3,328 | -1 |
| 1 Sept 2026, 04:18 | 3,329 | -2 |
| 29 Aug 2026, 14:02 | 3,331 | +2 |
| 26 Aug 2026, 14:07 | 3,329 | +1 |
| 23 Aug 2026, 07:47 | 3,328 | +28 |
| 20 Aug 2026, 05:55 | 3,300 | -6 |
| 17 Aug 2026, 10:04 | 3,306 | -2 |
| 13 Aug 2026, 13:48 | 3,308 | -3 |
| 10 Aug 2026, 19:12 | 3,311 | -5 |
| 7 Aug 2026, 17:24 | 3,316 | +1 |
| 7 Aug 2026, 02:15 | 3,315 | no change |
| 7 Aug 2026, 02:03 | 3,315 | first reading |
20 posts held, back to 31 March 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 3 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 31 July 2026. An engagement rate over an empty window would be a number about nothing.
174 reactions across 16 posts, in 8 distinct kinds. The most used accounts for 40.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 71 | 40.8% | |
| 🔥 | 57 | 32.8% | |
| 👍 | 31 | 17.8% | |
| 🤡 | 5 | 2.87% | |
| 💩 | 4 | 2.30% | |
| 🖕 | 3 | 1.72% | |
| 👏 | 2 | 1.15% | |
| 💯 | 1 | 0.575% |
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 17 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 174 reactions 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 31 March 2026 to 31 July 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://m.chzzk.naver.com/live/4b833ff9c48592929204e88b26ace362
❤2👍1
아이번달 빅테크실적만 봐야대는줄알았더니 메모리쟁이들의 엄청난이벤트가있었넹 cxmt 예상 상장일은 7월 27일이라고 어제뉴스떴고 공모가도 확정됐다?네? 우리는 cxmt ipo때 못참여하니까 뭘해야할까요~ 얼마전 미래에셋 레포트는 대략 $200b(300조원) 내외 밸류로 보고있는거같더라공 다른데는 최대 600조원까지도보는듯ㄷㄷ 어떤용감한 증권사는 60조원이래 근데 60이든 600조원이든 이건좀~ 얼마나 빅이벤트냐면 커촹반 중국의 나스닥 1위 시총이 구글검색상 180조원 내외인데 그거 나오자마자 따잇하느냐마냐 수준의이벤트네ㄷㄷ 나도 메모리조금있는 주식하는상놈이니까 IPOP 나오기전까지 열심히공부해두고 나오면 사이즈실어서 잔뜩참여해보고싶오
👏2❤1
https://x.com/LikeMJ5/status/2066507287871807904?s=20
https://x.com/LikeMJ5/status/2066493309909147662?s=20
👍3
https://m.chzzk.naver.com/live/4b833ff9c48592929204e88b26ace362
👍3
AQAv2 = Aligned Quote Asset v2 이게 무슨내용이냐 (다소 의역) 하이퍼리퀴드는 기존에 usdh같은거 자체 스테이블 코인 만들어 쓸라다가 코인베이스랑 쇼부쳐서 USDC 쓰기로 마음먹고 usdh 천천히 버림 대신에 USDC 유저들이 보유함으로서 오는 이자수익의 90%를 어시스턴트 펀드로 들어감 이게 보통 바이백에 쓰일예정
❤8👍1
https://t.me/mlmonchain/1356 하리는 이제 오피셜리하게 aqav2로 하루에 대충 50만달러 전후로 바이백추가 대충 현 바이백추세에서 20%이상 가속화
❤4
쓰레기 기득권집단 선관위 해체해라
🔥57❤11
crypto를 믿는다는건 이런 억까랑 싸우는 영원한 굴레다 난 진짜 근2년동안 수도없이 당해왔다 트럼프 erc-20 들고있을때 생각난다 비트코인도 마찬가지고 하이퍼리퀴드도 마찬가지고 지캐시가 정말로 이중지불문제로 문제가 생겼으면 작년 여름 가을때부터 있었던 T 주소 -> 쉴드풀에서 생기는 이동량 아니면 전체 유통량 현재 1700만개 정도되는 이 숫자에서 문제가 생기거나 그 이후 쉴드풀에 비정상적인 형태의 증가량이 존재할텐데 그런게 안보임 그냥 팀이 보안문제 찾아내서 리포트올리고 해결한건데 사람들은 자극적으로 이중지불 취약점 exploit이러면서 자극적인 FUD를 퍼트린다 근데 zooko는 원론적인 이야기도 좋지만 이런거에대해서 어느정도 설명을 해놔야지 이런 부류의 인간들은 그런걸 못한다
❤16💩3🖕1
0. 며칠전 지캐시 orchard 풀이 멈췃다는 제보가 있었음 1. 금방 복구되고 다시 정상되고 없던일 처럼 분위기는 흘러감 2. 지캐시에는 모든게 공개된 t 주소라는 Transparent Pool 이라는 개념이있고 프라이버시를 실현하는 Orchard Pool (shield pool)이 존재함 3. 지캐시는 계속해서 업그레이드하고 취약점을 찾아내는 과정에서 최근 Taylor Hornby 라는 보안 전문가가 팀에 합류하면서 취약점을 opus 4.8의 도움을 받아서 발견함 3.1 취약점은 쉽게말해 이중지불 문제로 내가 a->b a->c 이런식으로 붙여넣기가 아닌 복사를 했을 가능성임 4. 문제는 지캐시의 쉴드풀의 특성상 비트코인과 다르게 비트코인은 공개원장이기때문에 문제가 생겼으면 악용한 지갑이 추적이 가능한데 지캐시 쉴드풀은 반…
❤4🖕2👍1💩1
Bye bag의 힘 코인도풀렸고 가격도 1년전 고점보다 20%정도 비싸졌지만 바이백으로 유통량이 줄어들어서 전체 시총은 이제 그때 쯤 따라갔음
👍4
Showing the 12 most recent of 20 posts we hold for @STRONGBETCRYPTO. 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.
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.
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 2 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“강승부 크립토 2.0” (@STRONGBETCRYPTO), 3,412 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/STRONGBETCRYPTO.
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.