Telegram RegisterThe public register of Telegram
Telegram profile photo for HashUp TX

Channel

HashUp TX

@hashup_tx

On this record: Growth · Engagement · Posts · Cite this entry

408subscribers

-29 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-1003073810334
TypeChannel
Username@hashup_tx
CreatedBetween 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live29 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/hashup_tx

Growth

408437422.57 August 2026 — 437 subscribers8 August 2026 — 437 subscribers15 August 2026 — 427 subscribers23 August 2026 — 412 subscribers29 August 2026 — 408 subscribers7 August 202629 August 2026
5 measurements spanning 22 days, net -29. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 404–441 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 18:16408-4
23 Aug 2026, 07:44412-15
15 Aug 2026, 16:49427-10
8 Aug 2026, 05:16437no change
7 Aug 2026, 21:19437first reading

Engagement

20 posts held, back to 5 March 2026the 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 6 March 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

6 Mar 2026, 21:01 UTC351 viewsread 8 August 2026

✅ Successful Withdrawal 💸 Amount: 0.01 DOGE ($0.00) 🌐 Network: Dogecoin Network 👨‍💻 User: Fahim khan 🆔 Hash: eb969b9625...6bae #Withdrawal@hashup_tx #Dogecoin_Network@hashup_tx #DOGE@hashup_tx

6 Mar 2026, 20:24 UTC337 views0 reactionsread 8 August 2026

✅ Successful Withdrawal 💸 Amount: 0.01 DOGE ($0.00) 🌐 Network: Dogecoin Network 👨‍💻 User: Muhmammad Arif 🆔 Hash: bd6cd80822...1ef4 #Withdrawal@hashup_tx #Dogecoin_Network@hashup_tx #DOGE@hashup_tx

6 Mar 2026, 20:10 UTC324 viewsread 8 August 2026

🔥 Successful Purchase 🛍 Hashrate: 1000 💸 Amount: 0.18682 LTC ($10.00) 🌐 Network: Litecoin Network 👨‍💻 User: Igorvidal66 🆔 Hash: 7ce46e1d16...4119 #Purchase@hashup_tx #Litecoin_Network@hashup_tx #LTC@hashup_tx

6 Mar 2026, 14:55 UTC282 viewsread 8 August 2026

🔥 Successful Purchase 🛍 Hashrate: 170 💸 Amount: 0.03156 LTC ($1.70) 🌐 Network: Litecoin Network 👨‍💻 User: Abhijith M 🆔 Hash: 2d87bcbeb5...4861 #Purchase@hashup_tx #Litecoin_Network@hashup_tx #LTC@hashup_tx

6 Mar 2026, 14:54 UTC243 viewsread 8 August 2026

🔥 Successful Purchase 🛍 Hashrate: 2000 💸 Amount: 20.99 USDT ($20.00) 🌐 Network: Binance Smart Chain 👨‍💻 User: AGBERE KOMI 🆔 Hash: 0xd89772a2...9135 #Purchase@hashup_tx #Binance_Smart_Chain@hashup_tx #USDT@hashup_tx

6 Mar 2026, 13:37 UTC185 viewsread 8 August 2026

🔥 Successful Purchase 🛍 Hashrate: 110 💸 Amount: 1.1 USDC ($1.10) 🌐 Network: Ethereum Network 👨‍💻 User: Alfredo Garces 🆔 Hash: 0xdc6bd766...e8ba #Purchase@hashup_tx #Ethereum_Network@hashup_tx #USDC@hashup_tx

6 Mar 2026, 13:29 UTC124 viewsread 8 August 2026

🔥 Successful Purchase 🛍 Hashrate: 500 💸 Amount: 0.007838 BNB ($5.00) 🌐 Network: Binance Smart Chain 👨‍💻 User: William Soares 🆔 Hash: 0xdd0c788d...f2f3 #Purchase@hashup_tx #Binance_Smart_Chain@hashup_tx #BNB@hashup_tx

6 Mar 2026, 11:17 UTC110 viewsread 8 August 2026

🔥 Successful Purchase 🛍 Hashrate: 1000 💸 Amount: 10 USDT ($10.00) 🌐 Network: Ethereum Network 👨‍💻 User: ATL 🆔 Hash: 0x3788da49...3902 #Purchase@hashup_tx #Ethereum_Network@hashup_tx #USDT@hashup_tx

6 Mar 2026, 10:35 UTC97 viewsread 8 August 2026

🔥 Successful Purchase 🛍 Hashrate: 1000 💸 Amount: 34.87966 TRX ($10.00) 🌐 Network: Tron Network 👨‍💻 User: Samborejo Batucada 🆔 Hash: fd9eebeeda...2f98 #Purchase@hashup_tx #Tron_Network@hashup_tx #TRX@hashup_tx

6 Mar 2026, 09:53 UTC95 viewsread 8 August 2026

✅ Successful Withdrawal 💸 Amount: 0.165368 TRX ($0.05) 🌐 Network: Tron Network 👨‍💻 User: Chidera Onyekere 🆔 Hash: a871e4df78...b2bf #Withdrawal@hashup_tx #Tron_Network@hashup_tx #TRX@hashup_tx

6 Mar 2026, 08:05 UTC92 viewsread 8 August 2026

✅ Successful Withdrawal 💸 Amount: 0.31124 TRX ($0.09) 🌐 Network: Tron Network 👨‍💻 User: OrangeKitty 🆔 Hash: bac0308b62...213e #Withdrawal@hashup_tx #Tron_Network@hashup_tx #TRX@hashup_tx

6 Mar 2026, 07:20 UTC86 viewsread 8 August 2026

✅ Successful Withdrawal 💸 Amount: 0.032758 USDT ($0.03) 🌐 Network: Binance Smart Chain 👨‍💻 User: Karen 01 🆔 Hash: 0x71475b2f...d1d7 #Withdrawal@hashup_tx #Binance_Smart_Chain@hashup_tx #USDT@hashup_tx

Showing the 12 most recent of 20 posts we hold for @hashup_tx. 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.

“HashUp TX” (@hashup_tx), 408 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/hashup_tx.

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.