Telegram RegisterThe public register of Telegram
Telegram profile photo for Хурамшинский Лунаход

Channel

Хурамшинский Лунаход

@khuramsha

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Posts · Cite this entry

7subscribers

-1 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-1001465467308
TypeChannel
Username@khuramsha
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live14 November 2026
Measurements held3
Confirmed unchanged3 times, most recently 14 November 2026
On Telegramt.me/khuramsha

Topic

Religion — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 28 October 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.

Observations

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.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@khuramsha/48752 · this entry28 Feb 2026, 16:30 UTC@kalmyk_broadcast/3222128 Feb 2026, 18:30 UTC1.002.0 hours
@khuramsha/48753 · this entry1 Mar 2026, 16:30 UTC@kalmyk_broadcast/322221 Mar 2026, 18:30 UTC1.002.0 hours
@khuramsha/48754 · this entry2 Mar 2026, 16:30 UTC@kalmyk_broadcast/322232 Mar 2026, 18:30 UTC1.002.0 hours
@khuramsha/48756 · this entry4 Mar 2026, 16:30 UTC@kalmyk_broadcast/322254 Mar 2026, 18:30 UTC1.002.0 hours
@khuramsha/48759 · this entry7 Mar 2026, 16:30 UTC@kalmyk_broadcast/322287 Mar 2026, 18:30 UTC1.002.0 hours
@khuramsha/48764 · this entry12 Mar 2026, 16:30 UTC@kalmyk_broadcast/3223312 Mar 2026, 18:30 UTC1.002.0 hours
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@kalmyk_broadcast20 (8/8 hand-verifiable sample passed)1.002.0 hoursthis entry (20–0)

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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 20 comparable posts for this entry, running 28 February 2026 to 19 March 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.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 2 channels, the one whose matching posts we hold earliest is @khuramsha — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 11 November 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.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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.

Growth

787.57 August 2026 — 8 subscribers12 August 2026 — 8 subscribers28 October 2026 — 7 subscribers7 August 202628 October 2026
3 measurements spanning 82 days, net -1. 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 7–8 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Oct 2026, 21:567-1
12 Aug 2026, 15:038no change
7 Aug 2026, 18:078first reading

Engagement

20 posts held, back to 28 February 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 19 March 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

19 Mar 2026, 16:30 UTC6 viewsread 12 August 2026

20.03.2026 🌙 Лунный день: Второй. ✂ Последствия стрижки или бритья волос: ссоры и осуждения. ✨ В полной мере подходит для принятия обета ламы, вступления в должность, освящения храма и изображений божеств, поступления на лечение, издания законов и вынесения судебных решений, поставки закваски и т.д.

18 Mar 2026, 16:30 UTC6 viewsread 12 August 2026

19.03.2026 🌙 Лунный день: Первый. ✂ Последствия стрижки или бритья волос: сокращение жизни. ✨ Хорошо совершать все действия, приносящие пользу (во всем), также благоприятно копать колодец, сажать деревья, копать яму на новом нетронутом участке земли, начинать доброе дело, отправляться в дорогу и т.д. Воспрещается: слушать наставления по учению, совершать обряды по усопшим, почитать и делать подношения.

17 Mar 2026, 16:30 UTC6 viewsread 12 August 2026

18.03.2026 🌙 Лунный день: Тридцатый. ✂ Последствия стрижки или бритья волос: встреча с Владыкой Смерти (сокращение продолжительности жизни). ✨ Хорош для поставки закваски, чтения книг по дхарме, укрепления связей между родственниками, купли-продажи, для возведения фундамента, принятия обета послушника и монаха, совершения обряда для долголетия и богатства, занятия земледелием. Запрещается совершать свадебные обряды и…

16 Mar 2026, 16:30 UTC4 viewsread 12 August 2026

17.03.2026 🌙 Лунный день: Двадцать девятый. ✂ Последствия стрижки или бритья волос: несчастье. ✨ Хорошо усмирять врага, злых духов, а также совершать все гневные действия. Нехорошо приводить невестку в дом, совершать похоронный обряд по усопшему, продавать скот, производить куплю-продажу, совершать обмен.

15 Mar 2026, 16:30 UTC4 viewsread 12 August 2026

16.03.2026 🌙 Лунный день: Двадцать восьмой. ✂ Последствия стрижки или бритья волос: красивая внешность. ✨ В этот день хорошо отправляться в дорогу, крыть крышу. Нехорошо в этот день совершать похоронный обряд по усопшему, приводить невестку в дом.

14 Mar 2026, 16:30 UTC5 viewsread 12 August 2026

15.03.2026 🌙 Лунный день: Двадцать седьмой. ✂ Последствия стрижки или бритья волос: радость. ✨ Хорошо отправляться в дорогу, совершать похоронный обряд по усопшему, ставить закваску. В этот день нехорошо давать обещания, приводить невестку в дом, играть свадьбу.

13 Mar 2026, 16:30 UTC4 viewsread 12 August 2026

14.03.2026 🌙 Лунный день: Двадцать шестой. ✂ Последствия стрижки или бритья волос: блаженство. ✨ В этот день хорошо пахать землю и ставить закваску. Нехорошо отправляться в дорогу, продавать скот, совершать обмен.

12 Mar 2026, 16:30 UTC5 viewsread 12 August 2026

13.03.2026 🌙 Лунный день: Двадцать пятый. ✂ Последствия стрижки или бритья волос: счастье. ✨ В этот день хорошо отправляться в дорогу, сеять зерно, совершать похоронный обряд по усопшему, совершать куплю-продажу.

11 Mar 2026, 16:30 UTC3 viewsread 12 August 2026

12.03.2026 🌙 Лунный день: Двадцать четвертый. ✂ Последствия стрижки или бритья волос: заразное заболевание. ✨ День хорош для отправления в дорогу. Хорошо давать обещания, читать наставления по дхарме, делать подношения, исполнять обряд для умножения богатства. Воспрещается совершать освящение храмов и других объектов почитания.

10 Mar 2026, 16:30 UTC4 viewsread 12 August 2026

11.03.2026 🌙 Лунный день: Двадцать третий. ✂ Последствия стрижки или бритья волос: увеличение благ. ✨ Хорош для отправления в дорогу, освящения храмов и других объектов почитания, для общегородских и административных дел.

9 Mar 2026, 16:30 UTC3 viewsread 12 August 2026

10.03.2026 🌙 Лунный день: Двадцать второй. ✂ Последствия стрижки или бритья волос: увеличение болезни. ✨ День хорош для обучения грамоте, астрологии, искусству и ремеслам, а также нанимать работника, отдавать на лечение, надевать украшения, производить куплю-продажу, изготовлять лекарства, рыть колодец, выполнять обряды для умножения богатства.

8 Mar 2026, 16:30 UTC3 viewsread 12 August 2026

09.03.2026 🌙 Лунный день: Двадцать первый. ✂ Последствия стрижки или бритья волос: увеличение физической силы. ✨ В этот день хорошо находиться в дороге, сеять хлеб. Он благоприятен для всех благих дел.

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

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

“Хурамшинский Лунаход” (@khuramsha), 7 subscribers as measured 28 October 2026. Telegram Register, tgregister.com/channel/khuramsha.

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.