Telegram RegisterThe public register of Telegram
Telegram profile photo for AIRDROP CORNER

Channel

AIRDROP CORNER

@HopiumCorner

On this record: Topic · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

44subscribers

-7 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002164063849
TypeChannel
Username@HopiumCorner
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live3 November 2026
Measurements held7
Confirmed unchanged5 times, most recently 3 November 2026
On Telegramt.me/HopiumCorner

Topic

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 29 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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.

Growth

445147.57 August 2026 — 51 subscribers10 August 2026 — 51 subscribers15 August 2026 — 50 subscribers29 August 2026 — 49 subscribers14 September 2026 — 46 subscribers27 September 2026 — 45 subscribers8 October 2026 — 44 subscribers7 August 20268 October 2026
7 measurements spanning 62 days, net -7. 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 43–52 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Oct 2026, 01:2044-1
27 Sept 2026, 00:2145-1
14 Sept 2026, 04:0046-3
29 Aug 2026, 07:5649-1
15 Aug 2026, 02:3650-1
10 Aug 2026, 10:4651no change
7 Aug 2026, 12:5851first reading

Engagement

20 posts held, back to 31 December 2024 — 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 20 posts for this entry, the most recent from 19 February 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

23 Jan 2025, 09:01 UTC283 viewsread 10 August 2026

Memhash GIft Free Mining Access t.me/memhash_bot/start?startapp=1o6XdP_gift

22 Jan 2025, 15:04 UTC176 viewsread 10 August 2026
Photo

Claim PX Tutorial Claim & Swap PX Prepare 1 TON ➡️ Open : http://t.me/tokentable_bot/pixel ➖ Connect Your Wallet ( Tonkepeer ) ➖ Claim PX ➖ Swap : https://dedust.io/swap/TON/PX ➖ Done

22 Jan 2025, 13:04 UTC122 viewsread 10 August 2026

🎁 GIFT - Memhash Free Mining Access, cuman 1 setiap hari. t.me/memhash_bot/start?startapp=1o6XdP_gift

19 Jan 2025, 22:22 UTC112 viewsread 10 August 2026
Photo

🎁 GIFT - Memhash Free Mining Access Siapa cepat dia dapat, cuman 1 setiap hari. t.me/memhash_bot/start?startapp=1o6XdP_gift

19 Jan 2025, 14:13 UTC149 viewsread 10 August 2026
Photo

✅ Ton BattleGround - Game Telegram! Game Multipemain Pertama di Telegram & Ton seperti PUBG & Free Fire! 📱 TonBattleGround✅️

15 Jan 2025, 11:12 UTC99 viewsread 10 August 2026
Photo

🌱 Seed - Mining Endsy ⭐️Finish Eligibility Conditions ⭐️Complete All tasks ⭐️Seed Balance is most important 🔗 SEED App

15 Jan 2025, 10:39 UTC120 viewsread 10 August 2026
Photo

Airdrop Duckchain sudah mendarat di CEX, besok listing 🦆 DuckChain

10 Jan 2025, 15:00 UTC64 viewsread 10 August 2026
Photo

Discover Sigma: A project that rewards you for your on-chain activity on TON! 🚀 Your activity on the TON blockchain determines your reward. Here’s how it works: - Enter the app. - Connect your TON wallet. - Sigma scans your activity - Get rewarded with points instantly! Quick, simple, and transparent. Join Sigma: https://t.me/sigmatonbot/app?startapp=ref_rdv6ng

10 Jan 2025, 14:29 UTC49 viewsread 10 August 2026

✅ Memhash Secret Codes : market_liquidity 🔗 @Memhash_bot

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

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

“AIRDROP CORNER” (@HopiumCorner), 44 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/HopiumCorner.

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.