Telegram RegisterThe public register of Telegram
Telegram profile photo for Что тут происходит?

Channel

Что тут происходит?

@belwtf

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

117subscribers

-3 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001108335080
TypeChannel
Username@belwtf
CreatedBetween 1 February 2017 and 31 October 2019 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live4 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 4 September 2026
On Telegramt.me/belwtf

Growth

117120118.56 August 2026 — 120 subscribers9 August 2026 — 120 subscribers19 August 2026 — 119 subscribers27 August 2026 — 120 subscribers4 September 2026 — 117 subscribers6 August 20264 September 2026
5 measurements spanning 29 days, net -3. 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 117–120 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Sept 2026, 03:36117-3
27 Aug 2026, 19:28120+1
19 Aug 2026, 20:44119-1
9 Aug 2026, 04:16120no change
6 Aug 2026, 12:51120first reading

Engagement

16 posts held, back to 4 November 2019the 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 16 posts for this entry, the most recent from 29 March 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
6m 04s
Average length
46s

Measured directly from 8 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

29 Mar 2026, 16:03 UTCviews —

The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 19 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

29 May 2022, 17:11 UTC804 viewsread 9 August 2026

Мэри Поппинс от мэрии Белгорода. Красиво же.

23 Jun 2020, 19:41 UTC≈2,310 viewsread 9 August 2026
Video

В Парке Победы неофициально начался фестиваль "Везёлка Live"

1 Jun 2020, 17:53 UTC≈2,070 viewsread 9 August 2026
Photo

Еще немного последствий сегодняшней непогоды от жителей Белгорода

30 Mar 2020, 18:23 UTC≈1,310 viewsread 9 August 2026
Photo

Заслуженный офтальмолог Белгорода Тамара Ивановна Кунина в качестве профилактики и лечения коронавируса настоятельно рекомендует обнимать берёзы под патриотические марши. Ну и смотреть программы юмористического характера. Пользуйтесь. Бесплатно. Без отправки смс.

13 Mar 2020, 18:06 UTC≈1,040 viewsread 9 August 2026
Photo

На Губкина только сегодня закончился Новый год

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

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

“Что тут происходит?” (@belwtf), 117 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/belwtf.

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.