Telegram RegisterThe public register of Telegram
Telegram profile photo for Hacker4ik

Channel

Hacker4ik

@Haker4ik

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

7,235subscribers

-182 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001314731882
TypeChannel
Username@Haker4ik
Created16 January 2020measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live24 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 24 August 2026
On Telegramt.me/Haker4ik

Growth

7,2357,4177,3267 August 2026 — 7,417 subscribers7 August 2026 — 7,413 subscribers10 August 2026 — 7,391 subscribers13 August 2026 — 7,343 subscribers17 August 2026 — 7,296 subscribers20 August 2026 — 7,261 subscribers24 August 2026 — 7,235 subscribers7 August 202624 August 2026
7 measurements spanning 17 days, net -182. 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 7,208–7,444 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 03:477,235-26
20 Aug 2026, 05:157,261-35
17 Aug 2026, 10:167,296-47
13 Aug 2026, 10:257,343-48
10 Aug 2026, 00:317,391-22
7 Aug 2026, 07:007,413-4
7 Aug 2026, 00:017,417first reading

Engagement

2 posts held, back to 16 January 2020the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 14 pagesof 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 2 posts for this entry, the most recent from 16 January 2020. An engagement rate over an empty window would be a number about nothing.

Recent posts

16 Jan 2020, 15:44 UTC≈466,000 viewsread 20 August 2026

❗️Diqqat: Buyurtmaga mukammal Telegram botlar va Web saytlar yasab beraman (qimor va stavkalardan tashqari) ⤵️ Iltimos boshqa maqsadda bezovta qilmang. ❗️Внимание: Сделаю Телеграм боты и Сайты под заказ (кроме азартных игр и ставок)⤵️ Пожалуйста, не беспокойте ни с какой другой целью. 🪩Сайт: Hacker4ik.uz 🤖Боты: @Bots_of_TG ✈️Лич: @iSal1mov

Showing the 2 most recent of 2 posts we hold for @Haker4ik. 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.

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

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

“Hacker4ik” (@Haker4ik), 7,235 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/Haker4ik.

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.