Telegram RegisterThe public register of Telegram

Channel

𝙼𝚊𝚝𝚝𝚑𝚒𝚊𝚜 𝙲𝚣𝚎𝚛𝚗𝚒𝚗 [𝙷𝙿]

@Matthias_Hp

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

20subscribers

+0 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1003934463485
TypeChannel
Username@Matthias_Hp
DescriptionBelongs to @HeavenlyPunishmentNet Avatar cr: jiedepigeyi lofter
CreatedBetween 1 April 2026 and 19 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
On Telegramt.me/Matthias_Hp

Growth

209 August 2026 — 20 subscribers11 August 2026 — 20 subscribers9 August 202611 August 2026
2 measurements spanning 2 days. 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 19–21 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 15:1720no change
9 Aug 2026, 20:3220first reading

Engagement

20 posts held, back to 19 July 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
55.8%
avg views ÷ 20 subscribers
Avg views / post
11.2
20 posts measured
Reaction rate
25.5%
reactions ÷ views · ER floor
Posts in window
20
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 13 of 20 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 9 August 2026
Posts held20 (19 July 20269 August 2026)
Views total223
Reactions total35
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Aug 2026, 15:17 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
1
Links
10

Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

35 reactions across 13 posts, in 6 distinct kinds. The most used accounts for 31.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🐳1131.4%
🕊822.9%
👾720.0%
617.1%
🍾25.71%
💊12.86%

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 13 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 35reactions 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 19 July 2026 to 9 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

9 Aug 2026, 12:16 UTC6 views3 reactionsread 11 August 2026

⭐⭐⭐⭐⭐⭐ ⭐⭐⭐⭐⭐⭐ ⭐ ✖️Из-за моих бесконечных попыток ускорить работу восстановление руки идёт медленнее, чем я планировал. Отец всё ещё мной недоволен и сегодня впервые за неделю зашёл ко мне — сказать, что я должен присутствовать на вечернем мероприятии. Там будут его деловые партнёры, и мне нужно будет помочь разыграть «счастливую семью»... ✖️Меня просят о таком не впервые, но каждый раз это сильно выбивает из колеи. О

🍾1👾1🕊1

3 Aug 2026, 10:09 UTC13 views1 reactionsread 11 August 2026

⭐⭐⭐⭐⭐⭐ ⭐⭐⭐⭐⭐⭐ ⭐ ✖️После того короткого разговора с Хелелем я чувствую себя правда лучше. Даже не предполагал, что подобное может так сильно на меня повлиять... ✖️Казалось бы, я общаюсь с родителями, Луисом, андроидами, клиентами, другими работниками... Но никто из них не хотел просто поговорить со мной. Это очень странное чувство. Хуже всего, что мне оно понравилось, и я хочу разобраться в этом... ✖️Впрочем, отец поч

🐳1

1 Aug 2026, 18:20 UTC12 views1 reactionsread 11 August 2026

𝙰𝚛𝚌𝚑𝚒𝚟𝚎 𝚛𝚎𝚌𝚘𝚛𝚍 #𝟸 𝟶𝟾/𝟶𝟷/𝟸𝟶𝟸𝟼 𝙼𝚎𝚎𝚝𝚒𝚗𝚐 𝚠𝚒𝚝𝚑 𝙷𝚎𝚕𝚎𝚕 ⭐ ✖️Я чуть тихо усмехнулся, и моя улыбка немного померкла. – Ох, понятно... ✖️Теперь мне стало по-настоящему стыдно. И за свой внешний вид, и за то, что я не поверил в искренность слов Хелеля. Вероятно, та история с андроидом Ромеро окончательно разрушила моё доверие кому-либо... ✖️Погрузившись в свои мысли, я едва успел остановиться, чтобы не столкнуться с Хелелем. О

🐳1

1 Aug 2026, 17:40 UTC8 views4 reactionsread 11 August 2026

𝙰𝚛𝚌𝚑𝚒𝚟𝚎 𝚛𝚎𝚌𝚘𝚛𝚍 #𝟸 𝟶𝟾/𝟶𝟷/𝟸𝟶𝟸𝟼 𝙼𝚎𝚎𝚝𝚒𝚗𝚐 𝚠𝚒𝚝𝚑 𝙷𝚎𝚕𝚎𝚕 ⭐ ✖️Я кивнул и без лишних вопросов пошёл за Хелелем. ✖️Он точно отличался от остальных верующих. Услышав о моей проблеме, он не стал говорить «Бог любит тебя» или зачитывать нравоучительные строки из Библии... Он просто побыл рядом, как обычный человек. Наверное, ему и правда было интересно узнать обо мне? Хотя я не могу быть в этом уверен... Возможно, это просто часть

1🐳1👾1🕊1

