🌳Еще один день, наполненный новыми встречами, впечатлениями и знакомством с Папушево Парк!
custom 53301496981855034692custom 53279023436629676751custom 53302548862295484781

Channel
@papushevopark
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
605subscribers
+12 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001510605499 |
|---|---|
| Type | Channel |
| Username | @papushevopark |
| Created | Between 1 July 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/papushevopark |
Real estate — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 14 Sept 2026, 07:38 | 605 | +3 |
| 6 Sept 2026, 22:40 | 602 | -6 |
| 28 Aug 2026, 12:23 | 608 | +9 |
| 20 Aug 2026, 15:57 | 599 | +2 |
| 14 Aug 2026, 08:36 | 597 | +4 |
| 6 Aug 2026, 17:48 | 593 | no change |
| 6 Aug 2026, 06:38 | 593 | first reading |
3 posts held, back to 17 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 3 posts for this entry, the most recent from 26 July 2026. An engagement rate over an empty window would be a number about nothing.
9 reactions across 3 posts, in 4 distinct kinds. The most used accounts for 33.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5327902343662967675 | 3 | 33.3% | |
| custom 5330149698185503469 | 3 | 33.3% | |
| custom 5330254886229548478 | 2 | 22.2% | |
| custom 5330252584127076337 | 1 | 11.1% |
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 3 of the 3 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 9 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 3 most recent posts we hold, published 17 July 2026 to 26 July 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.
🌳Еще один день, наполненный новыми встречами, впечатлениями и знакомством с Папушево Парк!
custom 53301496981855034692custom 53279023436629676751custom 53302548862295484781
🏘️ Edelweiss — свет, собранный в форме дома. Панорамные окна наполняют пространство естественным освещением, а строгая архитектура направляет его, создавая мягкую игру теней и объёма. Натуральные материалы усиливают это ощущение — дом будто живёт вместе с окружающей природой. Это резиденция, где свет становится частью архитектуры. 🌳
custom 53279023436629676751custom 53301496981855034691custom 53302525841270763371
Есть места, которые объединяет не только локация, но и философия. Папушево Парк – это пространство, где современный комфорт сочетается с природой, приватностью и вниманием к качеству жизни. Здесь создается среда для тех, кто ценит время, спокойствие и эстетику каждого дня. Именно поэтому HEDO Lounge стал частью этого места. Нас объединяет стремление создавать сервис и атмосферу, в которую хочется возвращаться снова…
custom 53279023436629676751custom 53302548862295484781
Showing the 3 most recent of 3 posts we hold for @papushevopark. 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.
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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“Папушево Парк | Элитный коттеджный поселок” (@papushevopark), 605 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/papushevopark.
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.