Telegram RegisterThe public register of Telegram
Telegram profile photo for   ‌fanfic

Channel

  ‌fanfic

@kmfanfic

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

83subscribers

+27 since we began measuring on 13 August 2026

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

Register entry

Telegram ID-1003951104356
TypeChannel
Username@kmfanfic
CreatedBetween 1 April 2026 and 21 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live14 November 2026
Measurements held9
Confirmed unchanged2 times, most recently 14 November 2026
On Telegramt.me/kmfanfic

Topic

Literature — 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 27 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 the other topics.

Growth

56967613 August 2026 — 56 subscribers15 August 2026 — 58 subscribers21 August 2026 — 92 subscribers5 September 2026 — 96 subscribers14 September 2026 — 94 subscribers25 September 2026 — 89 subscribers7 October 2026 — 86 subscribers22 October 2026 — 85 subscribers6 November 2026 — 83 subscribers8313 August 20266 November 2026
9 measurements spanning 84 days, net +27. 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 50–102 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Nov 2026, 08:5983-2
22 Oct 2026, 15:3785-1
7 Oct 2026, 10:5786-3
25 Sept 2026, 23:2289-5
14 Sept 2026, 00:4294-2
5 Sept 2026, 19:5996+4
21 Aug 2026, 23:1792+34
15 Aug 2026, 01:5458+2
13 Aug 2026, 22:0456first reading

Engagement

20 posts held, back to 21 July 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 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 11 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

84 reactions across 9 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🆒84100.0%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 14 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 84 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 21 July 2026 to 11 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

11 Aug 2026, 17:15 UTC23 viewsread 13 August 2026

عاشقش میشینننن، قشنگ ترین فیکشن بدون اسمات دنیا :) نمره ۱۰ براش کمه 💛

Signed   ák

11 Aug 2026, 17:14 UTC15 views6 reactionsread 13 August 2026
Forwarded from @koomiiinFile

𝓑𝓮𝓯𝓸𝓻 𝓘 𝓚𝓷𝓮𝔀 𝓨𝓸𝓾 🤩 قبل از اینکه بشناسمت 🤍 couple : kookmin ( full ) 🤍 genre : romance , slice of life 🤍 writer : ghazal 🤍 channel : @koomiinn جئون جونگکوک ؛ پسري که تو زندگیش هیچ ترسي از امتحان کردن چیزاي جدید نداره اما چي میشه اگه این پسر پرآوازه تو یه دورهمي با دوستاش تو یه کلاب معروف تو سئول با پارک جیمین عضو جدید اون گروه بخواد چیزي رو تجربه کنه که تاحالا نکرده ؟

🆒6

9 Aug 2026, 21:25 UTC33 viewsread 13 August 2026

خیلی جالب بود و استرس زا واقعا دوسش داشتم حتما بخونین ، اگه خشن دوست دارین لذت میبرین ؛ نمره ۹ از ۱۰ .

Signed   ák

9 Aug 2026, 21:24 UTC35 views5 reactionsread 13 August 2026
File

fic #DeathPoint ៸ نقطه مرگ 💀 • couple : kookmin , kookgi • genre : romance , angst , hursh , smut • hashtags : revenge , past love , happy end • reverted by @ares_fiction • channel : @jasper_fiction خلاصه : پارک جیمین ، بازیگری که از دوست پسرش جدا شد و دستور قتلش رو داد، حالا بعد از چهار سال با اون سر صحنه فیلم برداری رو به رو میشه . اونا قراره یه فیلم و با هم بازی کنن و نقش مقابل همن ؟ چی میشه اگه جونگ‌کوک…

🆒5

27 Jul 2026, 22:44 UTC79 viewsread 13 August 2026

خیلی وقت پیش خوندم و واقعا دوسش داشتم ، قلم خوبی داره ؛ نمره ۸.۵ از ۱۰ .

Signed   ák

