привет вишня
custom 547438231925716530426custom 53618721505400973059custom 52493559817537167527custom 52897417353316626526custom 54745904233075568523custom 51884772813491852102custom 52489651697945540562custom 52492767396071074472

Channel
@qo0kawe_chan
On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry
374subscribers
-5 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002289068593 |
|---|---|
| Type | Channel |
| Username | @qo0kawe_chan |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/qo0kawe_chan |
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 90% 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 |
|---|---|---|
| 19 Sept 2026, 02:21 | 374 | -8 |
| 10 Sept 2026, 01:37 | 382 | -3 |
| 31 Aug 2026, 12:35 | 385 | +6 |
| 24 Aug 2026, 11:57 | 379 | -2 |
| 17 Aug 2026, 15:48 | 381 | +1 |
| 9 Aug 2026, 23:37 | 380 | +1 |
| 9 Aug 2026, 17:47 | 379 | first reading |
14 posts held, back to 21 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 14 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.
687 reactions across 14 posts, in 8 distinct kinds. The most used accounts for 24.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5474382319257165304 | 171 | 24.9% | |
| custom 5361872150540097305 | 92 | 13.4% | |
| custom 5249276739607107447 | 83 | 12.1% | |
| custom 5248965169794554056 | 82 | 11.9% | |
| custom 5474590423307556852 | 80 | 11.6% | |
| custom 5289741735331662652 | 65 | 9.46% | |
| custom 5188477281349185210 | 62 | 9.02% | |
| custom 5249355981753716752 | 52 | 7.57% |
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 14 of the 14 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 687 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 21 July 2026 to 9 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @qo0kawe_chan. 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 14 most recent posts we hold for this entry, published 21 July 2026 to 9 August 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.
привет вишня
custom 547438231925716530426custom 53618721505400973059custom 52493559817537167527custom 52897417353316626526custom 54745904233075568523custom 51884772813491852102custom 52489651697945540562custom 52492767396071074472
🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟
custom 528974173533166265223custom 524935598175371675210custom 547459042330755685210custom 51884772813491852103custom 52489651697945540563custom 53618721505400973053custom 54743823192571653043custom 52492767396071074472
знакомьтесь, ещо адна мая ос по имени Мурка🎀 коммишки аткрыты кстате, пакупайт💓
custom 524896516979455405617custom 51884772813491852105custom 54743823192571653045custom 52492767396071074472custom 52493559817537167522custom 52897417353316626522custom 53618721505400973051custom 54745904233075568521
🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 私は草を食べるのが好きな小さな羊です。!! #арт в хорошем качестве тут! 🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟
custom 518847728134918521019custom 54743823192571653047custom 52489651697945540565custom 52492767396071074475custom 52493559817537167523custom 52897417353316626523custom 53618721505400973053custom 54745904233075568523
🔅🔅🔅💖💖💖 ⋆. 𐙚 ˚немножко хочу напомнить про свой мини магазинчик !!🧸 я недавно понизила цены почти на все вещи☺️ также теперь я продаю свои фигурки и уже скоро там появятся мягкие игрушки 🍓 🔅🔅🔅💖💖💖
custom 524896516979455405619custom 51884772813491852106custom 52897417353316626524custom 52492767396071074472custom 52493559817537167522custom 53618721505400973052custom 54743823192571653042custom 54745904233075568522
🌟🌟🌟🌟🌟🌟🌟🌟🌟 Любишь все, что связано с жсф?👍🥛🐁 🌟тогда тебе к нам!🌟 Подборка самых красивых jsf каналов 🌟🌟🌟
custom 547438231925716530414custom 53618721505400973053custom 51884772813491852102custom 52489651697945540561
🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 Застенчивая и робкая девушка. Обычно она становится жертвой издевательств. По какой-то причине, она создаёт у меня впечатление, что может сломаться и стать очень жестокой, если всё зайдёт слишком далеко. #косплей 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩
custom 547438231925716530419custom 52492767396071074478custom 52897417353316626528custom 51884772813491852105custom 53618721505400973053custom 54745904233075568523custom 52493559817537167522custom 52489651697945540561
🌟Follow me, I will show you the light
custom 536187215054009730524custom 547438231925716530410custom 52493559817537167527custom 51884772813491852103custom 52489651697945540563custom 52492767396071074473custom 52897417353316626523custom 54745904233075568523
мои дорогие, я скоро перееду в другую страну🍓 связи с этим я срочно продаю свои вещи, в том числе и косплеи, парики, платья и головные уборы я буду ОЧЕНЬ рада, если вы купите у меня хоть что нибудь💖 https://t.me/qo00kawee
custom 524896516979455405618custom 52492767396071074475custom 52493559817537167525custom 54743823192571653043custom 53618721505400973052custom 52897417353316626521custom 54745904233075568521
ೀ܀⊹˙┆✽ 𝑻𝒉𝒂𝒏𝒌𝒔(*ˊᵕˋ*)੭ ੈ🤩 𝜗𝜚┆˙⊹܀ೀ #косплей
custom 547459042330755685235custom 547438231925716530413custom 52492767396071074478custom 51884772813491852105custom 52493559817537167523custom 52897417353316626523custom 52489651697945540562custom 53618721505400973052
🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 спасибо за звездачки рипят бальшое, респект🤩🤩
custom 547438231925716530422custom 53618721505400973058custom 52493559817537167525custom 51884772813491852104custom 52489651697945540564custom 54745904233075568523custom 52492767396071074472custom 52897417353316626521
Photo, posted without a caption
custom 524927673960710744730custom 54745904233075568527custom 54743823192571653046custom 51884772813491852103custom 52489651697945540563custom 52897417353316626523custom 52493559817537167522custom 53618721505400973052
Showing the 12 most recent of 14 posts we hold for @qo0kawe_chan. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“вишнч!” (@qo0kawe_chan), 374 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/qo0kawe_chan.
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.