Channel
@pricehg
On this record: Topic · Growth · Engagement · Posts · Cite this entry
9subscribers
-1 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003818389038 |
|---|---|
| Type | Channel |
| Username | @pricehg |
| Created | 7 February 2026 — measured — dated from the channel’s first post |
| First recorded | 14 August 2026 |
| Last confirmed live | 2 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 2 October 2026 |
| On Telegram | t.me/pricehg |
Marketing & affiliate — 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 2 October 2026 and assigned it the closest of 31 fixed categories, at 68% 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 |
|---|---|---|
| 2 Oct 2026, 17:39 | 9 | -1 |
| 16 Aug 2026, 14:04 | 10 | no change |
| 14 Aug 2026, 23:01 | 10 | first reading |
4 posts held, back to 7 February 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 4 posts for this entry, the most recent from 2 April 2026. An engagement rate over an empty window would be a number about nothing.
🔍Услуга «Заместитель» от @higley_gr 💵• На 1 неделю: 2000₽ (сделки до 1500₽, руч после до 1000₽) 💵• На 2 недели: 4000₽ (сделки до 3000₽, руч после до 2000₽) 💵• На 3 недели: 6000₽ (сделки до 4000₽, руч после 3000₽) ➡️Описание услуги: ⚠️Регулярная выдача сделок вам в ЛС. После срока заместителя вы получаете вечное ручение на определённую сумму, указанную в прайсе⚠️
🔍Стажировка от @higley_gr 💵• 900₽ — 15 сделок. Вечное ручение до 500₽ после стажировки. 💵• 1800₽ — 30 сделок. Вечное ручение до 1000₽ после стажировки. 💵• 3000₽ — 50 сделок. Вечное ручение до 1555₽ после стажировки. 💵• 5500₽ — 100 сделок. Вечное ручение до 3333₽ после стажировки. ➡️Описание услуги: 🌛Покупая данную услугу, вы гарантировано получаете определённое количество сделок от меня. После конца стажировки вы п…
🌜Ручение от @higley_gr 💵Стоимость услуги: Сумма доверия +50% Пример: 500+50% = 750₽ 😶Преимущества: 🦋• Регулярное выдача сделок до вашей суммы ручения; 🦋• Комфортный коллектив подопечных в чатах; 🦋• Личная помощь по различным вопросам. 😈Примечания: • Минимальная сумма доверия: 500₽ • Срок ручения: до первого скама
Channel created
Showing the 4 most recent of 4 posts we hold for @pricehg. 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.
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 2 October 2026 — this entry's latest reading, not the date you are reading this.
“Цена услуг” (@pricehg), 9 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/pricehg.
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.