Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝐢𝐧𝐟𝐨

Channel

𝐢𝐧𝐟𝐨

@lysuninfo

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

5subscribers

+0 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-1002026534377
TypeChannel
Username@lysuninfo
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live15 September 2026
Measurements held2
On Telegramt.me/lysuninfo

Growth

57 August 2026 — 5 subscribers13 August 2026 — 5 subscribers7 August 202613 August 2026
2 measurements spanning 5 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”. The vertical axis spans 4–6 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 01:175no change
7 Aug 2026, 14:435first reading

Engagement

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

What this channel posts

Photos
65
Videos
3
Links
4

Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

4 Jul 2026, 17:29 UTC73 viewsread 13 August 2026
Photo

Туториал как делать зм. 3 вида зм. Обычно смотрю размер на нарезки и выбираю.

30 Mar 2026, 04:53 UTC58 viewsread 13 August 2026
Forwarded from @helpdiorfamPhoto

спасибо огромное за 3K. мы будем стараться делать больше материала 💋

29 Mar 2026, 17:11 UTC51 viewsread 13 August 2026
Photo

мы используем старые аватарки канала на пч, инфо, прайс и чат, чтобы не пропадал труд дизайнеров, которые создавали нам такие шедевры

Showing the 8 most recent of 8 posts we hold for @lysuninfo. 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 13 August 2026 — this entry's latest reading, not the date you are reading this.

“𝐢𝐧𝐟𝐨” (@lysuninfo), 5 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/lysuninfo.

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.