Channel
@amasa_updates
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
422subscribers
-19 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001302390027 |
|---|---|
| Type | Channel |
| Username | @amasa_updates |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 5 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 2 times, most recently 5 October 2026 |
| On Telegram | t.me/amasa_updates |
Other / unclassifiable — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 52% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Sept 2026, 04:17 | 422 | -3 |
| 11 Sept 2026, 07:36 | 425 | -2 |
| 3 Sept 2026, 04:18 | 427 | -3 |
| 27 Aug 2026, 19:42 | 430 | -3 |
| 21 Aug 2026, 18:06 | 433 | -3 |
| 15 Aug 2026, 10:54 | 436 | -5 |
| 7 Aug 2026, 01:31 | 441 | no change |
| 7 Aug 2026, 01:20 | 441 | first reading |
20 posts held, back to 4 November 2022 — the 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 February 2023. An engagement rate over an empty window would be a number about nothing.
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…»
📢 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
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…»
Happy Lunar New Year to our Amasa community 🎊 May 2023 bring you a year filled with peace & prosperity 🧧🐇
📢 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…
Wishing a Happy New Year to our Amasa Community 🎉 Here's to a prosperous, creative & cutting-edge 2022 🥂
Wishing our community a safe and happy holiday 💙
📢 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…
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»
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
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
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.
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.
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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“Amasa Announcements” (@amasa_updates), 422 subscribers as measured 25 September 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.