Telegram RegisterThe public register of Telegram
Telegram profile photo for Computing Forever Official

Channel

Computing Forever Official

@ComputingForeverOfficial

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

4,738subscribers

-108 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001250192398
TypeChannel
Username@ComputingForeverOfficial
Created10 May 2021 — measured — dated from the channel’s first post
First recorded6 August 2026
Last confirmed live26 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 26 September 2026
On Telegramt.me/ComputingForeverOfficial

Topic

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

4,7384,8464,7926 August 2026 — 4,846 subscribers6 August 2026 — 4,846 subscribers9 August 2026 — 4,841 subscribers12 August 2026 — 4,831 subscribers15 August 2026 — 4,827 subscribers18 August 2026 — 4,821 subscribers21 August 2026 — 4,813 subscribers24 August 2026 — 4,803 subscribers28 August 2026 — 4,796 subscribers31 August 2026 — 4,789 subscribers2 September 2026 — 4,783 subscribers7 September 2026 — 4,775 subscribers12 September 2026 — 4,769 subscribers15 September 2026 — 4,758 subscribers26 September 2026 — 4,738 subscribers6 August 202626 September 2026
15 measurements spanning 51 days, net -108. 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 4,722–4,862 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
26 Sept 2026, 03:204,738-20
15 Sept 2026, 16:394,758-11
12 Sept 2026, 00:194,769-6
7 Sept 2026, 19:024,775-8
2 Sept 2026, 19:184,783-6
31 Aug 2026, 03:424,789-7
28 Aug 2026, 05:094,796-7
24 Aug 2026, 20:354,803-10
21 Aug 2026, 14:384,813-8
18 Aug 2026, 11:074,821-6
15 Aug 2026, 15:234,827-4
12 Aug 2026, 11:244,831-10
9 Aug 2026, 05:214,841-5
6 Aug 2026, 10:344,846no change
6 Aug 2026, 09:514,846first reading

Engagement

2 posts held, back to 10 May 2021 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 8 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 May 2021. An engagement rate over an empty window would be a number about nothing.

Recent posts

Showing the 2 most recent of 2 posts we hold for @ComputingForeverOfficial. 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

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.

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 26 September 2026 — this entry's latest reading, not the date you are reading this.

“Computing Forever Official” (@ComputingForeverOfficial), 4,738 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/ComputingForeverOfficial.

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.