Telegram RegisterThe public register of Telegram

Channel

°□ᛕᚤᚹᛠᛜᛋᚺᛜᛊ ᚹᚤ℥ᚦᛜᚳⰓᛊ■•

@acelibrar

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

24subscribers

+0 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1004432401825
TypeChannel
Username@acelibrar
Created22 June 2026measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live12 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/acelibrar

Growth

2411 Aug 2026, 19:46 — 24 subscribers12 Aug 2026, 11:33 — 24 subscribers11 Aug 2026, 19:4612 Aug 2026, 11:33
2 measurements taken within a single day. 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 23–25 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 11:3324no change
11 Aug 2026, 19:4624first reading

Engagement

12 posts held, back to 22 June 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
213.3%
avg views ÷ 24 subscribers
Avg views / post
51.2
5 posts measured
Reaction rate
2.94%
reactions ÷ views · ER floor
Posts in window
5
of 12 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. It is computed over the 2 of 5 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 10 August 2026
Posts held12 (22 June 202610 August 2026)
Views total256
Reactions total3
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Aug 2026, 19:46 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

18 reactions across 5 posts, in 5 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
950.0%
633.3%
custom 523097143007774969815.56%
custom 523338298120001227015.56%
custom 544530200622900482115.56%

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

Measured over the 12 most recent posts we hold, published 22 June 2026 to 10 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

10 Aug 2026, 20:01 UTC33 views2 reactionsread 11 August 2026
Photo

. . . . Горячо.. нет.. холодно.. холодно.. Я..я..я. не чувствую ног.. только боль, которая растекается по всему телу.. от ног ли это? Мне ведь вдарили бошкой об край кровати?.. Все тело болит.. болит.. болит.. 📁📁📁📁📁📁 . . . . Я попытался сбежать, но какой итог? На сколько же это бесполезно.. Если он уже что то задумал, но видимо изначально были нулевые шансы... Мне мешали.. А кто мешал?.. Я.. не помню.. про кого я воо

custom 52309714300777496981custom 54453020062290048211

24 Jul 2026, 03:38 UTC53 viewsread 11 August 2026

— ⲏ𐔤 ⲧ𐔖𐔏ⲇᥲ ᥈ᥱⲿυ ᥴⲙυρⲏ𐔖 υ ⲏᥱ ⲙᥱɯᥲύ

24 Jul 2026, 03:33 UTC53 viewsread 11 August 2026

— ⲕρ𐔤ⲿᥱⲕ 𐔤 ⲏᥱᥱ υ ⲃᥒρяⲙь ⲙⲏ𐔖𐔏𐔖... ᥲ ⲧᥱᥒᥱρь ᥈ᥱⲿυ ᥴᥒυ

23 Jul 2026, 22:40 UTC69 views1 reactionsread 11 August 2026
Photo

📁 ᥲ я ᥒρᥱⲇ𐔤ᥒρᥱⲿⲇᥲ᥈ υ 𐔏𐔖ⲃ𐔖ρυ᥈ ɥⲧ𐔖 𐔖ⲏ ⲏᥱⲏ𐔖ρⲙᥲ᥈ьⲏыύ, ⲏ𐔖 ⲕⲧ𐔖 ⲙᥱⲏя ᥴ᥈𐔤ɯᥲᥱⲧ? υ ⲕ ɥᥱⲙ𐔤 ⲉⲧ𐔖 ᥒρυⲃᥱ᥈𐔖... 📁 📁 📁 ⲏᥱ ⲇ𐔤ⲙᥲю, ɥⲧ𐔖 ⲙᥲⲧⲧᥱ𐔖 ⲉⲧ𐔖 𐔏𐔖ⲃ𐔖ρυ᥈ ⲃ ⳝρᥱⲇ𐔤.. ⳝ𐔖ρυᥴ ⲙⲏ𐔖𐔏𐔖 𐔏𐔖ⲃ𐔖ρυ᥈ ᥒρ𐔖 ⲙᥱⲏя, υ ⲧ𐔖 ɥⲧ𐔖 𐔖ⲏ ⲭ𐔖ɥᥱⲧ ⲙᥱⲏя υᥴᥒρᥲⲃυⲧь. υᥴᥒρᥲⲃυⲧь. υᥴᥒρᥲⲃυⲧь. υᥴᥒρᥲⲃυⲧь. . . . 🤩я ᥴ᥈υɯⲕ𐔖ⲙ ⲙⲏ𐔖𐔏𐔖 ⲇ𐔤ⲙᥲю 🤩𐔖ɥᥱⲏь ⲙⲏ𐔖𐔏𐔖 ᥒρ𐔖υⳅ𐔖ɯ᥈𐔖 ⳅᥲ ᥒ𐔖ᥴ᥈ᥱⲇⲏυύ ⲇᥱⲏь. ⳝρ𐔖ᥴυ᥈ ⲃᥴᥱ ᥴⲃ𐔖υ ⲇᥱ᥈ᥲ, ⲇᥲ ⳝы ⲧ𐔤ᥒ𐔖 ᥈ᥱⲿᥲⲧь ρяⲇ𐔖ⲙ ᥴ ⲧᥱⲙ, ⲕⲧ𐔖 ⲏᥲ ⲇ𐔤ⲭ ⲙᥱⲏя ⲏᥱ ᥒᥱρᥱⲏ𐔖ᥴυⲧ🌟... ⲏ𐔤 υ ᥴ ɥᥲᥴυⲕ𐔖ⲙ. 📁🌟

