Telegram RegisterThe public register of Telegram
Telegram profile photo for fadikHub

Channel

fadikHub

@fadikHub

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry

102subscribers

-8 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1003945075927
TypeChannel
Username@fadikHub
Created11 June 2026 — measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live8 November 2026
Measurements held12
Confirmed unchanged1 time, most recently 8 November 2026
On Telegramt.me/fadikHub

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 26 September 2026 and assigned it the closest of 31 fixed categories, at 88% 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 the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@fadikHub/11 · this entry15 Jun 2026, 17:08 UTC@fadikWorld/1011 Jul 2026, 12:46 UTC1.0026 days
@fadikHub/19 · this entry18 Jun 2026, 22:21 UTC@fadikWorld/1711 Jul 2026, 12:46 UTC1.0023 days
@fadikHub/20 · this entry24 Jun 2026, 11:23 UTC@fadikWorld/1811 Jul 2026, 12:46 UTC1.0017 days
@fadikHub/21 · this entry28 Jun 2026, 22:24 UTC@fadikWorld/1911 Jul 2026, 12:46 UTC1.0013 days
@fadikHub/22 · this entry10 Jul 2026, 09:17 UTC@fadikWorld/2011 Jul 2026, 12:46 UTC1.0027 hours
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@fadikWorld5 (5/5 hand-verifiable sample passed)1.0017 daysthis entry (5–0)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 8 comparable posts for this entry, running 12 June 2026 to 11 July 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 2 channels, the one whose matching posts we hold earliest is @fadikHub — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

1021101069 August 2026 — 110 subscribers10 August 2026 — 110 subscribers17 August 2026 — 109 subscribers25 August 2026 — 107 subscribers2 September 2026 — 108 subscribers11 September 2026 — 107 subscribers29 September 2026 — 108 subscribers9 October 2026 — 107 subscribers16 October 2026 — 106 subscribers24 October 2026 — 104 subscribers31 October 2026 — 103 subscribers8 November 2026 — 102 subscribers9 August 20268 November 2026
12 measurements spanning 91 days, net -8. 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 101–111 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Nov 2026, 17:10102-1
31 Oct 2026, 15:46103-1
24 Oct 2026, 09:48104-2
16 Oct 2026, 09:26106-1
9 Oct 2026, 13:18107-1
29 Sept 2026, 17:01108+1
11 Sept 2026, 10:39107-1
2 Sept 2026, 08:43108+1
25 Aug 2026, 17:23107-2
17 Aug 2026, 19:04109-1
10 Aug 2026, 07:06110no change
9 Aug 2026, 20:45110first reading

Engagement

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

What this channel posts

Video runtime
20s
Average length
20s

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

47 reactions across 9 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤47100.0%

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 9 of the 20 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 47 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 11 June 2026 to 11 July 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.

Telegram Stars

Stars received
3
across the posts below
Posts paid on
3
of 19 we hold a reading for · 16%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @fadikHub. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 20 most recent posts we hold for this entry, published 11 June 2026 to 11 July 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

11 Jul 2026, 12:58 UTC116 views2 reactions1 Starread 9 August 2026

Некоторые каналы изменены в связи с безопасностью. Понимаю ваше неудобство, это будет последний перенос. Данный канал больше неактивен. 🌟 Всего будет перенесено 3 канала: @fadikstart @fadikhub @fadikVPNOfficial ✅ Новые каналы @fadikPoint @fadikWorld @fadikOfficialVpn Просьба всех подписаться на новые каналы и по желанию отписаться от старых.

❤2

10 Jul 2026, 09:17 UTC146 views4 reactions1 Starread 9 August 2026

Для безопасности с каналами, аккаунт был перенесен на другой юзернейм — @fadikOwner✅ Большая просьба писать в этот аккаунт, прошлый уже недействительный. ✅ Все каналы, боты работают как раньше.

❤4

28 Jun 2026, 22:24 UTC202 views10 reactions1 Starread 9 August 2026

⚔️ Какие изменения на этой недели произойдут в fadikHub 1. 30 июня проведется итог розыгрыша среди учащихся курсов 2. 30 июня повысится цена на курс Python для хакеров 3. Официальный Road-map по курсу Python для хакеров 4. Месячный отчет по пользователям в fadikVPN 5. Информация о выходе бесплатных курсов по смежным темам хакинга 6. Улучшение всего проекта в качестве контента и взаимодействия с пользователями Друго…

❤10

24 Jun 2026, 11:23 UTC226 views6 reactionsread 9 August 2026

🚩Совместно с BoCoder_Work и fadikofficial был создан канал и сообщество для всех, кто интересуется CTF и кибербезопасностью. 📣Канал про CTF: @DailyCTF_News Здесь публикуются: 🔸Новости из мира CTF и ИБ; 🔸Анонсы соревнований; 🔸Полезные инструменты и ресурсы; 🔸Гайды и writeup'ы; 🔸Материалы для обучения и практики. ⚔️ Закрытое сообщество: https://t.me/+sQe0pGRw9KdlNGI6 Вступление бесплатное! Внутри - общение по т…

❤6

18 Jun 2026, 22:21 UTC230 views11 reactionsread 9 August 2026

✅ Ребрендинг проекта fadik был успешно завершен. 1. Новые каналы 2. Изменённые сайты 3. Новые сообщества 4. Новые боты Спасибо что вы рядом ❤️ Только начало.

❤11

18 Jun 2026, 13:50 UTC210 views5 reactionsread 9 August 2026

В Новости — Этический Хакинг (CyberSecurity) стартовал розыгрыш.

❤5

17 Jun 2026, 23:00 UTC216 views5 reactionsread 9 August 2026

В fadikHacking стартовал дроп материалов

❤5

15 Jun 2026, 17:08 UTC197 viewsread 9 August 2026

🃏 Глобальное обновление сайта — https://fadik.netlify.app ⚡ Создан новый сайт VPN — https://fadikvpn.netlify.app

15 Jun 2026, 17:08 UTC134 viewsread 9 August 2026

💬 Актуальные на данный момент планы у проекта 1️⃣ Курс по Python для хакеров (Ссылка на курс) 2️⃣Большая экосистема в телеграмм боте, в котором будут множества функций, возможностей и навигаций в другие проекты 3️⃣ Глобальное обновление личного бота для большей удобности и комфорта (Ссылка на vpn) 4️⃣ Сайт по VPN 5️⃣ Личные закрытые практические консультации по хакингу

15 Jun 2026, 17:08 UTC140 viewsread 9 August 2026

В FadikVPN запустилась акция которая позволяет купить VPN на 40% дешевле Подробнее в данном посте

15 Jun 2026, 17:08 UTC144 viewsread 9 August 2026

Интересный факт: Суммарное количество подписчиков всех тгк экосистемы fadik более 2169

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Mentions

Named by 5 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.

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

“fadikHub” (@fadikHub), 102 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/fadikHub.

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.