Channel
@bitupannouncement
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
11subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001629627715 |
|---|---|
| Type | Channel |
| Username | @bitupannouncement |
| Created | Between 1 October 2021 and 16 October 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/bitupannouncement |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 07:46 | 11 | no change |
| 7 Aug 2026, 01:24 | 11 | first reading |
20 posts held, back to 16 October 2021 — 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 8 April 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
The owner of this channel has been inactive for the last 18 months. If they remain inactive for the next 8 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 30 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
We’re back to 1Million MarketCap! Thanks to all the supporters that strong believe in the project and in the team. Buying the dip could be scary, especially in BSC nowadays, you have our respect. Who bought at 500k MCap now have doubled their capital. Now we are going back to 3M MCap, with the sureness to be one of the best community in the BSC. LET’S FUCKING GO.
We broke again 700k MCap! The best BSC community!!! We’re going back to previous MCap! 🚀🚀🚀🚀
Dip is being eaten! Congrats to strong believers
✨MarketCAP update: 589,906$ 💰Total supply: 140.4 million 📈Price in $$: 4.20 x 10⁻³$ 🔥Burned tokens: 15.7 million Updated at: 2021-10-21 16:12:01 UTC
Guys, the staff are still here. We won’t go anywhere, we’re keep working hard for make this project a great success. We’re just experiencing a dip, that is ABSOLUTELY normal. Doubt are legit, we’re here also for answer to them BUT, as always, remember that FUD will not be tolerated. Thanks.
EVERYONE! JOIN T.ME/AMACENTRAL AND VOTEEEEEEEEEEEEE https://t.me/BitUP_Official/76951
https://twitter.com/BitUPBSC/status/1449938053896753155?s=20
https://twitter.com/Bsc100x_gems/status/1449924230066307073
BitUP is flying, dips getting eaten fast! $16,000 buy just made it jump above $2M! Amazing article coming to Yahoo finance, Marketwatch, BitcoinInsider and 60 other news sites💹 Still trending on Dextools and voice chat has almost 100 people! LFG BTC on its way to break $65,000 🚀🚀 Unique reward vesting, if you sell you cannot receive rewards for 6 hours! This has allowed for diamond hands to hold the chart up and Bit…
THE GIVEAWAY IS STILL LIVE. 💹🔥 REMEMBER, SHILL UNDER THESE TWEETS + LIKE OUR COMMUNITIES TWEETS TO SUPPORT THEM! ALSO, SEND YOUR PROOF TO STONKS! https://twitter.com/BitUPBSC/status/1449910330176516098 https://twitter.com/Cryptic_Maestro/status/1449904113836249095 https://twitter.com/BitUPBSC/status/1449905184486871041 https://twitter.com/BitUPBSC/status/1449900787421831173
Showing the 12 most recent of 20 posts we hold for @bitupannouncement. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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.
@bitupannouncement named 5 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“BitUP - Announcement” (@bitupannouncement), 11 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/bitupannouncement.
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.