Channel

Aiosmmfollows ~ Updates 📢

@Aiosmmfollows_update

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

1,108subscribers

-15 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID	-1001523691713
Type	Channel
Username	@Aiosmmfollows_update
Created	Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded	8 August 2026
Last confirmed live	19 September 2026
Measurements held	13
Confirmed unchanged	1 time, most recently 19 September 2026
On Telegram	t.me/Aiosmmfollows_update

Topic

Ecommerce storefront — 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 87% 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.

Growth

13 measurements spanning 43 days, net -15. 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 1,103–1,126 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
19 Sept 2026, 15:58	1,108	-4
15 Sept 2026, 01:19	1,112	+2
11 Sept 2026, 04:36	1,110	+3
6 Sept 2026, 16:17	1,107	+1
2 Sept 2026, 15:08	1,106	-1
30 Aug 2026, 22:28	1,107	-4
27 Aug 2026, 21:07	1,111	-1
25 Aug 2026, 03:06	1,112	-3
21 Aug 2026, 12:58	1,115	-4
18 Aug 2026, 13:43	1,119	+2
11 Aug 2026, 19:53	1,117	-6
8 Aug 2026, 00:01	1,123	no change
7 Aug 2026, 20:07	1,123	first reading

Engagement

20 posts held, back to 2 June 2026 — 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 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

4 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 75.0% of them.

Every reaction kind recorded on the sample, most used first
Reaction	Count	Share	Share, drawn
❤	3	75.0%
👍	1	25.0%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 3 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 4 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 2 June 2026 to 3 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

3 Aug 2026, 11:26 UTC49 viewsread 8 August 2026

27 Jul 2026, 08:00 UTC109 views1 reactionsread 8 August 2026

❤1

14 Jul 2026, 06:24 UTC185 viewsread 8 August 2026

13 Jul 2026, 07:43 UTC146 viewsread 8 August 2026

13 Jul 2026, 07:21 UTC98 viewsread 8 August 2026

7 Jul 2026, 05:35 UTC129 viewsread 8 August 2026

Signed Эйамин Ислам

5 Jul 2026, 06:42 UTC121 views2 reactionsread 8 August 2026

❤2

Signed Эйамин Ислам

5 Jul 2026, 06:08 UTC110 viewsread 8 August 2026

Signed Эйамин Ислам

4 Jul 2026, 04:53 UTC119 viewsread 8 August 2026

Signed Эйамин Ислам

30 Jun 2026, 09:31 UTC135 viewsread 8 August 2026

Signed Эйамин Ислам

28 Jun 2026, 10:24 UTC134 viewsread 8 August 2026

Signed Эйамин Ислам

27 Jun 2026, 04:37 UTC142 viewsread 8 August 2026

Signed Эйамин Ислам

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

“Aiosmmfollows ~ Updates 📢” (@Aiosmmfollows_update), 1,108 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/Aiosmmfollows_update.

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.