Channel
@ttdclient
On this record: Growth · Engagement · Posts · Telegram's recommendations · Cite this entry
312subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001419319458 |
|---|---|
| Type | Channel |
| Username | @ttdclient |
| Created | Between 1 April 2019 and 31 October 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 27 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 27 August 2026 |
| On Telegram | t.me/ttdclient |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 01:05 | 312 | -1 |
| 14 Aug 2026, 09:35 | 313 | -1 |
| 8 Aug 2026, 07:35 | 314 | no change |
| 7 Aug 2026, 11:16 | 314 | first reading |
20 posts held, back to 19 November 2024 — 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 20 posts for this entry, the most recent from 20 May 2025. An engagement rate over an empty window would be a number about nothing.
Client version 71.1 has been release on all platforms. It is a client and server side change that adds live range progress and client speed data to the server in 5 minute intervals. This will allow the server to have a more accurate pool speed and allow you to monitor your clients more reliably. I do recommend that you have every instance of the client running a unique WorkerName. Everything will still work if yo…
71 Pool is officially up and running. I think I have most of the cosmetic issues corrected now. Let me know if you see anything wrong. This is going to be a long one so strap in.
Channel name was changed to «ttdclient 71bit pool»
Channel photo updated
The 69 Bit pool is up and running. I am sure there are some bugs here and there so just let me know and I will get them taken care of. Happy cracking!
Channel photo updated
Channel name was changed to «ttdclient 69bit pool»
AU-BONUS account created. Maxi has donated his 24,521 ranges that I put into an account to be split accordingly with any active users at the time the key is found (Assuming we find it). So think of it as an Active User Bonus.
New client is up with much improved speed thanks to fixedpaul. Also added pause feature to windows version by pressing 'p'
Custom builds to work with 50xx now in download section. Now tested on vast with a 5090. Also the clore and vast scripts have been modified to download the appropriate version if you are trying to use a 5070 5080 or 5090 card.
Pool 68 is now up and running. Let me know if you notice anything I may have forgotten. https://www.ttdsales.com/68bit/
Channel name was changed to «ttdclient 68bit pool»
Showing the 12 most recent of 20 posts we hold for @ttdclient. 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.
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 27 August 2026 — this entry's latest reading, not the date you are reading this.
“ttdclient 71bit pool” (@ttdclient), 312 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/ttdclient.
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.