Telegram RegisterThe public register of Telegram
Telegram profile photo for chr1swave

Channel

chr1swave

@chr1swav

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry

34,623subscribers

+2,250 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001292405994
TypeChannel
Username@chr1swav
Descriptionнебольшая спамка twitch.tv/chr1swave Сотрудничество - [email protected] А+. clck.ru/3G2A8d
Created18 February 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live28 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 28 September 2026
On Telegramt.me/chr1swav

Topic

Gaming — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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.

Growth

32,30434,62333,463.56 August 2026 — 32,373 subscribers6 August 2026 — 32,370 subscribers7 August 2026 — 32,368 subscribers8 August 2026 — 32,354 subscribers9 August 2026 — 32,373 subscribers10 August 2026 — 32,359 subscribers11 August 2026 — 32,356 subscribers12 August 2026 — 32,304 subscribers13 August 2026 — 32,360 subscribers14 August 2026 — 32,490 subscribers16 August 2026 — 32,539 subscribers17 August 2026 — 32,565 subscribers18 August 2026 — 32,625 subscribers19 August 2026 — 32,924 subscribers20 August 2026 — 33,141 subscribers21 August 2026 — 33,232 subscribers23 August 2026 — 33,254 subscribers25 August 2026 — 33,246 subscribers26 August 2026 — 33,331 subscribers27 August 2026 — 33,373 subscribers28 August 2026 — 33,382 subscribers29 August 2026 — 33,385 subscribers30 August 2026 — 33,393 subscribers31 August 2026 — 33,366 subscribers1 September 2026 — 33,333 subscribers2 September 2026 — 33,314 subscribers4 September 2026 — 33,292 subscribers7 September 2026 — 33,258 subscribers10 September 2026 — 33,476 subscribers12 September 2026 — 33,557 subscribers14 September 2026 — 33,543 subscribers15 September 2026 — 33,525 subscribers17 September 2026 — 33,501 subscribers28 September 2026 — 34,623 subscribers6 August 202628 September 2026
34 measurements spanning 54 days, net +2,250. 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 31,956–34,971 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
28 Sept 2026, 23:4234,623+1,122
17 Sept 2026, 19:0033,501-24
15 Sept 2026, 15:1933,525-18
14 Sept 2026, 02:0233,543-14
12 Sept 2026, 10:1833,557+81
10 Sept 2026, 07:5933,476+218
7 Sept 2026, 00:2033,258-34
4 Sept 2026, 11:5633,292-22
2 Sept 2026, 21:5633,314-19
1 Sept 2026, 17:2533,333-33
31 Aug 2026, 20:3633,366-27
30 Aug 2026, 18:2533,393+8
29 Aug 2026, 16:0433,385+3
28 Aug 2026, 18:4433,382+9
27 Aug 2026, 21:2733,373+42
26 Aug 2026, 22:3633,331+85
25 Aug 2026, 23:3333,246-8
23 Aug 2026, 09:4833,254+22
21 Aug 2026, 21:0733,232+91
20 Aug 2026, 19:1433,141first reading

Engagement

71 posts held, back to 17 February 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 97 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
56.0%
avg views ÷ 34,623 subscribers
Avg views / post
19,400
33 posts measured
Reaction rate
4.11%
reactions ÷ views · ER floor
Posts in window
33
of 71 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 29 September 2026
Posts held71 (17 February 2026 – 29 September 2026)
Views total639,500
Reactions total26,271
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Sept 2026, 20:44 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.

What this channel posts

Photos
674
Videos
33
Links
100

Lifetime counters from Telegram’s own channel header, read 29 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
1m 04s
Average length
1m 04s

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.

Reaction mix

52,630 reactions across 71 posts, in 4 distinct kinds. The most used accounts for 50.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 540471623602406175726,57350.5%
custom 520218899880137887623,91145.4%
custom 52042708038094848821,6573.15%
custom 52019349042411881414890.929%

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 71 of the 71 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 52,630 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 71 most recent posts we hold, published 17 February 2026 to 29 September 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
2,944
across the posts below
Posts paid on
57
of 71 we hold a reading for · 80%
Most on one post
2,410
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @chr1swav. 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 71 most recent posts we hold for this entry, published 17 February 2026 to 29 September 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

29 Sept 2026, 13:57 UTC≈8,600 views946 reactions3 Starsread 29 September 2026
Photo

Photo, posted without a caption

custom 5404716236024061757665custom 5202188998801378876281

29 Sept 2026, 09:58 UTC≈11,100 views1,286 reactionsread 29 September 2026
Photo

???

custom 5404716236024061757990custom 5202188998801378876296

28 Sept 2026, 18:51 UTC≈12,100 views409 reactions1 Starread 29 September 2026

HB vlog 🎀 https://vt.tiktok.com/ZSbrvrBt9/

custom 5404716236024061757324custom 520218899880137887685

