Telegram RegisterThe public register of Telegram
Telegram profile photo for Antidrain by Zun

Channel

Antidrain by Zun

@AntidrainbyZun

On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry

970subscribers

-11 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-1002875838549
TypeChannel
Username@AntidrainbyZun
CreatedBetween 1 June 2025 and 10 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live13 September 2026
Measurements held6
Confirmed unchanged2 times, most recently 13 September 2026
On Telegramt.me/AntidrainbyZun

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

970981975.57 August 2026 — 981 subscribers8 August 2026 — 981 subscribers15 August 2026 — 978 subscribers21 August 2026 — 973 subscribers29 August 2026 — 972 subscribers5 September 2026 — 970 subscribers7 August 20265 September 2026
6 measurements spanning 29 days, net -11. 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 968–983 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 07:20970-2
29 Aug 2026, 02:06972-1
21 Aug 2026, 15:47973-5
15 Aug 2026, 02:13978-3
8 Aug 2026, 00:45981no change
7 Aug 2026, 15:00981first reading

Engagement

19 posts held, back to 10 July 2025the 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 19 posts for this entry, the most recent from 9 April 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

6 Dec 2025, 10:43 UTC≈1,350 viewsread 8 August 2026
Photo

If anyone is eligible for $POWER airdrop but can't claim or unstake their tokens due to lack of Gas fee in Ronin Network, You can DM me on X I will add support of Ronin Network, Solana Network and Sui Network on my antidrain.dev website soon

8 Nov 2025, 23:18 UTC≈1,730 viewsread 8 August 2026
Photo

If anyone have compromised SUI wallet and eligible for $MMT (Momentum Airdrop) but can't claim due to lack of gas fee, you can DM me on X to rescue your airdrop

23 Oct 2025, 06:30 UTC≈1,770 viewsread 8 August 2026
Photo

🧩 Update : $ERA 2nd Phase Claim Till now, I performed the rescue operation on these addresses, there are still a lot addresses, yet be performed on them when time comes. Among these 29 addresses, I failed in 5 addresses which are mentioned below : 0x648f09326aE1012Be76449422E888427E24a3872 0xf7399f451F4AB82340F012A27781e9f79c469c4e 0xa786de311BB70a2A15D9a6a3B48A1a660de78171 0x2eecb88952AcEd531A7B29aC7320fecA57e73a

17 Oct 2025, 16:45 UTC≈1,480 viewsread 8 August 2026
Photo

🧩 $ERA 2nd Airdrop Claim Update Those who previously reached out to me for claiming their $ERA, I will be helping u in claiming the remaining staked $ERA token this time as well. These are addresses, i am handling at this moment. All the rescue operations will be performed from this wallet : 0x0E1730aAb680245971603F9EDEAa0C85EBeaaaaa If u saw any tx in above mentioned wallet addresses,from the wallet I provided

28 Sept 2025, 16:35 UTC≈1,610 viewsread 8 August 2026

✅ Anoma Antidrain If you have compromised wallet and you are eligible for Anoma Airdrop from that compromised wallet then fill up this form correctly. 👉 Form Link : Click Here Don't submit any extra details except the one which is asked in the form.

9 Sept 2025, 16:08 UTC≈2,000 viewsread 8 August 2026

If you have compromised wallet and eligible for Avantis ($AVNT) Airdrop from that wallet. Then DM me on X. 📌 Rules : Click Here

8 Sept 2025, 08:13 UTC≈14,300 viewsread 8 August 2026

🔔 Update : Linea Compromised Wallet Antidrain Read the details : Click Here

4 Sept 2025, 17:29 UTC≈2,220 viewsread 8 August 2026
Photo

This is the latest update I received from Linea team, I will let u all know if I get any new update. There is another method for claiming LINEA and transferring LINEA to another wallet address but this is less effective, If Linea team don't co-operate at all, probably then I need to use the less effective method

4 Sept 2025, 07:36 UTC≈1,770 viewsread 8 August 2026

Those who have compromised Union wallet can dm me on X for rescuing the airdrop tokens. https://x.com/Zun2025

31 Aug 2025, 22:28 UTC≈1,940 viewsread 8 August 2026

99% done ✅ Once I get the endpoint from Linea team, everyone who have their compromised wallets can claim linea airdrop using my website at their own, no code !! I will keep you all updated.

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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“Antidrain by Zun” (@AntidrainbyZun), 970 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/AntidrainbyZun.

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.