یکشنبه هست و بازار در حالت رنج شاید بهتر باشه بدون سود و زیان ببندیم !!!

Channel
BitMex & Binance Signal
@HiMyCrypto
On this record: Growth · Engagement · Posts · Citations · Cite this entry
266subscribers
-2 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001424455000 |
|---|---|
| Type | Channel |
| Username | @HiMyCrypto |
| Created | Between 1 April 2019 and 7 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 27 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 27 August 2026 |
| On Telegram | t.me/HiMyCrypto |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 22:02 | 266 | -1 |
| 20 Aug 2026, 07:11 | 267 | -2 |
| 12 Aug 2026, 18:24 | 269 | +1 |
| 7 Aug 2026, 00:31 | 268 | no change |
| 6 Aug 2026, 15:55 | 268 | first reading |
Engagement
17 posts held, back to 7 August 2021 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 17 posts for this entry, the most recent from 16 October 2022. An engagement rate over an empty window would be a number about nothing.
Recent posts
#BTC Long 19150 Lev Max 10x R/R = 3 Max 5% Cap TP 19860 TP 20250 Stop 18830 - همانطور که ملاحظه میکنید ، کندل های صعودی قدرتمند و به دنبال آن کندلهای اصلاحی با کاهش حجم معاملات رو داریم . یکبار TP1 سفارشات کامل شده پس TP2 می تواند دست یافتنی باشد . @HiMyCrypto
🚀🚀 Spot Signal Report 🚀🚀 29-30-31 Sep ✅ BNB +35% ✅ SOV +100% ✅ BZRX 20% Congratulations VIP membership با ما همراه باشید . عذر می خوام که در عمومی زیاد فعالیت نداریم . 😉 🌐We are HiMyCrypto Fewer Signal Better profits in @HiMyCrypto
🚀🚀 One Chart and Other profits ✅ BTC 2/3 Targets Done !! +70% on 10X Lev !! البته خروج موقت !!! سیگنالهای دیگه به همراه چارت امروز صادر شد !! موفق و پیروز باشید @HiMyCrypto
#SUSHI USDT 👉Set orders Long : 11.0 10.1 🎯 Targets: 13.2 , (16.2) ⭕️Stop : 9.8 @HiMyCrypto
🚀🚀 BooM BooM ✅ 2/2 Targets Done ! +45% Profits in Spot in 3 Days +200% in 5X Lev Low Signal Good Profits In @HiMyCrypto
👇Report Signal Spot & Futures👇
My Idea for Possible #BTC Movement https://www.tradingview.com/x/ufTtsAC2/
👉 you Can Close Short in Low LOSSes We ReEnter again ... Waiting for good time ... @HiMyCrypto
👇Free Futures Signal👇
#BTC Futures 👉Set orders Short: 47900 🎯 Targets: 47000 , 46100 , (44700) Max LEV : 10X Use Low balance ⭕️STOP : 48900 @HiMyCrypto
👉 BoooooM ✅ BTC 49500 .... Close Long Position Just an idea ... @HiMyCrypto
Showing the 12 most recent of 17 posts we hold for @HiMyCrypto. 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 — 965,593 of 1,624,174entries 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.
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 27 August 2026 — this entry's latest reading, not the date you are reading this.
“BitMex & Binance Signal” (@HiMyCrypto), 266 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/HiMyCrypto.
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.