Telegram RegisterThe public register of Telegram
Telegram profile photo for Нікому крім нас

Channel

Нікому крім нас

@shkidlyvo

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

569subscribers

-3 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001881238578
TypeChannel
Username@shkidlyvo
Created27 October 2022measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live14 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 14 September 2026
On Telegramt.me/shkidlyvo

Topic

Religion — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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

569574571.56 August 2026 — 572 subscribers6 August 2026 — 572 subscribers14 August 2026 — 574 subscribers21 August 2026 — 570 subscribers29 August 2026 — 571 subscribers14 September 2026 — 569 subscribers6 August 202614 September 2026
6 measurements spanning 38 days, net -3. 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 568–575 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Sept 2026, 00:41569-2
29 Aug 2026, 00:25571+1
21 Aug 2026, 21:09570-4
14 Aug 2026, 21:53574+2
6 Aug 2026, 18:04572no change
6 Aug 2026, 15:49572first reading

Engagement

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

Reaction mix

316 reactions across 14 posts, in 14 distinct kinds. The most used accounts for 45.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
14445.6%
🙏4815.2%
💔3210.1%
❤‍🔥247.59%
😡185.70%
🤡144.43%
🤔123.80%
😢72.22%
🥱72.22%
🌚30.949%
👍20.633%
🤪20.633%
🫡20.633%
🤬10.316%

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

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

25 Jul 2026, 15:05 UTC305 views22 reactionsread 6 August 2026
Photo

Переведення братії Феодосіївського до Лаври виглядає мені правильним кроком. Щоб відстояти цей простір у музейників і лишити баланс на користь монастиря потрібне і монашество, і громада. Отець Макарій сприяє тому щоб громада наповнювала монастирські богослужіння. І маю надію, що жіноча обитель в Феодосіївському буде рости. Це гарна данина історії — жіночий монастир навпроти Лаври.

21🤬1

24 Jul 2026, 15:53 UTC295 views13 reactionsread 6 August 2026
Photo

Кондиціонер на місці. Порядок.

🥱7🌚3🤪2👍1

15 Jul 2026, 19:37 UTC535 views33 reactionsread 6 August 2026
Photo

Чудова світлина. Завжди молюсь до Святого Серафима і саме перед цією іконою. Святий Серафиме, своїми молитвами будь заступником нам і спини злочини своїх нерозумних духовних чад, що забули Бога.

❤‍🔥249

11 Jul 2026, 15:18 UTC568 views17 reactionsread 6 August 2026
Photo

Ох, який же він душний.

🤡142👍1

10 Jul 2026, 10:24 UTC589 views28 reactionsread 6 August 2026
Video

Мав радість долучатись сьогодні до літургії. Дуже теплі відчуття, приємно було бачити знайомі обличчя серед мирян і духовенства. Тішила присутність перших осіб держави. Якщо преподобний Антоній збирає нас разом — значить все не марно. Звісно, трохи засмучує що така подія не є подією масштабу, який помітно у всьому Києві. Давайте це виправляти. Розкажіть сьогодні комусь зі знайомих про преподобного Антонія Києво-Печ

28

3 Jul 2026, 14:55 UTC497 views23 reactionsread 6 August 2026
Photo

Вшанування памʼяті преподобного Антонія Печерського І 975 річниці заснування святої обителі. В Лаврі відбудуться богослужіння за участі афонських монахів та візантійського хору. Це важлива подія в житті монастиря, визначна подія для всіх киян, тому церква закликає вірних до спільної молитви. Четвер 9 липня 17:00 Всенічне бдіння Пʼятниця 10 липня 9:00 Божественна літургія

🙏167

28 Jun 2026, 07:59 UTC597 views22 reactionsread 6 August 2026
Photo

Слухаємо Слово Боже

🙏175

17 Jun 2026, 15:35 UTC≈1,040 views25 reactionsread 6 August 2026
Photo

Зрештою ситуація прояснилась. Найочевидніша відповідь виявилась правдивою — у архієпископа Лаврентія і єпархії грошей на оренду нема. Тож служити буде той, в кого є. Безоплатна оренда історичних святинь — це не для ПЦУ.

😡18😢7

15 Jun 2026, 06:27 UTC615 views45 reactionsread 6 August 2026
Photo

Молитвами Богородиці, Господи помилуй нас!

💔32🙏11🫡2

14 Jun 2026, 11:39 UTC677 views12 reactionsread 6 August 2026
Photo

Рік в Кирилівській церкві служив архієпископ Лаврентій з духовенством і хоч нечисленною, але громадою. Декілька тижнів тому виникли проблеми з орендою храму, який належить до заповідника Софія Київська. Тут раптом проблеми вирішились і настоятелем призначили отця Богдана. Не знаю в чому справа, але виглядає максимально дивно.

🤔12

8 Jun 2026, 11:45 UTC570 views20 reactionsread 6 August 2026
Forwarded from @philosophical_orthodoxPhoto

Православна Церква не має проблеми єдиного та множинного, тому святкує П’ятидесятницю як сходження Духа на кожного у Церкві. Дух сходить на особистостей. Як людська природа Христа не розчинилася, не змішалася у божестві, так і союз з Богом не передбачає знищення особистості, розпливання чи стирання особливостей, як це можна зустріти у поганських філософів. Це союз особистості з особистістю. Ісус Христос друга Особа

16🙏4

Showing the 12 most recent of 14 posts we hold for @shkidlyvo. 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 14 September 2026 — this entry's latest reading, not the date you are reading this.

“Нікому крім нас” (@shkidlyvo), 569 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/shkidlyvo.

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.