Telegram RegisterThe public register of Telegram
Telegram profile photo for ⚜️ اتو موسیوند ⚜️

Channel

⚜️ اتو موسیوند ⚜️

@auto_mousivand

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

1,160subscribers

+3 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-1001932521099
TypeChannel
Username@auto_mousivand
CreatedBetween 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/auto_mousivand

Growth

1,1561,1601,1587 August 2026 — 1,157 subscribers7 August 2026 — 1,157 subscribers8 August 2026 — 1,156 subscribers11 August 2026 — 1,158 subscribers14 August 2026 — 1,160 subscribers7 August 202614 August 2026
5 measurements spanning 7 days, net +3. 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,155–1,161 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 19:061,160+2
11 Aug 2026, 06:261,158+2
8 Aug 2026, 02:311,156-1
7 Aug 2026, 23:341,157no change
7 Aug 2026, 12:551,157first reading

Engagement

20 posts held, back to 5 August 2026the 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.

ERR · 30 days
8.87%
avg views ÷ 1,160 subscribers
Avg views / post
103
20 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
20
of 20 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held20 (5 August 20267 August 2026)
Views total2,058
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 23:34 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

7 Aug 2026, 16:26 UTC62 viewsread 7 August 2026

خریدار ریرا سفید سر دنده جدید برج روز قیمت 👌👌 09128934595

Signed ebrahim mousivand

6 Aug 2026, 08:44 UTC125 viewsread 7 August 2026

تمام پر برکت اقای عنصری 🌹🙏

Signed ebrahim mousivand

6 Aug 2026, 08:35 UTC128 viewsread 7 August 2026

سورن موتور پارس دریچه برقی 405 برج روزز 1/560 پلاک تهران 09128934595 09127670901

Signed ebrahim mousivand

6 Aug 2026, 08:34 UTC127 viewsread 7 August 2026

دنا اتومات مشکی 405برج 4 پلاک ،،تهران،حومه سند اماده 09127670901 09128934595

Signed ebrahim mousivand

6 Aug 2026, 08:31 UTC29 viewsread 7 August 2026

۲۰۷ 207 پانا اتومات سفید ۴۰۵ روز پلاک تهران حومه 🔥🔥2/600 09127670901 09128934595

Signed ebrahim mousivand

6 Aug 2026, 08:30 UTC27 viewsread 7 August 2026

207 پانا اتومات مشکی 405 برج 2 پلاک تهران 09128934595 09127670901

Signed ebrahim mousivand

6 Aug 2026, 07:48 UTC113 viewsread 7 August 2026

تمام پر برکت هایپر خودور🌹🙏

Signed ebrahim mousivand

6 Aug 2026, 06:43 UTC32 viewsread 7 August 2026

چانگان cs55 خاکستری واردات 2025 پلاک تهران روزز کارت طلایی نقدی 🔥🔥 5/740 09127670901 09128934595

Signed ebrahim mousivand

6 Aug 2026, 06:43 UTC31 viewsread 7 August 2026

ریرا مشکی سر دنده جدید 405 برج روز 3/620 پلاک تهران ،،،حومه 09128934595 09127670901

Signed ebrahim mousivand

6 Aug 2026, 06:40 UTC106 viewsread 7 August 2026

هایما S7سفید 405 بر2 یا 3 4/500 پلاک تهران سند یک ساعته 09127670901 09128934595

Signed ebrahim mousivand

6 Aug 2026, 06:19 UTC104 viewsread 7 August 2026

سورن دوگانه سیمی ۴۰۵ روز تهران مخزن کوچک حومه به شرط واریزی 1/910 09127670901 09128934595

Signed ebrahim mousivand

6 Aug 2026, 06:19 UTC115 viewsread 7 August 2026
Forwarded from @funnypinkVideo

1405/5/15 روزی پر از عشق ومحبت🌸🍃 روزى پر از مـوفـقيت و شـادى🌸🍃 روزى پر از خـنـده و دل خـوشى 🌸🍃 و روزی پر از خـبـرهـای خـوب 🌸🍃 براتون آرزومندم..... آخرهفته تون عالی و بینظیر🌸🍃 @funnypink

Signed ebrahim mousivand

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

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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.

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.

“⚜️ اتو موسیوند ⚜️” (@auto_mousivand), 1,160 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/auto_mousivand.

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.