Telegram RegisterThe public register of Telegram
Telegram profile photo for .

Channel

.

@Yasinistaar

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry

200subscribers

-1 since we began measuring on 1 October 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001891935774
TypeChannel
Username@Yasinistaar
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded1 October 2026
Last confirmed live6 October 2026
Measurements held2
Confirmed unchanged1 time, most recently 6 October 2026
On Telegramt.me/Yasinistaar

Growth

200201200.51 October 2026 — 201 subscribers6 October 2026 — 200 subscribers1 October 20266 October 2026
2 measurements spanning 5 days, net -1. 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 200–201 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Oct 2026, 03:59200-1
1 Oct 2026, 13:22201first reading

Engagement

20 posts held, back to 28 May 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 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 17 August 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
5m 11s
Average length
52s

Measured directly from 6 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Recent posts

20 Jul 2025, 20:55 UTC698 viewsread 1 October 2026
File

یه ریمیکس جذاب با حضور علی یاسینی ، شایع ، مهیار ، مسلک ، لنا -Orkide | @vibeRemix

16 Jul 2025, 18:29 UTC563 viewsread 1 October 2026
Forwarded from @Amirhocyxn_channel

نوان-علی یاسینی-اشوان- هم موزیکشون رفت واسه مجوز گرفتن @amirhocyxn_channel

12 Jun 2025, 09:55 UTC≈1,990 viewsread 1 October 2026
Photo

توییت لیما راجب کنسرت تهران ..😕

Signed panii

8 Jun 2025, 18:05 UTC674 viewsread 1 October 2026
Forwarded from @Yasiniloove

یکی سر اجرای میرسه خبرا غش کرده و یه سریا گفتن تشنج کرده متاسفانه و بردنش بیرون):

8 Jun 2025, 18:05 UTC623 viewsread 1 October 2026
Forwarded from @mehrgolyasiniVideo

اتفاقی که امشب تو کنسرت افتاد 🙁 کنسرت بوشهر _اختصاصی چنل _ کپی بصورت فورواردی...! 📌 1404/3/18 - 𝗠𝗘𝗛𝗥𝗬𝗬𝗔𝗦𝗜𝗡𝗜 _𝗚𝗢𝗜𝗡 𝗧𝗢 𝗠𝗬 𝗖𝗛𝗔𝗡𝗘𝗟: @mehrgolyasini

8 Jun 2025, 15:07 UTC595 viewsread 1 October 2026

کنسرت هشتگرد✨ 28 خرداد ماه - بلیت فروشي فردا ساعتِ 16 - از سایتِ هنرتیکت…

6 Jun 2025, 17:23 UTC633 viewsread 1 October 2026

کنسرت هشتگرد🖇️ 28 خرداد ماه - بلیت فروشي فردا ساعتِ 16 از سایت هنرتیکت

2 Jun 2025, 18:49 UTC444 viewsread 1 October 2026

کنسرت ابادان✨ 23 خرداد ماه - بلیت فروشي فردا ساعتِ 20 - از سایتِ هنرتیکت…

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

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

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.

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.

تهران كنسرت Tehran Concert
@tehranconcertt · 19,342
Telegram ranks this channel #10 of 62 here — alongside 61 others — read 1 October 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list 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 6 October 2026 — this entry's latest reading, not the date you are reading this.

“.” (@Yasinistaar), 200 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/Yasinistaar.

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.