Telegram RegisterThe public register of Telegram
Telegram profile photo for ᥰᥱρᥱ᥊᧐днᥙκ ᴛ᧐κᥴᥙ᥊ᥱ᧘ [🧪🦭]

Channel

ᥰᥱρᥱ᥊᧐днᥙκ ᴛ᧐κᥴᥙ᥊ᥱ᧘ [🧪🦭]

@churchaloves1x

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

10subscribers

-26 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1004438410759
TypeChannel
Username@churchaloves1x
CreatedBetween 1 June 2026 and 3 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live17 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/churchaloves1x

Growth

9653710 August 2026 — 36 subscribers10 August 2026 — 36 subscribers11 August 2026 — 44 subscribers17 August 2026 — 59 subscribers24 August 2026 — 62 subscribers31 August 2026 — 65 subscribers9 September 2026 — 9 subscribers17 September 2026 — 10 subscribers1010 August 202617 September 2026
8 measurements spanning 38 days, net -26. 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 1–73 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 17:3810+1
9 Sept 2026, 09:369-56
31 Aug 2026, 08:0465+3
24 Aug 2026, 23:1762+3
17 Aug 2026, 20:3759+15
11 Aug 2026, 10:4544+8
10 Aug 2026, 23:0136no change
10 Aug 2026, 10:4636first reading

Engagement

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

What this channel posts

Video runtime
13s
Average length
13s

Measured directly from 1 video 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

173 reactions across 12 posts, in 8 distinct kinds. The most used accounts for 24.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54003382985498525854324.9%
custom 54200920428501166784123.7%
custom 54200882246241916423017.3%
custom 54183453097156070662916.8%
custom 5420298274294769049126.94%
custom 5420177590008716183116.36%
🕊42.31%
👀31.73%

Custom emoji. 6 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

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

Measured over the 17 most recent posts we hold, published 3 August 2026 to 10 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

10 Aug 2026, 18:50 UTC30 views3 reactionsread 10 August 2026

про пост напомню ок.. 🤩 урап 40 пдп пасибав #щп

custom 54200882246241916421custom 54200920428501166781custom 54201775900087161831

10 Aug 2026, 16:31 UTC30 viewsread 10 August 2026
Forwarded from @vflowerskisserPhoto

🐏🐏🐏 🎀𝗐𝗈𝗂𝖿𝗅𝓸 𝘀𝖺𝖿𝖾𝗉𝗅𝖺𝖼𝖾 🌫 ❌🐏🐏❌🐏❌✨🤍🦇🍼 данный канал посвящен моей любви к Флавер 🥹🥹 💎 🤩🤩 🌫🤩🪙🤍🍼🍼🤍🤩🎀❌🤩 🤩🎁 𝗻𝖺𝗏𝗂𝗀𝖺𝗍𝗂𝗈𝗇 🥹🥹📼📼📼

10 Aug 2026, 14:15 UTC28 viewsread 10 August 2026
Forwarded from @selfsplovePhoto

ㅤㅤ ִㅤㅤ ﹫ ㅤ 🤩𝑠𝒉𝑐𝑚 𝑙𝑜𝑣𝑒𝑠 ֵ 🫧🫧 ׄ ୨ 💊 🔤юбите и будьте любимы вместе с нами .ㅤ♡ꨵ ׄ ㅤㅤ ݁ㅤ 𝑏𝑜𝑜𝑠𝑡 ㅤ 𝑟𝑢𝑙𝑒𝑠 ㅤ 𝑎𝑑𝑚𝑙𝑖𝑠𝑡 ㅤㅤ ㅤㅤ 𝑚𝑝 𝑝𝑜𝑠𝑡 ㅤ 𝑡𝑎𝑘𝑒 𝑏𝑜𝑡 ☁☁☁

10 Aug 2026, 12:25 UTC34 views5 reactionsread 10 August 2026

блин го вп я 40 пдп хочу🥺 #щп

custom 54183453097156070662custom 54200920428501166782custom 54202982742947690491

10 Aug 2026, 11:33 UTC34 views2 reactionsread 10 August 2026

пр, крч у меня наконец-то дотянулись руки начать пытаться прописывать лор токсихел,, для начала я возьмусь за ау по лору роблокса (уже в процессе бтв!!) затем думаю еще сделать ау по ф*рсакену💀💀 и обычную ирл ау типо,, и мб потом еще какие нибудь ау придумаю второстепенные 💚 кстати было бы крута если бы какой нибудь шарющий либо креативный человечек отозвался бы помочь🌟 **намек🥺 #щп #важное (?)

custom 54200920428501166782

10 Aug 2026, 09:19 UTC34 views41 reactionsread 10 August 2026
Photo

🍼💕ew post!! 🌟 🍼🍼 урап еще одна милейшая кмм готова🌀 мою маму уже заебывает то шо я сток денег на коммишки трачу.. (я не собираюсь останавливаться)) 🍼кр:: @kacuchaan #арт #чурчхела #1x4 #адмтейк #кмм

custom 540033829854985258513custom 541834530971560706612custom 542009204285011667810custom 54200882246241916423👀1🕊1custom 54202982742947690491

9 Aug 2026, 19:01 UTC36 views9 reactionsread 10 August 2026
Forwarded from @AnonAskBotPhoto

💬 У тебя новое анонимное сообщение! hewo! Типа гифт я не знаю можно ли кидать сюдо гифты, но пуст будет как токсихелы ( — — " ) ⬅️ Свайпни для ответа.

custom 54183453097156070663custom 54200882246241916423custom 54200920428501166783

9 Aug 2026, 16:11 UTC36 views25 reactionsread 10 August 2026
Photo

🍼💕ew post!! 🌟 🍼🍼 милая кмм с плюш иксом от нару🪽🪽 🍼кр:: @NaruElla #арт #чурчхела #1x4 #адмтейк #кмм

custom 54200882246241916427custom 54003382985498525856custom 54201775900087161836custom 54183453097156070663custom 54200920428501166782custom 54202982742947690491

8 Aug 2026, 14:45 UTC32 views5 reactionsread 10 August 2026
Forwarded from @vflowerskisserPhoto

♡ Интерактив! Я вам: Вы и ваш не_ф/о как ароматы из фрагрантики Один хедканон Вы и ваш ф/о как два предмета Вы мне: Подписка на канал без дальнейшей отписки Репост этого поста в любой тгк Фото вас и вашего не_ф/о, название вашего не_сш, чутка о характерах, ваш юз Места 1 / 1О

custom 54200882246241916422custom 54200920428501166782custom 54202982742947690491

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

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

“ᥰᥱρᥱ᥊᧐днᥙκ ᴛ᧐κᥴᥙ᥊ᥱ᧘ [🧪🦭]” (@churchaloves1x), 10 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/churchaloves1x.

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.