🌟🌟
💘6❤🔥2
Signed пенчи лмао

Channel
@penchilelele
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
420subscribers
-14 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001684477282 |
|---|---|
| Type | Channel |
| Username | @penchilelele |
| Created | 28 October 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 8 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/penchilelele |
Other / unclassifiable — 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 61% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 14:18 | 420 | -8 |
| 9 Sept 2026, 13:59 | 428 | -5 |
| 31 Aug 2026, 01:25 | 433 | -6 |
| 23 Aug 2026, 09:53 | 439 | +8 |
| 16 Aug 2026, 01:45 | 431 | -2 |
| 9 Aug 2026, 08:32 | 433 | -1 |
| 8 Aug 2026, 11:00 | 434 | no change |
| 8 Aug 2026, 10:56 | 434 | first reading |
15 posts held, back to 28 July 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 15 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
1,127 reactions across 14 posts, in 11 distinct kinds. The most used accounts for 19.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5278547117823010018 | 214 | 19.0% | |
| 💘 | 213 | 18.9% | |
| custom 5447529032671324495 | 155 | 13.8% | |
| custom 5208523839339771238 | 146 | 13.0% | |
| ❤ | 123 | 10.9% | |
| custom 5267494320134455084 | 109 | 9.67% | |
| 💋 | 70 | 6.21% | |
| ❤🔥 | 48 | 4.26% | |
| 🔥 | 37 | 3.28% | |
| 💅 | 9 | 0.799% | |
| 😭 | 3 | 0.266% |
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 14 of the 15 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 1,127 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 28 July 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.
🌟🌟
💘6❤🔥2
Signed пенчи лмао
я недевственник 🥺🥺
💋28custom 527854711782301001825custom 544752903267132449520❤🔥12🔥8💘3custom 52085238393397712383❤2
Signed пенчи лмао
File, posted without a caption
💘13custom 54475290326713244959💅7❤1
Signed пенчи лмао
あなたの中には空虚しかありません 💘
💘37custom 526749432013445508428custom 527854711782301001826❤14❤🔥3🔥3custom 54475290326713244953
Signed пенчи лмао
жертвы фишерского гаража ❤️❤️
custom 526749432013445508431custom 527854711782301001831❤28❤🔥8custom 54475290326713244956💋4🔥4💘2
Signed пенчи лмао
я вас люю дурачки 🫰🫰
💘23custom 527854711782301001818❤16🔥4custom 52674943201344550843❤🔥1
Signed пенчи лмао
Аврлдь.ыыпол😁😁👍
💘35custom 520852383933977123833custom 544752903267132449532custom 52785471178230100189❤3custom 52674943201344550843🔥2❤🔥1
Signed пенчи лмао
клубничная темка. фулл будет в комментариях. 😕
❤35custom 544752903267132449535💘31❤🔥5🔥5custom 52674943201344550845custom 52085238393397712384custom 52785471178230100184
Signed пенчи лмао
че за урод
custom 520852383933977123822custom 527854711782301001817❤13💋7❤🔥3💘1
Signed пенчи лмао
Channel photo updated
опять ч господи боже
💋31custom 520852383933977123828custom 527854711782301001826custom 52674943201344550846💘4❤🔥3🔥3❤2
Signed пенчи лмао
соскучилис по моим порисулькам да
custom 520852383933977123817custom 544752903267132449513custom 52674943201344550848❤4💘2❤🔥1🔥1
Signed пенчи лмао
Showing the 12 most recent of 15 posts we hold for @penchilelele. 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.
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.
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.
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.
“гнилой пенчи 🥩” (@penchilelele), 420 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/penchilelele.
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.