1 Aug 2026, 17:03 UTC8 views4 reactionsread 11 August 2026

𝙰𝚛𝚌𝚑𝚒𝚟𝚎 𝚛𝚎𝚌𝚘𝚛𝚍 #𝟸 𝟶𝟾/𝟶𝟷/𝟸𝟶𝟸𝟼 𝙼𝚎𝚎𝚝𝚒𝚗𝚐 𝚠𝚒𝚝𝚑 𝙷𝚎𝚕𝚎𝚕 ⭐ ✖️Я знаю, что доверять словам малознакомого человека не стоит, и что было вполне ожидаемо, что он меня понимает — ведь в церкви, как ни иронично, не любят андроидов... Однако даже если слова Хелеля — ложь, от них на душе становится намного легче. Наконец-то я получил понимание от другого человека, которого так и не дождался от отца. Впервые за долгое время я смог выдо

1🐳1👾1🕊1

1 Aug 2026, 16:20 UTC6 views4 reactionsread 11 August 2026

𝙰𝚛𝚌𝚑𝚒𝚟𝚎 𝚛𝚎𝚌𝚘𝚛𝚍 #𝟸 𝟶𝟾/𝟶𝟷/𝟸𝟶𝟸𝟼 𝙼𝚎𝚎𝚝𝚒𝚗𝚐 𝚠𝚒𝚝𝚑 𝙷𝚎𝚕𝚎𝚕 ⭐ ✖️Похоже, искренность была наигранной. Стоило ожидать... И теперь я понятия не имею, что ему ответить. Если солгу — заметит, врать я не умею. Если скажу правду — засмеёт, что не смог себя защитить... ✖️ – Да, ты прав, не критично... Просто неудачное столкновение с андроидом. ✖️ ✖️Мне было неловко продолжать эту тему, и я приобнял коробку так, чтобы бинт на руке не был

1🐳1👾1🕊1

1 Aug 2026, 15:40 UTC7 views4 reactionsread 11 August 2026

𝙰𝚛𝚌𝚑𝚒𝚟𝚎 𝚛𝚎𝚌𝚘𝚛𝚍 #𝟸 𝟶𝟾/𝟶𝟷/𝟸𝟶𝟸𝟼 𝙼𝚎𝚎𝚝𝚒𝚗𝚐 𝚠𝚒𝚝𝚑 𝙷𝚎𝚕𝚎𝚕 ⭐ ✖️Я обернулся и увидел высокого светловолосого парня. Мне никогда не доводилось с ним разговаривать, но из тихих разговоров прихожан после служб я знал, что все зовут его Хелелем. О нём ходили только хорошие слухи — его здесь очень любили. ✖️Для меня было крайне неожиданно, что он не просто меня запомнил, но и сам подошёл заговорить. ✖️Я не понимал, что ему нужно, одн

1🐳1👾1🕊1

1 Aug 2026, 15:00 UTC7 views4 reactionsread 11 August 2026

𝙰𝚛𝚌𝚑𝚒𝚟𝚎 𝚛𝚎𝚌𝚘𝚛𝚍 #𝟸 𝟶𝟾/𝟶𝟷/𝟸𝟶𝟸𝟼 𝙼𝚎𝚎𝚝𝚒𝚗𝚐 𝚠𝚒𝚝𝚑 𝙷𝚎𝚕𝚎𝚕 ⭐ ✖️Впервые за несколько дней ко мне в мастерскую зашёл отец. Однако вместо обычного семейного разговора меня ждала беседа работодателя с работником... Отец был недоволен тем, как медленно продвигается моя работа, поэтому отправил меня в церковь — поговорить с местным пастором. Мы стараемся посещать церковь каждое воскресенье, но из-за последних событий пришлось пропуст

🍾1🐳1💊1🕊1

29 Jul 2026, 18:16 UTC9 views1 reactionsread 11 August 2026

⭐⭐⭐⭐⭐⭐ ⭐⭐⭐⭐⭐⭐ ⭐ ✖️В начале недели я попробовал снова вернуться к работе, однако это оказалось гораздо труднее, чем я изначально ожидал. Двигать рукой всё ещё больно, поэтому я делаю самый минимум и с большими перерывами... ✖️За последние несколько дней я ни разу не видел отца. Он полностью погрузился в работу — в основном общается с клиентами и ищет сотрудников на мою, надеюсь, временную замену. ✖️К сожалению, в то ж

🐳1

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

Citation-graph rank

Citation-graph rank — 685,808 of 1,480,688entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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.

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

“𝙼𝚊𝚝𝚝𝚑𝚒𝚊𝚜 𝙲𝚣𝚎𝚛𝚗𝚒𝚗 [𝙷𝙿]” (@Matthias_Hp), 20 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/Matthias_Hp.

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.