Telegram RegisterThe public register of Telegram
Telegram profile photo for Beregini

Channel

Beregini

@hackberegini

Has discussion group

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

85,582subscribers

+334 since we began measuring on 5 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001185457530
TypeChannel
Username@hackberegini
Created25 February 2020measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded10 August 2026
Last confirmed live21 August 2026
Measurements held17
Confirmed unchanged1 time, most recently 21 August 2026
On Telegramt.me/hackberegini

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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

85,23985,67285,455.55 August 2026 — 85,248 subscribers6 August 2026 — 85,239 subscribers7 August 2026 — 85,510 subscribers8 August 2026 — 85,589 subscribers9 August 2026 — 85,611 subscribers10 August 2026 — 85,637 subscribers10 August 2026 — 85,637 subscribers11 August 2026 — 85,636 subscribers12 August 2026 — 85,629 subscribers13 August 2026 — 85,620 subscribers14 August 2026 — 85,594 subscribers16 August 2026 — 85,672 subscribers17 August 2026 — 85,654 subscribers18 August 2026 — 85,638 subscribers19 August 2026 — 85,617 subscribers20 August 2026 — 85,598 subscribers21 August 2026 — 85,582 subscribers85,5825 August 202621 August 2026
17 measurements spanning 15 days, net +334. 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 85,174–85,737 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
21 Aug 2026, 09:1785,582-16
20 Aug 2026, 09:3485,598-19
19 Aug 2026, 11:1685,617-21
18 Aug 2026, 13:0485,638-16
17 Aug 2026, 13:5385,654-18
16 Aug 2026, 05:5885,672+78
14 Aug 2026, 19:1685,594-26
13 Aug 2026, 09:1585,620-9
12 Aug 2026, 09:2385,629-7
11 Aug 2026, 07:4285,636-1
10 Aug 2026, 19:4985,637no change
10 Aug 2026, 09:2385,637+26
9 Aug 2026, 11:0885,611+22
8 Aug 2026, 08:1185,589+79
7 Aug 2026, 11:4485,510+271
6 Aug 2026, 10:3185,239-9
5 Aug 2026, 22:1085,248first reading

Engagement

No public post preview. We read this entry on 11 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

Citation-graph rank

Citation-graph rank — 6,877 of 1,583,249entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

OMON Moscow
@omonmoscow · 9,437
7 posts
ЧВК Медиа
@chvkmedia · 25,408
5 posts
Бросок мангуста
@brosok_mangusta_Z · 4,660
4 posts
Мы за ОМОН
@za_OMON · 126
4 posts
КИБЕР ЧАТ
@KC_RF · 11
3 posts
Inside 🅉 Donetsk
@Doninside · 24,713
2 posts
InsaiderUA
@insaiderUA · 13
2 posts
Pravda_VZ
@pravda_vz · 14
2 posts
СИЛОВИКИ 🇷🇺
@SIL0VIKI · 184,670
2 posts
Вспомнить о войне
@Vspomni_o_Voine_neraz · 6,843
2 posts
Анти-оранж Z
@Antioranje · 29
1 post
ANTISEPTIC
@antiseptic_channel · 9,447
1 post
Свидетели Байрактара
@bayraktar1070 · 82,936
1 post
Каналы Telegram®
@channelstock · 138
1 post
Диванный спецнаZ
@divannyi_special · 5,873
1 post
Днепровский Рубеж
@Dnepro_Rub · 15,375
1 post
Дмитрий Конаныхин 🇷🇺
@grishkafilippov · 35,977
1 post
Енот из Херсона 🦝
@HersonEnot · 40,865
1 post
Картофельные войны
@KartofelnyeVojny · 26
1 post
Юрий Кот - Быть добру!
@koturi · 9,891
1 post
Андрей Медведев
@MedvedevVesti · 184,572
1 post
На окраине 404🇷🇺
@naokraine404 · 9,329
1 post
НемеZида
@nemeZ1da_ru · 46,562
1 post
Украина без вариантов/Україна без варіантів
@NewNovorossia · 53,114
1 post
РАБОТАЕМ БРАТЬЯ 🇷🇺
@news_z_v · 40
1 post
ОБЛИЧИТЕЛЬ_Z_
@Oblichitel · 34
1 post
Одесса. Реалии🇺🇦
@odessa_realii · 47
1 post
Оперативные сводки
@opersvodki · 408,938
1 post
Поисковый отряд "Ориентир"
@orientir74 · 188
1 post
Одетые в броню
@ovbron · 3,689
1 post
ПолитНавигатор. Новости и аналитика
@Politnavigator · 88,230
1 post
Русский инженер
@rusengineer · 124,278
1 post
Крылатые
@russian_airborne · 50,109
1 post
СВОБОДНОЕ ДЫХАНИЕ -- ☢ЯДрёна WatchЬ‼️
@shingarkin · 23,575
1 post
Для души и глаз
@Skaji_Mnenie · 3
1 post
В интернете сказали
@skazineta · 1,167
1 post
Утро Дагестан
@utro_dagesstan · 1
1 post
Вечный ZOV России 🇷🇺
@vechnyizov22 · 3,404
1 post
Владимир Орлов
@Vladimir_Orlov1977 · 5,751
1 post
ВОВА ИЗ ОБКОМА
@vovaizobkoma · 239
1 post
Заметки Александра Доронина "В знании - сила" или "Бизнес-разведка 3.0 + OSINT и AI".
@vzs071 · 866
1 post
WE ARE KILLNET
@WeAreKillnet_Channel · 11,451
1 post
ZGRP в эфире
@ZGRPonAIR · 248
1 post
ЖИВОВЪ | НОВОСТИ И МНЕНИЯ
@zhivoff22 · 16,204
1 post

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 81 registered channels — 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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

“Beregini” (@hackberegini), 85,582 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/hackberegini.

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.