Telegram RegisterThe public register of Telegram
Telegram profile photo for Щукино

Channel

Щукино

@shuklno

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Referenced elsewhere · Cite this entry

5,221subscribers

-118 since we began measuring on 5 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002043963091
TypeChannel
Username@shuklno
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live7 November 2026
Measurements held26
Confirmed unchanged1 time, most recently 7 November 2026
On Telegramt.me/shuklno

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 13 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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 the other topics.

Growth

5,2215,3425,281.55 August 2026 — 5,339 subscribers6 August 2026 — 5,339 subscribers6 August 2026 — 5,340 subscribers9 August 2026 — 5,342 subscribers12 August 2026 — 5,333 subscribers15 August 2026 — 5,335 subscribers18 August 2026 — 5,333 subscribers21 August 2026 — 5,315 subscribers24 August 2026 — 5,306 subscribers28 August 2026 — 5,296 subscribers31 August 2026 — 5,286 subscribers3 September 2026 — 5,284 subscribers9 September 2026 — 5,276 subscribers17 September 2026 — 5,271 subscribers26 September 2026 — 5,257 subscribers5 October 2026 — 5,242 subscribers11 October 2026 — 5,239 subscribers14 October 2026 — 5,241 subscribers17 October 2026 — 5,233 subscribers20 October 2026 — 5,237 subscribers23 October 2026 — 5,245 subscribers26 October 2026 — 5,242 subscribers29 October 2026 — 5,227 subscribers1 November 2026 — 5,229 subscribers4 November 2026 — 5,223 subscribers7 November 2026 — 5,221 subscribers5 August 20267 November 2026
26 measurements spanning 93 days, net -118. 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 5,203–5,360 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)SubscribersChange
7 Nov 2026, 00:155,221-2
4 Nov 2026, 05:285,223-6
1 Nov 2026, 10:055,229+2
29 Oct 2026, 14:395,227-15
26 Oct 2026, 03:575,242-3
23 Oct 2026, 09:065,245+8
20 Oct 2026, 07:315,237+4
17 Oct 2026, 08:055,233-8
14 Oct 2026, 17:575,241+2
11 Oct 2026, 05:385,239-3
5 Oct 2026, 03:215,242-15
26 Sept 2026, 09:585,257-14
17 Sept 2026, 02:395,271-5
9 Sept 2026, 02:405,276-8
3 Sept 2026, 16:005,284-2
31 Aug 2026, 14:135,286-10
28 Aug 2026, 05:475,296-10
24 Aug 2026, 21:535,306-9
21 Aug 2026, 00:445,315-18
18 Aug 2026, 09:475,333first reading

Engagement

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

What this channel posts

Video runtime
16s
Average length
8s

Measured directly from 2 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

277 reactions across 15 posts, in 14 distinct kinds. The most used accounts for 30.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤8430.3%
🔥5921.3%
😢3613.0%
🤡238.30%
😍186.50%
😱165.78%
🤔145.05%
🤷82.89%
💯72.53%
🕊41.44%
👍31.08%
👌20.722%
💩20.722%
🍓10.361%

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

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

11 Aug 2026, 14:02 UTC≈1,970 views6 reactionsread 12 August 2026
Photo

☔️ Уже в ближайшее время Москву накроет ливень, который продлится до ночи В МЧС также предупредили, что порывы ветра будут достигать 15 м/с.

❤4😢2

10 Aug 2026, 05:05 UTC≈2,330 views23 reactionsread 12 August 2026
Photo

Лето, окрестности станции метро «Октябрьского Поле», 2009-й год. Помните такой «Пассаж»? Сейчас он совсем по-другому выглядит, конечно 😍

❤19🔥3😍1

9 Aug 2026, 20:06 UTC≈2,420 views13 reactionsread 12 August 2026
Photo

Ночной фонтан в ЖК алые паруса

🔥11🍓1👍1

9 Aug 2026, 18:25 UTC≈1,010 views25 reactionsread 12 August 2026
Photo

Когда-то в этом детском саду дети плавали в собственном бассейне. В современных садах такая роскошь — большая редкость. Время идёт, всё меняется… Но старые фотографии иногда напоминают, каким был наш район раньше ❤️

❤25

9 Aug 2026, 11:57 UTC≈1,760 views0 reactionsread 12 August 2026
Photo

Нашли.карта москвича. Октябрьское поле.

8 Aug 2026, 17:31 UTC≈2,730 views16 reactionsread 12 August 2026
Photo

⚡️Под строгинским мостом возле яхт клуба с моста падают куски бетона будет аккуратнее

😱16

8 Aug 2026, 07:04 UTC≈1,980 views13 reactionsread 12 August 2026
Photo

Бегает собака, похоже, что потерялась. В парке на Щукинской набережной. Авиационная 74к2

😢13

7 Aug 2026, 09:17 UTC≈2,250 views32 reactionsread 12 August 2026

⚡️Предварительно, источником громкого звука оказался пролетавший на гиперзвуке самолёт ❤TG | 📲MAX

🤡23❤7💩2

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

Posts recorded as deleted after publishing

We recorded 4 posts on @shuklno as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
7 August 2026
Most recent seen missing
8 August 2026
Median time before seen missing
2 days
Seen missing in the last 30 days
0

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 3 registered channels — 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.

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.

Referenced elsewhere

This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.

Wikipedia

One Wikipedia article names this handle in its article text, found by searching for a t.me link inside the article source. A citation is a notability signal, not a verification: nobody here confirmed the cited post is genuine or still says what the article quotes. Article text is CC BY-SA 4.0, Wikipedia contributors; snippets below are short excerpts.

Щукино (район Москвы) (ru.wikipedia.org)
“…== Примечания == {{примечания}} == Ссылки == {{Навигация}} * [https://t.me/shuklno Официальная группа в Telegram «Щукино»] * [http://shukino.ru Официальный…”
read 1 November 2026

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

“Щукино” (@shuklno), 5,221 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/shuklno.

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.