Telegram RegisterThe public register of Telegram

Channel

BotSubscription

@BotSubscriptionTelegram

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

2,496subscribers

+25 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002357392766
TypeChannel
Username@BotSubscriptionTelegram
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live10 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/BotSubscriptionTelegram

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 93% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (3 of the pairs behind the counts below)
Posted firstThenOverlapGap
@tgmembership/12831 Dec 2025, 16:41 UTC@BotSubscriptionTelegram/124 · this entry31 Dec 2025, 17:03 UTC1.0022 minutes
@BotSubscriptionTelegram/125 · this entry25 Jan 2026, 15:12 UTC@tgmembership/12925 Jan 2026, 15:42 UTC1.0031 minutes
@BotSubscriptionTelegram/126 · this entry2 Apr 2026, 22:59 UTC@tgmembership/1302 Apr 2026, 23:00 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@tgmembership6 (6/6 hand-verifiable sample passed)1.00under a minutethis entry (51)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 1 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 19 comparable posts for this entry, running 28 May 2025 to 8 July 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @tgmembership. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

2,4702,4962,4837 August 2026 — 2,471 subscribers7 August 2026 — 2,470 subscribers10 August 2026 — 2,496 subscribers7 August 202610 August 2026
3 measurements spanning 4 days, net +25. 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 2,466–2,500 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 13:242,496+26
7 Aug 2026, 21:442,470-1
7 Aug 2026, 00:472,471first reading

Engagement

20 posts held, back to 28 May 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof 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 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

120 reactions across 17 posts, in 7 distinct kinds. The most used accounts for 89.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
10789.2%
🔥54.17%
👍32.50%
🤡21.67%
👏10.833%
🤔10.833%
🥰10.833%

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 20 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 120reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 28 May 2025 to 8 July 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

8 Jul 2026, 23:29 UTC≈2,090 views9 reactionsread 7 August 2026

We’ve just released a new BotSubscription update with improvements across broadcasts, welcome messages, payments, renewals, Telegram, Discord, and admin workflows. Highlights include more reliable Telegram broadcasts, improved welcome-message handling, clearer plan selection buttons, stronger payment and renewal flows, better Discord support-ticket handling, and expanded multi-language coverage. We’ve also made man

6👍3

1 Jul 2026, 22:39 UTC≈2,700 views7 reactionsread 7 August 2026

🚀 BotSubscription update: payments, renewals, Telegram, Discord & integrations We’ve shipped two BotSubscription updates in just over a week — one went live last week, and another one has been released today. These updates are all about making BotSubscription even more dependable for paid communities across Telegram and Discord. Payments and renewals are now smarter across supported providers, with improved handli

7

24 May 2026, 22:53 UTC≈4,150 views9 reactionsread 7 August 2026

🚀 Big BotSubscription update: Telegram Dashboard, 25 languages, Telegram Stars & coupon codes We’ve just released one of our biggest updates yet. The redesigned BotSubscription web dashboard is now fully available for Telegram, bringing the same modern management experience we recently launched for Discord. Project owners can now manage Discord and Telegram communities side-by-side from one clean dashboard. BotSub

9

2 Apr 2026, 22:59 UTC≈6,370 views20 reactionsread 7 August 2026

Back in December, we introduced the new generation of BotSubscription with Discord as the first platform built on our new multi-platform architecture. Today, we're bringing that same new-generation app to Telegram. To be clear, BotSubscription is not new to Telegram. Telegram has been part of BotSubscription for years. What's new today is that new Telegram bots/projects now start on the new BotSubscription app. Th

18👏1🤔1

25 Jan 2026, 15:12 UTC≈8,270 views25 reactionsread 7 August 2026

Hi everyone, We have a few important updates regarding our platform and policies. 1. Updates to our Policies We have updated our Terms of Service, Privacy Policy, and other core documents. You can review the full legal hub here: 👉 https://docs.botsubscription.com/policies/legal/ Why the change? We are expanding into new markets, and these updates define the rights and obligations required to operate securely in th

25

31 Dec 2025, 17:03 UTC≈6,820 views15 reactionsread 7 August 2026
Photo

Happy New Year, everyone 🎉 5 years ago this month, we launched on Telegram. Today, we're launching BotSubscription on Discord. It's been a long time coming. A lot of you have been asking for this, and honestly, it took us longer than we hoped — but we wanted to do it right. This is just the beginning. We've also redesigned botsubscription.com, and over the next few weeks you'll see updates across the docs, API ref

15

15 Dec 2025, 14:01 UTC≈5,130 views7 reactionsread 7 August 2026
Photo

Photo, posted without a caption

4🔥3

19 Jun 2025, 09:41 UTC≈11,200 views10 reactionsread 7 August 2026
Photo

Maximize your business potential with BotSubscription! Streamline your membership management, automate payments, track sales, and more — all in one platform. Start unlocking your business’s full potential today! 👉 @BotSubscriptionBot #botsubscription #telegrammarketing #telegramchannel #creatoreconomy #membershipbusiness #cryptopayments #nokyc #contentmonetization #subscriptionmodel #monetizeyourcontent #aiforbusi

8🔥2

17 Jun 2025, 09:41 UTC≈8,470 views2 reactionsread 7 August 2026
Photo

Optimize your customer service with AI-powered support integrated directly into your bot. This allows you to save time while providing fast and effective assistance to your members, ensuring they get the help they need — 24/7. Ready to upgrade your customer support and streamline your operations? Start today: @BotSubscriptionBot #botsubscription #digitalmonetization #telegramchannel #creatoreconomy #telegrambot #

2

16 Jun 2025, 09:41 UTC≈5,280 views3 reactionsread 7 August 2026
Photo

Here are some reasons why BotSubscription is perfect for Telegram membership management: 🔹 Easy to launch 🔹 Built-in customer service 🔹 Broadcasting made easy 🔹 Flexible membership options Simplify and grow your Telegram membership business starting today! @BotSubscriptionBot #botsubscription #aiforbusiness #entrepreneurtools #contentrevenue #saasbusiness #telegramautomation #telegramchannel #smartbots #membershi

3

13 Jun 2025, 09:41 UTC≈3,740 views2 reactionsread 7 August 2026
Photo

Leave the heavy lifting to BotSubscription. We automate memberships, payments, and renewals, so you can spend your time scaling your business and engaging your community. Let us take care of the backend while you focus on what matters most — growth! 🚀 Get started now! 👉 @BotSubscriptionBot #botsubscription #membershipsolutions #techforcreators #smartbots #subscriptionbusiness #passiveincome #saasbusiness #subscri

2

12 Jun 2025, 09:41 UTC≈2,680 views1 reactionsread 7 August 2026
Photo

Did you know? With BotSubscription’s coupon system, you can offer discounts to your Telegram members to attract new users and retain existing ones. Start offering discounts today and grow your community! 👉 @BotSubscriptionBot #botsubscription #passiverevenue #digitalmonetization #techforcreators #businessgrowth #automatedmembership #aiforbusiness #telegrambot #paywallsolutions #membershipbusiness #subscriptionbusi

1

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

Citation-graph rank

Citation-graph rank — 273,290 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

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.

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

“BotSubscription” (@BotSubscriptionTelegram), 2,496 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/BotSubscriptionTelegram.

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.