Telegram RegisterThe public register of Telegram

Channel

PROXY.LUXE

@proxy_luxe

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

228subscribers

+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-1001186833405
TypeChannel
Username@proxy_luxe
DescriptionНовости, оперативные сообщения о функционировании прокси-сервиса https://proxy.luxe Техподдержка: @andreyproxy ——————————————- News and updates on the proxy service https://proxy.luxe Technical support: @andreyproxy
CreatedBetween 1 April 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 August 2026
Measurements held2
On Telegramt.me/proxy_luxe

Growth

2286 Aug 2026, 16:41 — 228 subscribers7 Aug 2026, 03:00 — 228 subscribers6 Aug 2026, 16:417 Aug 2026, 03:00
2 measurements taken within a single day. 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 227–229 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 03:00228no change
6 Aug 2026, 16:41228first reading

Engagement

20 posts held, back to 9 March 2026the 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.

ERR · 30 days
104.8%
avg views ÷ 228 subscribers
Avg views / post
239
2 posts measured
Reaction rate
1.68%
reactions ÷ views · ER floor
Posts in window
2
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 1 of 2 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 17 July 2026
Posts held20 (9 March 202617 July 2026)
Views total478
Reactions total2
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 03:00 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
40
Videos
8
Links
60

Lifetime counters from Telegram’s own channel header, read 7 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.

Reaction mix

10 reactions across 5 posts, in 6 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
550.0%
110.0%
👍110.0%
👏110.0%
🔥110.0%
🤝110.0%

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 5 of the 20 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 10reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 9 March 2026 to 17 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.

Recent posts

17 Jul 2026, 11:44 UTC359 viewsread 7 August 2026
Photo

⚪️Мы собрали вопросы, которые чаще всего задают команде Cloaking.House, и подготовили короткие ответы. ❓Какие источники трафика поддерживает Cloaking.House? Сервис подходит для работы с Facebook, Google Ads, TikTok, Bing, нативными рекламными сетями и другими источниками, где требуется интеллектуальная фильтрация трафика. ❓Какие фильтры используются чаще всего? Самые популярные это GEO, устройство, браузер, ISP, VPN

15 Jul 2026, 08:34 UTC119 views2 reactionsread 7 August 2026
Forwarded from @miapet_itPhoto

💡 Запустили наш сайт miapet.ink Теперь у Miapet есть не только тг, но и свой отдельный дом(-ен). Пока это стартовая версия, дальше будем постепенно докручивать, добавлять материалы, обновлять разделы и собирать вокруг сайта нормальную инфраструктуру. Спасибо всем за поддержку! 🎁 @miapet_it

11

1 Jul 2026, 12:36 UTC512 viewsread 7 August 2026

Уважаемые пользователи! Сайт proxy.luxe работает. Спасибо за ожидание. —- Dear users! The proxy.luxe website is up and running. Thank you for your patience.

30 Jun 2026, 08:12 UTC511 views1 reactionsread 7 August 2026

Уважаемые пользователи! Сайт proxy.luxe временно не работает, из-за проблем у хостера в Нидерландах. В дата-центре Qupra продолжаются аварийно-восстановительные работы на системе кондиционирования. Для устранения неисправности привлечены сторонние специалисты, их прибытие ожидается к утру. Наши инженеры находятся на площадке Qupra. Извините за неудобства. —- Dear users, The site proxy.luxe is temporarily down due to

👏1

23 Jun 2026, 09:57 UTC539 views3 reactionsread 7 August 2026

Уважаемые пользователи! Мы принимаем оплату Webmoney (WMT). Купить WMT можно на бирже: https://exchanger.market/cards/home —- Dear users! We accept WebMoney (WMT) payments. You can purchase WMT at the exchange: https://exchanger.market/cards/home

👍1🔥1🤝1

3 Jun 2026, 16:47 UTC853 viewsread 7 August 2026

Уважаемые пользователи! Домен proxy.luxe больше недоступен с российских IP, по решению ркн. Для работы с сайтом используйте ВПН. —- Dear Users, The domain proxy.luxe is no longer accessible from Russian IP addresses, pursuant to a decision by Roskomnadzor. Please use a VPN to access the site.

3 Jun 2026, 05:33 UTC255 viewsread 7 August 2026

Уважаемые пользователи! Мы переехали, всё работает. —- Dear Users, We have moved—everything is up and running.

2 Jun 2026, 12:34 UTC252 viewsread 7 August 2026

Уважаемые пользователи. Мы переезжаем на новый европейский хостинг, сайт proxy.luxe будет какое-то время недоступен, пока не обновятся DNS. Спасибо за Ваше терпение и понимание. —- Dear Users, We are migrating to a new European hosting provider. The website proxy.luxe will be temporarily unavailable until the DNS records have updated. Thank you for your patience and understanding.

2 Jun 2026, 05:56 UTC221 views2 reactionsread 7 August 2026

Уважаемые пользователи! Наш сайт proxy.luxe скоро станет недоступен с российских IP из-за решения ркн. Для работы с сайтом используйте ВПН. —- Dear Users, Our website, proxy.luxe, will soon become inaccessible from Russian IP addresses due to a decision by Roskomnadzor. Please use a VPN to access the site.

2

27 May 2026, 14:37 UTC238 viewsread 7 August 2026

Работа сайта восстановлена. Спасибо за ожидание. ———————————————————————-- The website is back up and running. Thank you for your patience.

27 May 2026, 11:38 UTC233 viewsread 7 August 2026

Сетевая недоступность сервера в Нидерландах, где расположен наш сайт . О восстановлении работы сайта сообщим. Извините за неудобства. ———————————————————————-- The server located in the Netherlands, where our website is hosted, is currently inaccessible due to network issues. We will notify you once the site is back online. We apologize for the inconvenience.

26 May 2026, 16:47 UTC215 viewsread 7 August 2026

Уважаемые пользователи! Технические работы завершены. Спасибо за ожидание. —- Dear users! Maintenance work has been completed. Thank you for your patience.

Showing the 12 most recent of 20 posts we hold for @proxy_luxe. 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.

Citation-graph rank

Citation-graph rank — 118,967 of 1,160,990entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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.

Mentions

Named by 3 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.

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

“PROXY.LUXE” (@proxy_luxe), 228 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/proxy_luxe.

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.