Telegram RegisterThe public register of Telegram

Channel

BugBo Meme Token

@BugBoToken

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

21subscribers

+0 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-1002078106863
TypeChannel
Username@BugBoToken
DescriptionWelcome to $BUGBO $BUGBO Token: Making Crypto Go Bug-eyed with Excitement! https://www.Bugbo.xyz/
Created9 February 2024measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
On Telegramt.me/BugBoToken

Growth

217 August 2026 — 21 subscribers11 August 2026 — 21 subscribers7 August 202611 August 2026
2 measurements spanning 4 days. 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 20–22 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 14:0221no change
7 Aug 2026, 12:0921first reading

Engagement

18 posts held, back to 9 February 2024the 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 18 posts for this entry, the most recent from 11 September 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
4
Links
9

Lifetime counters from Telegram’s own channel header, read 11 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.

Recent posts

11 Sept 2025, 01:03 UTCviews —

The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 20 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

9 Feb 2024, 18:39 UTC574 viewsread 11 August 2026
Forwarded from @BuyBotTracker

🔶 Bugbo Entered BSC TRENDING! Token: 0xa90711721fabf21f4b82101c6e7e065e6f7828bb Group: BugBo Token 🦎 Chart 🔵 Trade 🤖 Snipe 🔶 Trending

9 Feb 2024, 18:35 UTC603 viewsread 11 August 2026
Photo

BugBo Token is being protected by @Safeguard Click below to verify you're human

9 Feb 2024, 18:02 UTC553 viewsread 11 August 2026
Photo

🚀 Big News! 🚀 Bugbo is now listed on AVE ! 🎉 Join us as we explore new horizons together! 🌟 #BugboOnAVE 🐞 https://ave.ai/token/0xa90711721fabf21f4b82101c6e7e065e6f7828bb-bsc

9 Feb 2024, 17:53 UTC310 viewsread 11 August 2026
Photo

⚡️ 月兔雷霆 - Moontok Xpress - 🔶 x.com/moontoklisting/status/1756013367536570540 🏆 代币 Coin: Bugbo ($BUGBO) | 电报群 Telegram (英) 🖥 合约 CA: 0xa90711721fabf21f4b82101c6e7e065e6f7828bb 🕯 池子 LIQ / 市值 MC: $3,255 / $5,032 🐇 Moontok.io | 🐰 Trending @Moonspace | @Moontalk | X 免责声明 Disclaimer

9 Feb 2024, 17:42 UTCviews —

BugBo Meme Token pinned «📨 NTM.ai Express Listing - Binance Smart Chain Coin: Bugbo (BUGBO) Contract: 0xa90711721fabf21f4b82101c6e7e065e6f7828bb Tax: 1%-1% Liqudity / Marketcap: $3.08K / $4.51K 📊 Chart | 🥞 Buy on Pancakeswap ____ BUGBO Socials Telegram | X | Website ____ …»

9 Feb 2024, 17:42 UTC249 viewsread 11 August 2026

📨 NTM.ai Express Listing - Binance Smart Chain Coin: Bugbo (BUGBO) Contract: 0xa90711721fabf21f4b82101c6e7e065e6f7828bb Tax: 1%-1% Liqudity / Marketcap: $3.08K / $4.51K 📊 Chart | 🥞 Buy on Pancakeswap ____ BUGBO Socials Telegram | X | Website ____ NTM.ai Socials 📢 Announcement 📨 NTM.ai Express 🇹🇷 TR | 🇮🇩 ID | 🇮🇳 IN | 🇺🇸 EN ____

9 Feb 2024, 16:54 UTC248 viewsread 11 August 2026
Photo

🟣 Website : https://www.Bugbo.xyz/ 🟣 Twitter : https://twitter.com/BugboToken 🟣Contract : 0xa90711721fabf21f4b82101c6e7e065e6f7828bb

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

Forward network

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.

Mentions

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.

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 11 August 2026 — this entry's latest reading, not the date you are reading this.

“BugBo Meme Token” (@BugBoToken), 21 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/BugBoToken.

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.