Telegram RegisterThe public register of Telegram
Telegram profile photo for 50 оттенков пиздеца🩷🖕

Channel

50 оттенков пиздеца🩷🖕

@lav_lav_my

On this record: Growth · Engagement · Posts · Handles named that no longer answer · Cite this entry

50subscribers

-4 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-1003150278636
TypeChannel
Username@lav_lav_my
CreatedBetween 1 September 2025 and 30 November 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live10 September 2026
Measurements held5
Confirmed unchanged2 times, most recently 10 September 2026
On Telegramt.me/lav_lav_my

Growth

5054527 August 2026 — 54 subscribers10 August 2026 — 54 subscribers16 August 2026 — 53 subscribers24 August 2026 — 51 subscribers31 August 2026 — 50 subscribers7 August 202631 August 2026
5 measurements spanning 24 days, net -4. 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 49–55 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
31 Aug 2026, 22:0450-1
24 Aug 2026, 06:5351-2
16 Aug 2026, 18:0553-1
10 Aug 2026, 09:0054no change
7 Aug 2026, 18:0754first reading

Engagement

15 posts held, back to 22 January 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 15 posts for this entry, the most recent from 2 February 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

2 Feb 2026, 07:26 UTC33 viewsread 10 August 2026

https://t.me/luna_kryt

Signed лиловая крут.🫂

23 Jan 2026, 04:11 UTC48 viewsread 10 August 2026
Voice message

Voice message, posted without a caption

Signed лиловая крут.🫂

23 Jan 2026, 04:00 UTC40 viewsread 10 August 2026
Voice message

Voice message, posted without a caption

Signed лиловая крут.🫂

23 Jan 2026, 03:57 UTC31 viewsread 10 August 2026
Voice message

Voice message, posted without a caption

Signed лиловая крут.🫂

23 Jan 2026, 03:49 UTC33 viewsread 10 August 2026
Video message

Video message, posted without a caption

Signed лиловая крут.🫂

23 Jan 2026, 03:44 UTC31 viewsread 10 August 2026
Video message

Video message, posted without a caption

Signed лиловая крут.🫂

23 Jan 2026, 03:44 UTC25 viewsread 10 August 2026
Video message

Video message, posted without a caption

Signed лиловая крут.🫂

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

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

“50 оттенков пиздеца🩷🖕” (@lav_lav_my), 50 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/lav_lav_my.

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.