28 Sept 2026, 18:02 UTC≈12,100 views657 reactions4 Starsread 29 September 2026

такс, ну влог вроде как готов выкладываю? и хочу еще успеть сегодня постримить, думаю к часам 22:00 будет стрим 🎀

custom 5202188998801378876550custom 5404716236024061757107

27 Sept 2026, 18:28 UTC≈13,000 views1,369 reactions3 Starsread 29 September 2026

ребята, если кто-то стесняется лайкать, не стесняйтесь!!! Скоро будут еще новые фотки в ой ой ой каких образах

custom 54047162360240617571,000custom 5202188998801378876369

27 Sept 2026, 18:15 UTC≈13,300 views3,162 reactions26 Starsread 29 September 2026
Photo

💅💄🌹

custom 52021889988013788762,680custom 5404716236024061757482

27 Sept 2026, 16:06 UTC≈13,000 views761 reactionsread 29 September 2026

планировала сегодня влог выложить, в итоге у меня перегрелся телефон и крашнулось все что монтировала 🥺 буду сейчас все заново делать, если успею загружу сегодня стрим тогда уже завтра и ждите через часика 2 фоточки со сьемки ▫️🤍

custom 5404716236024061757592custom 5202188998801378876169

26 Sept 2026, 12:23 UTC≈12,800 views879 reactionsread 29 September 2026
Photo

Я уже вернулась в Москву, сегодня смонтирую влог, сделаю делишки которые поднакопились и послезавтра стрим Вот такие прекрасные подарки доехали, все открыточки прочитала, очень приятно 🥺🤍 Спасибо вам еще раз за поздравления, обнимаю ▫️

custom 5404716236024061757706custom 5202188998801378876173

23 Sept 2026, 23:03 UTC≈18,400 views1,150 reactions1 Starread 29 September 2026

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

custom 5404716236024061757936custom 5202188998801378876214

23 Sept 2026, 13:30 UTC≈20,300 views1,449 reactions22 Starsread 29 September 2026
Video

🖤

custom 52021889988013788761,220custom 5404716236024061757229

23 Sept 2026, 09:04 UTC≈20,200 views659 reactionsread 29 September 2026

Стрим в 12:40 🎀 🍰

custom 5404716236024061757533custom 5202188998801378876126

22 Sept 2026, 21:31 UTC≈22,000 views1,776 reactions20 Starsread 29 September 2026
Photo

Photo, posted without a caption

custom 54047162360240617571,400custom 5202188998801378876376

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

Posts edited after publishing

@chr1swav edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
27 September 2026
Most recent edit
27 September 2026

Forward network

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

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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

STREAM INSIDE
@streaminside · 265,104
#1
Ликс
@dmlixxx · 361,606
#2
uglyfacekid
@uglyfacekkk · 230,304
#3
des0ut
@des0ut · 35,873
#4
heliN139 💀
@heleNyssss · 120,686
#5
Spokoynich
@spokoynich228 · 116,985
#6
skywhywalker
@skywhyw4lker · 191,940
#7
korya_mc
@korya_mc · 109,148
#8
Exile
@exilemusic13 · 1,445,701
#9
ZLOYn
@zloy · 194,758
#10
Рифмы и Панчи 🤯
@rhymestg · 1,415,446
#11
Улей Пчёлкина 🐝
@alexeeeeey · 32,134
#12
morphilina
@morphilina · 53,121
#13
Офис Стила | steel streams
@steelstaya · 212,319
#14
ДИНА БЛИН
@dinablin · 36,741
#15
кап кап кап
@brksyolo · 13,019
#16
ДАНИЛА ГОРИЛЛА 🦍
@danila_gorilla · 643,829
#17
tenderlybae💔
@plsbetenderly · 225,418
#18
Риса за Творчество / РЗТ
@risazatvorchestvo · 165,824
#19
EVELONE 1️⃣9️⃣2️⃣
@evelone192gg · 1,103,372
#20
by_owl
@byowl · 144,865
#21
Морфи или мерфи?
@morpheyaa · 188,050
#22
Бустер 🍄
@bigpencil · 1,205,572
#23
FREAK
@freak192 · 64,867
#24
yuuechka
@yueechka · 71,866
#25
Дневник Симпла
@s1mplegod123 · 246,250
#26
SKILLZOR
@ropz · 50,171
#27
KISHKI FAMILY
@kishkiFM · 39,186
#28
ПАРАДЕЕВИЧ
@paradeevich · 1,059,396
#29
Равшан Джульпаев
@RavshanNstream · 355,150
#30
Логово Внизу
@nebudetgg · 493,624
#31
НМШ
@nmshhub · 721,829
#32
ct0m
@ct0m · 217,917
#33
РАЙЗ ЛАВ Ю
@raiz · 310,112
#34
ФУЛЫ СТРИМЕРОВ
@fullstreamers · 7,386
#35
ТРУСЫ РАЙЗА
@raiznews · 518,726
#36
leva2k
@lev_streams · 95,308
#37
Развлекательный канал «ЮРАПИВО»
@yurapivas · 21,423
#38
УМОМ🧠
@ymombet · 11,869
#39
Бустероид 🥋🥊
@busteroid3000 · 440,020
#40
Перезаливы стримов
@fullstreamers2 · 26,023
#41
AUNKERE
@aunkeretg · 144,151
#42
DILARA
@dilalara753 · 271,556
#43
BUDA +
@budaog · 359,247
#44
40
@lix2004 · 98,430
#45
dyrachyo
@dyrachyo · 210,176
#46
Алексей Шевцов
@jolybells · 359,059
#47
MaxBetov
@burdakekw · 123,982
#48
Агрошкольник
@quickhuntik · 13,902
#49
ЛИТВИН
@litvintm · 1,569,936
#50
deko_O
@dekocsoff · 232,847
#51
FREAKS
@freaktwitch · 5,823
#52
bushido zho
@bushidozho · 188,314
#53
dasha228play
@dasha228play · 56,584
#54
4ch
@why4ch · 1,042,455
#55
Медийка
@mediyca · 726,755
#56
Мокривский завали ебало
@mokrivskiy · 416,450
#57
MELLSTROY BONUS
@mellstroybonus · 328,434
#58
M0NESY LIFE
@m0NESY13 · 254,181
#59
CS2NEWS | Counter-Strike 2
@newcsgo · 585,785
#60
PLOHOY PAREN
@plohoypacan · 380,482
#61
Nix
@nixtalk · 259,858
#62

