Telegram RegisterThe public register of Telegram
Telegram profile photo for фонарь аптека

Channel

фонарь аптека

@lzgushachy

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

67subscribers

+2 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1002059592994
TypeChannel
Username@lzgushachy
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live17 September 2026
Measurements held4
Confirmed unchanged4 times, most recently 17 September 2026
On Telegramt.me/lzgushachy

Growth

65676611 August 2026 — 65 subscribers12 August 2026 — 65 subscribers18 August 2026 — 66 subscribers25 August 2026 — 67 subscribers11 August 202625 August 2026
4 measurements spanning 14 days, net +2. 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 65–67 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Aug 2026, 05:1667+1
18 Aug 2026, 23:4766+1
12 Aug 2026, 10:4765no change
11 Aug 2026, 13:1865first reading

Engagement

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

What this channel posts

Video runtime
34s
Average length
11s

Measured directly from 3 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.

Reaction mix

78 reactions across 10 posts, in 6 distinct kinds. The most used accounts for 34.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52805620458953299182734.6%
custom 53618070689006329911620.5%
custom 54251053906709960741620.5%
🤩1012.8%
👍78.97%
custom 540257837739777405022.56%

Custom emoji. 4 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 10 of the 10 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 78 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 10 most recent posts we hold, published 22 July 2026 to 3 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

3 Aug 2026, 05:53 UTC68 views5 reactionsread 11 August 2026

бег будет продолжаться до бесконечности

👍3custom 54025783773977740502

1 Aug 2026, 12:18 UTC75 views5 reactionsread 11 August 2026

😰

custom 54251053906709960743custom 53618070689006329912

31 Jul 2026, 13:39 UTC73 views7 reactionsread 11 August 2026
Photo

делается

custom 52805620458953299184custom 54251053906709960742🤩1

28 Jul 2026, 17:36 UTC94 views10 reactionsread 11 August 2026
Photo

Photo, posted without a caption

custom 52805620458953299185custom 53618070689006329913👍2

26 Jul 2026, 17:52 UTC83 views9 reactionsread 11 August 2026
Photo

Photo, posted without a caption

custom 52805620458953299185🤩2custom 54251053906709960742

25 Jul 2026, 09:20 UTC85 views12 reactionsread 11 August 2026
Photo

0-0🥱🥱🥱

🤩7custom 54251053906709960743custom 52805620458953299182

24 Jul 2026, 08:52 UTC84 views10 reactionsread 11 August 2026
Photo

https://t.me/lyricaholic подпишитесь на моего мужа ребята

custom 53618070689006329915custom 52805620458953299183custom 54251053906709960742

23 Jul 2026, 08:18 UTC71 views8 reactionsread 11 August 2026
Photo

Photo, posted without a caption

custom 53618070689006329914custom 52805620458953299182custom 54251053906709960742

22 Jul 2026, 18:45 UTC74 views9 reactionsread 11 August 2026
Video

🥱

custom 52805620458953299185custom 53618070689006329912custom 54251053906709960742

22 Jul 2026, 05:13 UTC61 views3 reactionsread 11 August 2026
Photo

Photo, posted without a caption

👍2custom 52805620458953299181

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

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

“фонарь аптека” (@lzgushachy), 67 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/lzgushachy.

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.