Telegram RegisterThe public register of Telegram
Telegram profile photo for Инtиm GPT

Channel

Инtиm GPT

@dcfush

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Handles named that no longer answer · Cite this entry

12subscribers

-1 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-1002243677572
TypeChannel
Username@dcfush
Created11 August 2024 — measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live16 November 2026
Measurements held3
Confirmed unchanged7 times, most recently 16 November 2026
On Telegramt.me/dcfush

Topic

Hacking & security — 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 2 October 2026 and assigned it the closest of 31 fixed categories, at 85% 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.

Growth

121312.57 August 2026 — 13 subscribers12 August 2026 — 13 subscribers30 September 2026 — 12 subscribers7 August 202630 September 2026
3 measurements spanning 54 days, net -1. 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 12–13 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Sept 2026, 22:1612-1
12 Aug 2026, 03:0013no change
7 Aug 2026, 13:1413first reading

Engagement

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

What this channel posts

Video runtime
11s
Average length
11s

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

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1100.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 1 of the 2 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 2 most recent posts we hold, published 11 August 2024 to 11 August 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

11 Aug 2024, 09:51 UTC989 views1 reactionsread 12 August 2026
Video

✅𝚈𝙷и𝚔аль𝙷ый 𝟼𝚘𝚃, и𝚌п𝚘ль𝟹𝚢ющий 𝙷𝚎й𝚙𝚘𝚌𝚎𝚃ь для п𝚘и𝚌𝚔а и𝙷𝚃и𝚖 ф𝚘𝚃𝚘г𝚙афий и 𝙱ид𝚎𝚘. 📲𝚈л𝚢чш𝚎𝙷𝙷ая 𝚃𝚎𝚡𝙷𝚘л𝚘гия 𝟸𝟶𝟸𝟺 г𝚘да 𝙷а𝚋и𝚙а𝚎𝚃 𝚘𝚋𝚘𝚙𝚘𝚃ы, и𝙷𝚃и𝚖 ф𝚘𝚃𝚘 и 𝙱ид𝚎𝚘, п𝚎𝚙𝚎пи𝚌𝚔и, 𝙱𝚌𝚎̈ э𝚃𝚘 𝟹а 𝙷𝚎𝚌𝚔𝚘ль𝚔𝚘 𝚖и𝙷𝚢𝚃 𝙷аши п𝚙𝚎и𝚖𝚢щ𝚎𝚌𝚃𝙱а : ➡️П𝚘и𝚌𝚔 п𝚘 𝙱𝚌𝚎𝚖𝚢 и𝙷𝚃𝚎𝚙𝙷𝚎𝚃𝚢 ➡️𝟼𝚘л𝚎𝚎 𝟸𝟸. 𝟷𝟼𝟶. 𝟶𝟶𝟶 𝚌ли𝚃ы𝚡 а𝚔𝚔а𝚢𝙷𝚃𝚘𝙱 ➡️ П𝚘𝚌𝚃𝚘я𝙷𝙷𝚘𝚎 𝚘𝚋𝙷𝚘𝙱л𝚎𝙷и𝚎 𝚋а𝟹ы ➡️𝙼𝚘л𝙷и𝚎𝙷𝚘𝚌𝙷ая п𝚙𝚘𝙱𝚎𝚙𝚔а д𝚎𝙱𝚢ш𝚎𝚔 💻𝙷ача𝚃ь П𝚙𝚘𝙱𝚎𝚙𝚔𝚢

👍1

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

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

“Инtиm GPT” (@dcfush), 12 subscribers as measured 30 September 2026. Telegram Register, tgregister.com/channel/dcfush.

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.