Channel
👑دنـٍٍٍٜ٘ٗـٍٍٜٓٓیای⚘𖥘᭄🅛︎𝐈𝐕𝐄🦋عاشقـٍٍٍٜ٘ٗـٍٍٜٓٓی من و عشقم
@fazzz12
On this record: Topic · Growth · Engagement · Citations · Telegram's recommendations · Cite this entry
1,929subscribers
-43 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 | -1001426689605 |
|---|---|
| Type | Channel |
| Username | @fazzz12 |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 22 September 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/fazzz12 |
Topic
Personal blog — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 61% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Nov 2026, 03:35 | 1,929 | -4 |
| 4 Nov 2026, 06:46 | 1,933 | -6 |
| 1 Nov 2026, 12:19 | 1,939 | +7 |
| 26 Oct 2026, 01:11 | 1,932 | -2 |
| 22 Oct 2026, 17:15 | 1,934 | -3 |
| 19 Oct 2026, 12:59 | 1,937 | +2 |
| 16 Oct 2026, 20:21 | 1,935 | +5 |
| 13 Oct 2026, 09:49 | 1,930 | +9 |
| 7 Oct 2026, 02:16 | 1,921 | +2 |
| 29 Sept 2026, 22:56 | 1,919 | +2 |
| 22 Sept 2026, 01:12 | 1,917 | no change |
| 15 Sept 2026, 18:56 | 1,917 | -7 |
| 11 Sept 2026, 19:59 | 1,924 | -5 |
| 7 Sept 2026, 14:00 | 1,929 | -9 |
| 2 Sept 2026, 10:44 | 1,938 | -12 |
| 30 Aug 2026, 06:05 | 1,950 | -7 |
| 27 Aug 2026, 07:15 | 1,957 | -5 |
| 24 Aug 2026, 08:56 | 1,962 | -5 |
| 20 Aug 2026, 17:24 | 1,967 | +4 |
| 17 Aug 2026, 10:38 | 1,963 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
Mentions
Named by 52 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
@ashpazieirani · 43,7945 postsبـی تـــ♡ـــو هــــرڪَــز
@bitohargezjjj · 28,4775 postsدیوارنوشت
@divar_neveshtha · 20,0505 postsجملات طلایی
@jomlea · 29,5675 posts😍متن های خاص خدا😍
@khodaya_asheghtam · 17,0065 posts𝙆𝙡𝘽𝙚 𝙀𝙝𝙨𝙖𝙨𝙞♥️💍
@kolbeesasi · 16,0035 posts♨️میم مثل مـــ❤️ـــادر♨️
@madardostatdaramj · 21,9685 posts🎒ܩܟ̣ܝ݁ࡐטּߊܠܝܦ݃ࡅ࡙ߺܘ³¹⁵
@MAJNONE_ROGHAYEH315 · 17,7815 posts📷پیکس آرت📷
@PicsArrt · 16,0805 posts「پنآھِ‌حَـــرَم」
@PNAH_HARM · 24,2865 postsاستـــوری خاص،پروفایل شیڪ💝
@profilshiky · 17,5435 posts💞اشعار مولانا،سعدی💞
@shere_molavi · 32,7795 postsسخنان حکیمانه ناب
@sokhen_nab · 76,6355 postsڪربلانرفتھ‌ها🕊••
@STORY_HARAM · 17,1285 postsترفند محشر
@tarfand_mahshr · 30,5045 postsآشپزی|𝚌𝚘𝚘𝚔𝚒𝚗𝚐🍔🍳
@tazin_sofree · 46,4565 posts•[ وصـٰال ]•🌵
@vesssal · 25,0325 postsپروکسی فیلترشکن رایگان
@VPNPROXY4 · 31,5475 posts💛 استوری اینستاگرام 💛
@artonlinn · 11,6694 postsعُــشّــاقُ الـرُقَــیـِّـِہ{سلام الله}
@Oshaghroghaye_315 · 16,3164 postsرابطه زناشویی ... 👩❤️👨
@TebOzanashoye · 14,7024 posts『یــآدِٺ‌بــاشــد』
@yadet_bashad313 · 15,2204 posts|بیتآیی|
@BitaDd · 9,7203 postsدرمانگاه طب اسلامی گیاهی شفا
@salembem · 17,5103 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.
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.
@ahangmazani · 26,156
Telegram ranks this channel #15 of 64 here — alongside 63 others — read 12 September 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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“👑دنـٍٍٍٜ٘ٗـٍٍٜٓٓیای⚘𖥘᭄🅛︎𝐈𝐕𝐄🦋عاشقـٍٍٍٜ٘ٗـٍٍٜٓٓی من و عشقم” (@fazzz12), 1,929 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/fazzz12.
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.