27 Jul 2026, 22:43 UTC80 views7 reactionsread 13 August 2026
File

fic #Remedy ៸ راه حل - درمان 💎 • couple : kookmin , yoontae • genre : romance , angst , fluff , slice of life , smut • hashtags : sex education , happy end • writer : @thisisspring • channel : @Jikookers خلاصه : جیمین به گفته خانوادش برای کاراموز شدن توی کمپانی جئون بعد از سال ها جونگ‌کوک و میبینه، کسی که کل بچگیشون باهم بودن و گذروندن. اما چی میشه اگه جیمین جدید فوبیای لمس شدن و رابطه داشته باشه و هربار …

🆒7

25 Jul 2026, 20:43 UTC78 views7 reactionsread 13 August 2026

به معنای واقعی کلمه عاشقشم :) قلم خوبی داره و قراره کلی باهاش گریه کنین ؛ نمره ۹.۵ از ۱۰ .

🆒7

Signed   ák

25 Jul 2026, 20:41 UTC80 views9 reactionsread 13 August 2026
File

fic #WhiteLily ៸ لیلیوم سفید 🌟 • couple : kookmin • genre : romance , angst , dram , slice of life , smut • hashtags : past love , happy end • writer : anid • channel : @kookminlandfiction خلاصه : جیمین و جونگکوک عشق های اول همدیگه بودن ، در حالی که جونگکوک جیمین و ترک کرده بود بعد چند سال سرنوشت این دو رو دوباره سر راه هم قرار میده. اما چی میشه جونگکوک مثل روز اول عاشق باشه و جیمین ازش متنفر باشه ؟! 📤 pr…

🆒9

25 Jul 2026, 14:31 UTC70 viewsread 13 August 2026

راستش آنچنان فیکشن قوی نیست ، جیمین پاور باتمه ولی خیلی جاها واقعا کاراش عصبیم میکرد ، در کل برا وقت گذروندن بد نیست؛ نمره ۷ از ۱۰ رو میدم بهش .

Signed   ák

25 Jul 2026, 14:30 UTC71 views8 reactionsread 13 August 2026
File

fic #30DaysHusband ៸ شوهر سی روزه 💍 • couple : kookmin , vmin • genre : romance , mpreg , smut • hashtags : slow burn , one sided love , forbidden marriage , happy end • translator : fafa • channel : @kookminmetanoia خلاصه : جیمین عاشق تهیونگه و جونگ‌کوک عشق قدیمی نسبت بهش داره . جونگکوک وقتی متوجه میشه کسی که قراره بزور باهاش ازدواج کنه جیمینه بشدت خوشحال میشه اما اگه جیمین بهش بگه تنها یک ماه این قرارداد…

🆒8

21 Jul 2026, 22:10 UTC103 views9 reactionsread 13 August 2026

یکی از قشنگ ترین فیکشن های امگاورسی که میتونین بخونین ، یکم کلیشه ایه ولی ارزش خوندن داره . جونگکوک گرین فلگ ترینه 😭. نمره ۱۰ از ۱۰ !!

🆒9

Signed   ák

21 Jul 2026, 22:08 UTC110 views14 reactionsread 13 August 2026
File

fic #matthiola ៸ ماتیولا 💍 • couple : kookmin • genre : romance , omegaverse , angst , mpreg , smut • hashtags : enemies to lovers , slow burn , forbidden marriage , stereotype , happy end • writer : roya , fafa • channel : @matthiolagallery خلاصه : جیمین یک امگای شاد و شیطون که با رفیقاش خیلی خوش میگذرونه ، اما یروز که برمیگرده خونه پدرش ازش میخواد با پسر خانواده جئون بخوابه و یه وارث بیاره ؛ آیا جیمین ب…

🆒14

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

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.

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 6 November 2026 — this entry's latest reading, not the date you are reading this.

“  ‌fanfic” (@kmfanfic), 83 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/kmfanfic.

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.