Telegram RegisterThe public register of Telegram
Telegram profile photo for @pluginsc

Channel

@pluginsc

@pluginsc

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

3subscribers

-1 since we began measuring on 2 September 2026

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

Register entry

Telegram ID-1003980300170
TypeChannel
Username@pluginsc
Created29 August 2026 — measured — dated from the channel’s first post
First recorded2 September 2026
Last confirmed live24 October 2026
Measurements held6
Confirmed unchanged1 time, most recently 24 October 2026
On Telegramt.me/pluginsc

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 94% 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

23518.52 September 2026 — 4 subscribers3 September 2026 — 6 subscribers11 September 2026 — 13 subscribers1 October 2026 — 35 subscribers10 October 2026 — 2 subscribers24 October 2026 — 3 subscribers32 September 202624 October 2026
6 measurements spanning 52 days, net -1. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Oct 2026, 06:593+1
10 Oct 2026, 21:172-33
1 Oct 2026, 08:2135+22
11 Sept 2026, 21:0213+7
3 Sept 2026, 21:386+2
2 Sept 2026, 16:464first reading

Engagement

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

Recent posts

30 Aug 2026, 18:44 UTC54 views0 reactionsread 2 September 2026
Photo

Draft Guard – Автоматически сохраняет историю черновиков (лимит выставляется в настройках). Для вставки или очистки зажмите пустое поле ввода в чате (рекомендуются использовать с клавиатурой, которая поддерживает буфер обмена, например, Яндекс клавиатура, т. к. плагин фактически отключает возможность вставки текста через долгое нажатие)

30 Aug 2026, 12:12 UTC53 viewsread 2 September 2026

UDP: обновлён до версии 1.1.1: 1) Добавлено скрытие кнопки при поиске и в недавних чатах 2) Исправление лагов на слабых устройствах

30 Aug 2026, 06:46 UTC41 viewsread 2 September 2026
Photo

Cell Dumper (для разработчиков плагинов) – дамп полей DialogCell в текстовый файл "dialog_cell_fields.txt" в загрузках android

29 Aug 2026, 23:45 UTC33 viewsread 2 September 2026
Photo

Hide Bot Open Button – Скрывает кнопку "Открыть" (Mini Apps) у ботов и при поиске

29 Aug 2026, 22:32 UTC35 viewsread 2 September 2026

Навигация / Navigation ————— –———————————— 1. Hide Bot Open Button – Скрывает кнопку "Открыть" (Mini Apps) у ботов в списке чатов и при поиске 2. Cell Dumper (для разработчиков плагинов) – дамп полей DialogCell в текстовый файл "dialog_cell_fields.txt" в загрузках android 3. Draft Guard – Автоматически сохраняет историю черновиков (лимит выставляется в настройках). Для вставки или очистки зажмите пустое поле ввода …

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

Mentions

Named by 1 registered channel — 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.

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

“@pluginsc” (@pluginsc), 3 subscribers as measured 24 October 2026. Telegram Register, tgregister.com/channel/pluginsc.

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.