Telegram RegisterThe public register of Telegram
Telegram profile photo for архив//кскслевикссс ??

Channel

архив//кскслевикссс ??

@qslevixbro

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry

331subscribers

-7 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002218159906
TypeChannel
Username@qslevixbro
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/qslevixbro

Growth

331338334.57 August 2026 — 338 subscribers8 August 2026 — 338 subscribers15 August 2026 — 331 subscribers7 August 202615 August 2026
3 measurements spanning 8 days, net -7. 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 330–339 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 15:53331-7
8 Aug 2026, 07:03338no change
7 Aug 2026, 13:49338first reading

Engagement

17 posts held, back to 3 May 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
29.8%
avg views ÷ 331 subscribers
Avg views / post
98.5
2 posts measured
Reaction rate
2.03%
reactions ÷ views · ER floor
Posts in window
2
of 17 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 31 July 2026
Posts held17 (3 May 202631 July 2026)
Views total197
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 07:03 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

Video runtime
1m 00s
Average length
12s

Measured directly from 5 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

777 reactions across 16 posts, in 3 distinct kinds. The most used accounts for 39.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 544726644696078529630739.5%
custom 542015243009027310324831.9%
custom 527187587826609164722228.6%

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 areTelegram’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 16 of the 17 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 777reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 3 May 2026 to 31 July 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
1
across the posts below
Posts paid on
1
of 16 we hold a reading for · 6%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @qslevixbro. 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 17 most recent posts we hold for this entry, published 3 May 2026 to 31 July 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

31 Jul 2026, 17:19 UTC88 views1 reactionsread 8 August 2026

я тут если что

custom 52718758782660916471

Signed ?? кслевикскскс ‘•

31 Jul 2026, 17:06 UTC109 views3 reactionsread 8 August 2026

вы че тут

custom 52718758782660916473

Signed ?? кслевикскскс ‘•

26 Jun 2026, 08:58 UTC291 views6 reactionsread 8 August 2026

переезд!!!!!!! https://t.me/kslevix https://t.me/kslevix https://t.me/kslevix https://t.me/kslevix https://t.me/kslevix https://t.me/kslevix

custom 54201524300902731034custom 52718758782660916471custom 54472664469607852961

25 Jun 2026, 21:07 UTC300 views4 reactionsread 8 August 2026

https://t.me/kslevix https://t.me/kslevix https://t.me/kslevix https://t.me/kslevix https://t.me/kslevix https://t.me/kslevix

custom 54201524300902731033custom 54472664469607852961

25 Jun 2026, 20:13 UTCviews —

архив//кскслевикссс ?? pinned «типы, шухер!!!! новый бот тут уже!!! https://t.me/kslevix https://t.me/kslevix https://t.me/kslevix»

25 Jun 2026, 20:06 UTC256 views3 reactionsread 8 August 2026

переезд!!!!!!! https://t.me/kslevix https://t.me/kslevix https://t.me/kslevix https://t.me/kslevix https://t.me/kslevix https://t.me/kslevix от мью не отписываюсь, жду вас

custom 54201524300902731032custom 52718758782660916471

25 Jun 2026, 20:01 UTC231 views6 reactionsread 8 August 2026

типы, шухер!!!! новый бот тут уже!!! https://t.me/kslevix https://t.me/kslevix https://t.me/kslevix

custom 54201524300902731036

25 Jun 2026, 16:18 UTC223 views40 reactionsread 8 August 2026
Video

#моивидео #майоргром

custom 544726644696078529621custom 527187587826609164711custom 54201524300902731038

22 Jun 2026, 18:39 UTC306 views84 reactionsread 8 August 2026
Photo

🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 #nsfwalphabet #сергейразумовский 🤩🤩🤩🤩🤩 🤩🤩🤩🤩 материал в комментариях!

custom 527187587826609164744custom 544726644696078529622custom 542015243009027310318

20 Jun 2026, 19:17 UTC324 views52 reactionsread 8 August 2026
Video

#моивидео #сергейразумовский

custom 542015243009027310331custom 527187587826609164711custom 544726644696078529610

15 Jun 2026, 16:51 UTC460 views87 reactionsread 8 August 2026
Photo

😐🤩🤩🤩🤩🤩 🤩🤩🤩😐 ❤️‍🔥 🦇Трумен Капоте💔 🤩🤩⋆˙⟡♡ — гастроли🤩🤩 💔сюжет в комментариях! 🍒ССЫЛОЧКА НА ТРУМЕНА🍒 #боты #труменкапоте

custom 527187587826609164744custom 542015243009027310324custom 544726644696078529619

9 Jun 2026, 20:39 UTC579 views90 reactions1 Starread 8 August 2026
Photo

😐🤩🤩🤩🤩🤩 🤩🤩🤩😐 ❤️‍🔥 🦇Сергей Разумовский(stud)💔 🤩🤩⋆˙⟡♡ — крыша🤩🤩 💔сюжет в комментариях! 🍒ССЫЛОЧКА НА СЕРЁЖУ🍒 #боты #сергейразумовский

custom 544726644696078529649custom 527187587826609164724custom 542015243009027310317

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

Mentions

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.

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

“архив//кскслевикссс ??” (@qslevixbro), 331 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/qslevixbro.

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.