Telegram RegisterThe public register of Telegram
Telegram profile photo for Viridity

Channel

Viridity

@vviridityy

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

192subscribers

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

Growth

1841921887 August 2026 — 185 subscribers8 August 2026 — 184 subscribers8 August 2026 — 184 subscribers15 August 2026 — 185 subscribers23 August 2026 — 186 subscribers30 August 2026 — 192 subscribers7 August 202630 August 2026
6 measurements spanning 23 days, net +7. 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 183–193 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 04:39192+6
23 Aug 2026, 15:27186+1
15 Aug 2026, 10:45185+1
8 Aug 2026, 12:31184no change
8 Aug 2026, 04:32184-1
7 Aug 2026, 12:23185first reading

Engagement

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

What this channel posts

Video runtime
1m 05s
Average length
33s

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.

Recent posts

8 Aug 2026, 12:10 UTC15 viewsread 8 August 2026
Forwarded from @dykediary

In many cases this whole I hate all men performance from the cishets is becoming a way of not keeping men accountable for their actions. because "well they all suck". boys will be boys. the performative hatred will slowly turn into justification. It will become another "that's just what men do". we should not make this another way to lower the standards for men by assuming that they are inherently worse than us. they

8 Aug 2026, 12:10 UTC15 viewsread 8 August 2026
Forwarded from @dykediary

performative misandry will give you a false sense of progress while keeping you exactly where patriarchy wants you. It is very harmful to claim that you're a "man hater" while feeding the patriarchy and turning yet another act of rebellion against the patriarchy into a fetish or a playful role play with your male counterparts

7 Aug 2026, 23:24 UTC64 viewsread 8 August 2026

مربیم بهم یه برنامه‌ای داده که فقط باید بخوابم و فراموش کنم:))))

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

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.

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.

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

“Viridity” (@vviridityy), 192 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/vviridityy.

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.