Channel
@visteria_cosp
On this record: Previous handles · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
240subscribers
+12 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002214500792 |
|---|---|
| Type | Channel |
| Username | @visteria_cosp |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 31 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 31 August 2026 |
| On Telegram | t.me/visteria_cosp |
@visteria_cosp was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Aug 2026, 20:13 | 240 | +1 |
| 25 Aug 2026, 03:46 | 239 | +6 |
| 17 Aug 2026, 14:34 | 233 | +5 |
| 9 Aug 2026, 21:00 | 228 | no change |
| 9 Aug 2026, 20:49 | 228 | first reading |
9 posts held, back to 8 August 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 9 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.
40 reactions across 8 posts, in 5 distinct kinds. The most used accounts for 35.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5312519394306312752 | 14 | 35.0% | |
| custom 6046201526173569823 | 9 | 22.5% | |
| custom 6046297084900938513 | 8 | 20.0% | |
| ❤🔥 | 6 | 15.0% | |
| ❤ | 3 | 7.50% |
Custom emoji. 3 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 8 of the 9 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 40 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 8 August 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.
⚔️⚔️⚔️⚔️⚔️⚔️⚔️⚔️ 🔤🔤🔤🔤🔤 〽️ 〽️ 🔤🔤🔤🔤🔤🔤 ⚔️⚔️⚔️⚔️⚔️⚔️ 🤩My heart burns for love♥️ 🤩My soul burns for blood🖐 🤩I'll take you🩸 I'll break you❤️ 🤩🤩 I'll crush you🌟 🤩🤩 I'll break you☠️ 🤩🤩 ⚔️⚔️⚔️⚔️⚔️⚔️⚔️⚔️ —Иногда единственный способ выжить— это перестать верить в сказки. 🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀 реакт/рт? #косплей
❤3custom 60462015261735698232custom 53125193943063127521
Signed ~
Ну... А я тоже хочу #интерактив
custom 60462970849009385134
Signed ~
Photo, posted without a caption
❤🔥3custom 60462015261735698232custom 53125193943063127521
Signed ~
Оно думает что оно косплеер 💀
custom 60462970849009385134
Signed ~
Я тоже хочу
custom 53125193943063127525
Signed ~
гоу?
custom 53125193943063127524
Signed ~
чуть чуть стащила у фурэ оку
❤🔥3custom 53125193943063127521
Signed ~
мне кажется я щас пол краса репостну
Signed ~
летс гоу
custom 60462015261735698235custom 53125193943063127522
Signed ~
Showing the 9 most recent of 9 posts we hold for @visteria_cosp. 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.
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 31 August 2026 — this entry's latest reading, not the date you are reading this.
“ℬυᥴⲧꫀⲣυя࿔” (@visteria_cosp), 240 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/visteria_cosp.
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.