Telegram RegisterThe public register of Telegram
Telegram profile photo for Join TG Crypto..🎁

Channel

Join TG Crypto..🎁

@JoinTGCrypto

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry

91,253subscribers

-22,981 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001736854277
TypeChannel
Username@JoinTGCrypto
DescriptionJoin TG Crypto💪 🎁
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live9 November 2026
Measurements held61
Confirmed unchanged1 time, most recently 9 November 2026
On Telegramt.me/JoinTGCrypto

Topic

Giveaways & airdrops — 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 9 August 2026 and assigned it the closest of 31 fixed categories, at 95% 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 the other topics.

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 in near-verbatim form on 4 other registered channels. This entry also sits inside a group of 5 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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 (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@JoinCrypto_1/5315 Jul 2026, 13:37 UTC@JoinTGCrypto/223 · this entry30 Jul 2026, 23:35 UTC1.0015 days
@JoinTGCrypto/235 · this entry5 Aug 2026, 07:13 UTC@JoinCrypto_1/715 Aug 2026, 07:13 UTC1.00under a minute
@JoinTGCrypto/250 · this entry21 Sept 2026, 17:44 UTC@JoinCrypto_1/8421 Sept 2026, 17:44 UTC1.00under a minute
@JoinTGCrypto/251 · this entry21 Sept 2026, 19:01 UTC@JoinCrypto_1/8521 Sept 2026, 19:01 UTC1.00under a minute
@JoinTGCrypto/253 · this entry2 Oct 2026, 17:10 UTC@JoinCrypto_1/872 Oct 2026, 17:11 UTC1.00under a minute
@JoinTGCrypto/260 · this entry14 Oct 2026, 16:47 UTC@JoinCrypto_1/9314 Oct 2026, 16:48 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@JoinCrypto_126 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (20–6)
@Community_Crypto_119 (8/8 hand-verifiable sample passed)1.0013 hoursthis entry (12–7)
@Verified_A_Partner19 (8/8 hand-verifiable sample passed)1.002 minutes@Verified_A_Partner (17–2)
@saifulallbangla17 (8/8 hand-verifiable sample passed)1.004 minutes@saifulallbangla (12–5)

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. 24 of the 42 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 33 comparable posts for this entry, running 30 July 2026 to 9 November 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).

Of the group of 5 channels, the one whose matching posts we hold earliest is @Community_Crypto_1. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_mutual · clone_source, last confirmed 11 November 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.

Channels linked by matching posts

This channel is in a group of 5 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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

91,253114,234102,743.57 August 20269 November 2026
61 measurements spanning 94 days, net -22,981. 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 87,806–117,681 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 61
Measured (UTC)SubscribersChange
9 Nov 2026, 21:5191,253-224
8 Nov 2026, 12:4691,477-58
7 Nov 2026, 06:4991,535-131
6 Nov 2026, 05:2891,666-87
5 Nov 2026, 01:0691,753-78
3 Nov 2026, 21:4491,831-152
2 Nov 2026, 23:4991,983-172
2 Nov 2026, 02:5992,155-168
1 Nov 2026, 00:4492,323-191
31 Oct 2026, 01:2092,514-121
29 Oct 2026, 22:2992,635-127
29 Oct 2026, 00:1992,762-173
27 Oct 2026, 21:5992,935-137
26 Oct 2026, 17:5793,072-107
25 Oct 2026, 18:3893,179-96
24 Oct 2026, 18:4793,275-113
23 Oct 2026, 20:3993,388-132
22 Oct 2026, 21:2193,520-194
21 Oct 2026, 17:2893,714-216
20 Oct 2026, 11:0993,930first reading

Engagement

45 posts held, back to 30 July 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 196 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.28%
avg views ÷ 91,253 subscribers
Avg views / post
1,170
12 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
12
of 45 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 9 November 2026
Posts held45 (30 July 2026 – 9 November 2026)
Views total13,999
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 06:49 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
62
Links
52

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

