Telegram RegisterThe public register of Telegram

Channel

OctoDiary Nightly

@OctoDiary_Nightly

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

12subscribers

+0 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1002090530970
TypeChannel
Username@OctoDiary_Nightly
DescriptionТестовые сборки Android-приложения @OctoDiary
Created19 May 2024measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live12 August 2026
Measurements held2
On Telegramt.me/OctoDiary_Nightly

Growth

1210 August 2026 — 12 subscribers12 August 2026 — 12 subscribers10 August 202612 August 2026
2 measurements spanning 2 days. 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 11–13 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 04:1612no change
10 Aug 2026, 08:1612first reading

Engagement

19 posts held, back to 19 May 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 19 posts for this entry, the most recent from 13 May 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
17

Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

3 reactions across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍3100.0%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 2 of the 19 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 3reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 19 May 2024 to 13 May 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

13 May 2026, 17:00 UTC17 viewsread 12 August 2026
File

v2-develop / 70e3d89 -> 3e5e2ac • исправлен размер webview материалов библиотеки МЭШ

12 May 2026, 17:03 UTC19 viewsread 12 August 2026
File

v2-develop / a92038b -> 70e3d89 • исправлена работа моей школы

9 May 2026, 20:45 UTC25 viewsread 12 August 2026
File

v2-develop / a92038b • исправлены проблемы календаря на английском языке устройства (#58 от Morkovka21Vek)

24 Oct 2025, 16:05 UTC81 viewsread 12 August 2026
File

v2-develop / b8fe7287 - исправлены посещения и баланс питания (для мэш) В сторах как 2.1.8

24 Oct 2025, 12:04 UTC79 viewsread 12 August 2026
File

v2-develop / defbc51 - исправлен назойливый ченджлог на главном экране - исправлено открытие прикрепленных файлов на пути в сторы

24 Feb 2025, 18:21 UTC138 viewsread 12 August 2026
File

v2-develop / c0c3ee5 - исправлен запуск материалов библиотеки мэш (цдз) upd: в сторах как 2.1.2

24 Feb 2025, 17:54 UTC112 viewsread 12 August 2026
File

v2-develop / c895c46 к сожалению, мэш активно меняет апи, что негативно сказывается на работе приложения. будем искать новые варианты получения этих данных, но пока просто фикс. - отключен список класса (рейтинг работает) - отключен раздел "Документы"

28 Nov 2024, 20:20 UTC138 views3 reactionsread 12 August 2026
File

v2-develop / 513b90c - смена домена внешнего апи - исправление проблемы с присваиванием рейтинга

👍3

1 Sept 2024, 12:56 UTC170 viewsread 12 August 2026
File

v2-develop / 39ed820 Релизная версия 2.1.0 - раздел "кошелёк" - исправления

31 Aug 2024, 19:28 UTC151 viewsread 12 August 2026
File

v2-develop / 09107f4 Релиз кандидат - еда - документы - экзамены - стабилизация загрузки при рефреше

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

Citation-graph rank

Citation-graph rank — 162,519 of 1,480,688entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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.

Names

Channels on the register whose handles appear in this channel's posts.

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

“OctoDiary Nightly” (@OctoDiary_Nightly), 12 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/OctoDiary_Nightly.

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.