Telegram RegisterThe public register of Telegram
Telegram profile photo for ~пепел в худи

Channel

~пепел в худи

@pepel_v_hudi

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

527subscribers

+17 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-1002811261397
TypeChannel
Username@pepel_v_hudi
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/pepel_v_hudi

Topic

Personal blog — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 21 September 2026 and assigned it the closest of 31 fixed categories, at 80% 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.

Growth

5015275147 August 2026 — 510 subscribers7 August 2026 — 510 subscribers8 August 2026 — 509 subscribers15 August 2026 — 508 subscribers22 August 2026 — 519 subscribers30 August 2026 — 504 subscribers8 September 2026 — 501 subscribers17 September 2026 — 527 subscribers7 August 202617 September 2026
8 measurements spanning 42 days, net +17. 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 497–531 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 18:41527+26
8 Sept 2026, 21:21501-3
30 Aug 2026, 09:28504-15
22 Aug 2026, 22:33519+11
15 Aug 2026, 08:05508-1
8 Aug 2026, 01:13509-1
7 Aug 2026, 04:31510no change
7 Aug 2026, 04:18510first reading

Engagement

20 posts held, back to 5 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 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.

Reaction mix

130 reactions across 20 posts, in 5 distinct kinds. The most used accounts for 38.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54114884159023771505038.5%
custom 52020056079928203893325.4%
custom 53708743934025567062317.7%
1612.3%
custom 522659767160671115086.15%

Custom emoji. 4 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 20 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 130 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 5 August 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.

Recent posts

6 Aug 2026, 22:31 UTC34 views6 reactionsread 7 August 2026

Вечером покидаю ваши поздравления из лички

custom 52020056079928203892custom 53708743934025567062custom 54114884159023771502

6 Aug 2026, 22:30 UTC29 views3 reactionsread 7 August 2026
Forwarded from @pepelnahudi168

Надя с др я ей подарок уже подарила

custom 52020056079928203891custom 53708743934025567061custom 54114884159023771501

6 Aug 2026, 22:25 UTC25 views3 reactionsread 7 August 2026
Forwarded from @julilospxlsmsms

надю с дршк 🌹

custom 52020056079928203891custom 52265976716067111501custom 54114884159023771501

6 Aug 2026, 22:24 UTC36 views3 reactionsread 7 August 2026

С днем рождения!!!!

1custom 52020056079928203891custom 54114884159023771501

Signed maklinchik

6 Aug 2026, 21:24 UTC39 views9 reactionsread 7 August 2026
Forwarded from @pepel_asya

поздравляю пепел в худи с дршкой!!!!

custom 54114884159023771505custom 52020056079928203892custom 53708743934025567062

6 Aug 2026, 21:14 UTC43 views9 reactionsread 7 August 2026
Forwarded from @biskviv

любимку Надю (пепел в худи) с днюхой!

custom 52265976716067111503custom 53708743934025567063custom 54114884159023771503

6 Aug 2026, 21:14 UTC23 views10 reactionsread 7 August 2026
Forwarded from @pepelizaaa

Надю с днём рождения!!!🩷

custom 53708743934025567064custom 52020056079928203893custom 52265976716067111503

6 Aug 2026, 21:12 UTC43 views13 reactionsread 7 August 2026
Forwarded from @dillonixsss

пепел в худи, зая с дршкой!🎉 будь всегда такой же красивой и хорошей 🫶🏼 люблюю

5custom 52020056079928203894custom 54114884159023771504

6 Aug 2026, 21:01 UTC59 views10 reactionsread 7 August 2026

с дрешкой моя!!💕💕

custom 52020056079928203895custom 541148841590237715021custom 52265976716067111501custom 53708743934025567061

Signed fannahudi

6 Aug 2026, 20:59 UTC61 views4 reactionsread 7 August 2026

Минута

custom 54114884159023771502custom 52020056079928203891custom 53708743934025567061

6 Aug 2026, 20:50 UTC62 views12 reactionsread 7 August 2026

Я потом обязательно выложу все поздравления сюда

custom 537087439340255670643custom 54114884159023771503custom 52020056079928203892

6 Aug 2026, 20:30 UTC69 views11 reactionsread 7 August 2026

Пол часа до дня рождения

custom 52020056079928203897custom 53708743934025567062custom 54114884159023771502

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

“~пепел в худи” (@pepel_v_hudi), 527 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/pepel_v_hudi.

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.