Telegram RegisterThe public register of Telegram
Telegram profile photo for ķrevĩss ⋆

Channel

ķrevĩss ⋆

@kreviss

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

383subscribers

-9 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-1001762867839
TypeChannel
Username@kreviss
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live3 October 2026
Measurements held6
Confirmed unchanged1 time, most recently 3 October 2026
On Telegramt.me/kreviss

Topic

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 22 September 2026 and assigned it the closest of 31 fixed categories, at 87% 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

381392386.57 August 2026 — 392 subscribers8 August 2026 — 392 subscribers16 August 2026 — 389 subscribers24 August 2026 — 386 subscribers19 September 2026 — 381 subscribers3 October 2026 — 383 subscribers3837 August 20263 October 2026
6 measurements spanning 57 days, net -9. 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 379–394 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Oct 2026, 20:39383+2
19 Sept 2026, 09:39381-5
24 Aug 2026, 15:37386-3
16 Aug 2026, 03:26389-3
8 Aug 2026, 06:01392no change
7 Aug 2026, 16:08392first reading

Engagement

13 posts held, back to 15 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 13 posts for this entry, the most recent from 27 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
19s
Average length
10s

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

293 reactions across 10 posts, in 10 distinct kinds. The most used accounts for 16.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53864470858243994644816.4%
custom 52898650309578196234214.3%
custom 52963942788959199634214.3%
custom 53527311802339289724013.7%
custom 52538177956442388703311.3%
custom 53461160544247645753210.9%
custom 5355107121782360177217.17%
custom 5229054062187543276186.14%
custom 525383150088487940693.07%
custom 537055598170710140282.73%

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

Measured over the 13 most recent posts we hold, published 15 July 2026 to 27 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
112
across the posts below
Posts paid on
4
of 13 we hold a reading for · 31%
Most on one post
88
single highest reading

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

27 Jul 2026, 19:04 UTC207 views41 reactions1 Starread 8 August 2026

Posted without readable text

custom 535510712178236017721custom 52898650309578196238custom 53705559817071014028custom 53527311802339289724

23 Jul 2026, 13:34 UTC334 views15 reactionsread 8 August 2026

и теория и вождение в один день с перерывами на работу, устала

custom 525381779564423887011custom 52963942788959199634

23 Jul 2026, 13:33 UTC298 views25 reactions1 Starread 8 August 2026

Posted without readable text

custom 534611605442476457510custom 52290540621875432766custom 53527311802339289725custom 52898650309578196233custom 52538177956442388701

Signed dina

22 Jul 2026, 18:15 UTC285 views14 reactionsread 8 August 2026

ну хотя там как будто и показывать нечего, ниче особенного, но все равно сниму

custom 525381779564423887014

Signed dina

22 Jul 2026, 18:14 UTC274 views12 reactionsread 8 August 2026

на это без б сниму

custom 529639427889591996311custom 52898650309578196231

Signed dina

22 Jul 2026, 18:14 UTC269 viewsread 8 August 2026

💬 У тебя новое сообщение! Повседневный ↩️ Свайпни для ответа.

Signed dina

22 Jul 2026, 17:56 UTC273 viewsread 8 August 2026

💬 У тебя новое сообщение! сделай туториал на макияж пж😭 ↩️ Свайпни для ответа.

Signed dina

22 Jul 2026, 16:29 UTC260 views15 reactionsread 8 August 2026

завидую тем у кого дохрена места между глазом и бровью, столько власти в руках🙂🙂

custom 535273118023392897212custom 52538177956442388703

Signed dina

22 Jul 2026, 10:18 UTC262 views72 reactionsread 8 August 2026
Photo

Photo, posted without a caption

custom 529639427889591996327custom 528986503095781962318custom 535273118023392897214custom 53461160544247645758custom 52538177956442388704custom 52290540621875432761

Signed dina

15 Jul 2026, 14:32 UTC388 views51 reactions22 Starsread 8 August 2026
Photo

Photo, posted without a caption

custom 538644708582439946424custom 52898650309578196239custom 52290540621875432768custom 52538315008848794064custom 53461160544247645753custom 53527311802339289723

Signed dina

15 Jul 2026, 14:32 UTC306 views2 reactionsread 8 August 2026

ну в один пост не уложиться

custom 53864470858243994642

Signed dina

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

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

“ķrevĩss ⋆” (@kreviss), 383 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/kreviss.

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.