Telegram RegisterThe public register of Telegram
Telegram profile photo for 🌘𝕃 𝕀 𝕄 𝕀 ℕ 𝔸 𝕃🌒

Channel

🌘𝕃 𝕀 𝕄 𝕀 ℕ 𝔸 𝕃🌒

@liminal_roof

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

384subscribers

+38 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1003986422864
TypeChannel
Username@liminal_roof
CreatedBetween 1 April 2026 and 2 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live11 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 11 September 2026
On Telegramt.me/liminal_roof

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

Previous handles

@liminal_roof was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@SecretDEleanor
held 8 August 20268 August 2026

Growth

3463843658 August 2026 — 346 subscribers8 August 2026 — 346 subscribers2 September 2026 — 373 subscribers3 September 2026 — 381 subscribers11 September 2026 — 384 subscribers8 August 202611 September 2026
5 measurements spanning 35 days, net +38. 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 340–390 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Sept 2026, 16:36384+3
3 Sept 2026, 00:36381+8
2 Sept 2026, 06:00373+27
8 Aug 2026, 06:50346no change
8 Aug 2026, 02:51346first reading

Engagement

18 posts held, back to 2 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
62.6%
avg views ÷ 384 subscribers
Avg views / post
240
11 posts measured
Reaction rate
24.0%
reactions ÷ views · ER floor
Posts in window
12
of 18 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 31 August 2026
Posts held18 (2 August 202631 August 2026)
Views total2,644
Reactions total634
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken2 Sept 2026, 06:00 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.

Reaction mix

885 reactions across 17 posts, in 13 distinct kinds. The most used accounts for 28.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 537092449419605635725028.2%
custom 537331140509093899619421.9%
custom 530077474181090034111312.8%
custom 53931472691659067059911.2%
custom 5339120355858467591829.27%
custom 5458704473151000895576.44%
custom 5344039579471074665273.05%
custom 5271799655481498953252.82%
custom 5370774720096509791242.71%
custom 537067687215157202160.678%
custom 537108846745748310950.565%
custom 519967549374546353920.226%
🍌10.113%

Custom emoji. 12 of the rows above are 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 17 of the 18 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 885 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 2 August 2026 to 31 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.

Telegram Stars

Stars received
112
across the posts below
Posts paid on
10
of 17 we hold a reading for · 59%
Most on one post
20
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @liminal_roof. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 18 most recent posts we hold for this entry, published 2 August 2026 to 31 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

31 Aug 2026, 21:20 UTC186 views51 reactions6 Starsread 2 September 2026

Posted without readable text

custom 537092449419605635725custom 537331140509093899615custom 53007747418109003419custom 53707747200965097912

29 Aug 2026, 14:01 UTC357 views64 reactions17 Starsread 2 September 2026

Posted without readable text

custom 537331140509093899627custom 537092449419605635719custom 530077474181090034116custom 53707747200965097912

28 Aug 2026, 13:31 UTC183 views63 reactions8 Starsread 2 September 2026

Posted without readable text

custom 537092449419605635730custom 537331140509093899617custom 539314726916590670513custom 53007747418109003413

27 Aug 2026, 20:09 UTC181 views61 reactions15 Starsread 2 September 2026

Posted without readable text

custom 537092449419605635727custom 530077474181090034114custom 539314726916590670512custom 53733114050909389968

27 Aug 2026, 15:14 UTC175 views48 reactions20 Starsread 2 September 2026

Posted without readable text

custom 537331140509093899622custom 537077472009650979113custom 537092449419605635713

27 Aug 2026, 13:30 UTC161 views62 reactions17 Starsread 2 September 2026

Posted without readable text

custom 537092449419605635725custom 530077474181090034119custom 537331140509093899613custom 53931472691659067055

26 Aug 2026, 09:01 UTC187 views65 reactions6 Starsread 2 September 2026

Posted without readable text

custom 537092449419605635733custom 537331140509093899615custom 539314726916590670512custom 53007747418109003414custom 53707747200965097911

25 Aug 2026, 12:53 UTC338 views65 reactions11 Starsread 2 September 2026

Posted without readable text

custom 537092449419605635731custom 537331140509093899613custom 539314726916590670510custom 53706768721515720216custom 53707747200965097914custom 53007747418109003411

25 Aug 2026, 07:47 UTC334 views72 reactions6 Starsread 2 September 2026
Photo

🤩🤩 🤩🤩 🤩❤️❤️❤️❤️❤️❤️❤️❤️ Мне не нужно находить время. Я просто существую, а они вращаются вокруг меня. Как планеты. #МиссияФортуна #SevenHeartsStories #SHS #СХС #Себастьян

custom 530077474181090034128custom 537331140509093899621custom 539314726916590670518custom 53709244941960563574custom 53707747200965097911

23 Aug 2026, 20:08 UTC282 views54 reactions6 Starsread 2 September 2026
Photo

😀😀😀 🤩🤩🤩 🖤🖤🖤 🤩🤩🤩 🇯🇵🇯🇵🇯🇵🇯🇵⭐⭐ 🤩🤩🤩 🤩🤩🤩🤩 #СказкиПодземелий #ЛигаМечтателей #ЛМ #Шень

custom 537331140509093899625custom 537092449419605635714custom 530077474181090034111custom 53931472691659067054

23 Aug 2026, 15:02 UTC260 views29 reactionsread 2 September 2026

🎉 Результаты розыгрыша: 🏆 Победитель: 1. Людмила (@Lusik007) ✔️Проверить результаты

custom 537092449419605635717custom 53007747418109003416custom 53710884674574831095custom 53707747200965097911

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 1 registered channel — 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.

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.

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

“🌘𝕃 𝕀 𝕄 𝕀 ℕ 𝔸 𝕃🌒” (@liminal_roof), 384 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/liminal_roof.

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.