Telegram RegisterThe public register of Telegram
Telegram profile photo for Amasa Announcements

Channel

Amasa Announcements

@amasa_updates

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

433subscribers

-8 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-1001302390027
TypeChannel
Username@amasa_updates
CreatedBetween 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live21 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 21 August 2026
On Telegramt.me/amasa_updates

Growth

4334414377 August 2026 — 441 subscribers7 August 2026 — 441 subscribers15 August 2026 — 436 subscribers21 August 2026 — 433 subscribers7 August 202621 August 2026
4 measurements spanning 15 days, net -8. 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 432–442 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
21 Aug 2026, 18:06433-3
15 Aug 2026, 10:54436-5
7 Aug 2026, 01:31441no change
7 Aug 2026, 01:20441first reading

Engagement

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

Recent posts

3 Feb 2023, 09:36 UTCviews —

Amasa Announcements pinned «📢 Amasa Product Development Update 🛠 🪙 Updates made & tested for new ar token names ☑️ Completed pipeline checks for Prod deployment 📲 Updated UI/copy on dashboard, deposit, withdraw, allocation pages 🧩 Deployed changes for new frontend configuration proxy…»

3 Feb 2023, 09:36 UTC≈1,800 viewsread 7 August 2026

📢 Amasa Product Development Update 🛠 🪙 Updates made & tested for new ar token names ☑️ Completed pipeline checks for Prod deployment 📲 Updated UI/copy on dashboard, deposit, withdraw, allocation pages 🧩 Deployed changes for new frontend configuration proxy ⛓ Setup Chainlink keepers for new proxy 🟣 Deployed & tested withdrawals - base tokens / MATIC

23 Jan 2023, 03:27 UTCviews —

Amasa Announcements pinned «📢 Amasa Product Development Update🛠️ 📲 Refactored withdraw functions & UI changes 🥒 ar-aToken system cucumber testing 📄 Deployed/tested updated proxy contract 🧑‍🔧 Deployed patch fixes for withdraw workflow 🟣 Worked on wMATIC withdrawal 🪲 Graphs UI debugging…»

23 Jan 2023, 03:27 UTC≈1,780 viewsread 7 August 2026
Photo

Happy Lunar New Year to our Amasa community 🎊 May 2023 bring you a year filled with peace & prosperity 🧧🐇

23 Jan 2023, 03:26 UTC≈1,570 viewsread 7 August 2026

📢 Amasa Product Development Update🛠️ 📲 Refactored withdraw functions & UI changes 🥒 ar-aToken system cucumber testing 📄 Deployed/tested updated proxy contract 🧑‍🔧 Deployed patch fixes for withdraw workflow 🟣 Worked on wMATIC withdrawal 🪲 Graphs UI debugging & dev testing 👻 Deployed updated contract for Aave integration 🧾 Deployed/tested transactions page update 🦎 Tested graphs with Coingecko data API 🧪 Deployed/test

1 Jan 2023, 23:56 UTC≈1,320 viewsread 7 August 2026
Photo

Wishing a Happy New Year to our Amasa Community 🎉 Here's to a prosperous, creative & cutting-edge 2022 🥂

25 Dec 2022, 12:55 UTC≈1,060 viewsread 7 August 2026
Photo

Wishing our community a safe and happy holiday 💙

20 Dec 2022, 23:32 UTC978 viewsread 7 August 2026
Photo

📢 Updates to Amasa community channels As we round out 2022, the Amasa team been reviewing all activities to ensure we continue to utilize our budget optimally to deliver on Amasa’s core commitments through the protracted bear market. We’ve also been reviewing the best place for ongoing community engagement and input. In this context, we’ve decided to shift to a Discord server in 2023, and to set the Amasa Community

18 Dec 2022, 23:47 UTCviews —

Amasa Announcements pinned «Check out this week's dev update!👇 📢 Amasa Dev Update 🛠️ ✅ Completed payIncome front end updates 📈 Added wBTC Amplify option 💸 Worked on all withdrawals to USDC 📲 UI copy & info updates 🧪 Ongoing tests and bug fixes 🔨 Work continues on V1.1 features»

15 Dec 2022, 08:21 UTC412 viewsread 7 August 2026

Check out this week's dev update!👇 📢 Amasa Dev Update 🛠️ ✅ Completed payIncome front end updates 📈 Added wBTC Amplify option 💸 Worked on all withdrawals to USDC 📲 UI copy & info updates 🧪 Ongoing tests and bug fixes 🔨 Work continues on V1.1 features

8 Dec 2022, 12:02 UTC373 viewsread 7 August 2026

This week's dev update from the team!👇 📢 Amasa Dev Update - Dec 8 🛠 ⛽️ Block gas limit optimisation 🧪 Ongoing tests & bug fixing Continued working on V1.1 features 💸 payIncome block segmenting 🙋‍♂️ User deposits 📊 Dashboard user data feeds

2 Dec 2022, 00:02 UTC376 viewsread 7 August 2026

Check out this week's dev update!👇 📢 Amasa Dev Update - Dec 2 🛠 ⛽️ Gas cost optimisation & reduction 🧪 Ongoing testing & bug fixing Continued working on V1.1 features: 💸 payIncome front end 📲 User deposit front end 💰 Rewards distribution models

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

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

“Amasa Announcements” (@amasa_updates), 433 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/amasa_updates.

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.