hashpwn - https://forum.hashpwn.net hashmob - https://hashmob.net hashkiller - https://hashkiller.io hashes . org (offline) crackstation - https://crackstation.net

Channel
Cold Wallets
@ColdWalletsBrute
On this record: Growth · Engagement · Posts · Cite this entry
3subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003235998060 |
|---|---|
| Type | Channel |
| Username | @ColdWalletsBrute |
| Created | Between 1 October 2025 and 27 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 29 August 2026 |
| On Telegram | t.me/ColdWalletsBrute |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 11:36 | 3 | -1 |
| 13 Aug 2026, 09:19 | 4 | no change |
| 7 Aug 2026, 18:33 | 4 | first reading |
Engagement
20 posts held, back to 27 October 2025 — 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 17 November 2025. An engagement rate over an empty window would be a number about nothing.
Recent posts
https://hashkiller.io/listmanager
https://github.com/hashpwn/rules
https://github.com/cyclone-github/hashes.com-escrow-tool
validalgs = { "0": "MD5", "10": "md5($plaintext.$salt)", "11": "Joomla < 2.5.18", "20": "md5($salt.$plaintext)", "21": "osCommerce, xt:Commerce", "50": "HMAC-MD5 (key = $plaintext)", "60": "HMAC-MD5 (key = $salt)", "100": "SHA1", "101": "nsldap, SHA-1(Base64), Netscape LDAP SHA", "104": "SHA1.Substr(0, 32)", "110": "sha1($plaintext.$salt)", "111": "nsldaps, SSHA-1(Base6…
"13100": "Kerberos 5 TGS-REP etype 23", "13200": "AxCrypt", "13300": "AxCrypt in-memory SHA1", "13400": "KeePass 1 (AES/Twofish) and KeePass 2 (AES)", "13600": "WinZip", "13800": "Windows Phone 8+ PIN/plaintext", "13900": "OpenCart", "14400": "sha1(CX)", "14600": "LUKS", "14700": "iTunes backup < 10.0", "14800": "iTunes backup >= 10.0", "15200": "Blockchain, My Wallet, V2",…
https://hashmob.net/resources/hashmob
https://github.com/bee-san/Search-That-Hash
https://github.com/s0md3v/Hash-Buster
https://weakpass.com
https://weakpass.com/wordlists/hashkiller.dic
https://hashes.com/en/johntheripper
Showing the 12 most recent of 20 posts we hold for @ColdWalletsBrute. 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.
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 29 August 2026 — this entry's latest reading, not the date you are reading this.
“Cold Wallets” (@ColdWalletsBrute), 3 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/ColdWalletsBrute.
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.