custom 52333829812000122701

22 Jul 2026, 11:45 UTC48 viewsread 11 August 2026
Photo

🤩🤩🤩 🤩🤩🤩 🤩🤩🤩 —ⲧⲃ𐔖υ ρ𐔤ⲕυ 𐔖ɥᥱⲏь....ⲭ𐔖᥈𐔖ⲇⲏыᥱ✨📁 📁🌟

12 Jul 2026, 15:39 UTC94 viewsread 11 August 2026
Photo

ⲙⲏᥱ ᥴⲧρᥲɯⲏ𐔖, ᥴⲧρᥲɯⲏ𐔖, ᥴⲧρᥲɯⲏ𐔖.. ⲉⲧ𐔖ⲧ ⳝ᥈яⲧᥴⲕυύ ⳝ𐔖ρυᥴ, 𐔖ⲏ ⲙᥱⲏя ᥒρυᥴ᥈ᥱⲇ𐔤ᥱⲧ............. . . . . . . я ⳝ𐔖юᥴь. 💙💙🌟

12 Jul 2026, 05:04 UTC49 viewsread 11 August 2026
Forwarded from @LibrariumSMP_BorisPhoto

📁ㅤ📁📁📁📁 ㅤ 📁📁📁📁 ㅤ 📁📁📁📁📁📁 ㅤ 🤩🤩 ㅤ ㅤМы ведь хорошо общались. А теперь я вижу, как ты пытаешься избегать встреч. ㅤ ㅤ Наверное, люди при таком обижаются. ㅤИли злятся. 😠 ㅤ ㅤ Не знаю. 🧐 ㅤЯ не чувствую этого. ㅤ ㅤ ❤️ ㅤ 🔥 Киви была очень расстроена тобой. ㅤТак, что даже замолчала. ㅤТы прогнал её. Обидел. Мне не доставляет это радости. ㅤ

12 Jul 2026, 00:49 UTC66 views5 reactionsread 11 August 2026

