Channel
@fiction_12
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
7,637subscribers
+57 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001054767539 |
|---|---|
| Type | Channel |
| Username | @fiction_12 |
| Created | Between 1 May 2016 and 28 February 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/fiction_12 |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 52% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 11:57 | 7,637 | +5 |
| 12 Sept 2026, 03:21 | 7,632 | -4 |
| 7 Sept 2026, 11:00 | 7,636 | +2 |
| 3 Sept 2026, 01:38 | 7,634 | -2 |
| 31 Aug 2026, 04:18 | 7,636 | +6 |
| 28 Aug 2026, 11:53 | 7,630 | -11 |
| 25 Aug 2026, 11:47 | 7,641 | +6 |
| 22 Aug 2026, 09:49 | 7,635 | +30 |
| 18 Aug 2026, 22:35 | 7,605 | +4 |
| 16 Aug 2026, 03:36 | 7,601 | -3 |
| 12 Aug 2026, 20:34 | 7,604 | -2 |
| 9 Aug 2026, 20:52 | 7,606 | +28 |
| 6 Aug 2026, 11:41 | 7,578 | -2 |
| 6 Aug 2026, 03:06 | 7,580 | first reading |
24 posts held, back to 6 June 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 19 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 28 August 2026 |
|---|---|
| Posts held | 24 (6 June 2026 – 28 August 2026) |
| Views total | 300 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Aug 2026, 21:27 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Measured directly from 1 video 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.
صدفیلمی که قبل از مرگ باید دید در 🪁@honar7modiran متن های انگیزشی 🪁@khalse_daroon کتاب صوتی و فیلم مفهومی 🪁@ArchiveAudio گلچین کتابهای صوتی PDF 🪁@ketabegoia جملاتی که شما رو میخکوب میکنه! 🪁@its_anak آموزش زبان انگلیسی کدینگ جدید 🪁@Eng_Learners_Mb انگلیسی حرفه ای کودک و بزرگسال 🪁@RealEnConversations کتاب بخوانیم 🪁@LibMajazi خودت روانشناس فرزند پرخاشگرت باش 🪁@ghasemi8484 ترکی فووول صحبت کن 🪁@TurkishDilli کتاب…
#طبیعت #برگ @PURITY_SHOT
رمان دِمیان نویسنده: #هرمان_هسه @Fiction_12
تا انتهای شهریورماه، در گروه #خطبهخط_باهم میخواهیم رمان «دمیان» از نویسندۀ آلمانی #هرمان_هسه را بخوانیم و دربارهاش صحبت کنیم. این رمان بهصورت فایل پیدیاف در کانال گذاشته میشود، اما اگر دوست دارید آن را همراه با گروه بخوانید و در گپوگفتی صمیمانه شرکت کنید، میتوانید از طریق آدرس زیر در گروهِ متصل به کانال عضو شوید. @Fiction_11
تا انتهای مردادماه، در گروه #خطبهخط_باهم میخواهیم مجموعه داستانهای کوتاه «کمدیهای کیهانی» از نویسندۀ ایتالیایی #ایتالو_کالوینو را بخوانیم و دربارهاش صحبت کنیم. این مجموعهداستان بهصورت فایل پیدیاف در کانال گذاشته میشود، اما اگر دوست دارید آن را همراه با گروه بخوانید و در گپوگفتی صمیمانه شرکت کنید، میتوانید از طریق آدرس زیر در گروهِ متصل به کانال عضو شوید. @Fiction_11
مجموعه داستانهای کوتاه کمدیهای کیهانی نویسنده: #ایتالو_کالوینو @Fiction_12
سفرت بهخیر اما، تو و دوستی، خدا را چو ازین کویر وحشت به سلامتی گذشتی به شکوفهها به باران برسان سلام ما را @FICTION_12 🖤❤️
#کاریکلماتور رفتیم خرج زندگی را درآوریم، زندگی دخلمان را درآورد! #م_سرخوش @Fiction_12
#کاریکلماتور در غار تنهایی، موبایل آنتن نمیدهد! #م_سرخوش @Fiction_12
#پاراگراف «کاش وعدههای کشیشا درست بود و فقیربیچارهها دستکم اون دنیا دستشون به جایی بند بود». «آه، کشیشا! اگه خودشون به این حرفا اعتقاد داشتن، کمتر میخوردن و بیشتر کار میکردن تا اون بالا جایی واسه خودشون دستوپا کنن. نه باباجون، آدم وقتی مُرد دیگه مُرده!» #امیل_زولا از کتاب #ژرمینال @Fiction_12
خیالم که اوج گرفت، گیر کرد لای خطوط فقر. #م_سرخوش #کاریکلماتور مجله کاریکلماتور 🍎 @alirezajamshididastana
#یادداشتهای_روزمره همیشه خیال میکردم غمگینترین آدمهای دنیا کسانی هستند که یادشان نمیآید آخرینبار چه وقت خندیدهاند، تا اینکه به خودم آمدم و دیدم یادم نیست آخرینبار کِی گریه کردهام، و - بین خودمان بماند، هیچ ربطی به قَوی بودن ندارد - چقدر غمگین شدم از این که دیگر هیچ غمی نمیتواند اشکم را درآورد... #م_سرخوش @Fiction_12
Showing the 12 most recent of 24 posts we hold for @fiction_12. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 69 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.
Names
Channels on the register whose handles appear in this channel's 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.
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.
This channel appears in 6 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“کاغذِ خطخطی (داستان-رمان)” (@fiction_12), 7,637 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/fiction_12.
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.