Heisenberg's Store pinned «Heisenberg & FPays2 Fullz List REPLACEMENTS IF DEAD Spammed via DVLA & TV License Campaign @FuIIzHavenSales 08/08/2026 557483 - First Direct x6 465945 - HSBC 465944 - HSBC 465943 - HSBC x12 465942 - HSBC x15 459681 - HSBC 492942 - Barclays Platinum Credit…»

Channel
Heisenberg's Store
@XTlsF_VCyq84Zjg0f
On this record: Topic · Growth · Engagement · Posts · Cite this entry
4,419subscribers
+1,403 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 | -1001601061793 |
|---|---|
| Type | Channel |
| Username | @XTlsF_VCyq84Zjg0f |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/XTlsF_VCyq84Zjg0f |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Sept 2026, 23:20 | 4,419 | +385 |
| 11 Sept 2026, 09:59 | 4,034 | +189 |
| 6 Sept 2026, 08:17 | 3,845 | -55 |
| 1 Sept 2026, 19:45 | 3,900 | +138 |
| 30 Aug 2026, 02:22 | 3,762 | -56 |
| 27 Aug 2026, 10:55 | 3,818 | -37 |
| 24 Aug 2026, 18:16 | 3,855 | +629 |
| 20 Aug 2026, 16:38 | 3,226 | -35 |
| 17 Aug 2026, 10:17 | 3,261 | -69 |
| 13 Aug 2026, 10:05 | 3,330 | -30 |
| 10 Aug 2026, 10:46 | 3,360 | +346 |
| 7 Aug 2026, 20:52 | 3,014 | -2 |
| 7 Aug 2026, 12:18 | 3,016 | no change |
| 7 Aug 2026, 12:08 | 3,016 | first reading |
Engagement
31 posts held, back to 11 August 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 2 pages 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 31 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Photo, posted without a caption
Bin skipped straight g thanks
Photo, posted without a caption
3/3 live
Photo, posted without a caption
15/15 Added
Gara 👌🏼
5/5 All Livee
40/40
Photo, posted without a caption
7/7 All LIVE
Showing the 12 most recent of 31 posts we hold for @XTlsF_VCyq84Zjg0f. 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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“Heisenberg's Store” (@XTlsF_VCyq84Zjg0f), 4,419 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/XTlsF_VCyq84Zjg0f.
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.