26 Jun 2025, 18:30 UTC≈2,530 viewsread 12 August 2026
Отзывы 📍
Channel
Прайс For Lee Heeseung
@PriceHess
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
8subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002767877037 |
|---|---|
| Type | Channel |
| Username | @PriceHess |
| Created | Between 1 June 2025 and 15 June 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/PriceHess |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 14:32 | 8 | no change |
| 6 Aug 2026, 22:29 | 8 | first reading |
Engagement
3 posts held, back to 15 June 2025 — 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 pageof 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 June 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 1
- Links
- 1
Lifetime counters from Telegram’s own channel header, read 12 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.
Recent posts
15 Jun 2025, 21:04 UTC≈2,660 viewsread 12 August 2026
За приход не отвечаю, зависит от тематики канала Могу отказать в тематике постов, например таких, как 18+ Звёзды и рубли возврату не принадлежат, если я вдруг уже добила ваш пост
15 Jun 2025, 21:04 UTC≈3,700 viewsread 12 August 2026
Photo
Прайс от @hess01le Просмотры за рубли: 100пм - 20р 200пм - 35р 300пм - 50р 400пм - 55р 500пм - 60р 600пм - 75р 700пм - 90р Просмотры за звёзды: 100пм - 10⭐️ 150пм - 15⭐️ 200пм - 15⭐️ 300пм - 25⭐️ 400пм - 35⭐️ 500пм - 50⭐️ 600пм - 60⭐️ 700пм - 70⭐️ ⊹ ₊ ⁺‧₊˚ ♡ ପ(๑•ᴗ•๑)ଓ ♡˚₊‧⁺ ₊ ⊹ Реклама на время: 1ч - 15⭐️ ; 25р 4ч - 25⭐️ ; 40р 12ч - 40⭐️ ; 60р 2 дня - 50⭐️ ; 100р Закреп и подгоны бесплатные Шаблон и подгоны дела…
Showing the 3 most recent of 3 posts we hold for @PriceHess. 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
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Прайс For Lee Heeseung” (@PriceHess), 8 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/PriceHess.
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.