Telegram RegisterThe public register of Telegram
Telegram profile photo for Zharik Ufimskiy

Channel

Zharik Ufimskiy

@Zhara97

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

3subscribers

+1 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1004456226275
TypeChannel
Username@Zhara97
Created26 July 2026measured — dated from the channel’s first post
First recorded13 August 2026
Last confirmed live11 September 2026
Measurements held3
Confirmed unchanged4 times, most recently 11 September 2026
On Telegramt.me/Zhara97

Growth

232.512 August 2026 — 2 subscribers13 August 2026 — 2 subscribers20 August 2026 — 3 subscribers12 August 202620 August 2026
3 measurements spanning 8 days, net +1. 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 2–3 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
20 Aug 2026, 03:043+1
13 Aug 2026, 21:042no change
12 Aug 2026, 07:452first reading

Engagement

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

Recent posts

29 Jul 2026, 15:38 UTC13 viewsread 13 August 2026
Forwarded from @transfers_khlPhoto

🦌 🔄 💚 Нижегородское «Торпедо» в результате обмена на денежную компенсацию с «Салаватом Юлаевым», подписало двусторонний контракт с 19-летним защитником Максимом Агафоновым.

29 Jul 2026, 11:58 UTC10 viewsread 13 August 2026

Появилась информация что могут обменять игрока

29 Jul 2026, 11:56 UTC10 viewsread 13 August 2026

🍯 ➡️🦌 Защитник Максим Агафонов продолжит свою карьеру в нижегородском «Торпедо». Уфимцы получат денежную компенсацию за игрока.

28 Jul 2026, 13:48 UTC9 viewsread 13 August 2026
Photo

🦌 Форвард Алексей Кручинин покидает нижегородское «Торпедо». Контракт расторгнут по обоюдному согласию сторон.

28 Jul 2026, 09:30 UTC7 viewsread 13 August 2026
Forwarded from @transfers_khlPhoto

⚓️ 🔄 🔵 «Адмирал» и московское «Динамо» совершили обмен, в результате которого форвард Павел Шэн продолжит карьеру в Московском клубе. ➡️ ⚓️ Приморский клуб получает спортивные права на форварда Семёна Дер-Аргучинцева, а также денежную компенсацию.

27 Jul 2026, 10:53 UTC7 viewsread 13 August 2026
Photo

Максим Комтуа в кофте «Салавата Юлаева». Броссо переманивает второго друга к себе?

27 Jul 2026, 10:51 UTC6 viewsread 13 August 2026
Photo

⚡️«💚Салават Юлаев» интересуется Скоттом Риди и Грэмом Кларком 🏒К Грэму также проявляет интерес «🚜Трактор»

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

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.

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

“Zharik Ufimskiy” (@Zhara97), 3 subscribers as measured 20 August 2026. Telegram Register, tgregister.com/channel/Zhara97.

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.