Telegram RegisterThe public register of Telegram
Telegram profile photo for Venerate, (CLOSEDOWN).

Channel

Venerate, (CLOSEDOWN).

@venerrate

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

104subscribers

-6 since we began measuring on 13 August 2026

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

Register entry

Telegram ID-1003202043248
TypeChannel
Username@venerrate
CreatedBetween 1 October 2025 and 31 January 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live4 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 4 September 2026
On Telegramt.me/venerrate

Growth

10411010713 August 2026 — 110 subscribers14 August 2026 — 110 subscribers27 August 2026 — 108 subscribers4 September 2026 — 104 subscribers13 August 20264 September 2026
4 measurements spanning 21 days, net -6. 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 103–111 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Sept 2026, 05:59104-4
27 Aug 2026, 12:56108-2
14 Aug 2026, 18:06110no change
13 Aug 2026, 18:04110first reading

Engagement

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

Recent posts

19 Apr 2026, 12:11 UTC205 viewsread 13 August 2026

Ngga mau buka comsect, udah ya gua off dulu... Farewell, moots. Love you. 🤍

19 Apr 2026, 11:59 UTC206 viewsread 13 August 2026

Hello, moots. Sorry for my absence for a couple of days here.. I sadly want to announced that I'll officially gonna CLOSE this gallery for good and I'll leave my business account. I've been busy with my final thesis so much lately and I don't think I gave enough mutual benefits for all of you lately either. Thank you for all the days and time we spent together, but now we sadly must be apart. Feel free to unsubs my

17 Apr 2026, 06:17 UTC194 viewsread 13 August 2026

ㅤ Sound arrives restrained, absorbed by fabric and wood, becoming texture instead of interruption. Goodbye, dear @.Shurraka. Time prefers discretion here, stretching moments without declaration, allowing study to exist. ㅤ

17 Apr 2026, 06:17 UTC147 viewsread 13 August 2026

ㅤ Sound arrives restrained, absorbed by fabric and wood, becoming texture instead of interruption. Goodbye, dear @.Rwoodvan. Time prefers discretion here, stretching moments without declaration, allowing study to exist. ㅤ

15 Apr 2026, 04:17 UTC146 viewsread 13 August 2026
Forwarded from @SeraphmourPhoto

commis sama @mcieum di @ayubyu

14 Apr 2026, 07:19 UTC156 viewsread 13 August 2026

ㅤ Sound arrives restrained, absorbed by fabric and wood, becoming texture instead of interruption. Goodbye, dear @.Skylarf. Time prefers discretion here, stretching moments without declaration, allowing study to exist. ㅤ

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

Forward network

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.

Mentions

Named by 1 registered channel — 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.

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

“Venerate, (CLOSEDOWN).” (@venerrate), 104 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/venerrate.

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.