Telegram RegisterThe public register of Telegram
Telegram profile photo for atmswipegang

Channel

atmswipegang

@atmswipegang

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

222subscribers

-6 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-1002308361046
TypeChannel
Username@atmswipegang
Created26 February 2025 — measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live3 November 2026
Measurements held10
Confirmed unchanged1 time, most recently 3 November 2026
On Telegramt.me/atmswipegang

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 23 September 2026 and assigned it the closest of 31 fixed categories, at 84% 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

2222402317 August 2026 — 228 subscribers7 August 2026 — 228 subscribers8 August 2026 — 232 subscribers28 August 2026 — 230 subscribers13 September 2026 — 233 subscribers25 September 2026 — 240 subscribers14 October 2026 — 234 subscribers21 October 2026 — 227 subscribers27 October 2026 — 226 subscribers3 November 2026 — 222 subscribers7 August 20263 November 2026
10 measurements spanning 89 days, net -6. 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 219–243 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Nov 2026, 23:31222-4
27 Oct 2026, 20:30226-1
21 Oct 2026, 17:49227-7
14 Oct 2026, 05:17234-6
25 Sept 2026, 05:36240+7
13 Sept 2026, 01:57233+3
28 Aug 2026, 02:28230-2
8 Aug 2026, 07:25232+4
7 Aug 2026, 08:17228no change
7 Aug 2026, 08:04228first reading

Engagement

2 posts held, back to 26 February 2025 — 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 26 February 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

26 Feb 2025, 15:47 UTC≈1,070 viewsread 7 August 2026

❗️ Тёмный Архив переехал на новый адрес: https://t.me/+IMm3oeI1Zr84MTQ1 Подпишись, чтобы быть в курсе новых схем и мануалов!

Showing the 2 most recent of 2 posts we hold for @atmswipegang. 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 3 November 2026 — this entry's latest reading, not the date you are reading this.

“atmswipegang” (@atmswipegang), 222 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/atmswipegang.

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.