Telegram RegisterThe public register of Telegram
Telegram profile photo for Volcano Airdrops

Channel

Volcano Airdrops

@VolcanoAirdrops

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Posts · Posts recorded as deleted · Citations · Cite this entry

36subscribers

-17,341 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-1002288042457
TypeChannel
Username@VolcanoAirdrops
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live5 November 2026
Measurements held41
Confirmed unchanged1 time, most recently 5 November 2026
On Telegramt.me/VolcanoAirdrops

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

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 2 other registered channels. This entry also sits inside a group of 32 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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
@WizardAirdrops/249021 Jul 2026, 01:08 UTC@VolcanoAirdrops/3091 · this entry21 Jul 2026, 01:09 UTC1.00under a minute
@WizardAirdrops/256231 Jul 2026, 14:54 UTC@VolcanoAirdrops/3317 · this entry31 Jul 2026, 14:54 UTC1.00under a minute
@VolcanoAirdrops/3346 · this entry5 Aug 2026, 16:54 UTC@WizardAirdrops/26265 Aug 2026, 16:54 UTC1.00under a minute
@WizardAirdrops/279812 Aug 2026, 00:49 UTC@VolcanoAirdrops/3411 · this entry12 Aug 2026, 00:50 UTC1.00under a minute
@VolcanoAirdrops/3091 · this entry21 Jul 2026, 01:09 UTC@CHARIXNews/2872826 Jul 2026, 03:30 UTC1.005 days
@CHARIXNews/2883131 Jul 2026, 14:54 UTC@VolcanoAirdrops/3317 · this entry31 Jul 2026, 14:54 UTC1.00under a minute
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
@WizardAirdrops5 (5/5 hand-verifiable sample passed)1.00under a minute@WizardAirdrops (5–0)
@CHARIXNews5 (5/5 hand-verifiable sample passed)1.00under a minute@CHARIXNews (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. 2 of the 7 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 34 comparable posts for this entry, running 12 July 2026 to 19 August 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).

Of the group of 32 channels, the one whose matching posts we hold earliest is @PantherAirdrops. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 11 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.

Channels linked by matching posts

This channel is in a group of 32 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Airdrop Glance
@AirdropGlance · Channel
125,120 subscribers
Airdrop Neptune™
@AirdropNeptune · Channel
95,818 subscribers
Yono games
@AirdropEnvoy · Channel
84,552 subscribers
Wurve
@wurve · Channel
80,054 subscribers
Veteran Airdrops
@VeteranAirdrops · Channel
76,670 subscribers
Devil Earning
@devil_drop · Channel
72,200 subscribers
Airdrop Overlay
@AirdropOverlay · Channel
68,584 subscribers
Airdrop Segment
@AirdropSegment · Channel
66,556 subscribers
Mystery Airdrops
@MysteryAirdrops · Channel
64,408 subscribers
Yono tricks
@CryptoNewsXY · Channel
57,515 subscribers
Panther Airdrops
@PantherAirdrops · Channel
56,280 subscribers
Airdrop HiveX™
@AirdropHiveX · Channel
56,149 subscribers
CASINO ALERTS
@AIRDROPS_ALERTERS · Channel
52,674 subscribers
Archer Airdrops
@ArcherAirdrops · Channel
52,049 subscribers
Thunder drop♠️♦️
@Thunder_drop · Channel
51,983 subscribers
Earning vip
@EarningEnvy · Channel
50,281 subscribers
Default Loots
@SwiftIncomehub · Channel
48,589 subscribers
Airdrop Furious
@FuriousAirdrop · Channel
48,064 subscribers
Airdrop Omen
@AirdropOmen · Channel
47,946 subscribers
Fart Airdrop ™
@FartAirdrop · Channel
42,147 subscribers
Blunder Airdrop
@BlunderAirdrop · Channel
40,890 subscribers
Toss Winner
@Techno_Karan · Channel
33,463 subscribers
Elevate Airdrops
@ElevateAirdrops · Channel
30,360 subscribers
Dynamite Airdrops
@DynamiteAirdrops · Channel
29,958 subscribers
PRO LOOTERS
@VOLTTGz · Channel
27,108 subscribers
Techno Earning
@roqxo · Channel
25,572 subscribers
CHARIX | News
@CHARIXNews · Channel
23,571 subscribers
Wizard Airdrops
@WizardAirdrops · Channel
19,120 subscribers
Earning loots
@cryptosgiveaways · Channel
18,973 subscribers
Earner Sim™
@Earnersim · Channel
4,866 subscribers
@cryptoclashers
@NinjaGameNews · Channel
198 subscribers

Growth

