Telegram RegisterThe public register of Telegram
Telegram profile photo for Записки низших лиг

Channel

Записки низших лиг

@zapiski_fnl2

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

688subscribers

+21 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-1001980687021
TypeChannel
Username@zapiski_fnl2
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live19 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/zapiski_fnl2

Topic

Sports — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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

667688677.57 August 2026 — 667 subscribers8 August 2026 — 667 subscribers16 August 2026 — 675 subscribers24 August 2026 — 678 subscribers31 August 2026 — 682 subscribers10 September 2026 — 681 subscribers19 September 2026 — 688 subscribers7 August 202619 September 2026
7 measurements spanning 43 days, net +21. 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 664–691 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 06:37688+7
10 Sept 2026, 08:39681-1
31 Aug 2026, 16:03682+4
24 Aug 2026, 03:27678+3
16 Aug 2026, 03:18675+8
8 Aug 2026, 02:34667no change
7 Aug 2026, 11:09667first reading

Engagement

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

What this channel posts

Video runtime
1m 13s
Average length
1m 13s

Measured directly from 1 video 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

37 reactions across 7 posts, in 8 distinct kinds. The most used accounts for 40.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1540.5%
🏆616.2%
👏616.2%
410.8%
👎25.41%
💩25.41%
😨12.70%
🤮12.70%

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

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

7 Aug 2026, 14:42 UTC77 views5 reactionsread 8 August 2026
Video

Футбольный клуб Анри третий раз в истории сыграл в Кубке России. Да, снова неудачно, но на этот раз лучше, проиграв всего 1:2 и сделал отличный ролик про матч на стадионе Динамо во Владивостоке. По качеству, на мой взгляд, некоторые клубы Второй лиги могут позавидовать. Как вам? Записки низших лиг👈

👏4🏆1

7 Aug 2026, 12:51 UTC71 views5 reactionsread 8 August 2026
Forwarded from @ultras_actionPhoto

Фанаты "Тосно" на выезде в Гатчине. На арену их традиционно не пустили, поэтому поддерживали команду за забором. Все матчи на стадионе "Балтийский" уже несколько лет по неведомым причинам проводятся без зрителей.

👍4🏆1

7 Aug 2026, 09:17 UTC106 views1 reactionsread 8 August 2026
Photo

Расписание тура в Молодежной лиге. Игра в Хабаровске утром уже была сыграна, СКА наконец-то победил дома. В дивизионе А посмотрим на московское дерби, ЦСКА дома сыграет с махачкалинским Динамо, Родина с Уралом, остальные лидеры играют на выезде. Алмаз-Антец уже как второй тур вернулся на домашний стадион. В дивизионе Б выделю два центральных матча. Один состоится в Гатчине и закроет тур, а другой будет сыгран на Т

👏1

7 Aug 2026, 08:05 UTC96 views1 reactionsread 8 August 2026

Доброе утро. Сегодня пятница, а это значит.... день матчей в Молодёжной футбольной лиге (МФЛ).

👏1

6 Aug 2026, 14:45 UTC133 views2 reactionsread 8 August 2026
Photo

Если вдруг кто пропустил, полное расписание второго раунда "пути регионов" Кубка России вместе с датами и стадионами. А то в расписании первого раунда как-то грустно было без стадионов. 11 августа пройдут всего три игры в Петербурге, Обнинске и Черкесске, аж 21 матч мы увидим 12 августа, ну а 13 пройдёт оставшиеся две игры. Встреча Чертаново и Читы в итоге не будет сыграна, так как читинцы не смогут прилететь в Моск

🏆2

4 Aug 2026, 06:22 UTC169 views3 reactionsread 8 August 2026
Photo

🩵🩵🩵🩵🩵🩵 Начинаем день с итогов четвертого тура в Первой лиге. Мы увидели две разгромные победы от лидеров. Урал потихоньку набирает ход, может бросится в погоню за Нижним Новгородом. Но пока нижегородцев не остановить, впереди у них еще один домашний матч, так что есть возможность выбить пять из пяти. В матче тура отличную игру выдали Спартак из Костромы и Енисей, разделив очки. Хотя костромская команда могла бы быт

🏆2😨1

3 Aug 2026, 19:29 UTC199 views20 reactionsread 8 August 2026
Photo

Трибуны городского стадиона в Пушкине на вчерашнем матче Первой лиги чемпионата Санкт-Петербурга между Царским Селом и С.П.Б.К.Л.С. На первом за три года домашнем матче Царского села в Пушкине согласно протоколу присутствовало 387 зрителей. Очень даже неплохо для пятой по силе лиге российского футбола. На поле, кстати, гораздо сильнее оказались хозяева, 7:0 и одержали вторую победу в сезоне. Записки низших лиг👈

👍114👎2💩2🤮1

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

Republishes

Channels on the register whose posts this channel has forwarded.

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.

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

“Записки низших лиг” (@zapiski_fnl2), 688 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/zapiski_fnl2.

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.