Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝗦𝗵𝗮𝗻𝘁𝗼 𝗢𝗳𝗳𝗶𝗰𝗶𝗮𝗹 𝗕𝗗

Channel

𝗦𝗵𝗮𝗻𝘁𝗼 𝗢𝗳𝗳𝗶𝗰𝗶𝗮𝗹 𝗕𝗗

@ShantoCommunityBD

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Declared links · Cite this entry

102,102subscribers

-5,319 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002400115178
TypeChannel
Username@ShantoCommunityBD
DescriptionBast & Most Popular Crypto Airdrop & Instant Offer Channel In Bangladesh 📛 📌Owner & For Promote @the_shantoboss YouTube Channel -› https://www.youtube.com/@SHANTOCRYPTOBOSS
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live26 September 2026
Measurements held32
Confirmed unchanged1 time, most recently 26 September 2026
On Telegramt.me/ShantoCommunityBD

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 10 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 why it has no browse page of its own yet.

Growth

102,102109,539105,820.58 August 2026 — 107,421 subscribers8 August 2026 — 107,213 subscribers9 August 2026 — 107,668 subscribers10 August 2026 — 108,731 subscribers11 August 2026 — 109,539 subscribers12 August 2026 — 109,426 subscribers13 August 2026 — 109,238 subscribers15 August 2026 — 108,818 subscribers16 August 2026 — 108,520 subscribers17 August 2026 — 108,347 subscribers18 August 2026 — 108,028 subscribers19 August 2026 — 107,875 subscribers21 August 2026 — 107,837 subscribers22 August 2026 — 107,576 subscribers24 August 2026 — 107,169 subscribers25 August 2026 — 106,881 subscribers26 August 2026 — 106,626 subscribers27 August 2026 — 106,453 subscribers28 August 2026 — 106,324 subscribers29 August 2026 — 106,136 subscribers30 August 2026 — 105,886 subscribers31 August 2026 — 105,739 subscribers1 September 2026 — 105,531 subscribers2 September 2026 — 105,106 subscribers4 September 2026 — 104,903 subscribers6 September 2026 — 104,485 subscribers9 September 2026 — 104,066 subscribers12 September 2026 — 103,779 subscribers13 September 2026 — 103,560 subscribers15 September 2026 — 103,399 subscribers17 September 2026 — 103,121 subscribers26 September 2026 — 102,102 subscribers8 August 202626 September 2026
32 measurements spanning 49 days, net -5,319. 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 100,986–110,655 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 32
Measured (UTC)SubscribersChange
26 Sept 2026, 21:15102,102-1,019
17 Sept 2026, 15:37103,121-278
15 Sept 2026, 12:21103,399-161
13 Sept 2026, 20:36103,560-219
12 Sept 2026, 05:00103,779-287
9 Sept 2026, 21:39104,066-419
6 Sept 2026, 15:59104,485-418
4 Sept 2026, 04:00104,903-203
2 Sept 2026, 19:26105,106-425
1 Sept 2026, 14:25105,531-208
31 Aug 2026, 13:04105,739-147
30 Aug 2026, 11:34105,886-250
29 Aug 2026, 08:15106,136-188
28 Aug 2026, 10:38106,324-129
27 Aug 2026, 10:54106,453-173
26 Aug 2026, 08:26106,626-255
25 Aug 2026, 05:34106,881-288
24 Aug 2026, 02:43107,169-407
22 Aug 2026, 10:26107,576-261
21 Aug 2026, 01:44107,837first reading

Engagement

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

ERR · 30 days
2.19%
avg views ÷ 102,102 subscribers
Avg views / post
2,240
312 posts measured
Reaction rate
0.958%
reactions ÷ views · ER floor
Posts in window
312
of 630 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 27 September 2026
Posts held630 (5 August 2026 – 27 September 2026)
Views total697,897
Reactions total6,689
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Sept 2026, 08:43 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
≈8,370
Videos
≈286
Links
≈4,180

Lifetime counters from Telegram’s own channel header, read 27 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
15m 53s
Average length
56s

Measured directly from 17 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

12,083 reactions across 625 posts, in 12 distinct kinds. The most used accounts for 59.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤7,19059.5%
💔9818.12%
😎8226.80%
🔥7896.53%
💋5134.25%
🆒4243.51%
👍3602.98%
🥰3172.62%
❤‍🔥1971.63%
💯1691.40%
😍1691.40%
😁1521.26%

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

Measured over the 630 most recent posts we hold, published 5 August 2026 to 27 September 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.

Telegram Stars

Stars received
11
across the posts below
Posts paid on
9
of 630 we hold a reading for · 1%
Most on one post
2
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @ShantoCommunityBD. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 630 most recent posts we hold for this entry, published 5 August 2026 to 27 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

27 Sept 2026, 07:45 UTC578 views14 reactionsread 27 September 2026
Photo

এভাবে ton পাবেন up to 7 ton

❤7💔7

Signed 𝗦𝗵𝗮𝗻𝘁𝗼 𝗕𝗼𝘀𝘀

27 Sept 2026, 07:42 UTC626 views15 reactionsread 27 September 2026
Photo

