Telegram RegisterThe public register of Telegram
Telegram profile photo for ktmhusqvarnagasgas - save

Channel

ktmhusqvarnagasgas - save

@ktmhusqvarnagasgas

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

74subscribers

+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-1003841922734
TypeChannel
Username@ktmhusqvarnagasgas
Created26 January 2026 — measured — dated from the channel’s first post
First recorded10 August 2026
Last confirmed live16 November 2026
Measurements held11
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/ktmhusqvarnagasgas

Topic

Automotive — 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 28 September 2026 and assigned it the closest of 31 fixed categories, at 55% 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

6874717 August 2026 — 68 subscribers10 August 2026 — 68 subscribers23 August 2026 — 69 subscribers31 August 2026 — 71 subscribers16 September 2026 — 72 subscribers30 September 2026 — 74 subscribers10 October 2026 — 73 subscribers23 October 2026 — 72 subscribers30 October 2026 — 73 subscribers6 November 2026 — 72 subscribers16 November 2026 — 74 subscribers7 August 202616 November 2026
11 measurements spanning 101 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 67–75 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Nov 2026, 19:3074+2
6 Nov 2026, 11:5772-1
30 Oct 2026, 03:0673+1
23 Oct 2026, 21:3772-1
10 Oct 2026, 02:5673-1
30 Sept 2026, 19:5474+2
16 Sept 2026, 00:5772+1
31 Aug 2026, 06:4871+2
23 Aug 2026, 13:2369+1
10 Aug 2026, 01:0168no change
7 Aug 2026, 16:3468first reading

Engagement

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

Recent posts

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

“ktmhusqvarnagasgas - save” (@ktmhusqvarnagasgas), 74 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/ktmhusqvarnagasgas.

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.