Telegram RegisterThe public register of Telegram
Telegram profile photo for ❦︎༒︎𝐀𝐌𝐈𝐓 𝐁𝐇𝐀𝐈 𝗦𝗔𝗧𝗧𝗔 𝗞𝗜𝗡𝗚❦︎༒︎

Channel

❦︎༒︎𝐀𝐌𝐈𝐓 𝐁𝐇𝐀𝐈 𝗦𝗔𝗧𝗧𝗔 𝗞𝗜𝗡𝗚❦︎༒︎

@AMITBAISATAKING

On this record: Topic · Previous handles · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry

9,292subscribers

-596 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1001702618912
TypeChannel
Username@AMITBAISATAKING
Description𝐓𝐇𝐈𝐒 𝐂𝐇𝐀𝐍𝐍𝐄𝐋 𝐂𝐑𝐄𝐀𝐓𝐄 𝐁𝐘 **ONLY** 𝐄𝐍𝐓𝐄𝐑𝐓𝐀𝐈𝐍𝐌𝐄𝐍𝐓. 💥💥💥💥💥💥 🔥𝐍𝐎𝐓 🚫 𝐅𝐎𝐋𝐋𝐎𝐖 𝐁𝐘 𝐒𝐀𝐓𝐓𝐀 🔥 18 𝐒𝐄 𝐊𝐀𝐌 𝐊𝐄 𝐁𝐀𝐂𝐇𝐄 𝐂𝐇𝐄𝐍𝐍𝐀𝐋 𝐒𝐄 𝐃𝐔𝐑 𝐑𝐇𝐄 💪💪💪
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live14 November 2026
Measurements held19
On Telegramt.me/AMITBAISATAKING

Topic

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

Previous handles

@AMITBAISATAKING was previously reachable at these 8 handles, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@AMITBHAUSATAKING
held 10 November 2026 – 10 November 2026
@AMITBHAISAAATKINGG
held 3 November 2026 – 3 November 2026
@AMITBHAISATAKING
held 11 August 2026 – 15 October 2026
@AMTIBHAISTAAKING
held 30 August 2026 – 30 August 2026
@AMITBAHISATAKING
held 22 August 2026 – 22 August 2026
@AMITBHAISATKING
held 21 August 2026 – 21 August 2026
@AMITBHAIKINGOFSATA
held 13 August 2026 – 13 August 2026
@AMITBHAISTAAKING
held 8 August 2026 – 8 August 2026

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 5 other registered channels. 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
@shahajhcoabdalkogih/4739638 Aug 2026, 10:40 UTC@AMITBAISATAKING/511321 · this entry8 Aug 2026, 10:45 UTC1.004 minutes
@shahajhcoabdalkogih/4741028 Aug 2026, 13:44 UTC@AMITBAISATAKING/511594 · this entry8 Aug 2026, 16:41 UTC1.003.0 hours
@shahajhcoabdalkogih/4741038 Aug 2026, 13:45 UTC@AMITBAISATAKING/511595 · this entry8 Aug 2026, 16:41 UTC1.002.9 hours
@AMITBAISATAKING/513833 · this entry13 Aug 2026, 14:15 UTC@shahajhcoabdalkogih/48044420 Aug 2026, 14:23 UTC1.007 days
@AMITBAISATAKING/513837 · this entry13 Aug 2026, 14:17 UTC@shahajhcoabdalkogih/47992819 Aug 2026, 13:54 UTC1.006 days
@AMITBAISATAKING/518041 · this entry22 Aug 2026, 13:41 UTC@shahajhcoabdalkogih/48114422 Aug 2026, 14:14 UTC1.0033 minutes
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
@shahajhcoabdalkogih12 (8/8 hand-verifiable sample passed)1.004 minutes@shahajhcoabdalkogih (8–4)
@CHANDANABHAISATAKING8 (6/8 hand-verifiable sample passed)1.0021 hourseven
@MyloveK1436 (6/6 hand-verifiable sample passed)1.0020 minutesthis entry (5–1)
@i3jwjejjejejeje5 (5/5 hand-verifiable sample passed)1.003 minutesthis entry (4–1)
@bfjfjhchhdjgkfjvnfigbhgkvghv5 (5/5 hand-verifiable sample passed)1.0024 minutesthis entry (4–1)

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. 18 of the 18 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 165 comparable posts for this entry, running 6 August 2026 to 14 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).

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

