Telegram RegisterThe public register of Telegram
Telegram profile photo for Swim Protocol Announcements

Channel

Swim Protocol Announcements

@swimannouncements

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

118subscribers

-1 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-1001491994620
TypeChannel
Username@swimannouncements
CreatedBetween 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live28 August 2026
Measurements held3
Confirmed unchanged3 times, most recently 28 August 2026
On Telegramt.me/swimannouncements

Growth

118119118.57 August 2026 — 119 subscribers9 August 2026 — 119 subscribers14 August 2026 — 118 subscribers7 August 202614 August 2026
3 measurements spanning 8 days, net -1. 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 118–119 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 22:05118-1
9 Aug 2026, 04:17119no change
7 Aug 2026, 05:51119first reading

Engagement

20 posts held, back to 4 March 2022the 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 3 August 2022. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
8s
Average length
8s

Measured directly from 1 video 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

3 Aug 2022, 15:59 UTC321 viewsread 9 August 2026

Hey everyone 👋 The team at Swim is aware of the ongoing security issues involving Solana wallets being drained The root cause is being investigated and has not yet been found, but we recommend continuing to being prudent with handling security Here are some security best practices 👇 1/ We recommend using hardware wallets, not signing unrecognized transactions and revoking permissions to any suspicious links 2/ O

20 May 2022, 12:09 UTC599 viewsread 9 August 2026
Video

Hey Swimmers!!! We've got some really exciting news to share!!! 🎉 🔥🔥 Support for Avalanche & Polygon is LIVE 🔥🔥 Now you can swap native assets to and from Solana, BNBChain, Ethereum, Avalanche & Polygon! Try us out 👉 http://swim.io/swap https://twitter.com/SwimProtocol/status/1527620278330839040?s=20&t=AdMIaLTRZ3a0mSScwWqrxw

2 May 2022, 16:57 UTC542 viewsread 9 August 2026

https://twitter.com/SwimProtocol/status/1521139314977038338?s=20&t=RU_cNGW5r6JAXmLNC6vVcw Take a look at our April Month in Review! A lot has happened this past month and a lot more is on the way 👀

27 Apr 2022, 00:13 UTC969 viewsread 9 August 2026

https://swimprotocol.medium.com/introducing-the-otter-tots-nft-collection-swim-ido-b27f85584cfa Good evening, everyone, hope you're having a fab day! We've just dropped a HUGE Medium article on the details of our revolutionary IDO, which will be done in conjunction with the release of the Otter Tots NFT collection. This is to ensure a fairer distribution of tokens through giving an equal opportunity for all member

21 Apr 2022, 18:39 UTC630 viewsread 9 August 2026

https://swimprotocol.medium.com/swims-propeller-design-3fc665fb137c Hey Swimmers! We just dropped a new Medium article going over something we are currently building and are very excited about: the Propeller! This is Swim's very own relayer, which seeks to improve your user experience without compromising on what we swimmers hold most dear — decentralization. Here's a quick summary of the benefits with the Propel

18 Apr 2022, 00:24 UTC320 viewsread 9 August 2026

Hey Swimmers! 👋 We are super excited to be partnering with Serum & Burnt Finance to give away 5️⃣ whitelist spots for the #SerumSurfers to our community! For a chance to win: 1️⃣ Follow @SwimProtocol, @ProjectSerum & @BurntFinance on Twitter 2️⃣ Like & RT post below 🎯You're not going to want to miss this!!! https://twitter.com/SwimProtocol/status/1515846490937245696?s=20&t=5A2k0r5z8WXNYgrD7SXz2A

13 Apr 2022, 00:53 UTC414 viewsread 9 August 2026

👋 Hey Swimmers! Our team created this short survey to gain a stronger understanding of our community with hopes of taking what we learn to better serve our Swimmers! 🤗 Fill out the survey here 👇 https://forms.gle/AcKr6Mi2zja3EqkJA

31 Mar 2022, 00:10 UTC≈1,180 viewsread 9 August 2026

Hey Swimmers! Today we are proud to kick off the Swim Ambassador Program 🥳 The goal of this program is to bring Swimmers together from all over the world with the purpose of strengthening our community! Interested in becoming an Ambassador? Learn more here 👇 https://swimprotocol.medium.com/swim-ambassador-program-50de74e9c57a

25 Mar 2022, 16:57 UTC465 viewsread 9 August 2026

Hey Swimmers 👋 Remember you still have 6️⃣ days to claim your Skinny Dipper collectible and always be remembered as an early supporter of our protocol! All you have to do is try us out 👉 http://swim.io/swap https://twitter.com/SwimProtocol/status/1507333983478054912?s=20&t=b2WrasYv4NqdlXsPACPEJA

15 Mar 2022, 17:58 UTC592 viewsread 9 August 2026

Swimmers, Don't forget to check out our AMA tomorrow (March 16th) at 8pm UTC+8 with Bonfida! Our founder will be answering all of the community's questions there! https://twitter.com/SwimProtocol/status/1503695004249706496?s=20&t=VIh6S5yXvQM8_Rv391UL7g

15 Mar 2022, 17:01 UTC≈1,150 viewsread 9 August 2026
File

ATTENTION Swimmers, this is NOT our website. THIS IS NOT OUR PRODUCT. If you are looking for the correct link to our product and website, you can find it here: swim.io Please be safe.

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

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

“Swim Protocol Announcements” (@swimannouncements), 118 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/swimannouncements.

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.