Channel name was changed to «persicosaffron»

Channel
persicosaffron
@persicosaffron
On this record: Topic · Growth · Engagement · Posts · Cite this entry
56subscribers
-2 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 | -1001002851513 |
|---|---|
| Type | Channel |
| Username | @persicosaffron |
| Created | Between 1 September 2015 and 31 December 2015 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 6 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 6 October 2026 |
| On Telegram | t.me/persicosaffron |
Topic
Other / unclassifiable — 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 29 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Sept 2026, 08:41 | 56 | -1 |
| 15 Aug 2026, 18:15 | 57 | -1 |
| 10 Aug 2026, 06:16 | 58 | no change |
| 7 Aug 2026, 22:57 | 58 | first reading |
Engagement
20 posts held, back to 5 May 2019 — 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 19 April 2024. An engagement rate over an empty window would be a number about nothing.
Recent posts
Channel photo updated
Channel photo removed
Channel name was changed to «persico»
Channel name was changed to «Persicosaffron»
شنبتون پر انرژي و صبح دلتون روشنِ روشن☺️🌷 . . . همراهِ ما در اينستاگرام
روزگارت خوش باد و دلت سرخوش تر خانه ات مثل هوا پر ابر و نفس گرم خدا که به هر رهگذری میدمد شوق خوش زیستن و بودن را روزگارت خوش باد
آخر هفتتون خوش و خرم 🌷 . . . @persicosaffron
سلام روزتون بخير🌷 . . . آب ،چند پر زعفرون و چند دونه غنچه ي گل محمدي بهمراه شيرين كننده ي طبيعي مثل عسل. هم سادست هم پر خاصيت و خوش عطر و از همه مهم تر #ارگانيك و سالم 🍹 . . . #پرسيكو#سلامتي
در اينستا گرام هم همراه ما باشيد . . . . . . @Persicosaffron
زندگي فهم نفهميدن هاست زندگي پنجره اي باز به دنياي وجود،تا كه اين پنجره باز است جهاني با ماست. آسمان،نور،خدا،عشق،سعادت با ماست. فرصت بازي اين پنجره را دريابيم🌷
ما با کیفیت محصولاتمان مرز ها را شکستیم و خرسندیم که در همه جا کنار شما و همراهتانیم . . . @Persicosaffron
Showing the 12 most recent of 20 posts we hold for @persicosaffron. 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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“persicosaffron” (@persicosaffron), 56 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/persicosaffron.
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.