Telegram RegisterThe public register of Telegram
Telegram profile photo for eechrt

Channel

eechrt

@eechrt

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

196subscribers

-2 since we began measuring on 28 August 2026

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

Register entry

Telegram ID-1002189745002
TypeChannel
Username@eechrt
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded28 August 2026
Last confirmed live6 September 2026
Measurements held3
Confirmed unchanged1 time, most recently 6 September 2026
On Telegramt.me/eechrt

Growth

19619819728 August 2026 — 198 subscribers29 August 2026 — 198 subscribers6 September 2026 — 196 subscribers28 August 20266 September 2026
3 measurements spanning 8 days, net -2. 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 196–198 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Sept 2026, 03:17196-2
29 Aug 2026, 04:34198no change
28 Aug 2026, 15:46198first reading

Engagement

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

ERR · 30 days
49.4%
avg views ÷ 196 subscribers
Avg views / post
96.9
9 posts measured
Reaction rate
27.4%
reactions ÷ views · ER floor
Posts in window
9
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. It is computed over the 8 of 9 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 26 August 2026
Posts held18 (29 July 202626 August 2026)
Views total872
Reactions total222
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 15: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

485 reactions across 17 posts, in 48 distinct kinds. The most used accounts for 10.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52089352542570760115310.9%
custom 5411351178812367568377.63%
custom 5415629644843993800357.22%
custom 5413815540852496418347.01%
custom 5411381136209255343255.15%
custom 5206584094669943528244.95%
custom 5303420884046857595204.12%
custom 5316536576002522765204.12%
custom 5442995518596750510204.12%
custom 5440537792281089172193.92%
custom 5422763761616330424163.30%
custom 5215176035011690523132.68%
custom 5420454623989212722122.47%
custom 5350298003951359264112.27%
custom 5440640313150450712112.27%
custom 5447245710858664130102.06%
custom 518858894190891718991.86%
custom 544037844899441451891.86%
custom 519074998476866956571.44%
custom 535056387101691743471.44%
28 further kinds9319.2%

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 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 485 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 29 July 2026 to 26 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
82
across the posts below
Posts paid on
5
of 18 we hold a reading for · 28%
Most on one post
66
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @eechrt. 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 29 July 2026 to 26 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

26 Aug 2026, 15:13 UTC45 views25 reactionsread 28 August 2026
Photo

это я наблюдаю как мастер делает за минуту то, с чем я ебался полчаса:

custom 51885889419089171899custom 51909595791727429166custom 54112511318441749094custom 52289092573651616963custom 54610360992268744262custom 54113167460595551431

24 Aug 2026, 14:07 UTC58 views12 reactionsread 28 August 2026
File

File, posted without a caption

custom 54405377922810891726custom 52335809405376630863custom 53933740133743760652custom 54138155408524964181

24 Aug 2026, 14:07 UTC55 views16 reactionsread 28 August 2026
Photo

хотел слить эти пикчи только в щп, но залью и в основу🤩 я в кайфах с того, как ахуенно рей вписывается в атмосферу темных дождливых гавайских тропиков 🤩🥥 и я не мог не вкинуть в такой замес пару отсыл очек к трекам godsmack, которые у меня давно и плотно ассоциируются с реем и его вуду-худу-трайбл вайбом💭

custom 541381554085249641811custom 54405377922810891722custom 52088179458153075481custom 52335809405376630861custom 53933740133743760651

22 Aug 2026, 14:50 UTC100 views62 reactions66 Starsread 28 August 2026
Photo

закрытие сезона 🤩🍃 лето прошло с кайфом~

custom 541562964484399380035custom 544053779228108917211custom 54138155408524964188custom 52088179458153075484custom 54204546239892127223custom 52042734709842008901

19 Aug 2026, 12:03 UTC130 views6 reactionsread 28 August 2026
Sticker

Sticker, posted without a caption

custom 54204546239892127226

19 Aug 2026, 11:40 UTC140 views52 reactions8 Starsread 28 August 2026
Photo

артео с додгой до внезапной коллабы🌴 я вторчал с его блек адиков и носков рисовал кроссовки, а получил тотал тропик вайб ❤️🤩

custom 530342088404685759520custom 541381554085249641814custom 544064031315045071211custom 54204546239892127223custom 54720205296259826073custom 52017251552183266991

12 Aug 2026, 15:32 UTC150 views40 reactions6 Starsread 28 August 2026
Photo

захотелось потренить эмоции да и вщ вспомнить, как он выглядит рисовать рея всегда прикол, пушо у него очень активная мимика, но я почему-то этим почти не пользуюсь 🥸

custom 541138113620925534323custom 53505638710169174347custom 52089352542570760116custom 53957569170647711732custom 52335809405376630861custom 53776346075019614681

12 Aug 2026, 14:27 UTC133 views9 reactionsread 28 August 2026

человек, который кинул донат на хипо, спасибо тебе огромное🤩🤩 от души подгон, пушо на работу-то я вышел, а до зп еще как до луны и обратно

custom 54112781557783987555custom 52089352542570760112custom 54113811362092553432

8 Aug 2026, 12:09 UTC177 views38 reactionsread 28 August 2026
Photo

совершаю каминг аут как селикасексуал 🤩 🤩

custom 544299551859675051020custom 54403784489944145189custom 54407701671916767236custom 54429254290254482112custom 54426115828802279501

8 Aug 2026, 06:27 UTC181 views12 reactionsread 28 August 2026

походу этим двоим уже пох - пивас, энергос или бензин по 69 😁

custom 52089352542570760116custom 54227637616163304244custom 54110966547554435331custom 54408052871392522561

8 Aug 2026, 06:27 UTC150 views26 reactionsread 28 August 2026
Forwarded from @gtrazePhoto

крепких братских сжатий много не бывает [🤩]

custom 542276376161633042412custom 52089352542570760115custom 54110966547554435333custom 54408052871392522563custom 54002661602791654702custom 54113980197257007511

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

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 2 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.

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

“eechrt” (@eechrt), 196 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/eechrt.

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.