Telegram RegisterThe public register of Telegram

Channel

Cosmos Airdrops

@cosmos_airdropsy

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

6subscribers

+0 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-1001706856314
TypeChannel
Username@cosmos_airdropsy
DescriptionLeaking Cosmos $ATOM ecosystem airdrops and stakedrops. My power is $ATOM ⚛️ Everyone likes airdrops 🪂
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live13 August 2026
Measurements held2
On Telegramt.me/cosmos_airdropsy

Growth

67 August 2026 — 6 subscribers12 August 2026 — 6 subscribers7 August 202612 August 2026
2 measurements spanning 6 days. 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 5–7 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 20:336no change
7 Aug 2026, 08:196first reading

Engagement

20 posts held, back to 13 August 2023the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 15 August 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
852
Videos
46
Links
2,190

Lifetime counters from Telegram’s own channel header, read 12 August 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
4m 38s
Average length
2m 19s

Measured directly from 2 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.

Recent posts

15 Aug 2023, 03:21 UTC85 viewsread 12 August 2026
Photo

Seems like there is a lot of hype and excitement but everyone should be ready for an airdrop at a later date, with vesting, etc. Again: no official info! Per Discord: https://t.co/5iyvx10DQG we are likely to hear about the airdrop prior to TGE or 12 PM UTC on August 15th. 2/ https://t.co/qIe3hLuotB

15 Aug 2023, 03:21 UTC100 viewsread 12 August 2026

Full link to the @SeiNetwork AMA with @bsc_daily: https://t.co/agykABaqhO check: 35:40 and 56:20 3/

15 Aug 2023, 03:21 UTC100 viewsread 12 August 2026

@azimuthph @bsc_daily Given the hype (real and imagined) around $SEI and overall Discord over reliance would not be surprised. DYOR and DO NOT FOMO.

15 Aug 2023, 03:21 UTC47 viewsread 12 August 2026
Video

$SEI mainnet and airdrop expectations: ➡️Sei has not announced timing or eligibility criteria ➡️ $SEI AMA on @bsc_daily: "could be tomorrow, could be one day after that..." ➡️Discord: "The announcement of the airdrop will be made before TGE" TGE Aug 15th What do you think? 1/ https://t.co/hwren9VpuB

14 Aug 2023, 22:43 UTC27 viewsread 12 August 2026

@seppwurscht @Neutron_org @0xSpaydh @hxrts US geo-block is a great idea! 🤔 (sorry, I just couldn't resist)

14 Aug 2023, 22:43 UTC30 viewsread 12 August 2026

@AlexCosmonaut Yeah but I think (I hope?) most can juggle _two_ thoughts in their heads at the same time: 1. continue to call out bullshit 2. continue to build

14 Aug 2023, 13:01 UTC19 viewsread 12 August 2026

🔁 RT @DinoFriends_io: 🦖 Dino Friends Alert! 🦕 The SNAPSHOT is happening this week! This is your last chance to acquire our #NFT and qualify for the upcoming airdrop 🪂 Don't miss out! 🌍💚 https://t.co/hTlU9O9EnB

14 Aug 2023, 13:01 UTC13 viewsread 12 August 2026

What is your average price at which you bought $ATOM? My 7-8$ long time ago 😅

Showing the 12 most recent of 20 posts we hold for @cosmos_airdropsy. 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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“Cosmos Airdrops” (@cosmos_airdropsy), 6 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/cosmos_airdropsy.

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.