Telegram’s own ‘edited’ marker: 1 of 12 posts held from the last 30 days (8.33%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

9 Nov 2026, 04:14 UTC302 viewsread 11 November 2026
Photo

New Airdrops : Zoi Network Get Reward : Confirmed ( TGE 2027 ) 🪂 Register Link https://zoi.network/invite/EPVCQH ➖ Download the app ➖ Complete signup ➖ Verify Email ➖ Enter invite code: EPVCQH (instant bonus) ➖ Sync Everday ➖ Complete all task ➖ Done

3 Nov 2026, 03:45 UTC801 viewsread 11 November 2026
Photo

Interlink Kyc Sponsor 👍 Now Link:- https://itlg.interlinklabs.ai/kyc?ref=111222333444 Code-: 111222333444

2 Nov 2026, 06:34 UTC856 viewsread 11 November 2026
Photo

Bullshot Daily Claim GEM S ✅ Join Link https://t.me/JoinTGCrypto/264

1 Nov 2026, 13:24 UTC≈1,000 viewsread 11 November 2026
Photo

10k $LOOT = 94$ 😱 Join here Daily Claim 👍

31 Oct 2026, 14:26 UTC≈1,100 viewsread 11 November 2026
Photo

Billions Airdrop Claim Live 😁 https://staking.billions.network

31 Oct 2026, 04:36 UTC≈1,090 viewsread 11 November 2026
Photo

Loot 1000 Token = 8$ 🎁 😬Bot Link : https://t.me/LootVaultDexBot?start=ref_5096488357 Join & Connect Wallet ✔️ - Start & Open bot - Connect wallet ( Ton) - Approve fee - Start mining ⭐️ ( Keep collecting - Apply withdraw once you reach threshold )

28 Oct 2026, 05:39 UTC≈1,300 viewsread 11 November 2026
Photo

🪂Bullshot Potential Airdrop 🎁Reward: Earn GEM + XP = Future $BULL Token 💵Bullshot Raised $7.7M Fund ✅Join Link: https://gem.bullshot.io/r/0x66429549 🟢Connect your MetaMask wallet. 🟢Go to Profile → Quests. 🟢Complete Daily, Weekly, and One-Time Quests. 🟢Go to Mining and deploy a miner. 🟢Each miner requires 10 Energy Power to deploy. 🟢Energy Power replenishes every 10 minutes. 🟢Collect GEMS and ore from your miners e…

22 Oct 2026, 05:53 UTC≈1,360 viewsread 11 November 2026
Photo

Lebrel Ai Waitlist For All user 🪂Join Link: https://early.lebrel.ai/r/HVUUYZ -Enter Email -Enter X username -Complete simple task

19 Oct 2026, 18:51 UTC≈1,660 viewsread 11 November 2026
Photo

🎁Q Lounge Wallet Airdrop 🎁Reward : MQP Points Convert $MQX ✅Airdrop Link:- https://affiliate.dj-maxrex.com/i/440973808190 ✅Download App & Register with Email ✅Submit Code : 440973808190 ✅Save Phrase & Back Up ✅Open WalletChoose MQP Points ✅Complete Easy Tasks ✅Done

19 Oct 2026, 05:21 UTC≈1,500 viewsread 11 November 2026
Photo

New Airdrops : Avior Get Reward : $5 when Approved 🪂 Register : https://useavior.com/r/czhx7ky ➖ Submit Email ➖ Submit X Username (Optional) ➖ Dons

14 Oct 2026, 16:47 UTC≈1,830 viewsread 11 November 2026
Photo

New Airdrop : ZMINE Earn free $MINE token daily by minning 🔥 👉 Limited supply - $210M $MINE 👉 100% free for all. 👉 No wallet connect needed. 👉 Listing after mining ends. ✅ Go to Join - https://zmine.si/register?ref=02QQDCFY Refer - 02QQDCFY ➖ Create Account ➖ Backup Pharse & ID Login ➖ Go Mining ➖ Complete All Task ➖ Use ChatGPT For Answers ➖ Done

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

Posts edited after publishing

@JoinTGCrypto edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
2 September 2026
Most recent edit
2 September 2026

Posts recorded as deleted after publishing

We recorded 3 posts on @JoinTGCrypto as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
24 August 2026
Most recent seen missing
2 October 2026
Median time before seen missing
5 days
Seen missing in the last 30 days
0

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

“Join TG Crypto..🎁” (@JoinTGCrypto), 91,253 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/JoinTGCrypto.

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.