Channel
@PPark1ns
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
143subscribers
-8 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003828597322 |
|---|---|
| Type | Channel |
| Username | @PPark1ns |
| Created | Between 1 February 2026 and 5 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/PPark1ns |
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 25 September 2026 and assigned it the closest of 31 fixed categories, at 86% 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 |
|---|---|---|
| 26 Sept 2026, 20:01 | 143 | -7 |
| 11 Sept 2026, 17:57 | 150 | -3 |
| 2 Sept 2026, 09:03 | 153 | -2 |
| 26 Aug 2026, 11:58 | 155 | +2 |
| 19 Aug 2026, 12:14 | 153 | +2 |
| 11 Aug 2026, 11:01 | 151 | no change |
| 11 Aug 2026, 10:54 | 151 | first reading |
10 posts held, back to 5 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 10 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
167 reactions across 4 posts, in 9 distinct kinds. The most used accounts for 17.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5278425681917673092 | 29 | 17.4% | |
| custom 5247155042942746838 | 26 | 15.6% | |
| custom 5276112292272960008 | 24 | 14.4% | |
| custom 5426927504776522852 | 24 | 14.4% | |
| custom 5190890623472786416 | 15 | 8.98% | |
| custom 5452044340379550409 | 14 | 8.38% | |
| custom 5246746432639106966 | 13 | 7.78% | |
| custom 5276379550907922999 | 11 | 6.59% | |
| custom 5427125532833641644 | 11 | 6.59% |
Custom emoji. Every row above is a 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 4 of the 10 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 167 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 5 July 2026 to 11 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.
🖤ˏˋ ┈─𝐀𝐍𝐎𝐍 𝐓𝐈𝐌𝐄. 𝖿𝗋𝗈𝗆 𝗒𝗈𝗎:: • Репост на свой дневник. (Для охвата) • Подписка. (Без отписок после) • Ссылка на дневник. 𝖿𝗋𝗈𝗆 𝗆𝖾:: • Ваш канал простыми:: да, нет, возможно. (Без объяснений почему) ┈─> 𝐀𝐍𝐎𝐍.
Sticker, posted without a caption
🤩🤩🤩🤩🤩🤩🤩🤩🤩 🔤ith: my favorite girl 🔤Присутствуют отклонения от канона. написанное может отличаться от канона персонажей или дневников. создано исключительно в юмористических целях.🔤 #connection #messager
custom 542692750477652285213custom 524715504294274683811custom 52784256819176730929custom 51908906234727864165custom 54271255328336416443custom 52467464326391069661custom 52761122922729600081
Sticker, posted without a caption
🔤ne for the road, ooh ooh One for the road, ooh ooh 🔤rom the bottom of your heart, the relegation zone I saw this coming from the start The shake rattle and roll The cracks in blackout blinds cast patterns on the ceiling But you're feeling fine I thought it was dark outside I thought it was dark outside 🔤ne for the road So we all get back to yours and you sit and talk to me on the floor There's no need to show me r…
custom 524715504294274683813custom 54269275047765228529custom 54520443403795504099custom 51908906234727864166custom 54271255328336416445custom 52467464326391069664custom 52784256819176730923custom 52761122922729600082
Sticker, posted without a caption
🤩🤩🤩🤩🤩🤩🤩🤩🤩 🔤ith: my love boyfriend 🔤Присутствуют отклонения от канона. написанное может отличаться от канона персонажей или дневников. создано исключительно в юмористических целях.🔤 #lover #messager
custom 52761122922729600089custom 52784256819176730929custom 52467464326391069668custom 54520443403795504094custom 51908906234727864163custom 54271255328336416443custom 54269275047765228522custom 52471550429427468381
Sticker, posted without a caption
🔠🔡🔡🔡🔡🔡🔡🔡 🔡🔡🔡🔡🔡 🔡 🔡🔡🔡🔡 🐾Когда я умру, вспомни меня, когда почувствуешь аромат цветочных духов 🐾Когда я умру, вспомни меня в сообщениях, написанных с ошибками и капсом 🐾Когда я умру, вспомни мои частые, иногда глупые голосовые в разное время 🐾Когда я умру, вспомни меня в любви к путешествиям и воспоминаниям 🐾Когда я умру, вспомни меня, когда будешь смотреть "Чёрная весна", "Фишер", "Пророк. История Александр…
custom 527611229227296000812custom 527637955090792299911custom 52784256819176730928custom 51908906234727864161custom 52471550429427468381custom 54520443403795504091
Sticker, posted without a caption
Showing the 10 most recent of 10 posts we hold for @PPark1ns. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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 33 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. The 22 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
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.
@PPark1ns named 3 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
References a handle that is not a live channel — we have no record it ever was one.
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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“𝑺𝑷𝑨𝑹𝑲𝑳𝑰𝑵𝑮 𝑭𝑬𝑬𝑳𝑰𝑵𝑮𝑺” (@PPark1ns), 143 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/PPark1ns.
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.