Telegram RegisterThe public register of Telegram
Telegram profile photo for ﹫ 𝗌𝗎𝗉𝗉𝗈𝗋𝗍 𝗅𝗂𝗌𝗍

Channel

﹫ 𝗌𝗎𝗉𝗉𝗈𝗋𝗍 𝗅𝗂𝗌𝗍

@vincentsbunny

On this record: Previous handles · Growth · Engagement · Posts · Citations · Cite this entry

1subscribers

+0 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1003915208528
TypeChannel
Username@vincentsbunny
Created9 July 2026 — measured — dated from the channel’s first post
First recorded15 August 2026
Last confirmed live1 September 2026
Measurements held2
On Telegramt.me/vincentsbunny

Previous handles

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

@vincentsbunny
held 15 August 2026 – 15 August 2026

Growth

111 August 2026 — 1 subscribers15 August 2026 — 1 subscribers11 August 202615 August 2026
2 measurements spanning 4 days. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 06:451no change
11 Aug 2026, 16:301first reading

Engagement

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

Recent posts

11 Jul 2026, 19:54 UTC22 viewsread 15 August 2026

﹫ все не_сш варк ﹝ 🐾🪽 ﹞- ноншейр - @billcipherspuppy ﹫ Джинемо ﹝ 🇨🇭🥀 ﹞ - ноншейр - @Nemokissme Джинтето ﹝ 🥖🥀 ﹞ - шейр - @Nemokissme ﹫ RadioDeer ﹝ 📻🦌 ﹞ - ноншейр - @linacastle Trauma Survivors ﹝ 👮‍♂👠 ﹞ - селектив - @linacastle HariKagami ﹝ 🪡🪞 ﹞ - селектив - @linacastle ﹫ Кунируны ﹝ 🌙📗 ﹞ - нег - @kunikidaobsession ﹫ поляны, нервы, хувы воксении ﹝ 💀✨ ﹞ - ноншейр+миррор-селектив+шейр+войд - @hutaossweety ﹫ Сайри/Сакихара…

Showing the 4 most recent of 4 posts we hold for @vincentsbunny. 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.

Mentions

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.

“﹫ 𝗌𝗎𝗉𝗉𝗈𝗋𝗍 𝗅𝗂𝗌𝗍” (@vincentsbunny), 1 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/vincentsbunny.

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.