Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝗟𝗶𝗺𝗲𝗿𝗲𝗻𝗰𝗲

Channel

𝗟𝗶𝗺𝗲𝗿𝗲𝗻𝗰𝗲

@Limerence_M

On this record: Topic · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry

1,053subscribers

-190 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001931492596
TypeChannel
Username@Limerence_M
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 September 2026
Measurements held13
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/Limerence_M

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 19 September 2026 and assigned it the closest of 31 fixed categories, at 48% 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

1,0531,2431,1488 August 2026 — 1,243 subscribers9 August 2026 — 1,234 subscribers12 August 2026 — 1,207 subscribers15 August 2026 — 1,201 subscribers18 August 2026 — 1,182 subscribers21 August 2026 — 1,161 subscribers24 August 2026 — 1,121 subscribers27 August 2026 — 1,129 subscribers31 August 2026 — 1,111 subscribers3 September 2026 — 1,121 subscribers7 September 2026 — 1,083 subscribers11 September 2026 — 1,069 subscribers15 September 2026 — 1,053 subscribers8 August 202615 September 2026
13 measurements spanning 38 days, net -190. 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 1,025–1,272 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 18:011,053-16
11 Sept 2026, 18:141,069-14
7 Sept 2026, 15:181,083-38
3 Sept 2026, 00:251,121+10
31 Aug 2026, 01:231,111-18
27 Aug 2026, 23:261,129+8
24 Aug 2026, 19:531,121-40
21 Aug 2026, 05:171,161-21
18 Aug 2026, 10:461,182-19
15 Aug 2026, 20:161,201-6
12 Aug 2026, 09:541,207-27
9 Aug 2026, 16:211,234-9
8 Aug 2026, 21:011,243first reading

Engagement

19 posts held, back to 8 August 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 19 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

8 Aug 2026, 20:44 UTC12 viewsread 8 August 2026

تو انقدر حرفات، رفتارات، لبخندات، غرغر کردنات و در کل بودنت قشنگه که بیا تمام قلب من مالِ تو.

Signed MaYsa

8 Aug 2026, 20:38 UTC21 viewsread 8 August 2026

چت جی پی تی می‌گفت هرچقدر جسماتون یه فاصله ای بزارن، روحاتون بهم وابسته‌ شدن، چقدر راست گفت.

Signed MaYsa

8 Aug 2026, 20:36 UTC21 viewsread 8 August 2026

من وقتی بهت میگم دوسِت دارم، واقعا تموم حسم اون تو نیست، من وقتی عمق عشقمو بهت نشون میدم که باهام حرف بزنی و نقاب قوی بودنتو برداری، اون وقت میبینی چقدر جون میکنم تا بهت امید بدم و عشقمو ابراز کنم با حرفام.

Signed MaYsa

8 Aug 2026, 20:34 UTC21 viewsread 8 August 2026

ولی واقعا حالم یه جوری باهات خوبه که دلم میخاد تا ابد بمونه همینجوری.

Signed MaYsa

8 Aug 2026, 20:32 UTC22 viewsread 8 August 2026

‏شاید بتونی تو طول روز وانمود کنی حالت خوبه و همچی طبیعیه، ولی شب که شد، دهنت سرویسه.

Signed MaYsa

8 Aug 2026, 19:40 UTC13 viewsread 8 August 2026

تا فردا صبح میمونه، سین بزنید.

Signed MaYsa

8 Aug 2026, 19:39 UTC13 viewsread 8 August 2026

سیندرلا یه کفشش در اومد شوهر کرد ولی تو همه چیتو در آوردی هنوز معلوم نیست ماله کی ای😉

Signed MaYsa

8 Aug 2026, 19:38 UTC8 viewsread 8 August 2026
Forwarded from @cocobunut

جـایے میـان دیـروز و امروز ㅤㅤㅤㅤㅤ────୨ৎ──── هیـچ‌کس نفهمیـد از چه زمانـے دنـیا براے او بےصـدا شد. همه‌چیـز سر جـایش بود؛ آدم‌هـا همـان حرف‌هـا را مےزدنـد، خیـابـان‌ها همـان مسیـرها را داشـتند و روزها مثـل همیـشه از پے هم مـےآمدنـد. فقط او دیـگر نمےتوانسـت مثـل قبل با هیـچ‌کدامشـان ارتباط بگیـرد. انگار جـایے بیـن دیـروز و امـروز، چیـزے را گم کرده بـود کـه حتـے اسـمش را هم نمےدانسـت. گاهـے دلـش مےخواسـت کسے از او بپرسد …

Signed MaYsa

8 Aug 2026, 19:38 UTC12 viewsread 8 August 2026
Forwarded from @Love_MazeePhoto

Photo, posted without a caption

Signed MaYsa

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

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

Named by 4 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.

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.

فونت اینشاتfont inshot
@insot_5 · 27,478
Telegram ranks this channel #32 of 50 here — alongside 49 others — read 11 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 15 September 2026 — this entry's latest reading, not the date you are reading this.

“𝗟𝗶𝗺𝗲𝗿𝗲𝗻𝗰𝗲” (@Limerence_M), 1,053 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/Limerence_M.

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.