❤️.please, be my little baby . . 🤩🤩🤩🤩.🤩.tt 🤩 #mcr@Escherlow
custom 54405595162256614667custom 52628834279290518224custom 52627529210527849153custom 52494993563519745661

Channel
@Escherlow
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
43subscribers
+0 since we began measuring on 14 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002324342750 |
|---|---|
| Type | Channel |
| Username | @Escherlow |
| Description | owner : sian | сиан (она/её) ♰::♰ – @simustdie | @ano_N1mBot |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 September 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/Escherlow |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Sept 2026, 17:22 | 43 | no change |
| 14 Sept 2026, 16:47 | 43 | first reading |
16 posts held, back to 1 June 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.
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 13 September 2026 |
|---|---|
| Posts held | 16 (1 June 2026 – 13 September 2026) |
| Views total | 34 |
| Reactions total | 20 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Sept 2026, 17:22 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 14 September 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.
Measured directly from 5 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
99 reactions across 9 posts, in 13 distinct kinds. The most used accounts for 31.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5262883427929051822 | 31 | 31.3% | |
| custom 5440559516225661466 | 23 | 23.2% | |
| custom 5265237383539874166 | 10 | 10.1% | |
| custom 5190869414924281728 | 8 | 8.08% | |
| custom 5262752921052784915 | 5 | 5.05% | |
| custom 5262901849043783676 | 5 | 5.05% | |
| custom 5314707061668344174 | 5 | 5.05% | |
| custom 5204374883751973667 | 4 | 4.04% | |
| custom 5195315685328177860 | 2 | 2.02% | |
| custom 5325606739477817150 | 2 | 2.02% | |
| custom 5445387192610353023 | 2 | 2.02% | |
| custom 5249499356351974566 | 1 | 1.01% | |
| custom 5433989221285117347 | 1 | 1.01% |
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 9 of the 16 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 99 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 1 June 2026 to 13 September 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.
❤️.please, be my little baby . . 🤩🤩🤩🤩.🤩.tt 🤩 #mcr@Escherlow
custom 54405595162256614667custom 52628834279290518224custom 52627529210527849153custom 52494993563519745661
🤩. присоединяюсь к пиару замечательной кф, в которой тоже админю 🖤
custom 52628834279290518225
🤩.
custom 52628834279290518224
Sticker, posted without a caption
❤️. t.me/+ddQwcmQVvh5kZGFi щп ! я там активнее
❤️.so I will wait for the next time you want me 🤩🤩🤩🤩.🤩.tt 🤩 #mcr@Escherlow
custom 526288342792905182210custom 54405595162256614666custom 52652373835398741663custom 52627529210527849152custom 52629018490437836761custom 54453871926103530231
Sticker, posted without a caption
🤩 brother, if you have the chance to pick me up 🤩 😰. . 🤩 can I sleep on your couch 🤩🤩🤩 🤩🤩🤩🤩.🤩. #mcr@Escherlow & #self@Escherlow
custom 52628834279290518227custom 51908694149242817286custom 54405595162256614664custom 52652373835398741661custom 54453871926103530231
@VoiceShazamBot | info
custom 52629018490437836763
Sticker, posted without a caption
❤️.I wish you loved me less. . 🤩🤩🤩🤩.🤩.tt 🤩 #mcr@Escherlow
custom 52652373835398741666custom 54405595162256614666custom 51908694149242817282custom 52628834279290518221custom 52629018490437836761
🤩. holy peak
Showing the 12 most recent of 16 posts we hold for @Escherlow. 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.
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.
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.
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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“ˊˊ𝗀𝗎𝗂𝗅𝗍 𝗍𝗋𝗂𝗉𝗉𝗂𝗇𝗀. .” (@Escherlow), 43 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/Escherlow.
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.