217,3778,689.57 August 2026 — 17,377 subscribers7 August 2026 — 17,377 subscribers8 August 2026 — 17,356 subscribers9 August 2026 — 17,326 subscribers10 August 2026 — 17,371 subscribers11 August 2026 — 17,334 subscribers12 August 2026 — 17,323 subscribers13 August 2026 — 17,287 subscribers14 August 2026 — 17,249 subscribers16 August 2026 — 17,204 subscribers17 August 2026 — 17,158 subscribers18 August 2026 — 17,103 subscribers19 August 2026 — 17,068 subscribers20 August 2026 — 17,056 subscribers21 August 2026 — 17,033 subscribers22 August 2026 — 17,004 subscribers24 August 2026 — 16,960 subscribers25 August 2026 — 16,934 subscribers26 August 2026 — 16,895 subscribers27 August 2026 — 16,875 subscribers28 August 2026 — 16,858 subscribers29 August 2026 — 16,840 subscribers30 August 2026 — 16,822 subscribers31 August 2026 — 16,794 subscribers1 September 2026 — 16,778 subscribers2 September 2026 — 16,761 subscribers3 September 2026 — 16,740 subscribers5 September 2026 — 16,591 subscribers8 September 2026 — 16,522 subscribers11 September 2026 — 16,455 subscribers13 September 2026 — 16,399 subscribers15 September 2026 — 16,365 subscribers16 September 2026 — 16,306 subscribers19 September 2026 — 16,256 subscribers26 September 2026 — 16,106 subscribers4 October 2026 — 15,934 subscribers9 October 2026 — 2 subscribers16 October 2026 — 16 subscribers23 October 2026 — 21 subscribers30 October 2026 — 29 subscribers5 November 2026 — 36 subscribers367 August 20265 November 2026
41 measurements spanning 90 days, net -17,341. 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”.
Measurement log — every subscribers count we have recorded, most recent 20 of 41
Measured (UTC)SubscribersChange
5 Nov 2026, 08:2636+7
30 Oct 2026, 05:0829+8
23 Oct 2026, 00:4921+5
16 Oct 2026, 11:3816+14
9 Oct 2026, 01:012-15,932
4 Oct 2026, 12:5415,934-172
26 Sept 2026, 00:5616,106-150
19 Sept 2026, 09:3616,256-50
16 Sept 2026, 20:4016,306-59
15 Sept 2026, 00:1816,365-34
13 Sept 2026, 09:3916,399-56
11 Sept 2026, 15:3716,455-67
8 Sept 2026, 22:0116,522-69
5 Sept 2026, 17:3616,591-149
3 Sept 2026, 16:1916,740-21
2 Sept 2026, 06:4216,761-17
1 Sept 2026, 05:1316,778-16
31 Aug 2026, 06:3416,794-28
30 Aug 2026, 06:5616,822-18
29 Aug 2026, 06:2716,840first reading

Engagement

80 posts held, back to 12 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 54 pages 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 80 posts for this entry, the most recent from 20 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

19 Aug 2026, 04:59 UTC118 viewsread 3 September 2026
Photo

1$+1$+1$ DGB Free Task AutoPay Bot 1 Level Refer :- 1$ DGB 2 Level Refer :- 0.1$ DGB 3 Level Refer :- 0.05$ DGB 🎁 Bonus:- 0.1$ DGB 💝 TASK Bonus:- 0.1$ +0.1$+0.1$+0.1$ Free 🤑😱🤫 👉 Link :- https://t.me/A1DGBTaskAutopaybot?start=r1120524928 👉 Min Withdrawal:- 1$ DGB Only ADD Channel price :- 1$ Only Dm :- @VipTechEarning09 ✅ Withdrawal AutoPay DGB ✅

17 Aug 2026, 22:47 UTC116 viewsread 3 September 2026

1$ Ton Auto payment bot Bonus 0.15$ 🎁 and Redeem code 0.1$ 🎁 0.1$ Code :- FreeTonLive

17 Aug 2026, 20:27 UTC113 viewsread 3 September 2026

1$ Ton Auto payment bot Bonus 0.15$ 🎁 and Redeem code 0.1$ 🎁 0.1$ Code :- FreeTonLive

17 Aug 2026, 10:20 UTC90 viewsread 3 September 2026

1$ Ton Auto payment bot Bonus 0.15$ 🎁 and Redeem code 0.1$ 🎁 0.1$ Code :- FreeTonLive

Showing the 12 most recent of 80 posts we hold for @VolcanoAirdrops. 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 recorded as deleted after publishing

We recorded 6 posts on @VolcanoAirdrops as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
8 August 2026
Most recent seen missing
10 August 2026
Median time before seen missing
22 hours
Seen missing in the last 30 days
0

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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

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.

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

“Volcano Airdrops” (@VolcanoAirdrops), 36 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/VolcanoAirdrops.

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.