Read from Telegram’s recommendation API, most recently 4 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

morphilina
@morphilina · 53,121
Telegram ranks this channel #3 of 33 here — alongside 32 others — read 23 August 2026
Улей Пчёлкина 🐝
@alexeeeeey · 32,134
Telegram ranks this channel #6 of 63 here — alongside 62 others — read 5 September 2026
ДИНА БЛИН
@dinablin · 36,741
Telegram ranks this channel #6 of 63 here — alongside 62 others — read 1 September 2026
KISHKI FAMILY
@kishkiFM · 39,186
Telegram ranks this channel #8 of 60 here — alongside 59 others — read 30 August 2026
🏴‍☠️ Fasoollka 🏴‍☠️
@fassoollkaa · 25,010
Telegram ranks this channel #11 of 51 here — alongside 50 others — read 14 September 2026
планета Жопа
@planetapopa · 74,250
Telegram ranks this channel #12 of 65 here — alongside 64 others — read 23 September 2026
Развлекательный канал «ЮРАПИВО»
@yurapivas · 21,423
Telegram ranks this channel #12 of 72 here — alongside 71 others — read 23 September 2026
я gaechka 🕵️‍♂️
@gaechkatm · 57,446
Telegram ranks this channel #15 of 65 here — alongside 64 others — read 23 August 2026
des0ut
@des0ut · 35,873
Telegram ranks this channel #18 of 59 here — alongside 58 others — read 1 September 2026
Диана Rolls Royce
@DianaRice · 40,545
Telegram ranks this channel #22 of 62 here — alongside 61 others — read 14 September 2026
jamside in the building
@krrypt · 20,865
Telegram ranks this channel #23 of 69 here — alongside 68 others — read 25 September 2026
yuuechka
@yueechka · 71,866
Telegram ranks this channel #25 of 64 here — alongside 63 others — read 30 August 2026
leva2k
@lev_streams · 95,308
Telegram ranks this channel #26 of 65 here — alongside 64 others — read 21 August 2026
moranabattory
@moranatamara · 29,594
Telegram ranks this channel #28 of 52 here — alongside 51 others — read 16 September 2026
dasha228play
@dasha228play · 56,584
Telegram ranks this channel #28 of 62 here — alongside 61 others — read 23 August 2026
uglyfacebet
@uglyface_bet · 27,263
Telegram ranks this channel #34 of 52 here — alongside 51 others — read 10 September 2026
Перезаливы стримов
@fullstreamers2 · 26,023
Telegram ranks this channel #35 of 56 here — alongside 55 others — read 13 September 2026
SKILLZOR
@ropz · 50,171
Telegram ranks this channel #39 of 61 here — alongside 60 others — read 30 August 2026
FREAK
@freak192 · 64,867
Telegram ranks this channel #43 of 71 here — alongside 70 others — read 21 August 2026
строгочмо
@strogo228 · 444,342
Telegram ranks this channel #52 of 74 here — alongside 73 others — read 23 September 2026

This channel appears in 20 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“chr1swave” (@chr1swav), 34,623 subscribers as measured 28 September 2026. Telegram Register, tgregister.com/channel/chr1swav.

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.