Telegram RegisterThe public register of Telegram
Telegram profile photo for эск4пе ☻

Channel

эск4пе ☻

@escu1t

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

378subscribers

+9 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001824010704
TypeChannel
Username@escu1t
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live22 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/escu1t

Growth

369378373.57 August 2026 — 369 subscribers8 August 2026 — 369 subscribers15 August 2026 — 374 subscribers22 August 2026 — 378 subscribers7 August 202622 August 2026
4 measurements spanning 14 days, net +9. 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 368–379 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 01:34378+4
15 Aug 2026, 13:58374+5
8 Aug 2026, 06:20369no change
7 Aug 2026, 16:01369first reading

Engagement

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

ERR · 30 days
41.5%
avg views ÷ 378 subscribers
Avg views / post
157
2 posts measured
Reaction rate
16.6%
reactions ÷ views · ER floor
Posts in window
2
of 7 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 29 July 2026
Posts held7 (5 July 202629 July 2026)
Views total314
Reactions total52
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 06:20 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

207 reactions across 7 posts, in 7 distinct kinds. The most used accounts for 23.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52109084610170873874923.7%
custom 54584696458140907514019.3%
custom 53373233415418288313918.8%
custom 52988701342685140543717.9%
custom 5197323608308865038178.21%
custom 5294331041031413879136.28%
custom 5447262706044260846125.80%

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

Measured over the 7 most recent posts we hold, published 5 July 2026 to 29 July 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
1
across the posts below
Posts paid on
1
of 7 we hold a reading for · 14%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @escu1t. 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 7 most recent posts we hold for this entry, published 5 July 2026 to 29 July 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

29 Jul 2026, 08:50 UTC156 views27 reactionsread 8 August 2026
Photo

CASE: 060 детали TYPE: индивидуальный проект TIME: ██ч STATUS: OPEN ближайшие окошки | записаться #tatts@escu1t #personal@escu1t

custom 545846964581409075112custom 52943310410314138798custom 53373233415418288315custom 51973236083088650381custom 52109084610170873871

29 Jul 2026, 08:49 UTC158 views25 reactionsread 8 August 2026
Photo

CASE: 060 меч с лилиями для этого проекта мне дали референс и свободу дальнейшего развития 🌟 дополнили все моими любимыми точечными рисунками! TYPE: индивидуальный проект TIME: ██ч STATUS: OPEN ближайшие окошки | записаться #tatts@escu1t #personal@escu1t

custom 544726270604426084610custom 52988701342685140546custom 54584696458140907515custom 53373233415418288312custom 52109084610170873871custom 52943310410314138791

23 Jul 2026, 03:25 UTC227 views20 reactionsread 8 August 2026
Photo

CASE: 058 коррекция и новые мини-тату подкорректировали не мою надпись (фото. 1) и дополнили ее новой таткой, а на другой руке сделали дату рождения TYPE: индивидуальный проект TIME: ~1ч STATUS: OPEN ближайшие окошки | записаться #tatts@escu1t #personal@escu1t

custom 529887013426851405410custom 52109084610170873875custom 51973236083088650383custom 54584696458140907512

22 Jul 2026, 06:50 UTC213 views34 reactionsread 8 August 2026
Photo

CASE: 059 подарочная татуировка татка по сертификату, подаренному на день рождения. изначально хотели сделать только котика, но на сеансе дополнили его звездочкой TYPE: индивидуальный проект TIME: ~1,5ч STATUS: OPEN ближайшие окошки | записаться #tatts@escu1t #personal@escu1t

custom 533732334154182883114custom 51973236083088650389custom 52109084610170873875custom 54584696458140907514custom 54472627060442608462

21 Jul 2026, 15:36 UTC208 views23 reactionsread 8 August 2026
Photo

CASE: 063 на прошлой неделе начали рукав законтурили фрихенд верха плеча и собор + немного покрасили его. ангел не мой TYPE: индивидуальный проект TIME: 1-й сеанс, ██ч STATUS: OPEN ближайшие окошки | записаться #tatts@escu1t #personal@escu1t

custom 529887013426851405410custom 54584696458140907516custom 52109084610170873875custom 51973236083088650382

12 Jul 2026, 15:58 UTC312 views31 reactionsread 8 August 2026
Photo

CASE: 061–062 парные татуировки вообще этот пост для инст, но очень уж мне нравится, как живо выглядит! TYPE: индивидуальный проект TIME: 2 сеанса × ~5ч (на одну) STATUS: OPEN ближайшие окошки | записаться #tatts@escu1t #personal@escu1t

custom 521090846101708738714custom 53373233415418288318custom 54584696458140907518custom 52943310410314138791

5 Jul 2026, 14:04 UTC332 views47 reactions1 Starread 8 August 2026
Forwarded from @sle3py_nailsPhoto

у @escu1t дршка!! все бегом там поздравлять подписываться и дарить записи на татуировочки 🎉🤪 а я искренне желаю хайповать дальше и так как еще никто не хайповал

custom 521090846101708738718custom 529887013426851405411custom 533732334154182883110custom 52943310410314138793custom 54584696458140907513custom 51973236083088650382

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

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.

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

“эск4пе ☻” (@escu1t), 378 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/escu1t.

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.