даже эдиты этой хуйне делать нет мотивации.

Channel
Wertyss (ВЕРТИСС) || rest
@wertyss1
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
604subscribers
-27 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002491482375 |
|---|---|
| Type | Channel |
| Username | @wertyss1 |
| Created | Between 1 October 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 10 September 2026 |
| On Telegram | t.me/wertyss1 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Sept 2026, 05:21 | 604 | -3 |
| 31 Aug 2026, 14:17 | 607 | -7 |
| 24 Aug 2026, 17:02 | 614 | -6 |
| 16 Aug 2026, 07:15 | 620 | -12 |
| 9 Aug 2026, 05:53 | 632 | +1 |
| 8 Aug 2026, 06:02 | 631 | first reading |
Engagement
11 posts held, back to 29 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 11 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 1m 31s
- Average length
- 30s
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.
Reaction mix
183 reactions across 7 posts, in 6 distinct kinds. The most used accounts for 33.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5373107995439800397 | 61 | 33.3% | |
| custom 5409378388664146010 | 46 | 25.1% | |
| custom 5334835988541751073 | 42 | 23.0% | |
| custom 5308024741095827952 | 19 | 10.4% | |
| custom 5341624476410846951 | 14 | 7.65% | |
| custom 5447305569817862776 | 1 | 0.546% |
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 7 of the 11 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 183 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 29 July 2026 to 5 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.
Recent posts
я не беру свои слова назад
Вот, ловите сиванчика пока вертисс спит
custom 537310799543980039720custom 533483598854175107314custom 540937838866414601011custom 53080247410958279521custom 53416244764108469511
Signed 𝐚𝐞𝐩.𝐚𝐦𝐨𝐫𝐚
Я просто в ахуе
Signed 𝐚𝐞𝐩.𝐚𝐦𝐨𝐫𝐚
FINE SHIT
custom 530802474109582795214custom 53348359885417510737
ДЖИНМАН НА БАЙКЕ!!!! А ВЫ АВЫЛАОЫЛ АДЛЖЫВ
custom 534162447641084695110custom 53731079954398003979
сука и все спят
я одна это вижу?🌟 мунджо вернись я набью татуировку на лбу
custom 540937838866414601016
ЧТО ЧТО ЧТО ЭТО впервые словила что то такое раньше аморы лол
custom 54093783886641460109
Я тоже хочу
custom 537310799543980039718custom 54093783886641460105custom 53416244764108469513custom 53080247410958279521custom 53348359885417510731
✨😊😊😊 😊😊😊😊✨ SPOILERS почему в интро склейка выглядит так кабута джинман джи а уебал😢 SDT: лп амора scp: @seklirespc #edit #ashopforkillers #vo1dgrp
custom 533483598854175107320custom 537310799543980039714custom 54093783886641460105custom 53080247410958279523custom 54473055698178627761
Showing the 11 most recent of 11 posts we hold for @wertyss1. 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.
Mentions
Named by 7 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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@wertyss1 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 9 August 2026 – 9 August 2026
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 10 September 2026 — this entry's latest reading, not the date you are reading this.
“Wertyss (ВЕРТИСС) || rest” (@wertyss1), 604 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/wertyss1.
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.