Channel
@solidityofficialchannel
On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
957subscribers
-19 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002097152306 |
|---|---|
| Type | Channel |
| Username | @solidityofficialchannel |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 11 September 2026 |
| On Telegram | t.me/solidityofficialchannel |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 14:19 | 957 | -9 |
| 2 Sept 2026, 14:37 | 966 | -4 |
| 27 Aug 2026, 05:25 | 970 | -3 |
| 15 Aug 2026, 02:38 | 973 | -3 |
| 8 Aug 2026, 00:46 | 976 | no change |
| 7 Aug 2026, 14:52 | 976 | first reading |
20 posts held, back to 13 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 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 2 August 2026. An engagement rate over an empty window would be a number about nothing.
205 reactions across 20 posts, in 10 distinct kinds. The most used accounts for 44.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 92 | 44.9% | |
| 👏 | 51 | 24.9% | |
| 👍 | 34 | 16.6% | |
| 🔥 | 13 | 6.34% | |
| 👌 | 5 | 2.44% | |
| 🤩 | 5 | 2.44% | |
| 🥰 | 2 | 0.976% | |
| 🎉 | 1 | 0.488% | |
| 🏆 | 1 | 0.488% | |
| 🤝 | 1 | 0.488% |
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 20 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 205 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 13 July 2026 to 2 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.
Ciao a tutti, voglio condividere il consuntivo del mese, ragionando come sempre sui dati, su un capitale standard di 500€ per strategia. AUDCAD +6.86% GBPNZD +2.55% EURCHF −5.61% Su 1.500€ complessivi, l'ecosistema chiude a +1.27% (+19€). Qui il dato interessante non è il numero in sé, ma il comportamento della struttura. EURCHF ha avuto un mese negativo, eppure AUDCAD e GBPNZD hanno tenuto e riportato il netto i…
❤13👌3👏3
Ciao a tutti, vi aggiorno su quanto accaduto ieri su EURCHF. Dopo aver aperto tutte le operazioni disponibili, il software ha deciso di chiudere in perdita, in seguito a un movimento contrario alle nostre posizioni sell: il prezzo ha continuato a salire. Questo modus operandi è stato implementato per la salvaguardia e la tutela del capitale. Come vi ho comunicato in questi giorni, la perdita può arrivare con una pe…
👏6👍3
Ciao a tutti, raccolgo qui le domande che mi avete fatto (o che vi fareste) sul nuovo GBPNZD. "GBPNZD è la strategia andata peggio in live. Perché rilanciarla?" Perché il problema non era la pair, era il sistema. E non ve lo dico per fede: il vecchio GBPNZD di stop ne ha presi due, marzo 2025 e gennaio 2026, e sono andato a guardare, dati alla mano, come il nuovo sistema attraversa in backtest esattamente quei due …
❤9👏1
Video, posted without a caption
👏6🏆1👍1
La strada da qui: trio completo, ora si punta al recupero
❤6🤩1
Quanto rischia davvero: esposizione massima 0,13 lotti in 13 anni e mezzo
❤6
Due metà dello storico, entrambe in utile
❤6🎉1
Gennaio 2026: il secondo stop (−40% live), il nuovo chiude a +33,70€
❤4👏1🔥1
Marzo 2025: il mese del primo stop del vecchio (−29% live), il nuovo chiude a +33,35€
❤5👍1🔥1
Backtest completo 2013-2026: +3.157€, stop di protezione mai toccato
❤7🤩1
Ciao a tutti, come confermato, lunedì entra in funzione il nuovo GBPNZD 🇬🇧🇳🇿 E con lui, il trio torna al completo. Anche questa volta non mi limito a mostrarvi il risultato finale, vi racconto come ci sono arrivato, perché su questa pair sentivo di doverlo fare ancora di più. GBPNZD è stata la strategia più in difficoltà di tutto l'ecosistema, non lo nascondo e non lo cancello: il live è lì, pubblico, con i suoi num…
❤14👏2
ci siamo...
🤩3👌2🤝1
Showing the 12 most recent of 20 posts we hold for @solidityofficialchannel. 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.
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.
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 1 seed channel's Telegram-generated recommendation list 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 11 September 2026 — this entry's latest reading, not the date you are reading this.
“Solidity Trading” (@solidityofficialchannel), 957 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/solidityofficialchannel.
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.