Binance Trade bStocks Spin Get 3$ - 1000$ Token For All User Event Link : https://www.binance.com/activity/chance - Trade 50$ In Bstock Get 3 Spin - Spin & Collect Reward - Done
Signed *•.¸♡ 𝙈𝘿 𝙉𝘼𝙆𝙄𝘽𝙐𝙇 ♡¸.•*

Channel
@Airdopprovider
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,051subscribers
-21 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001580506129 |
|---|---|
| Type | Channel |
| Username | @Airdopprovider |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 9 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 9 November 2026 |
| On Telegram | t.me/Airdopprovider |
Giveaways & airdrops — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 18 September 2026 and assigned it the closest of 31 fixed categories, at 82% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Nov 2026, 00:44 | 1,051 | -4 |
| 5 Nov 2026, 08:57 | 1,055 | -1 |
| 2 Nov 2026, 17:06 | 1,056 | -4 |
| 30 Oct 2026, 14:19 | 1,060 | -2 |
| 27 Oct 2026, 16:50 | 1,062 | -5 |
| 24 Oct 2026, 09:29 | 1,067 | -10 |
| 21 Oct 2026, 02:40 | 1,077 | -10 |
| 17 Oct 2026, 14:17 | 1,087 | -6 |
| 14 Oct 2026, 05:56 | 1,093 | -6 |
| 10 Oct 2026, 11:17 | 1,099 | -10 |
| 4 Oct 2026, 18:00 | 1,109 | -1 |
| 25 Sept 2026, 04:56 | 1,110 | -9 |
| 16 Sept 2026, 18:20 | 1,119 | +1 |
| 13 Sept 2026, 01:20 | 1,118 | +5 |
| 9 Sept 2026, 08:36 | 1,113 | +65 |
| 31 Aug 2026, 08:38 | 1,048 | -6 |
| 28 Aug 2026, 01:45 | 1,054 | -7 |
| 24 Aug 2026, 23:53 | 1,061 | +1 |
| 21 Aug 2026, 01:36 | 1,060 | +2 |
| 18 Aug 2026, 04:33 | 1,058 | first reading |
17 posts held, back to 27 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 1 page of 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 17 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
8 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 62.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😱 | 5 | 62.5% | |
| 🔥 | 3 | 37.5% |
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 3 of the 17 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 8 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 27 July 2026 to 7 August 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.
Binance Trade bStocks Spin Get 3$ - 1000$ Token For All User Event Link : https://www.binance.com/activity/chance - Trade 50$ In Bstock Get 3 Spin - Spin & Collect Reward - Done
Signed *•.¸♡ 𝙈𝘿 𝙉𝘼𝙆𝙄𝘽𝙐𝙇 ♡¸.•*
Lol Now 20x Turnover Need For Gems 💔 4x to Direct 20x 😅 আমি 6M+ Game এ Volime করে Available Balance Check করতে গিয়ে দেখি এই অবস্থা আগে যেখানে 4x Turnover করলেই Balance Available হয়ে যেতো এখন সেখানে 20x করা লাগবে এখন Offer Skip করাটাই Better হবে 🥴
Signed *•.¸♡ 𝙈𝘿 𝙉𝘼𝙆𝙄𝘽𝙐𝙇 ♡¸.•*
Topnod Spin Event Payment Receive. Check Your Wallet 👍
Signed *•.¸♡ 𝙈𝘿 𝙉𝘼𝙆𝙄𝘽𝙐𝙇 ♡¸.•*
Again $5 From IMPGameFi 😘 https://t.me/Airdopprovider/7801
🔥2
Signed *•.¸♡ 𝙈𝘿 𝙉𝘼𝙆𝙄𝘽𝙐𝙇 ♡¸.•*
Almost $1 Task Available On Gomine 👌 https://t.me/Airdopprovider/7773
Signed *•.¸♡ 𝙈𝘿 𝙉𝘼𝙆𝙄𝘽𝙐𝙇 ♡¸.•*
Again $2 Withdraw Done 😘 https://t.me/Airdopprovider/7801
Signed *•.¸♡ 𝙈𝘿 𝙉𝘼𝙆𝙄𝘽𝙐𝙇 ♡¸.•*
Cloudflare Pay Wallet 🔥 Join Link : https://cloudflare.pay/ Create your wallet Claim Username Done
Signed *•.¸♡ 𝙈𝘿 𝙉𝘼𝙆𝙄𝘽𝙐𝙇 ♡¸.•*
IMPGameFi Payment Received 😘 https://t.me/Airdopprovider/7801
Signed *•.¸♡ 𝙈𝘿 𝙉𝘼𝙆𝙄𝘽𝙐𝙇 ♡¸.•*
67% For Airdrop & This Season Only 8 Days Left 👍 Token Already Listed With $25M Market cap 🔥 But এই Season এ কত % Airdrop দিবে সেটা বলা যাচ্ছে না। চাইলে এই কয়টা দিন এটাতে focus দিতে পারেন আশা করি Par Account এ $5 to $10+ Earning হবে 👍 https://telegram.me/sixsevenclub_bot/app?startapp=ref_dd95a629
Signed *•.¸♡ 𝙈𝘿 𝙉𝘼𝙆𝙄𝘽𝙐𝙇 ♡¸.•*
Six Seven Club Bot এ তো 2 টার বেশি Goal হয়ইনা তাই এই Balance দেখে মোনকে সান্ত্বনা দিচ্ছি 🤣 https://telegram.me/sixsevenclub_bot/app?startapp=ref_dd95a629 Collect Today's Ticket & Try Your Luck 👍
Signed *•.¸♡ 𝙈𝘿 𝙉𝘼𝙆𝙄𝘽𝙐𝙇 ♡¸.•*
Voice message, posted without a caption
Signed *•.¸♡ 𝙈𝘿 𝙉𝘼𝙆𝙄𝘽𝙐𝙇 ♡¸.•*
IMPGameFi Bot Invite Event Par Refer 50K Gem ~ $0.50 Bot Link : https://t.me/IMPGameFiBot/gamefi?startapp=c3JjPXNjZW5lMSZpYz1NVEJqTnpoag%3D%3D - Open Bot & Connect Your Ton Wallet - Complete Social Task & Play Game - Invite Friend & Earn 50K Gem $0.50 - Play Game & Convert Gem to Gold - Bring Gold Coin to Available Balance - Then Withdraw Gold Coin Instantly You Can Also Earn $IMP Coin & You Can Sell It During The…
🔥1
Signed *•.¸♡ 𝙈𝘿 𝙉𝘼𝙆𝙄𝘽𝙐𝙇 ♡¸.•*
Showing the 12 most recent of 17 posts we hold for @Airdopprovider. 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.
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.
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.
“Airdrop provider 🤑™” (@Airdopprovider), 1,051 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/Airdopprovider.
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.