Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝐿𝑖𝑚𝑒𝑟𝑒𝑛𝑐𝑒 𝑓𝑙𝑜𝑜𝑑 𝑖𝑛𝑓𝑜

Channel

𝐿𝑖𝑚𝑒𝑟𝑒𝑛𝑐𝑒 𝑓𝑙𝑜𝑜𝑑 𝑖𝑛𝑓𝑜

@limerencInfo

On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

641subscribers

+332 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1003983071970
TypeChannel
Username@limerencInfo
CreatedBetween 1 April 2026 and 29 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live30 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/limerencInfo

Growth

3096414756 August 2026 — 309 subscribers6 August 2026 — 309 subscribers7 August 2026 — 312 subscribers15 August 2026 — 375 subscribers22 August 2026 — 505 subscribers30 August 2026 — 641 subscribers6 August 202630 August 2026
6 measurements spanning 23 days, net +332. 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 259–691 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 06:54641+136
22 Aug 2026, 07:47505+130
15 Aug 2026, 10:16375+63
7 Aug 2026, 06:55312+3
6 Aug 2026, 22:18309no change
6 Aug 2026, 19:46309first reading

Engagement

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

Reaction mix

120 reactions across 10 posts, in 8 distinct kinds. The most used accounts for 25.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 51927870448074943663025.0%
custom 53391080765469795352117.5%
custom 53394703012038203681714.2%
custom 54135776297290724491310.8%
custom 5192916039855264626119.17%
custom 5314584728114845566119.17%
custom 532554082890969191897.50%
custom 542014155523307134186.67%

Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

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 10 of the 19 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 120 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 29 July 2026 to 6 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

4 Aug 2026, 10:31 UTC168 views9 reactionsread 6 August 2026
Photo

ⵈ۫‌‌꒰𝇂‌ 🔤🔤🔤ׄ◯⃘🎀🎀˖݊ꥈ ⸼𓄸𞥊꯭ Люблю безумно

custom 53391080765469795353custom 51927870448074943662custom 53145847281148455662custom 53394703012038203681custom 54201415552330713411

3 Aug 2026, 18:41 UTC173 views5 reactionsread 6 August 2026

Проверка союзов Это не чистка. Мне нужно убедиться в активности всех союзов От следящих требуется : 1. Инфо 2. Допы 3. След Срок до 06.08

custom 53394703012038203684custom 53391080765469795351

3 Aug 2026, 14:09 UTC179 views3 reactionsread 6 August 2026

набор закрыт‼️

custom 51929160398552646263

31 Jul 2026, 19:51 UTC314 views27 reactionsread 6 August 2026

Я @Aivedddd приношу свои извинения перед флудом @limerencInfo и его владельцем @Limerena за то что взяла их название, а после моя подруга заставляла флуд @limerencInfo сменить название. Если вы увидите, что я опять взяла у кого-то название, разрешаю вам ебать меня и всю мою родословную.

custom 519278704480749436611custom 53394703012038203686custom 53391080765469795354custom 51929160398552646262custom 53145847281148455662custom 54135776297290724491custom 54201415552330713411

31 Jul 2026, 19:29 UTC267 views3 reactionsread 6 August 2026
Forwarded from @QuotLyBotSticker

Sticker, posted without a caption

custom 53391080765469795352custom 54135776297290724491

29 Jul 2026, 19:58 UTC661 views17 reactionsread 6 August 2026
Photo

[🔤] 𝘞𝘦𝘭𝘤𝘰𝘮𝘦 𝘵𝘰 𝘭𝘪𝘮𝘦𝘳𝘦𝘯𝘤𝘦. + . * — @limerencInfo L𝘪𝘮𝘦𝘳𝘦𝘯𝘴𝘦 𝘧𝘭𝘰𝘰𝘥 — пространство , где случайные встречи становятся судьбоносными. 🪧🪧🪧🤩 🪧🪧🪧🤩 🪧🔤🔤🔤🔤 вы ищете место, где каждого искренне ценят и слышат — вы по адресу. ⧼⧼🤩𓍢ִ໋ ‌⃜៹𔔁 #rp :🍓:. #limr ʾ۫ׄ◡︎‌۫— 🪧 @loretol ⵈ۫‌‌꒰𝇂‌ ׄ◯⃘ Минимальный порог сообщений, мы за комфорт, а не количество! (120 сообщений) ⵈ۫‌‌꒰𝇂‌ ׄ◯⃘ Смех и тепло в каждом сообщении ⵈ۫‌‌꒰𝇂‌ ׄ◯⃘ Много интеракт

custom 51927870448074943665custom 54135776297290724494custom 53145847281148455662custom 53391080765469795352custom 53394703012038203682custom 51929160398552646261custom 53255408289096919181

29 Jul 2026, 19:57 UTC380 views13 reactionsread 6 August 2026

ⵈ۫‌‌꒰𝇂‌ ׄ◯⃘🎀🎀˖݊ꥈ ⸼࣪ ִ𓄸𞥊꯭ 🤩ɦᴇ sᴇᴛ 🤩s close 🌟➿𔘘꯭‌ ‌⃜.ִ۟ ࣪᠘iִⲙēɼεꪀℭꫀ⸼࣪𓈒 ⟩› ࣪ ждем вас в нашем флуде! Брони актуальны ⎯ʾ۫ׄ ꒰ 75/75 ꒱‌⃜.ִ۟ Участники࣪ ⎯ʾ۫ׄ ꒰ 3 ꒱ ‌⃜.ִ۟ ࣪Брони ⧼⧼🤩𓍢ִ໋ ‌⃜៹𔔁 #rp :🍓:. #limr ʾ۫ׄ◡︎‌۫— ➿ @loretol ;; @Liimerick

custom 53255408289096919184custom 51927870448074943662custom 53391080765469795352custom 53394703012038203682custom 54135776297290724492custom 53145847281148455661

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

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

“𝐿𝑖𝑚𝑒𝑟𝑒𝑛𝑐𝑒 𝑓𝑙𝑜𝑜𝑑 𝑖𝑛𝑓𝑜” (@limerencInfo), 641 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/limerencInfo.

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.