Telegram RegisterThe public register of Telegram
Telegram profile photo for Дневники Нолы

Channel

Дневники Нолы

@nolasdiary

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

102subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002851837638
TypeChannel
Username@nolasdiary
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live2 October 2026
Measurements held6
Confirmed unchanged1 time, most recently 2 October 2026
On Telegramt.me/nolasdiary

Topic

Personal blog — 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 27 September 2026 and assigned it the closest of 31 fixed categories, at 52% 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

101104102.57 August 2026 — 102 subscribers9 August 2026 — 102 subscribers24 August 2026 — 101 subscribers9 September 2026 — 103 subscribers17 September 2026 — 104 subscribers2 October 2026 — 102 subscribers1027 August 20262 October 2026
6 measurements spanning 56 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 101–104 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Oct 2026, 14:57102-2
17 Sept 2026, 04:55104+1
9 Sept 2026, 17:15103+2
24 Aug 2026, 14:17101-1
9 Aug 2026, 10:02102no change
7 Aug 2026, 19:32102first reading

Engagement

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

What this channel posts

Video runtime
21s
Average length
5s

Measured directly from 4 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

156 reactions across 5 posts, in 8 distinct kinds. The most used accounts for 31.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤4931.4%
custom 54157254913341689042616.7%
custom 53121387141749989932113.5%
💔1610.3%
🔥148.97%
custom 5188308218551475917127.69%
custom 534609887455558111295.77%
custom 537328416211340934595.77%

Custom emoji. 5 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

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 5 of the 5 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 156 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 5 most recent posts we hold, published 24 July 2026 to 8 August 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

8 Aug 2026, 14:32 UTC39 views27 reactionsread 9 August 2026
Photo

У Нолочки есть собственный пляжный зонтик и она каждый день кайфует на пляжах! Обязательно потом расскажем где были, на что смотрели и чем занимались, а пока держите рандомные кусочки, у отпускной собачки все отлично 🏝

❤13custom 51883082185514759177custom 53121387141749989936🔥1

3 Aug 2026, 15:31 UTC80 views35 reactionsread 9 August 2026
Photo

Ближайшее время будет только красивое отпускное 🏖 Сегодня были на диком пляже недалеко от Коприно, разблокировали навык катания на сапе - как родной, в общем-то, сели и поехали (всего однажды навернулись). Но оказалось, что и мы сами не особо любители сапа)) Попробовали и здорово) Локация пляжа просто вау - очень чисто и красиво, народу мало, выход с пляжа - небольшой подъем в сосновый лес, выглядит сказочно💕и с пог…

❤16🔥13custom 53121387141749989936

2 Aug 2026, 17:54 UTC66 views42 reactionsread 9 August 2026
Video

Собачка уже окончательно поправилась и передает всем радостные приветы с красивой Волги 🩵

custom 541572549133416890420custom 53121387141749989939custom 53732841621134093459❤4

29 Jul 2026, 07:34 UTC115 views25 reactionsread 9 August 2026
Photo

Месяц у нас выдался активный на тему здоровья ❤️‍🩹 На этот раз приболели - Нолка стала очень грустная и вялая, отказ от еды и высокая температура. Думаем на грязную воду в водоеме, в котором искупалась накануне - случайно заглотила там воды и, возможно, как раз подхватила какую-то инфекцию( Сейчас все уже в порядке, состояние почти вернулось к норме. Анализы неплохие, но антибиотики и сопутствующие таблеточки назнач…

💔16custom 53460988745555811129

24 Jul 2026, 09:15 UTC110 views27 reactionsread 9 August 2026
Photo

Такая жизнь ежедневная - ни о чем и обо всем 💚

❤16custom 54157254913341689046custom 51883082185514759175

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

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

“Дневники Нолы” (@nolasdiary), 102 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/nolasdiary.

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.