Ладно, я могу вам показать как выглядит Жоржичек пока я готовлю
custom 541582542663320284016custom 52265465056613062619

Channel
@vasilzza
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
295subscribers
+23 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001694784332 |
|---|---|
| Type | Channel |
| Username | @vasilzza |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 11 September 2026 |
| On Telegram | t.me/vasilzza |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 10:41 | 295 | +10 |
| 3 Sept 2026, 10:56 | 285 | +8 |
| 20 Aug 2026, 09:57 | 277 | +2 |
| 14 Aug 2026, 01:29 | 275 | +2 |
| 7 Aug 2026, 19:24 | 273 | +1 |
| 7 Aug 2026, 07:17 | 272 | first reading |
20 posts held, back to 2 August 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 20 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
240 reactions across 19 posts, in 9 distinct kinds. The most used accounts for 24.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5812054988825824796 | 59 | 24.6% | |
| custom 5415825426633202840 | 46 | 19.2% | |
| 🔥 | 34 | 14.2% | |
| 😭 | 28 | 11.7% | |
| 🤣 | 25 | 10.4% | |
| custom 5226546505661306261 | 16 | 6.67% | |
| 🤯 | 15 | 6.25% | |
| 🙏 | 11 | 4.58% | |
| custom 5220106983885002341 | 6 | 2.50% |
Custom emoji. 4 of the rows above are 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 19 of the 20 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 240 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 2 August 2026 to 6 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 541582542663320284016custom 52265465056613062619
Самое вот для моей нетерпеливой души душное в стендапе это долгая награда. Вот я две недели работала над блоком про мать, он писался как сам собой, зрителям заходит, много нетривиальных заходов, чернухи, мне прям нравится. Сегодня ещё уплотнила прям жесть и в Батуми его расскажу кусочком и потом третий блок сяду писать, который предыдущие два так красиво замиксует, что прям вау. И прикиньте, я всё это покажу на съё…
🤯5custom 52265465056613062615
Купила билеты в Батуми, назад пути нет, придётся выступать
🔥17custom 52201069838850023412🙏1
Ну что, работает?
custom 58120549888258247968custom 54158254266332028403
Уже три лари
🤣12
Бог любит троицу
🙏7
Когда я делала эту шутку, я не думала что она так долго будет актуальна
😭9custom 54158254266332028404
Здравствуйте, теперь это не канал Василисы Никольской, это счётчик блэкаутов в Тбилиси. На данный момент происходит третье выключение света по всей стране за неделю.
😭16custom 58120549888258247964🤯2custom 54158254266332028401
Все кто говорил что аниме для немытых затворников, выкусите, я только что посмотрела серию, где персонаж стал сильнее потому что начал мыться и вести себя вежливо
custom 581205498882582479616custom 52201069838850023411custom 52265465056613062611
Всё, вечер анонсов закончился, выбирайте по своей географии и силам
custom 58120549888258247962
А в субботу если вы в Гюмри, я не обижусь, если придёте на коллегу Кристину (обижусь если не придёте)
custom 58120549888258247963
Привет, одна тысяча шестьсот семь человек! Безвизовых городов становится все меньше. Надежд на солдаут нет, но когда меня это останавливало😐 Если вы в Гюмри (ну вдруг), то билеты можно взять в DM Бара ТУТ
custom 58120549888258247964
Showing the 12 most recent of 20 posts we hold for @vasilzza. 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.
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.
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.
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 11 September 2026 — this entry's latest reading, not the date you are reading this.
“Что там у Василисы” (@vasilzza), 295 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/vasilzza.
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.