как переименовать канал.
custom 60420778335833984221

Channel
@liamaour
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
38subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002731592983 |
|---|---|
| Type | Channel |
| Username | @liamaour |
| Description | this will be a true romantic story like none that has come before...👻 |
| Created | Between 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/liamaour |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 20:32 | 38 | no change |
| 6 Aug 2026, 16:04 | 38 | first reading |
17 posts held, back to 29 April 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 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 10 August 2026 |
|---|---|
| Posts held | 17 (29 April 2026 – 10 August 2026) |
| Views total | 201 |
| Reactions total | 49 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Aug 2026, 20:32 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.
Lifetime counters from Telegram’s own channel header, read 10 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
174 reactions across 17 posts, in 11 distinct kinds. The most used accounts for 30.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 6042077833583398422 | 53 | 30.5% | |
| custom 5217777041436343635 | 30 | 17.2% | |
| 💘 | 27 | 15.5% | |
| custom 5220137091605739183 | 17 | 9.77% | |
| custom 5307818930557975574 | 13 | 7.47% | |
| custom 5285354301684730285 | 11 | 6.32% | |
| custom 5206185775107966338 | 7 | 4.02% | |
| custom 5429527012257595895 | 6 | 3.45% | |
| custom 5408969975929008147 | 5 | 2.87% | |
| custom 5389018551463989407 | 3 | 1.72% | |
| custom 5309804133161651520 | 2 | 1.15% |
Custom emoji. 10 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 17 of the 17 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 174reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 29 April 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.
как переименовать канал.
custom 60420778335833984221
деменция и наклейка с химеру (возможно не связаны)
custom 52201370916057391833💘2custom 60420778335833984222
вольное ночное творчество
custom 52201370916057391835custom 60420778335833984225custom 52177770414363436353
ненамеренный фаворитизм и закрытый гештальт
custom 60420778335833984228💘5custom 52177770414363436355custom 54295270122575958951
на днях проведывала подруню в больнице и прям в электричке по дороге писала ей стих
custom 53078189305579755747💘1custom 60420778335833984221
эггхед фэтфак это мой самопровозглашенный аватар хаоса который время от времени меняет прически а также имеет свойство внезапно беременеть
custom 60420778335833984224custom 52177770414363436353custom 54295270122575958953
для этого чудища выведен отдельный хештег #eggheadfatfuck
custom 60420778335833984226custom 52177770414363436353custom 53078189305579755743
интересный факт абсолютно все мои вкиды о "любви" или с её упоминанием так или иначе посвящены селфцесту
custom 52177770414363436354💘3custom 60420778335833984223
все где есть слово «посмотри» рано или поздно будет объединено в цельную композицию (надеюсь)
custom 52177770414363436354custom 52201370916057391833custom 60420778335833984223
крик души ☝️
💘6custom 54089699759290081475custom 60420778335833984224
НИКТО НИЧЕГО НЕ ВИДЕЛ
custom 52853543016847302852custom 60420778335833984222
сделаем вид что месяц гордости только начался
custom 60420778335833984227💘3custom 52177770414363436351custom 52201370916057391831
Showing the 12 most recent of 17 posts we hold for @liamaour. 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 — 647,501 of 1,189,255entries 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.
Named by 18 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.
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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“Liamaour C14H20Br2N2 чимин/юнги” (@liamaour), 38 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/liamaour.
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.