Telegram RegisterThe public register of Telegram
Telegram profile photo for protected.by

Channel

protected.by

@protected_by

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

585subscribers

-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-1002475309134
TypeChannel
Username@protected_by
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live28 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 28 August 2026
On Telegramt.me/protected_by

Growth

585592588.57 August 2026 — 592 subscribers8 August 2026 — 592 subscribers21 August 2026 — 591 subscribers28 August 2026 — 585 subscribers7 August 202628 August 2026
4 measurements spanning 21 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 584–593 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Aug 2026, 21:57585-6
21 Aug 2026, 07:03591-1
8 Aug 2026, 03:17592no change
7 Aug 2026, 18:25592first reading

Engagement

12 posts held, back to 24 December 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 12 posts for this entry, the most recent from 5 July 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

5 Jul 2026, 18:19 UTC200 viewsread 8 August 2026

новая итерация того чем я занимался здесь

5 Jul 2026, 18:17 UTC184 viewsread 8 August 2026
Forwarded from @ss_aaaaaaaaPhoto

Photo, posted without a caption

19 Mar 2026, 20:34 UTC761 viewsread 8 August 2026

Я продолжаю делать татушки протектед просто совсем не веду канал любые вопросы/запись @ss_aaaaaaaaa

8 Feb 2026, 11:16 UTC998 viewsread 8 August 2026

Новых эскизов пока не будет, их достаточно много разных свободных, а если делать новые то только если будет идея с чем то новеньким, вот так…

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

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

“protected.by” (@protected_by), 585 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/protected_by.

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.