Growth

9,2929,9149,6038 August 2026 — 9,888 subscribers9 August 2026 — 9,914 subscribers11 August 2026 — 9,876 subscribers11 August 2026 — 9,878 subscribers13 August 2026 — 9,834 subscribers14 August 2026 — 9,858 subscribers21 August 2026 — 9,787 subscribers22 August 2026 — 9,775 subscribers22 August 2026 — 9,775 subscribers23 August 2026 — 9,792 subscribers29 August 2026 — 9,739 subscribers30 August 2026 — 9,739 subscribers30 August 2026 — 9,719 subscribers15 October 2026 — 9,576 subscribers3 November 2026 — 9,498 subscribers3 November 2026 — 9,497 subscribers10 November 2026 — 9,351 subscribers14 November 2026 — 9,292 subscribers14 November 2026 — 9,292 subscribers8 August 202614 November 2026
19 measurements spanning 98 days, net -596. 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 9,199–10,007 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Nov 2026, 11:229,292no change
14 Nov 2026, 10:489,292-59
10 Nov 2026, 17:229,351-146
3 Nov 2026, 12:209,497-1
3 Nov 2026, 11:229,498-78
15 Oct 2026, 09:069,576-143
30 Aug 2026, 16:479,719-20
30 Aug 2026, 00:009,739no change
29 Aug 2026, 23:459,739-53
23 Aug 2026, 05:159,792+17
22 Aug 2026, 14:309,775no change
22 Aug 2026, 14:159,775-12
21 Aug 2026, 17:309,787-71
14 Aug 2026, 19:069,858+24
13 Aug 2026, 14:179,834-44
11 Aug 2026, 22:259,878+2
11 Aug 2026, 17:169,876-38
9 Aug 2026, 10:519,914+26
8 Aug 2026, 10:469,888first reading

Engagement

304 posts held, back to 6 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 22 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
10.1%
avg views ÷ 9,292 subscribers
Avg views / post
936
60 posts measured
Reaction rate
0.486%
reactions ÷ views · ER floor
Posts in window
60
of 304 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. It is computed over the 37 of 60 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 14 November 2026
Posts held304 (6 August 2026 – 14 November 2026)
Views total56,133
Reactions total201
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Nov 2026, 11:22 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
702
Videos
7
Links
662

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

Video runtime
51s
Average length
26s

Measured directly from 2 videos 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

724 reactions across 148 posts, in 10 distinct kinds. The most used accounts for 88.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤64188.5%
👍628.56%
🔥91.24%
💋30.414%
🍾20.276%
🤩20.276%
🤯20.276%
👌10.138%
👏10.138%
💯10.138%

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

Measured over the 304 most recent posts we hold, published 6 August 2026 to 14 November 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

Telegram’s own ‘edited’ marker: 1 of 60 posts held from the last 30 days (1.67%) 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).

14 Nov 2026, 10:48 UTC254 viewsread 14 November 2026

https://t.me/AMITBAISATAKING/537888 https://t.me/AMITBAISATAKING/537888 https://t.me/AMITBAISATAKING/537888 https://t.me/AMITBAISATAKING/537888 https://t.me/AMITBAISATAKING/537888 ओर क्या चाहिए भाईसाब सबको 😒❤️ दिल्ली बाजार सिंगल ❤️5️⃣3️⃣❤️ रोज 3 से 4 गेम सिंगल बलास्ट 🎉🎉

Signed AMIT

14 Nov 2026, 10:48 UTC224 viewsread 14 November 2026

दिल्ली बाजार ☝️[[5️⃣3️⃣]]☝️बलास्ट सिंगल 😍✔️ श्री गणेश ➪ पोस्ट करदी ज्वाइन फास्ट 💨 ऊपर वाले चेनल पर विथ ट्रिक गेम डाली जाती हा ☘☃️ जिसको देखना है लिंक पर क्लिक करें 🌸🌸🌸

Signed AMIT

14 Nov 2026, 10:47 UTC243 viewsread 14 November 2026
Voice message