New Bot kop All https://t.me/JellyTapBot?startapp=ref_u8152469314 বটে জয়েন করে Taks করলে ২ টা চাবি পাবেন ওই টা দিয়া spin করলে 0.007 ton করে পাবেন পতি রেফার ও 1 টা চাবি পাবেন মিনিমাম উইথড্র মাএ 0.03 ton

❤9💔5🔥1

Signed 𝗦𝗵𝗮𝗻𝘁𝗼 𝗕𝗼𝘀𝘀

27 Sept 2026, 07:22 UTC219 views10 reactionsread 27 September 2026
Photo

New kop Fast all https://t.me/sevnnetwork_miner_bot?start=ref_8152469314 Do 1 Task Make a Withdrawal Burn the token (est free 0.16$)

❤5🔥3💔1💯1

Signed 𝗦𝗵𝗮𝗻𝘁𝗼 𝗕𝗼𝘀𝘀

27 Sept 2026, 07:14 UTC332 views10 reactionsread 27 September 2026
Photo

আলহামদুলিল্লাহ আবারও 4.8 ton পেমেন্ট রিসিভ বট লিংক :- https://t.me/FINVORAWeb3bot?start=ref_TRX8152469314

❤4💔4😎2

Signed 𝗦𝗵𝗮𝗻𝘁𝗼 𝗕𝗼𝘀𝘀

26 Sept 2026, 22:02 UTC≈1,170 views22 reactionsread 27 September 2026

পেমেন্ট ১০০% ভেরিফাই এটা কোপান সবাই বট:- https://t.me/GramPirateBot?start=8152469314 ডুকে সব Tasks গুলা করেন যে সময় পোস্ট দেখবেন ওই সময় আমি ঘুম এটা সাজিয়ে রেখে গেছিলাম

❤19🔥3

Signed 𝗦𝗵𝗮𝗻𝘁𝗼 𝗕𝗼𝘀𝘀

26 Sept 2026, 20:29 UTC≈1,650 views16 reactionsread 27 September 2026
Photo

🔮 Prediction markets were never meant to be binary. Most prediction markets reduce the future to one simple question: YES or NO. Halley takes a different approach. With 2–10 possible outcomes in a single market, you can trade the future as it actually exists — full of competing possibilities, unexpected turns and outcomes that don't fit neatly into two boxes. And because Halley is an open prediction DEX, anyone …

💯6❤4🆒4😎2

Signed 𝗦𝗵𝗮𝗻𝘁𝗼 𝗕𝗼𝘀𝘀

26 Sept 2026, 20:07 UTC≈1,410 views3 reactionsread 27 September 2026

https://t.me/JellyTapBot?startapp=ref_u8152469314

❤2👍1

Signed 𝗦𝗵𝗮𝗻𝘁𝗼 𝗕𝗼𝘀𝘀

26 Sept 2026, 17:08 UTC≈1,820 views61 reactionsread 27 September 2026

আলহামদুলিল্লাহ এখন ভালো আছে আমি যে কি পরিমান ভয় পাইছিলাম

❤49😎6👍3🥰3

Signed 𝗦𝗵𝗮𝗻𝘁𝗼 𝗕𝗼𝘀𝘀

26 Sept 2026, 14:10 UTC≈2,030 views129 reactionsread 27 September 2026

আমার বাবার জন্য সবাই দোয়া করবেন হঠাৎ অসুস্থ হয়ে পড়েছে

❤83💔40💯5👍1

Signed 𝗦𝗵𝗮𝗻𝘁𝗼 𝗕𝗼𝘀𝘀

26 Sept 2026, 12:09 UTC≈2,120 views22 reactionsread 27 September 2026

2 বার free উইথড্র করতে দেই পড়ে ডিপোজিট করতে বলে তাই যা করবেন সব এক সাথে উইথড্র ওকে

❤17🥰5

Signed 𝗦𝗵𝗮𝗻𝘁𝗼 𝗕𝗼𝘀𝘀

26 Sept 2026, 11:43 UTC≈2,110 views19 reactionsread 27 September 2026

জয়েন করেই 2 ton এটা দিয়ে পতি দিন 0.1 ton ইনকাম তাতে রেফার না করতে পারলেও কোপ দিতে পারবেন সবাই

❤14😎3🔥2

Signed 𝗦𝗵𝗮𝗻𝘁𝗼 𝗕𝗼𝘀𝘀

26 Sept 2026, 11:40 UTC≈2,100 views16 reactionsread 27 September 2026
Photo

কোপ আবারও 0.78 ton পেমেন্ট রিসিভ ১ সেকেন্ড পেমেন্ট পেলাম অটো পেমেন্ট বট:- https://t.me/FINVORAWeb3bot?start=ref_TRX8152469314

❤10💯4🔥2

Signed 𝗦𝗵𝗮𝗻𝘁𝗼 𝗕𝗼𝘀𝘀

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

@ShantoCommunityBD edited 3 posts 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
13 August 2026
Most recent edit
19 September 2026

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.

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

“𝗦𝗵𝗮𝗻𝘁𝗼 𝗢𝗳𝗳𝗶𝗰𝗶𝗮𝗹 𝗕𝗗” (@ShantoCommunityBD), 102,102 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/ShantoCommunityBD.

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.