Telegram RegisterThe public register of Telegram
Telegram profile photo for Сетка TG каналов

Channel

Сетка TG каналов

@pricevr777

On this record: Growth · Engagement · Posts · Citations · Cite this entry

41subscribers

-5 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002528618657
TypeChannel
Username@pricevr777
Created30 June 2025measured — dated from the channel’s first post
First recorded10 August 2026
Last confirmed live18 September 2026
Measurements held5
Confirmed unchanged2 times, most recently 18 September 2026
On Telegramt.me/pricevr777

Growth

414643.57 August 2026 — 46 subscribers10 August 2026 — 46 subscribers22 August 2026 — 44 subscribers30 August 2026 — 42 subscribers9 September 2026 — 41 subscribers7 August 20269 September 2026
5 measurements spanning 33 days, net -5. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 40–47 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 12:3641-1
30 Aug 2026, 08:2242-2
22 Aug 2026, 10:2744-2
10 Aug 2026, 14:1646no change
7 Aug 2026, 16:2846first reading

Engagement

2 posts held, back to 30 June 2025the 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 2 posts for this entry, the most recent from 15 January 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

15 Jan 2026, 06:01 UTC≈43,100 viewsread 10 August 2026

🎁Моя Сетка Telegram Каналов, размещение рекламного поста по формату: 48 часов закреп, пост остается в ленте - бессрочно. Любые иные варианты размещения обсуждаются по запросу. Запросить прайс пишите @vr777 🎁Crypto Priority 🇷🇺Тренды России | Новости 🤍Россия Вещает | Новости 🛒ТВОЙ WB 🎁PRO SPORT 📣Московский Портал 24 ⚠️Шок Новости | Срочно 🛍WB SHOP | Подборка 🎁AUTO RUSS Канал Про Тачки 💱Про Деньги | Новости 🌐Технологии

Showing the 2 most recent of 2 posts we hold for @pricevr777. 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

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 9 September 2026 — this entry's latest reading, not the date you are reading this.

“Сетка TG каналов” (@pricevr777), 41 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/pricevr777.

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.