Telegram RegisterThe public register of Telegram

Channel

TGmembership.com

@tgmembership

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

1,326subscribers

-5 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-1001155537302
TypeChannel
Username@tgmembership
CreatedBetween 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/tgmembership

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 90% 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/128 · this entry31 Dec 2025, 16:41 UTC@BotSubscriptionTelegram/12431 Dec 2025, 17:03 UTC1.0022 minutes
@BotSubscriptionTelegram/12525 Jan 2026, 15:12 UTC@tgmembership/129 · this entry25 Jan 2026, 15:42 UTC1.0031 minutes
@BotSubscriptionTelegram/1262 Apr 2026, 22:59 UTC@tgmembership/130 · this entry2 Apr 2026, 23:00 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@BotSubscriptionTelegram6 (6/6 hand-verifiable sample passed)1.00under a minute@BotSubscriptionTelegram (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 2 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 20 July 2024 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 — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, 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

1,3261,3311,328.57 August 2026 — 1,331 subscribers7 August 2026 — 1,331 subscribers10 August 2026 — 1,329 subscribers13 August 2026 — 1,326 subscribers7 August 202613 August 2026
4 measurements spanning 7 days, net -5. 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 1,325–1,332 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 13:271,326-3
10 Aug 2026, 23:571,329-2
7 Aug 2026, 00:461,331no change
7 Aug 2026, 00:331,331first reading

Engagement

20 posts held, back to 20 July 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 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

104 reactions across 16 posts, in 10 distinct kinds. The most used accounts for 41.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
4341.3%
🔥3331.7%
👍1413.5%
👏32.88%
😍32.88%
custom 543849646304475297221.92%
👎21.92%
🤩21.92%
custom 544496506174964417010.962%
🥰10.962%

Custom emoji. 2 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

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 16 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 104reactions 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 20 July 2024 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 UTC196 viewsread 7 August 2026
Forwarded from @BotSubscriptionTelegram

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

1 Jul 2026, 22:39 UTC283 viewsread 7 August 2026
Forwarded from @BotSubscriptionTelegram

🚀 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

24 May 2026, 22:53 UTC394 views1 reactionsread 7 August 2026
Forwarded from @BotSubscriptionTelegram

🚀 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

🔥1

2 Apr 2026, 23:00 UTC635 viewsread 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

25 Jan 2026, 15:42 UTC755 views1 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

🔥1

31 Dec 2025, 16:41 UTC742 views4 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

4

14 May 2025, 22:48 UTC≈1,850 views6 reactionsread 7 August 2026

BotSubscription v1.58 We’ve just rolled out new API filters and a powerful /analytics page with detailed charts and business stats! Highlights: • New /paymentGateways/usage and /orders/source endpoints • Filter orders by payment_gateway or show unclaimed ones (member_id = 0) • Updated /users/count with improved structure • Webhook now includes claim_at timestamp • 📈 Brand new /analytics page – see your key numbers a

👍3👎21

15 Mar 2025, 17:04 UTC≈1,660 views6 reactionsread 7 August 2026
Forwarded from @BotSubscriptionTelegram

BotSubscription v1.57 – More Data, More Payment Options, More Control! 🚀 This update brings powerful insights, expanded crypto payment options, and new affiliate marketing tools to help you scale your business like never before! 🔥 NEW FEATURES 🔹 /topCustomersBySpend API – Easily see which customers have spent the most on your service over their lifetime. 🔹 Expanded Crypto Support – Now supporting XRP, USDT (TON),

🔥42

10 Feb 2025, 18:18 UTC≈1,660 viewsread 7 August 2026

TGmembership 1.56 - 10 Feb '25 🔹 Web Portal Buttons in Free Chats – By default, buttons now lead to your web portal for a more professional look, but you can switch them back to point to your bot anytime! 🔹 Disable In-Bot Payments (Optional) – Choose between web portal-only payments or the default bot + web payments. 🔹 Manual Payment Option – Need a semi-automated way to accept payments? Now you can add a custom pay

31 Jan 2025, 12:32 UTC≈1,480 views8 reactionsread 7 August 2026

🚀 TGmembership Update: Version 1.55 is Here! We’re kicking off 2025 strong with our 4th update this January! Today, we’re excited to introduce Custom Domains for Web Portals – a game-changer for your brand’s professionalism and customer trust. ✨ What’s New? 🏡 Custom Domains: Replace the default subhere.net/12345 link with your own domain (e.g., yourbusiness.com). It’s all about making your web portal look sleek, co

5😍2👏1

28 Jan 2025, 23:43 UTC≈1,130 views7 reactionsread 7 August 2026

🚀 TGmembership 1.54 is here! 🌐 Customize your web portal URL to reflect your brand—stand out with unique, professional links like /mybusiness. 🔐 New IP address options for web portal logins and orders for added security. 📊 Dive deeper into your sales with the new /salesForPeriod API endpoint. Upgrade your experience today! 👌 📖 Full details: https://docs.tgmembership.com/version-history/1.54

5👍2

Showing the 12 most recent of 20 posts we hold for @tgmembership. 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 — 567,040 of 1,480,688entries 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

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

Named by 2 registered channels — 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.

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

“TGmembership.com” (@tgmembership), 1,326 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/tgmembership.

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.