Note 👉 गेम चाहे मेरा खेलों चाहे किसी और का चाहे अपना खुद का सिर्फ और सिर्फ अर्पित भाई के पास खेलों इनका रेट है 10 के 1000 का बिंदास खेलों विश्वास का एक ही नाम 👇👇👇👇 https://wa.me/+919499243221 🙏😘 अर्पित भाई के पास 😘🙏

Signed AMIT

14 Nov 2026, 10:47 UTC274 views1 reactionsread 14 November 2026

🛑 🅰🆁🅿🅸🆃  🇰‌🇭‌🇦‌🇮‌🇼‌🇦‌🇱‌🛑 ⭕ɴʟɪɴᴇ 🇰ʜᴀɪᴡᴀʟ ████████████████████ DELHI BAZAR 03:00PM SHREE GANESH 04:30PM FARIDABAD 05:55PM GAZIABAD 09:20PM GALI 11:20PM DESAWAR 03:00AM ████████████████████ RATE__ JODI 10 ke 1000💸💸 RATE__ HARUF 100 ke 1000💸💸 ████████████████████ https://wa.me/+919499243221 https://wa.me/+919499243221 https://wa.me/+919499243…

❤1

Signed AMIT

14 Nov 2026, 09:49 UTC463 views1 reactionsread 14 November 2026
Sticker

Sticker, posted without a caption

❤1

Signed AMIT

14 Nov 2026, 09:49 UTC458 views2 reactionsread 14 November 2026

✓दिल्ली बाजार✓𝙇𝐈𝗩𝗘 5️⃣3️⃣✅🔥 🎉🎉बहुत बहुत बधाई हो दोस्तो 🎉🎉 Big Big Congratulations ✅️🔥 सभी भाइयो को बहुत बहुत बेदाई हो आपका अपना अमित भाई 💯 🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥

👍2

Signed AMIT

14 Nov 2026, 09:19 UTC591 views1 reactionsread 14 November 2026

꧁༆❣️DB SG 𝐓𝐑𝐈𝐂𝐊❣️༆꧂ ❤️‍🩹[[[•30•31•32•33•34•]]]❤️‍🩹 🤍[[[•35•36•37•38•39•]]]🤍 ❣️[👉🆎3️⃣3️⃣3️⃣🆎👈]❣️ #𝐀𝐌𝐈𝐓_𝐁𝐇𝐀𝐈❣️🥳

👏1

Signed AMIT

14 Nov 2026, 03:57 UTC737 views4 reactionsread 14 November 2026

✓गली चोर✓𝙇𝐈𝗩𝗘 9️⃣3️⃣✅🔥 🎉🎉बहुत बहुत बधाई हो दोस्तो 🎉🎉 Big Big Congratulations ✅️🔥 सभी भाइयो को बहुत बहुत बेदाई हो आपका अपना अमित भाई 💯 🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥

❤4

Signed AMIT

13 Nov 2026, 17:31 UTC≈1,100 views8 reactionsread 14 November 2026

꧁༆ ❣️GL DS 𝐓𝐑𝐈𝐂𝐊❣️༆꧂ ❤️‍🩹[[[•20•21•22•23•24•]]]❤️‍🩹 🤍[[[•25•26•27•28•29•]]]🤍 ❣️[👉🆎2️⃣2️⃣2️⃣🆎👈]❣️ #𝐀𝐌𝐈𝐓_𝐁𝐇𝐀𝐈❣️🥳

❤8

Signed AMIT

13 Nov 2026, 10:01 UTC≈1,390 views2 reactionsread 14 November 2026
Sticker

Sticker, posted without a caption

❤2

Signed AMIT

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

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Gk TRICKS ™
@Delhi_Up_Bihar_Police_Gk_TRICKS · 173,331
Telegram ranks this channel #41 of 69 here — alongside 68 others — read 12 August 2026
SSC RAILWAY GK GS Tricks
@SSC_GD_BSSC_GK_GS_Tricks_HINDI · 195,685
Telegram ranks this channel #41 of 72 here — alongside 71 others — read 11 August 2026

This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“❦︎༒︎𝐀𝐌𝐈𝐓 𝐁𝐇𝐀𝐈 𝗦𝗔𝗧𝗧𝗔 𝗞𝗜𝗡𝗚❦︎༒︎” (@AMITBAISATAKING), 9,292 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/AMITBAISATAKING.

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.