9 Jun 2026, 15:05 UTC44 viewsread 9 August 2026
آیدی @bleedicei
Signed LENNOX
Channel
Advertising
@chalesh_estarz
On this record: Growth · Engagement · Posts · Citations · Cite this entry
106subscribers
-7 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003015350742 |
|---|---|
| Type | Channel |
| Username | @chalesh_estarz |
| Created | 18 September 2025 — measured — dated from the channel’s first post |
| First recorded | 9 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/chalesh_estarz |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 08:21 | 106 | -1 |
| 5 Sept 2026, 02:56 | 107 | -1 |
| 21 Aug 2026, 22:07 | 108 | -4 |
| 14 Aug 2026, 18:05 | 112 | -1 |
| 9 Aug 2026, 06:18 | 113 | no change |
| 7 Aug 2026, 17:40 | 113 | first reading |
Engagement
7 posts held, back to 18 September 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 7 posts for this entry, the most recent from 9 June 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
9 Jun 2026, 15:05 UTC47 viewsread 9 August 2026
سلام درود عرض خسته نباشید چنل ترشح به فروش میرسید با بهترین قیمت https://t.me/Traasho
Signed LENNOX
4 Jun 2026, 21:02 UTC61 viewsread 9 August 2026
Photo
Photo, posted without a caption
Signed LENNOX
4 Jun 2026, 21:01 UTC61 viewsread 9 August 2026
Photo
Photo, posted without a caption
Signed LENNOX
2 Jun 2026, 19:39 UTC98 views0 reactionsread 9 August 2026
تعرفه تبلیغات در چنل «ترشح» 🧠🩸 ⏰ تبلیغات زمانی 3 ساعت : 150.000 6 ساعت : 250.000 9 ساعت : 300.000 12 ساعت : 330.000 24 ساعت : 330.000 ━━━━━━━━━━━━━━ ━━━━━━━━━━━━━━ ━━━━━━━━━━━━━━ 📌 پین پست : 30.000 💬 هر ریپلای : 8.000 🔄 ریشات : 20.000 ━━━━━━━━━━━━━━ 📍 توضیحات • ممبرها واقعی و فعال هستند. • تبلیغات در کانال ترشح با بهترین بازده انجام میشود. • تعرفهها ثابت و منصفانه هستند. ━━━━━━━━━━━━━━ 📥 جهت هماهنگی و ثبت تبلیغ:…
Signed LENNOX
2 Jun 2026, 19:31 UTC≈6,240 viewsread 9 August 2026
تبلیغات
Signed LENNOX
18 Sept 2025, 17:49 UTCviews —
Channel created
Showing the 7 most recent of 7 posts we hold for @chalesh_estarz. 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.
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.
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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“Advertising” (@chalesh_estarz), 106 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/chalesh_estarz.
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.