Telegram RegisterThe public register of Telegram
Telegram profile photo for گروه تولیدی تک

Channel

گروه تولیدی تک

@tolidmizassali

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

1,339subscribers

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

Growth

1,3391,3601,349.57 August 2026 — 1,360 subscribers7 August 2026 — 1,360 subscribers10 August 2026 — 1,358 subscribers13 August 2026 — 1,357 subscribers16 August 2026 — 1,355 subscribers19 August 2026 — 1,351 subscribers23 August 2026 — 1,349 subscribers26 August 2026 — 1,347 subscribers29 August 2026 — 1,344 subscribers1 September 2026 — 1,341 subscribers5 September 2026 — 1,339 subscribers7 August 20265 September 2026
11 measurements spanning 29 days, net -21. 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,336–1,363 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 01:581,339-2
1 Sept 2026, 12:561,341-3
29 Aug 2026, 16:431,344-3
26 Aug 2026, 11:221,347-2
23 Aug 2026, 05:071,349-2
19 Aug 2026, 21:221,351-4
16 Aug 2026, 20:371,355-2
13 Aug 2026, 07:441,357-1
10 Aug 2026, 05:201,358-2
7 Aug 2026, 04:081,360no change
7 Aug 2026, 02:001,360first reading

Engagement

9 posts held, back to 16 December 2025the 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 9 posts for this entry, the most recent from 16 December 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

16 Dec 2025, 17:29 UTC313 viewsread 7 August 2026

بیوتی دوموتوره 101 👆👆👆 قطر》60سانت صفحه کاغذ دیواری کارتن》4عددی قیمت 》1.090.000

16 Dec 2025, 17:29 UTC272 viewsread 7 August 2026

سیتیزن کد 06👆👆👆 کارتن》3عددی صحفه چوب قطر》75سانت قیمت》1.315.000

16 Dec 2025, 17:29 UTC198 viewsread 7 August 2026

سیتیزن کد 05👆👆👆 کارتن》3عددی صحفه چوب قطر》75سانت قیمت》1.315.000

16 Dec 2025, 17:29 UTC162 viewsread 7 August 2026

سیتیزن کد 04👆👆👆 کارتن》3عددی صحفه چوب قطر》75سانت قیمت》1.315.000

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

“گروه تولیدی تک” (@tolidmizassali), 1,339 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/tolidmizassali.

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.