Channel
@r1zzparty
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,893subscribers
+34 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002316479774 |
|---|---|
| Type | Channel |
| Username | @r1zzparty |
| Created | Between 1 September 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 | 15 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/r1zzparty |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 16 September 2026 and assigned it the closest of 31 fixed categories, at 56% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 20:38 | 1,893 | -3 |
| 12 Sept 2026, 04:19 | 1,896 | -1 |
| 7 Sept 2026, 17:36 | 1,897 | -12 |
| 2 Sept 2026, 08:16 | 1,909 | -6 |
| 27 Aug 2026, 05:08 | 1,915 | +3 |
| 24 Aug 2026, 15:36 | 1,912 | +26 |
| 20 Aug 2026, 20:27 | 1,886 | +21 |
| 17 Aug 2026, 21:25 | 1,865 | +1 |
| 14 Aug 2026, 19:34 | 1,864 | +4 |
| 11 Aug 2026, 01:51 | 1,860 | +2 |
| 8 Aug 2026, 12:37 | 1,858 | -1 |
| 8 Aug 2026, 03:21 | 1,859 | first reading |
20 posts held, back to 11 June 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
356 reactions across 19 posts, in 5 distinct kinds. The most used accounts for 32.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5251586701867913196 | 114 | 32.0% | |
| 👏 | 73 | 20.5% | |
| 🔥 | 72 | 20.2% | |
| custom 5251463934522724604 | 52 | 14.6% | |
| 🎉 | 45 | 12.6% |
Custom emoji. 2 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 356 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 11 June 2026 to 7 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.
А теперь к хорошим новостям. В августе от меня, «фокуса», будет две тусовки: — RIZZ 16+ — NOIR 18+ Все тусовки пройдут без отмен, за исключением случаев, связанных с военными действиями. Нам пора восстановить то, чего мы вам не смогли дать.
🎉10custom 52515867018679131965custom 52514639345227246044👏1🔥1
🌟🌟🌟 R4VE PARTY 🌟🌟🌟 🐾BLACK AND WHITE🐾 ⭐Ялта, давайте все вместе отвлечемся от данной ситуации в Ялте, и оторвемся по полной на нашей тусовке R4VE PARTY🌟 🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 🗓DATE • 08.08 🎆PLACE • ул.Мира 21Г 🔞FC • 14+ 🎧DJ • GUBIN ⏳TIME • 16:00-22:00 📝PRICE TICKETS • ⭐STANDART • 500 ⭐FAST • 700 ⭐VIP • 1500 (1 чел) 5000 (5 чел)
🔥7🎉5👏5
он чо за делюгу творит изм* Кстати,на свет можете забить,для вас будет работать генератор,так что в эту ночь ничего не будет мешать
custom 52515867018679131964custom 52514639345227246043
Вы просто забыли наверное что Rizz всегда готовит для вас самое грандиозное и неизведанное,не одна тусовка не заходила в этот бойс бар)
custom 52515867018679131968
Что-то вы мало пишете,давайте 25 реакций закидываю место где будем проводить,может так захотите
custom 52514639345227246047
*** Boys Yalta August
🔥5custom 52515867018679131964👏1
Вся информация по этой тусовке будет в https://t.me/noir_yalta
Давно с вами не общались,время течет также быстро как и вода,тусовка 18+ будет,место ахереете реально,у кого кайф есть в промы залететь черканите в лс @tvoy_fokys_pokys
👏7custom 52514639345227246047custom 52515867018679131967
Напомню вам что до сих пор ведется набор в промоутеры. Подробности @Sofa_Shaini или @tvoy_fokys_fokys
custom 52515867018679131962
Обращаем внимание! На территории Республики Крым действует запрет на съемку и публикацию материалов о работе ПВО, дислокации или перемещении воинских формирований, местах падений объектов, координатах происшествий! Будьте умнее,не публикуйте видео и фотоматериалы.
🔥12👏5
Поздравляем с новым организатором в Rizz,@Sofa_Shaini ,отныне она также занимается тусовкой.
custom 52515867018679131966🎉2custom 52514639345227246042
Хочется вернуть прайм Rizz’a когда мы собирали по 400 человек,но без вашей помощи это конечно никак,давайте все кому не лень в сторки закинут постик этот и мы будем думать чтобы вам бомбового замутить
custom 525146393452272460418custom 525158670186791319612🎉8👏4🔥1
Showing the 12 most recent of 20 posts we hold for @r1zzparty. 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 4 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.
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.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“R!ZZ PARTY | AUTUMN” (@r1zzparty), 1,893 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/r1zzparty.
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.