Узел восстановлен, наблюдаем за его работой.
Channel
Shinomiya_Status
@shinomiya_status
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
325subscribers
+39 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003495722888 |
|---|---|
| Type | Channel |
| Username | @shinomiya_status |
| Created | Between 1 November 2025 and 30 April 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 7 October 2026 |
| On Telegram | t.me/shinomiya_status |
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 22 September 2026 and assigned it the closest of 31 fixed categories, at 86% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Oct 2026, 21:16 | 325 | +21 |
| 26 Sept 2026, 10:58 | 304 | +4 |
| 13 Sept 2026, 04:15 | 300 | +7 |
| 4 Sept 2026, 22:17 | 293 | +2 |
| 27 Aug 2026, 19:47 | 291 | +2 |
| 20 Aug 2026, 12:08 | 289 | +3 |
| 12 Aug 2026, 11:54 | 286 | no change |
| 12 Aug 2026, 07:31 | 286 | first reading |
Engagement
20 posts held, back to 2 June 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 11 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Фиксируем недоступность узла Epyc-9454p-1, проверяем информацию.
Работы успешно завершены.
Уважаемые клиенты, в ближайшее время будут проведены технические работы в боте, во время работ бот будет недоступен, все сервера продолжат свою работу без изменений. О завершении работ - уведомим.
Подключение восстановлено. Наблюдаем дальнейшую работу роутера.
Уважаемые клиенты, через 2 минуты будет произведен перезапуск роутера в локации Финляндии, подключение восстановится в течение 5 минут после начала перезагрузки. Приносим извинения за доставленные неудобства.
Проблемы вызывающая задержки подключения к серверам в Финляндии, устранена.
Фиксируем многочисленные жалобы с подключением к серверам в Финляндии, оповестили вышестоящего провайдера, ждем ответа от него. Приносим извинения за доставленные неудобства.
Уважаемые клиенты, Сообщаем, что в 20:00 utc+3 будут проведены технические работы, во время технических работ будет кратковременный простой сервера, пожалуйста завершите все работы на серверах ко времени проведения работ, необходима перезагрузка сервера. Пользовательские данные будут сохранены и не пострадают. О завершении работ уведомим дополнительно.
Подключение восстановлено.
Проблемы у вышестоящего провайдера в локации Финляндии, ждем ответа от ДЦ.
Уважаемые клиенты, Сообщаем, что в ближайшее время в локации Германии возможны кратковременные перебои в работе сервисов, а также временные ограничения пропускной способности интернет-канала в связи с проведением плановых работ по переключению сетевого порта. Данные работы выполняются в рамках масштабирования и модернизации сетевой инфраструктуры с целью повышения стабильности, производительности и дальнейшего разв…
Showing the 12 most recent of 20 posts we hold for @shinomiya_status. 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 7 October 2026 — this entry's latest reading, not the date you are reading this.
“Shinomiya_Status” (@shinomiya_status), 325 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/shinomiya_status.
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.