Telegram RegisterThe public register of Telegram
Telegram profile photo for Ганьба и мрiя

Channel

Ганьба и мрiя

@novorossialives

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

10subscribers

+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-1001915391736
TypeChannel
Username@novorossialives
DescriptionИнтересные ролики🤣🤣🤣
CreatedBetween 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live14 August 2026
Measurements held2
On Telegramt.me/novorossialives

Growth

107 August 2026 — 10 subscribers12 August 2026 — 10 subscribers7 August 202612 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 9–11 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 09:1610no change
7 Aug 2026, 11:0710first reading

Engagement

20 posts held, back to 8 May 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 20 posts for this entry, the most recent from 21 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
129
Videos
1,020
Links
132

Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
18m 48s
Average length
59s

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

Recent posts

21 Jun 2026, 20:33 UTC4 viewsread 12 August 2026
Forwarded from @absrdblogVideo

"Навіть якщо у нас закінчиться зброя, ми будемо воювати лопатами"

Signed Shindy

7 Jan 2026, 22:59 UTC17 viewsread 12 August 2026
Video

В Польше нельзя . Их там дебилами прыщатыми обзывают😂😂😂

Signed Shindy

26 Oct 2025, 06:37 UTC24 viewsread 12 August 2026
Forwarded from @burpobedaVideo

❗️Заслуживает внимания

Signed Shindy

18 Jun 2025, 20:23 UTC32 viewsread 12 August 2026
Forwarded from @Ti_mezVideo

Укро бабульки в Польше , такие милые 😇 💖Подписаться ЧасZ

Signed Shindy

15 Jun 2025, 05:40 UTC31 viewsread 12 August 2026
Forwarded from @Tama_tv_LifeVideo

Похоже на правду

Signed Shindy

15 Jun 2025, 04:59 UTC31 viewsread 12 August 2026
Forwarded from @saloyroniliPhoto

Польша заработала на украинских беженцах в 8 раз больше, чем предоставила помощи, — исследование Агентства ООН по делам беженцев. Украинские беженцы заполнили польский рынок труда. По данным исследование, трудоустроено около 69% украинцев. Благодаря притоку рабочей силы Польша смогла заработать 329 миллиардов злотых. При этом на помощь Украине страной было выделено около 40 миллиардов злотых. Просто бизнес. Ничего

Signed Shindy

14 Jun 2025, 21:36 UTC25 viewsread 12 August 2026
Forwarded from @infasokaVideo

Это нейросеть или архивные кадры? ИНФАСОТКА👁‍🗨ПОДПИСАТЬСЯ

Signed Shindy

10 Jun 2025, 14:12 UTC24 viewsread 12 August 2026
Forwarded from @saloyroniliVideo

Да-да, поголовно ✅поддержать канал ⭐️бот для связи

Signed Shindy

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

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

“Ганьба и мрiя” (@novorossialives), 10 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/novorossialives.

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.