Telegram RegisterThe public register of Telegram
Telegram profile photo for Test/Prod Changes

Channel

Test/Prod Changes

@testprodchanges

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

26subscribers

+14 since we began measuring on 10 September 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004398382763
TypeChannel
Username@testprodchanges
CreatedBetween 1 June 2026 and 11 September 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 September 2026
Last confirmed live4 November 2026
Measurements held8
Confirmed unchanged1 time, most recently 4 November 2026
On Telegramt.me/testprodchanges

Topic

Technology — 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 1 October 2026 and assigned it the closest of 31 fixed categories, at 90% 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

12261910 September 2026 — 12 subscribers14 September 2026 — 12 subscribers24 September 2026 — 18 subscribers6 October 2026 — 21 subscribers14 October 2026 — 22 subscribers20 October 2026 — 24 subscribers28 October 2026 — 25 subscribers4 November 2026 — 26 subscribers10 September 20264 November 2026
8 measurements spanning 54 days, net +14. 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 10–28 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Nov 2026, 06:2726+1
28 Oct 2026, 16:2125+1
20 Oct 2026, 19:4924+2
14 Oct 2026, 03:2022+1
6 Oct 2026, 14:5621+3
24 Sept 2026, 22:5818+6
14 Sept 2026, 05:2212no change
10 Sept 2026, 21:4712first reading

Engagement

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

Recent posts

14 Sept 2026, 00:05 UTC7 viewsread 14 September 2026

🔄 Изменения на тестовом сервере Обновлено: 7 файл(ов) • b-/botfather.css • b-/botfather.js • b-/bugtracker-app.css • b-/bugtracker-dark.css • b-/bugtracker.css • b-/bugtracker.js • b-/telegram.css Коммит → https://github.com/glebxdlolreal/testserverchangesall/commit/babdc4926a6752eda21b779cf765b280307f6c78

13 Sept 2026, 20:52 UTC10 viewsread 14 September 2026

🔄 Изменения на тестовом сервере Обновлено: 4 файл(ов) • i-/bugtracker-app.css • i-/bugtracker-dark.css • i-/bugtracker.css • i-/bugtracker.js Коммит → https://github.com/glebxdlolreal/testserverchangesall/commit/e41c825cdb3dc6686736cffa68ee7714f4a8fbc7

12 Sept 2026, 20:01 UTC80 viewsread 14 September 2026

🔄 Изменения на продуктовом сервере Обновлено: 4 файл(ов) • bugtracker-app.css • bugtracker-dark.css • bugtracker.css • bugtracker.js Коммит → https://github.com/glebxdlolreal/prodserverchangesall/commit/c3274d27ef721510af4277e607d64346819297c8

12 Sept 2026, 17:34 UTC17 viewsread 14 September 2026

🔄 Изменения на тестовом сервере Обновлено: 1 файл(ов) • l-/bugtracker.js Коммит → https://github.com/glebxdlolreal/testserverchangesall/commit/0c2e15b33d15444fd69f874ed7b5b25f828b269c

12 Sept 2026, 16:24 UTC15 viewsread 14 September 2026

🔄 Изменения на тестовом сервере Обновлено: 1 файл(ов) • l-/bugtracker-app.css Коммит → https://github.com/glebxdlolreal/testserverchangesall/commit/931a14011786145e718dce9faa18541328bbd895

12 Sept 2026, 16:09 UTC14 viewsread 14 September 2026

🔄 Изменения на тестовом сервере Обновлено: 4 файл(ов) • l-/bugtracker-app.css • l-/bugtracker-dark.css • l-/bugtracker.css • l-/bugtracker.js Коммит → https://github.com/glebxdlolreal/testserverchangesall/commit/6b31265166208e7e8cc354118eae1c23e10f7cc6

12 Sept 2026, 15:29 UTC20 viewsread 14 September 2026

🔄 Изменения на тестовом сервере Обновлено: 4 файл(ов) • l-/bugtracker-app.css • l-/bugtracker-dark.css • l-/bugtracker.css • l-/bugtracker.js Коммит → https://github.com/glebxdlolreal/testserverchangesall/commit/44cf4397514679596cbe6d2ebed584e5cc1373d9

12 Sept 2026, 14:50 UTC18 viewsread 14 September 2026

🔄 Изменения на тестовом сервере Обновлено: 2 файл(ов) • l-/bugtracker-app.css • l-/bugtracker.js Коммит → https://github.com/glebxdlolreal/testserverchangesall/commit/e5498ed366a23d6f980662c05b754af612895239

12 Sept 2026, 14:34 UTC13 viewsread 14 September 2026

🔄 Изменения на тестовом сервере Обновлено: 2 файл(ов) • l-/bugtracker-app.css • l-/bugtracker.css Коммит → https://github.com/glebxdlolreal/testserverchangesall/commit/354967f56ab724bc2d8902fae6a8fcae34718803

12 Sept 2026, 14:27 UTC11 viewsread 14 September 2026

🔄 Изменения на тестовом сервере Обновлено: 4 файл(ов) • l-/bugtracker-app.css • l-/bugtracker-dark.css • l-/bugtracker.css • l-/bugtracker.js Коммит → https://github.com/glebxdlolreal/testserverchangesall/commit/7fd36cfffcb8851b801e23ffb61dd84fe484efb2

12 Sept 2026, 14:11 UTC12 viewsread 14 September 2026

🔄 Изменения на тестовом сервере Обновлено: 4 файл(ов) • l-/bugtracker-app.css • l-/bugtracker-dark.css • l-/bugtracker.css • l-/bugtracker.js Коммит → https://github.com/glebxdlolreal/testserverchangesall/commit/41fa21d4309e939f14beda251d8de3d926c8bd83

12 Sept 2026, 14:03 UTC11 viewsread 14 September 2026

🔄 Изменения на тестовом сервере Обновлено: 4 файл(ов) • l-/bugtracker-app.css • l-/bugtracker-dark.css • l-/bugtracker.css • l-/bugtracker.js Коммит → https://github.com/glebxdlolreal/testserverchangesall/commit/dd4b9699bdba78ba5e9240d891c4277fbcc0c075

Showing the 12 most recent of 20 posts we hold for @testprodchanges. 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“Test/Prod Changes” (@testprodchanges), 26 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/testprodchanges.

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.