Channel
@SLOVOPRAVDU
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
217subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001726969619 |
|---|---|
| Type | Channel |
| Username | @SLOVOPRAVDU |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/SLOVOPRAVDU |
Religion — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @siracha1/295130 Jul 2026, 21:50 UTC | @SLOVOPRAVDU/3876 · this entry30 Jul 2026, 21:51 UTC | 1.00 | under a minute |
| @siracha1/295331 Jul 2026, 22:01 UTC | @SLOVOPRAVDU/3878 · this entry31 Jul 2026, 22:01 UTC | 1.00 | under a minute |
| @siracha1/29552 Aug 2026, 04:26 UTC | @SLOVOPRAVDU/3880 · this entry2 Aug 2026, 04:27 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @siracha1 | 9 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (5–4) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 1 of the 4 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 12 comparable posts for this entry, running 28 July 2026 to 6 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Across the whole group of 2, the earliest publisher we hold is @siracha1. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_mutual, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 22:35 | 217 | -1 |
| 2 Sept 2026, 01:19 | 218 | -1 |
| 20 Aug 2026, 16:58 | 219 | -1 |
| 14 Aug 2026, 13:36 | 220 | +1 |
| 7 Aug 2026, 03:30 | 219 | no change |
| 7 Aug 2026, 01:32 | 219 | first reading |
20 posts held, back to 27 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 20 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
10 reactions across 10 posts, in 2 distinct kinds. The most used accounts for 90.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🕊 | 9 | 90.0% | |
| 🙏 | 1 | 10.0% |
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 10 of the 20 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 10 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 27 July 2026 to 6 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.
ЗАВИСТь Зависть: природа, проявления и духовные последствия Зависть — одно из самых древних и разрушительных состояний человеческого сердца. Она возникает тихо, почти незаметно, но её последствия могут быть тяжёлыми: от внутренней горечи и утраты мира до разрушения отношений и даже гибели. Писание показывает, что зависть — не просто эмоция, а духовная болезнь, искажающая взгляд человека на Бога, на ближнего и на са…
🙏1
Signed Alex B.
Не бойся говорю, и не тревожься. Те реки бед тебя не захлеснут. Пойдёшь ли чрез огонь, не обожжешься. Я в пламени тебя сём сберегу. А Я Господь, твой Бог Святой Израилев. Спаситель твой, тебя Я возлюбил. И днём, и ночью буду охранять тебя. Я за тебя так дорого платил. Заветом для народов тебя сделаю. Я силен землю вновь восстановить, Чтобы опустошенное наследие Опять Своей рукою возвратить. Я так хочу утешить и по…
🕊1
Photo, posted without a caption
🕊1
Photo, posted without a caption
🕊1
Photo, posted without a caption
🕊1
Signed Alex B.
ВОПРОСЫ к проповедникам утверждающим, что Бог не смотрит на дела человека, а ценит только его веру. Мф.25:35-46 …идите от Меня, проклятые, в огонь вечный, уготованный диаволу и ангелам его: 42 ибо алкал Я, и вы не дали Мне есть; жаждал, и вы не напоили Меня; 43 был странником, и не приняли Меня; был наг, и не одели Меня; болен и в темнице, и не посетили Меня. 44 Тогда и они скажут Ему в ответ: Господи! когда мы ви…
Signed Alex B.
Photo, posted without a caption
🕊1
ПЕЧАЛь Печаль есть естественное чувство, знакомое всем здравомыслящим людям. Разве что малолетний ребёнок или умалишённый человек может не знать чувств печали. Екл. 1:17,18 И предал я сердце мое тому, чтобы познать мудрость и познать безумие и глупость: узнал, что и это--томление духа; потому что во многой мудрости много печали; и кто умножает познания, умножает скорбь. Печаль мирская 2Кор. 7:10 Ибо печаль рад…
Signed Alex B.
ВСË КО БЛАГУ. Ко благу всë тебе Я допускаю. Не усомнися в милости Моей. А если скорби в жизни посылаю. То это благо для души твоей. Ты часто мысли эти допускаешь: "Зачем мне скорби Бог послал? Не любит Он меня, не понимает И на молитвы отвечать Он перестал. " Зачем ты угнетаешь так себя? И почему не веришь Мне, дитя? И усомнился ты в любви Моей. Поверь, что милость это для души твоей. Хочу Я убелить тебя дитя. И …
ИНОЙ ДУХ Почему Иисус Навин и Халев дали иной отчёт о земле обетованной, в отличие от десяти других соглядатаев? Потому что в них был иной дух — дух доверия и послушания Богу. А от этого их взгляд и оценка обстоятельств были совершенно другими. Писание говорит: «Раб Мой Халев… имел иной дух и совершенно повиновался Мне» (Числа 14:24) Их вера не возникла случайно. Они были в тех же условиях и пережили такие же обст…
Signed Alex B.
Где потеряла церковь огонь Где та молитва, что небо склоняла? Где те сердца, что искали Христа? Где та слеза, что в ночи проливалась? Где покаяние, где ты семья? Сегодня много красивых собраний, Много мелодий и ярких речей. Но среди шума земных оправданий Где же дыхание Божье, скажи? Не в свете сцены Господь пребывает, Не в громких словах и людской похвале. Он в сокрушённых сердцах обитает, В тихой молитве на греш…
Где потеряла церковь огонь Где та молитва, что небо склоняла? Где те сердца, что искали Христа? Где та слеза, что в ночи проливалась? Где покаяние, где ты семья? Сегодня много красивых собраний, Много мелодий и ярких речей. Но среди шума земных оправданий Где же дыхание Божье, скажи? Не в свете сцены Господь пребывает, Не в громких словах и людской похвале. Он в сокрушённых сердцах обитает, В тихой молитве на греш…
Showing the 12 most recent of 20 posts we hold for @SLOVOPRAVDU. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“Христианская Страница” (@SLOVOPRAVDU), 217 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/SLOVOPRAVDU.
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.