Telegram RegisterThe public register of Telegram
Telegram profile photo for sugarzilla updates

Channel

sugarzilla updates

@fakeidupdates

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

94subscribers

-4 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-1001884460672
TypeChannel
Username@fakeidupdates
Created15 November 2022 — measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live17 November 2026
Measurements held5
Confirmed unchanged5 times, most recently 17 November 2026
On Telegramt.me/fakeidupdates

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

9498967 August 2026 — 98 subscribers9 August 2026 — 98 subscribers22 August 2026 — 97 subscribers5 September 2026 — 96 subscribers16 October 2026 — 94 subscribers7 August 202616 October 2026
5 measurements spanning 70 days, net -4. 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 93–99 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Oct 2026, 11:5694-2
5 Sept 2026, 18:1696-1
22 Aug 2026, 06:3597-1
9 Aug 2026, 11:3198no change
7 Aug 2026, 12:5098first reading

Engagement

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

Recent posts

9 Jun 2026, 18:52 UTC49 viewsread 9 August 2026

HQ Physical Scannable IDs are back PM to buy @sugarzilla Escrow acccepted.

7 Jun 2026, 07:26 UTC58 viewsread 9 August 2026

Stimmy Plugs ( Medium to High Balance) Only dealing via escrow Can also collab on deposit as well

4 Jun 2026, 11:02 UTC69 viewsread 9 August 2026

Anyone doing screenconnect in canada or have contact. PM @sugarzilla

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

“sugarzilla updates” (@fakeidupdates), 94 subscribers as measured 16 October 2026. Telegram Register, tgregister.com/channel/fakeidupdates.

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.