https://x.com/pramod8393/status/2094263103290540152
Signed ⓅⓇⒶⓂⓄⒹ

Channel
@TSLCrypto
On this record: Topic · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
1,472subscribers
-10 since we began measuring on 3 September 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001201912848 |
|---|---|
| Type | Channel |
| Username | @TSLCrypto |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 3 September 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/TSLCrypto |
Other / unclassifiable — 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 26 September 2026 and assigned it the closest of 31 fixed categories, at 58% 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 |
|---|---|---|
| 26 Sept 2026, 11:58 | 1,472 | +1 |
| 17 Sept 2026, 04:21 | 1,471 | +4 |
| 12 Sept 2026, 18:20 | 1,467 | +3 |
| 9 Sept 2026, 03:14 | 1,464 | -18 |
| 3 Sept 2026, 10:45 | 1,482 | no change |
| 3 Sept 2026, 10:30 | 1,482 | first reading |
20 posts held, back to 15 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 1 page of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 31 August 2026 |
|---|---|
| Posts held | 20 (15 March 2026 – 31 August 2026) |
| Views total | 545 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 10:45 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.
https://x.com/pramod8393/status/2094263103290540152
Signed ⓅⓇⒶⓂⓄⒹ
https://x.com/prasadcrypto/status/2094148191696609493?s=20
Signed ⓅⓇⒶⓂⓄⒹ
https://x.com/solanabrokers Free mint
Signed ⓅⓇⒶⓂⓄⒹ
Still converting USDT through random OTC/P2P? 👀 Then wondering why your bank account got frozen? 💀 Try @RedotPay instead. url.hk/i/en/d9y0f 💳 Virtual Card → Swiggy, Zomato, Zepto, Flipkart & more 💵 Need cash? Get the physical card & withdraw from ATM ⚡ Spend your USDT directly for everyday payments Why deal with OTC headaches every time? USDT → INR → Spend. Simple. 🚀 Give @RedotPay a try 👀
Signed ⓅⓇⒶⓂⓄⒹ
https://x.com/i/status/2093218241032360389
Signed ⓅⓇⒶⓂⓄⒹ
A Free Tool to Find Tokens You Forgot You Had... DeFi Saver built Token Saver, a tool that scans your old DeFi smart wallets for any leftover tokens still sitting there. The best part is that it’s completely free. So far, the tool has found over $67M in unclaimed tokens across 87K smart wallets, including ETH, USDT, WBTC and more. These funds are usually leftovers from old DeFi positions, debt repayments, swaps o…
Signed ̷C̷̷r̷̷y̷̷p̷̷t̷̷o̷̷ ̷R̷̷o̷̷h̷̷i̷̷t̷
https://x.com/i/status/2080879377550922099 If you have funds, you can join Airdrop..
Signed ⓅⓇⒶⓂⓄⒹ
https://x.com/i/status/2079552487057731855
Signed ⓅⓇⒶⓂⓄⒹ
https://x.com/i/status/2079071961184076145 Follow x for more Updates
Signed ⓅⓇⒶⓂⓄⒹ
https://x.com/pramod8393/status/2078757477236220308?s=20
Signed ⓅⓇⒶⓂⓄⒹ
Earn 5$-15$/Day (Passive income - 0$ Investment) Daily $3K-$5K freee Bonus Distribution (crsh market) • Platform Link https://app.crshmarket.com/r/F7C27748 Dont Invest grab free bonus
Signed ⓅⓇⒶⓂⓄⒹ
https://waitlist.arcus.xyz/s/PAMS93 Connect the wallet you previously used for perp interactions. • Connect your X account and complete the follow tasks. • Invite at least 2-5 friends, or drop your referral link in the comments. Solid project Dont miss.
Signed ⓅⓇⒶⓂⓄⒹ
Showing the 12 most recent of 20 posts we hold for @TSLCrypto. 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.
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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“Silent Crypto Looters” (@TSLCrypto), 1,472 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/TSLCrypto.
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.