Сё равно вылетели против ветрола, пхпх
custom 53706045792620455871

Channel
@erentypage
On this record: Previous handles · Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Handles named that no longer answer · Cite this entry
115subscribers
-21 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004431400787 |
|---|---|
| Type | Channel |
| Username | @erentypage |
| Created | Between 1 June 2026 and 19 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 5 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 5 September 2026 |
| On Telegram | t.me/erentypage |
@erentypage was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Sept 2026, 07:42 | 115 | -6 |
| 27 Aug 2026, 16:55 | 121 | -4 |
| 19 Aug 2026, 23:32 | 125 | -10 |
| 12 Aug 2026, 19:18 | 135 | -1 |
| 11 Aug 2026, 20:17 | 136 | first reading |
18 posts held, back to 19 July 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 18 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 3 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.
30 reactions across 14 posts, in 5 distinct kinds. The most used accounts for 30.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5370604579262045587 | 9 | 30.0% | |
| custom 5371092341517983825 | 8 | 26.7% | |
| custom 5251374148231384890 | 5 | 16.7% | |
| custom 5330176825198925478 | 5 | 16.7% | |
| custom 5328034508396583057 | 3 | 10.0% |
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 14 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 30 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 19 July 2026 to 9 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 53706045792620455871
Продвинули нас в итоги
custom 53710923415179838251
Играем кбх 67. Чота -вайби типы СС МС не прикрепляют. Там страни чувак максимально всё читал, в попу мя имел
custom 53710923415179838251
Пару хайповых моментов пока играл мм с кентиками
custom 53710923415179838252
Сигмучи Егоров 👅
custom 53710923415179838251
Купил настройку сенсы у ворзекса. Бля, просто божественно чувствуется, настолько отзывчивая, что пришлось обратно в 166 переходить. Если кому-то интересна настройка сенсы на рог 6/7/8 или же айфон, то смело берите тут https://t.me/worzzzess_settings Ручаюсь :3
custom 53710923415179838253
Если на днях возьму сё квалы кф и начну пилить демки, будет ли интересно вам смотреть?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
custom 53706045792620455873
Проснулся утром от звонка тиммейта и слов "ТЫ ГДЕ?" А я короче даже не дома, посапывал сладко, ну и побежал домой чтобы сыграть. Пока бежал дали ТП, всё равно сыграли и я дичацше всосал. Спасибо хорошо
custom 53301768251989254782
Voice message, posted without a caption
custom 53280345083965830572custom 52513741482313848901
Могу демки как 2500 апаю выкладывать, но эт долго для просмотра и, возможно, кому-то неинтересно будет. Могу фишки всякие
custom 53301768251989254783
Сижу на работи, скука смертная. Если кому-то интересно видеть какой-либо контент, то скиньте в комменты что вам интересно пж. А то я хз чо снимать
custom 53706045792620455873
Дилдо скин
custom 53706045792620455872
Showing the 12 most recent of 18 posts we hold for @erentypage. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Если на днях возьму сё квалы кф и начну пилить демки, будет ли интересно вам смотреть?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 18 most recent posts we hold, published 19 July 2026 to 9 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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.
@erentypage named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 5 September 2026 — this entry's latest reading, not the date you are reading this.
“erenty page” (@erentypage), 115 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/erentypage.
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.