ⲧяⲿᥱ᥈𐔖.. ⲧяⲿᥱ᥈𐔖..ⲧяⲿᥱ᥈𐔖... я ⲏᥱ ⳅⲏᥲю ɥⲧ𐔖 ⲙⲏᥱ ⲇᥱ᥈ᥲⲧь, 2.. ⲏᥱⲧ, 3 ᥴ𐔤ⲧ𐔖ⲕ ᥒρᥲⲕⲧυɥᥱᥴⲕυ ρᥲⳝ𐔖ⲧᥲ᥈, ρᥲⳅыᥴⲕυⲃᥲя ⲇⲃᥱρυ, ᥒ𐔤ⲧυ ⲃ ⳝυⳝ᥈υ𐔖ⲧᥱⲕ𐔤 υ ᥒыⲧᥲяᥴь ᥴ ⲉⲧυⲙ ⲕᥲⲕ ⲧ𐔖 ρᥲⳝ𐔖ⲧᥲⲧь.. υ ɥⲧ𐔖 ᥒ𐔖 υⲧ𐔖𐔏𐔤? ᥒᥱρᥴ𐔖ⲏᥲⲿυ ᥒρ𐔖ⲏυⲕ᥈υ ⲧ𐔤ⲇᥲ, ⲕ𐔤ⲇᥲ υⲙ ᥴ𐔤ⲃᥲⲧьᥴя ⲏᥱ ᥴⲧ𐔖υⲧ 𐔤ⲿ ⲧ𐔖ɥⲏ𐔖. —————————— ⳝы᥈ᥲ ᥈υ ⲉⲧ𐔖 ɥᥲᥴⲧь ᥒρ𐔖ⳝ᥈ᥱⲙ? 𐔖ⲭ ⲏᥱⲧ.. ⲏᥱⲧ ⲏᥱⲧ ⲏᥱⲧ.. ⳝ𐔖ρυᥴ.. ⳝ᥈яⲧь, я ᥱ𐔏𐔖 ᥴ𐔖ⲃᥴᥱⲙ ⲏᥱ ᥒ𐔖ⲏυⲙᥲю! ⲉⲧ𐔖ⲧ ᥴ𐔤ⲙᥲᥴɯᥱⲇɯυύ, ⲕ𐔖ⲧ𐔖ρыύ ⲏᥱᥴᥱⲧ ⲃᥴяⲕ𐔤ю ⲭᥱρⲏю. 𐔖ⲏ ⲭ𐔖ⲧᥱ᥈ ⲏᥲⲃρᥱⲇυⲧь яⳝ᥈𐔖ɥⲕ𐔤.. ᥈υⳝ𐔖

5

9 Jul 2026, 14:32 UTC49 views4 reactionsread 11 August 2026

ⲙᥲⲧⲧᥱ𐔖... ⲕᥲⲕ𐔖й ⲿᥱ ⲧы ⳝᥱᥴяɥυύ. 💙💙🌟

4

6 Jul 2026, 18:32 UTC70 views6 reactionsread 11 August 2026
Photo

〰️〰️〰️💙....ⲙⲏⲟⲅⲟ ⲏⲁⲣⲟⲇⲩ ⲣяⲇⲟⲙ ⲟⲕⲁⳅⲁⲗⲟⲥь.. ɯⲩⲙⲏⲟ, ⲟɥⲉⲏь ɯⲩⲙⲏⲟ. 🌟ⲗⲉⲅɥⲉ ⲭⲟⲇυⲧ ⲃ ⲟⲇυⲏⲟɥⲕⲩ, ⲕⲧⲟ ⲧⲟ ⲗυⳝⲟ ⲁⲅⲣⲉⲥⲥυⲃⲏыύ, ⲗυⳝⲟ ɥⲉⲣⲉⳅ ɥⲩⲣ ⲅⲗⲩⲡыύ 〰️〰️〰️ υ ⲉⲧⲁ ⲙⲟⲗь... ⲙⲉⲏя.... ⲡⲣⲉⲥⲗⲉⲇⲩⲉⲧ?💙〰️〰️〰️ . . . . . ..ɥⲧ𐔖 ⲧ𐔤ⲧ ⳝы᥈𐔖 ⲇ𐔖 ⲏᥲᥴ?.. 💙💙🌟

6

22 Jun 2026, 03:31 UTC102 viewsread 11 August 2026
Photo

〰️〰️ 💙💙💙ᥴ᥈υɯⲕ𐔖ⲙ ᥒы᥈ьⲏ𐔖 ⲧ𐔤ⲧ.. υ ɥᥱ𐔏𐔖 я ⳅⲇᥱᥴь ⲇᥱ᥈ᥲю..💙💙💙 〰️〰️ ⭐️⭐️🌟

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

Citation-graph rank

Citation-graph rank — 754,011 of 1,345,403entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

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

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

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.

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

“°□ᛕᚤᚹᛠᛜᛋᚺᛜᛊ ᚹᚤ℥ᚦᛜᚳⰓᛊ■•” (@acelibrar), 24 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/acelibrar.

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.