The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 29 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

Channel
AutoLayer Announcements
@AutoLayerPortal
On this record: Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
9,126subscribers
-199 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001575537445 |
|---|---|
| Type | Channel |
| Username | @AutoLayerPortal |
| Created | Between 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 28 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 28 August 2026 |
| On Telegram | t.me/AutoLayerPortal |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Aug 2026, 22:54 | 9,126 | -22 |
| 25 Aug 2026, 18:24 | 9,148 | -29 |
| 22 Aug 2026, 08:58 | 9,177 | -36 |
| 19 Aug 2026, 04:34 | 9,213 | -40 |
| 16 Aug 2026, 06:46 | 9,253 | -23 |
| 13 Aug 2026, 03:14 | 9,276 | -18 |
| 10 Aug 2026, 08:11 | 9,294 | -24 |
| 7 Aug 2026, 04:00 | 9,318 | -7 |
| 6 Aug 2026, 07:32 | 9,325 | first reading |
Engagement
15 posts held, back to 7 October 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 31 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- —
- no view readings in window
- Avg views / post
- —
- no view readings
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 1
- of 15 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 15 August 2026 |
|---|---|
| Posts held | 15 (7 October 2025 – 15 August 2026) |
| Views total | — |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Aug 2026, 15:12 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Recent posts
After years of building and iterating in DeFi and AI, AutoLayer has reached its conclusion. Despite technical excellence and constant innovation, market realities and operational constraints made continued development unsustainable, and thus, we will responsibly close our doors. We thank everyone for being part of this incredible journey. Full details here: https://x.com/AutoLayer/status/1992941319442891150
Signed 0xYnaR | AutoLayer
GM ✨ https://x.com/AutoLayer/status/1980954742110261474
Signed Ian | AutoLayer
Enjoy the view 🎈 https://x.com/AutoLayer/status/1980279126629183979
Signed Ian | AutoLayer
Another AI Agent Market Report coming in hot 🔥 Let's look at how things are doing over on Ethereum. So far, we've got a good mix of price increases and good sentiment 🙆 Check them out, and other AI agents here: https://app.autolayer.io https://x.com/AutoLayer/status/1978834560801763520
Signed Ian | AutoLayer
Hey ✨ https://x.com/AutoLayer/status/1978453334576300096
Signed Ian | AutoLayer
Stay perched 🦉 https://x.com/AutoLayer/status/1978062161995038958
Signed 0xYnaR | AutoLayer
Let's start this week off with positive news ➕ The AI Agent market is in a good place today, particularly over at Base. Sentiment is at a high level, and so are the prices! This is our AI Agent Market Report for the week 👑 https://x.com/AutoLayer/status/1977721872809955549
Signed Ian | AutoLayer
Let's go full bull mode ✨ https://x.com/AutoLayer/status/1977675962398671294
Signed Ian | AutoLayer
Time to kick your feet up and relax, for it has been a long week. One trade or move you’re proud of this week?? We’d love to know 🧡 https://x.com/AutoLayer/status/1976649105423389064
Signed Ian | AutoLayer
The latest Farseer release is in development 🦉 This update will include new features, such as enhanced integration with $LAY3R and improved interoperability across the AutoLayer ecosystem Check out what the new features will be in this thread 🧵 https://x.com/AutoLayer/status/1976588567372775860
Signed Ian | AutoLayer
GM Time to make your shot count ⚽️ https://x.com/AutoLayer/status/1976226180023095459
Signed Ian | AutoLayer
Showing the 12 most recent of 15 posts we hold for @AutoLayerPortal. 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.
Citation-graph rank
Citation-graph rank — 208,882 of 1,626,884entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@RWA_Inc_Announcements · 41,854
Telegram ranks this channel #11 of 87 here — alongside 86 others — read 29 August 2026
@selfchainxyz · 109,618
Telegram ranks this channel #23 of 91 here — alongside 90 others — read 14 August 2026
@HomerAndCrypto · 426,463
Telegram ranks this channel #45 of 71 here — alongside 70 others — read 19 August 2026
@kannada_kpsc_quiz · 40,665
Telegram ranks this channel #49 of 56 here — alongside 55 others — read 30 August 2026
@yeezygem · 57,772
Telegram ranks this channel #58 of 62 here — alongside 61 others — read 26 August 2026
@ForwardProtocol · 46,315
Telegram ranks this channel #62 of 80 here — alongside 79 others — read 27 August 2026
@sakutin_csharp · 72,872
Telegram ranks this channel #79 of 86 here — alongside 85 others — read 19 August 2026
@infiniteseasdev · 50,935
Telegram ranks this channel #86 of 91 here — alongside 90 others — read 25 August 2026
@clusterprotocolann · 44,495
Telegram ranks this channel #89 of 92 here — alongside 91 others — read 28 August 2026
This channel appears in 9 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 28 August 2026 — this entry's latest reading, not the date you are reading this.
“AutoLayer Announcements” (@AutoLayerPortal), 9,126 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/AutoLayerPortal.
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.