Telegram RegisterThe public register of Telegram
Telegram profile photo for non-human

Channel

non-human

@urpledp_hr

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

22subscribers

+0 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1004494983117
TypeChannel
Username@urpledp_hr
Descriptionкр fruittos twt
CreatedBetween 1 June 2026 and 9 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live16 September 2026
Measurements held2
On Telegramt.me/urpledp_hr

Growth

228 August 2026 — 22 subscribers11 August 2026 — 22 subscribers8 August 202611 August 2026
2 measurements spanning 3 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 21–23 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 13:1722no change
8 Aug 2026, 08:0222first reading

Engagement

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

What this channel posts

Photos
11
Videos
1
Links
7

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

82 reactions across 19 posts, in 7 distinct kinds. The most used accounts for 23.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54360578965782115071923.2%
🆒1923.2%
👍1619.5%
👾911.0%
😎911.0%
custom 521972964094328672256.10%
🤷‍♂56.10%

Custom emoji. 2 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 19 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 82 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 9 August 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, 18:01 UTC10 views4 reactionsread 11 August 2026

мне остается только ждать. . . . конец записи.

🆒2👍1😎1

9 Aug 2026, 18:01 UTC10 views5 reactionsread 11 August 2026

. . . с этого момента прошло две недели. он так и не связался со мной. я не понимаю, почему? он всегда сообщал мне, если у него появлялись какие-то дела. а теперь? он точно здесь. он так и не покидал территорию смп. я знаю. но он даже не увиделся со мной. что-то случилось? я не знаю чего-то? он перестал мне доверять? я знаю, что с ним нельзя связываться до того, пока он сам не напишет. но я не могу, тревога сжира…

custom 52197296409432867222custom 54360578965782115072🆒1

9 Aug 2026, 17:56 UTC10 views5 reactionsread 11 August 2026

⭐️: . . . да, ты права. спасибо. ⭐️: я думаю, что мне.. пора возвращаться. 👻: конечно. перевари всю эту инфу и отдохни там. ⭐️: . . . как скажешь

😎3👍1🆒1

9 Aug 2026, 17:54 UTC10 views5 reactionsread 11 August 2026
Photo

👻: венера, послушай. . . 👻: в этом нет ничего такого. все в курсе, что вы с «👤» были достаточно близки. 👻: ты ведь сам на опыте знаешь, что «👤» безумно скрытный. как и ты. уверена, что он свяжется с тобой, просто позже. так будет безопаснее для вас двоих. он, думаю, тоже это понимает.

👾3🆒1custom 52197296409432867221

9 Aug 2026, 17:51 UTC10 views4 reactionsread 11 August 2026

👻: ого. . . нехило тебя так триггернуло. 👻: . . .

custom 54360578965782115072👍1🆒1

9 Aug 2026, 17:50 UTC10 views4 reactionsread 11 August 2026

👻: . . . ничего особенного. сказал, что в смп есть дела, поэтому он вернется на некоторое время сюда. мистер загадка не хотел это все обсуждать через пейджер. ⭐️: это. . . неудивительно. 👻: . . . 👻: я думала, что ты будешь безумно рад и всё такое. . . ⭐️: а по мне не видно?

👾2🆒1custom 54360578965782115071

9 Aug 2026, 17:50 UTC10 views4 reactionsread 11 August 2026

⭐️: что он. . . что он сказал?

🤷‍♂2👍1custom 54360578965782115071

9 Aug 2026, 17:49 UTC10 views4 reactionsread 11 August 2026

👻: ты. . . ты не знал? я думала, что он, типа, связался с тобой первым... ⭐️: нет. . . нет, от него не было ни слова. 👻: мда, прикинь, его не было слышно полгода, а теперь—

🆒2👍1custom 54360578965782115071

9 Aug 2026, 17:44 UTC10 views4 reactionsread 11 August 2026

❌❌❌❌. . .❌❌❌❌❌

custom 52197296409432867222👍1custom 54360578965782115071

9 Aug 2026, 17:43 UTC10 views4 reactionsread 11 August 2026

👻: а, и кстати. . . 👻: «👤» вышел на связь

👍2🆒1custom 54360578965782115071

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

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

“non-human” (@urpledp_hr), 22 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/urpledp_hr.

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.