Other / unclassifiable — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 59% 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
14 measurements spanning 41 days, net -271. 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 6,905–7,258 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
17 Sept 2026, 05:00
6,946
-24
13 Sept 2026, 09:01
6,970
-26
9 Sept 2026, 13:39
6,996
-15
3 Sept 2026, 20:38
7,011
-2
31 Aug 2026, 11:58
7,013
-40
28 Aug 2026, 15:47
7,053
-10
25 Aug 2026, 10:34
7,063
-9
22 Aug 2026, 06:25
7,072
-11
19 Aug 2026, 04:55
7,083
-18
16 Aug 2026, 06:54
7,101
-28
13 Aug 2026, 00:04
7,129
-52
10 Aug 2026, 10:07
7,181
-36
7 Aug 2026, 12:00
7,217
no change
7 Aug 2026, 11:48
7,217
first reading
Engagement
2 posts held, back to 17 February 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 14 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 2 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.
Showing the 2 most recent of 2 posts we hold for @backupkanall. 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.
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Named by 7 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
Handles this channel named that no longer answer
Dead references
7
handles named in this channel’s posts, vacant today
Evidenced gone
1
we ourselves saw one of these resolve, at some point
Never seen alive
6
vacant every time we have ever looked
@backupkanall named 7 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
@feedbackgateaway named in 3 posts, 8 August 2026 – 11 August 2026 · confirmed gone 20 August 2026 (two independent sightings — see how we confirm a dead handle)evidenced
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@feedbackgateoriginal named in 3 posts, 8 August 2026 – 11 August 2026
@feedbackgruppeee named in 3 posts, 8 August 2026 – 11 August 2026
@gruppe7 named in 3 posts, 8 August 2026 – 11 August 2026
@sucheundfinde0 named in 3 posts, 8 August 2026 – 11 August 2026
@werbegruppe26 named in 3 posts, 8 August 2026 – 11 August 2026
@werbungspam named in 3 posts, 8 August 2026 – 11 August 2026
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 17 September 2026 — this
entry's latest reading, not the date you are reading this.
“Feedbackgruppe Backup” (@backupkanall), 6,946 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/backupkanall.
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.
