Channel
@Primocryptosignal
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
65subscribers
-4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001561961206 |
|---|---|
| Type | Channel |
| Username | @Primocryptosignal |
| Created | Between 1 August 2021 and 22 June 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 9 October 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 9 October 2026 |
| On Telegram | t.me/Primocryptosignal |
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 28 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 9 Oct 2026, 14:57 | 65 | -1 |
| 14 Sept 2026, 12:16 | 66 | -1 |
| 6 Sept 2026, 13:59 | 67 | -1 |
| 23 Aug 2026, 15:45 | 68 | -1 |
| 10 Aug 2026, 00:16 | 69 | no change |
| 7 Aug 2026, 04:52 | 69 | first reading |
20 posts held, back to 22 June 2022 — 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 page 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 27 June 2022. An engagement rate over an empty window would be a number about nothing.
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 2 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 3 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 22 June 2022 to 27 June 2022, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Okay I have a lesson for you, as I said this person told me about the liquidation with 40x leverage. I ask him how much is in your futures wallet? He answered... $300 and he invested more than $20 with a leverage effect of 40. Here the scenario is that, now, he will be liquidated easily. I generally recommend to the person with $300-500 in futures portfolio is that not to invest more than $2-3 per trade for secure tr…
One of you is sending me a message that if he opens a trade with 40X, it will be easy for him to liquidate. I think some of you may not know how much you would have to open a trade for. It's one of the more important things for the futures. So from now, I'm not going to talk about the leverage that you should be using because I personally don't know how much you have in your portfolio. These are usually things I tea…
❤1
if btc hit his own sl we are going to close this.
Blz/Usdt Long Current: 0.0963 T1: 0.0981 T2: 0.1000 T3: 0.1030 T4: 0.1062 trade size and Lev upto u
And this
Close this
Give you some trades to invest in.
In fact, so far, there has been no result. Nobody wins. Considering the current scenario, we will reach 24k over the next few days.
Guys, we've got an update. i long the btc from here , currently 21345 . We have a target of 24,000. Let's see what my analysis tells us once we hit 24k. Please note, sl is 20700. R GUY
Bull try hard, now it's time for the bear show
It's more likely that the bear wins. Your friend, R GUY
For now we are moving towards 19800
Showing the 12 most recent of 20 posts we hold for @Primocryptosignal. 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.
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 9 October 2026 — this entry's latest reading, not the date you are reading this.
“Binance Signals by R Guy!” (@Primocryptosignal), 65 subscribers as measured 9 October 2026. Telegram Register, tgregister.com/channel/Primocryptosignal.
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.