Your own branded support bot, free today Multi-bot hosting, forum-topic ticketing, pinned customer cards, custom greetings, one-click moderation and broadcasting with delivery reports. Your bot name, your group, your rules. No seat pricing, no platform migration, no free trial clock.

Channel
Weego.tech Bots
@WeeGoBots
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
10,717subscribers
+255 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1002092633669 |
|---|---|
| Type | Channel |
| Username | @WeeGoBots |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/WeeGoBots |
Topic
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 11 September 2026 and assigned it the closest of 31 fixed categories, at 83% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Oct 2026, 06:20 | 10,717 | +9 |
| 7 Oct 2026, 10:18 | 10,708 | +27 |
| 2 Oct 2026, 14:20 | 10,681 | +264 |
| 18 Sept 2026, 12:38 | 10,417 | +65 |
| 16 Sept 2026, 04:36 | 10,352 | +17 |
| 14 Sept 2026, 12:20 | 10,335 | -15 |
| 10 Sept 2026, 18:37 | 10,350 | +6 |
| 7 Sept 2026, 14:58 | 10,344 | -20 |
| 4 Sept 2026, 17:38 | 10,364 | -17 |
| 3 Sept 2026, 06:24 | 10,381 | -13 |
| 2 Sept 2026, 00:37 | 10,394 | -3 |
| 1 Sept 2026, 01:39 | 10,397 | -15 |
| 31 Aug 2026, 03:09 | 10,412 | +4 |
| 30 Aug 2026, 01:25 | 10,408 | -12 |
| 29 Aug 2026, 02:34 | 10,420 | -10 |
| 28 Aug 2026, 04:57 | 10,430 | -10 |
| 27 Aug 2026, 04:25 | 10,440 | -8 |
| 26 Aug 2026, 07:16 | 10,448 | -5 |
| 25 Aug 2026, 04:49 | 10,453 | -20 |
| 23 Aug 2026, 22:57 | 10,473 | first reading |
Engagement
81 posts held, back to 2 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 37 pages 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 81 posts for this entry, the most recent from 29 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 26s
- Average length
- 26s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
16 reactions across 15 posts, in 2 distinct kinds. The most used accounts for 93.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 15 | 93.8% | |
| 💯 | 1 | 6.25% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 17 of the 81 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 16 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 81 most recent posts we hold, published 2 August 2026 to 29 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
Everything Channel Guru does, at no cost today Instant approvals, custom greetings with media and buttons, a post builder, scheduled publishing, subscriber-level broadcasts and full white-labelling with your own bot. All of it live right now, free. Paid tiers are coming — early users keep what they've set up.
❤1
Migrating to a new channel? Take everything with you. Clone the full history into the new channel, then accept the sync prompt so future posts keep flowing from the old one while your audience moves over. Add a footer pointing to the new home. Clone jobs are restart-proof — if the backend restarts, it resumes where it stopped.
How does your team handle Telegram support right now? Personal DMs · A shared group everyone shouts in · An external helpdesk tool · Honestly, badly. No wrong answers — but if you picked one of the first two, the crossed-wires problem is coming for you at scale.
Hitting the 2 GB wall on large videos? The free tier caps files at 2 GB and adds a 10-second cooldown between requests to keep the service stable. Premium lifts the cap to 4 GB, removes the cooldown entirely and routes your requests with priority.
Why edit sync needs a database Telegram gives a bot no memory of what it sent. So ForwardBuddy keeps a message map — every source message ID paired with its destination copy. That map is what makes edit mirroring, reply threading and clean deletions possible. Boring infrastructure, visible results.
Linking your channel takes one forwarded post Tap Add Channel, then forward any existing post from your channel into the bot. That single forward carries the chat ID and proves you have access — no ID hunting, no numeric codes to paste. The bot confirms and you move straight on to your greeting.
Inherited a broken bot? We take those too. A developer disappeared. The bot half works. Nobody has the source cleanly documented. We do rescue work: audit what's there, document it, fix what's breaking, and either stabilise it or rebuild the parts that can't be saved.
7 things ForwardBuddy can automate before lunch 1. Mirror a channel with no forward tag. 2. Filter by content type. 3. Block spam keywords. 4. Rebrand handles automatically. 5. Delay posts to your free tier. 6. Sync edits across every copy. 7. Backfill an entire channel history. All from one Telegram chat.
5 signs you've outgrown DM support You've replied to the wrong person this week. 2. You scroll to find an old conversation. 3. Two teammates answered the same question. 4. You've lost a request entirely. 5. You're using your personal account because there's no shared one.
Message one channel's members, not all of them Channel-wise broadcast targets only the subscribers of a specific linked channel. Announce a price change to your paid group without spamming your free one. The bot shows your total audience size before you send, so you always know the reach.
Localise your feed while it forwards. Keyword Replacement isn't only for branding. Swap terminology for a different market, standardise the words your audience actually uses, or strip developer credits and phone numbers before content reaches a public channel. All of it applied on the way out.
Showing the 12 most recent of 81 posts we hold for @WeeGoBots. 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.
Mentions
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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.
Handles this channel named that no longer answer
- Dead references
- 3
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 3
- vacant every time we have ever looked
@WeeGoBots named 3 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 2 posts, 19 August 2026 – 23 August 2026
named in 2 posts, 13 August 2026 – 18 August 2026
named in 2 posts, 8 August 2026 – 9 August 2026
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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“Weego.tech Bots” (@WeeGoBots), 10,717 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/WeeGoBots.
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.