Telegram RegisterThe public register of Telegram
Telegram profile photo for zelenograd’s saviour

Channel

zelenograd’s saviour

@pochemu_zhivoy

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

160subscribers

-11 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-1002073783709
TypeChannel
Username@pochemu_zhivoy
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live12 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/pochemu_zhivoy

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 25 September 2026 and assigned it the closest of 31 fixed categories, at 63% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

160171165.57 August 2026 — 171 subscribers8 August 2026 — 171 subscribers14 August 2026 — 169 subscribers20 August 2026 — 166 subscribers3 September 2026 — 165 subscribers12 September 2026 — 163 subscribers1 October 2026 — 164 subscribers12 October 2026 — 160 subscribers7 August 202612 October 2026
8 measurements spanning 66 days, net -11. 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 158–173 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 05:38160-4
1 Oct 2026, 02:02164+1
12 Sept 2026, 02:20163-2
3 Sept 2026, 01:45165-1
20 Aug 2026, 19:53166-3
14 Aug 2026, 19:25169-2
8 Aug 2026, 14:46171no change
7 Aug 2026, 16:02171first reading

Engagement

19 posts held, back to 26 July 2026 — the 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 19 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
10s
Average length
10s

Measured directly from 1 video 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

96 reactions across 15 posts, in 10 distinct kinds. The most used accounts for 22.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍2222.9%
🐳1515.6%
🤣1414.6%
custom 54224180511087337691111.5%
custom 543863082680164273588.33%
custom 544523847936771718888.33%
🔥88.33%
🏆77.29%
custom 531878664064939765222.08%
custom 532334087364623118311.04%

Custom emoji. 5 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 15 of the 19 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 96 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 26 July 2026 to 8 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

8 Aug 2026, 13:09 UTC43 views2 reactionsread 8 August 2026
Photo

как меня ебашит этот бас я снят кстати

🏆2

Signed саша гадспид

8 Aug 2026, 10:19 UTC64 views2 reactionsread 8 August 2026
Photo

мне пиздец выполняю все что говорят подписчики день первый

🏆2

Signed саша гадспид

8 Aug 2026, 07:27 UTC71 views1 reactionsread 8 August 2026

Posted without readable text

👍1

Signed саша гадспид

6 Aug 2026, 11:32 UTC82 views2 reactionsread 8 August 2026
Video message

Video message, posted without a caption

custom 54452384793677171882

Signed саша гадспид

3 Aug 2026, 20:59 UTC116 viewsread 8 August 2026

бегуны из Москвы кто может мне одолжить трейловую пару в размере 10 или 10,5 US в субботу бегу ориентирование поэтому нужно сцепление

Signed саша гадспид

2 Aug 2026, 10:10 UTC149 views14 reactionsread 8 August 2026
Video message

Video message, posted without a caption

custom 542241805110873376911🤣3

Signed саша гадспид

31 Jul 2026, 12:27 UTC176 views7 reactionsread 8 August 2026
Photo

хотел вас попросить вчера ночью добить 2 миллиарда без меня справились спасибо

🏆3👍2🔥2

Signed саша гадспид

31 Jul 2026, 05:12 UTC138 views2 reactionsread 8 August 2026
File

File, posted without a caption

custom 53187866406493976522

Signed саша гадспид

28 Jul 2026, 21:35 UTC157 views3 reactionsread 8 August 2026

предлагаю реально нассать ей в рюкзак

🐳3

Signed алина

28 Jul 2026, 16:44 UTC145 views7 reactionsread 8 August 2026
Photo

Photo, posted without a caption

🐳6custom 53233408736462311831

Signed алина

28 Jul 2026, 16:44 UTC137 views6 reactionsread 8 August 2026
Photo

Photo, posted without a caption

🐳6

Signed саша гадспид

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

“zelenograd’s saviour” (@pochemu_zhivoy), 160 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/pochemu_zhivoy.

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.