Telegram RegisterThe public register of Telegram
Telegram profile photo for Лыкошино - это Мы

Channel

Лыкошино - это Мы

@likoshino

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

666subscribers

+36 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-1001320176297
TypeChannel
Username@likoshino
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live12 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 12 September 2026
On Telegramt.me/likoshino

Topic

Local community — 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 100% 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

6306666487 August 2026 — 630 subscribers7 August 2026 — 639 subscribers8 August 2026 — 639 subscribers14 August 2026 — 656 subscribers20 August 2026 — 658 subscribers27 August 2026 — 657 subscribers4 September 2026 — 655 subscribers12 September 2026 — 666 subscribers7 August 202612 September 2026
8 measurements spanning 36 days, net +36. 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 625–671 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Sept 2026, 15:59666+11
4 Sept 2026, 18:17655-2
27 Aug 2026, 19:44657-1
20 Aug 2026, 23:43658+2
14 Aug 2026, 21:47656+17
8 Aug 2026, 02:48639no change
7 Aug 2026, 20:12639+9
7 Aug 2026, 14:14630first reading

Engagement

20 posts held, back to 30 July 2025 — 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

7 Aug 2026, 15:47 UTC≈8,320 viewsread 8 August 2026

Завтра в Лыкошине день поселка

11 Jul 2026, 16:15 UTC≈10,800 viewsread 8 August 2026

Лыкошино Березайка сегодня без света после лёгкого урагана

30 Jun 2026, 15:29 UTC≈14,600 viewsread 8 August 2026

56-я аптека (на площади) сегодня работает последний день

27 Jun 2026, 15:57 UTC≈1,840 viewsread 8 August 2026

Ямы на участке Корыхново - Березайка выборочно залатали

27 Jun 2026, 05:30 UTC≈2,070 viewsread 8 August 2026

В Бологое на Роснефти сейчас очередь километр. Бензина нет никакого

26 Jun 2026, 11:19 UTC≈14,300 viewsread 8 August 2026

В Бологое на Роснефти сейчас нет никакого бензина, утром был

22 Jun 2026, 13:02 UTC≈13,200 viewsread 8 August 2026

Сейчас в Бологое бензина нет ни на одной заправке

30 May 2026, 16:39 UTC≈3,230 viewsread 8 August 2026
Photo

Остатки школы/библиотеки/жилого дома

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

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

“Лыкошино - это Мы” (@likoshino), 666 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/likoshino.

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.