24 Feb 2026, 18:52 UTC4 viewsread 12 August 2026
Photo
I found a great way to monetize my Telegram channel. Sharing it with you! Join Inside Ads and start earning. 💰 https://t.me/InsideAds_bot/open?startapp=r_5208401522
Channel
Proxy BMProto
@ProxyBMProto
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
7subscribers
+0 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 | -1002857224982 |
|---|---|
| Type | Channel |
| Username | @ProxyBMProto |
| Description | Proxy BMProto is a secure and efficient proxy protocol designed to protect privacy, encrypt data, and optimize network performance. Ideal for safe browsing, server security, and reliable data transfer. #ProxyBMProto #ProxyServer #SecureProxy #NetworkSecu |
| Created | 11 August 2025 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/ProxyBMProto |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 18:03 | 7 | no change |
| 7 Aug 2026, 17:01 | 7 | first reading |
Engagement
8 posts held, back to 11 August 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 8 posts for this entry, the most recent from 24 February 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 1
- Links
- 3
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
2 Feb 2026, 18:11 UTC7 viewsread 12 August 2026
Forwarded from @proxymtproto
Server: Unknown Port: 5777 Secret: eeRigzNJvXrFGRMCIMJdEA @ProxyMTProto
2 Feb 2026, 18:11 UTC5 viewsread 12 August 2026
Forwarded from @proxymtproto
Server: Unknown Port: 80 Secret: 7nnnAQIAAQAH8AMDhuJMOt0%3D @ProxyMTProto
11 Aug 2025, 02:09 UTC28 viewsread 12 August 2026
https://t.me/proxy?server=Focos-mokos.berlino-landcvixo.yokohama-1borino.eromatic.info.&port=443&secret=iORid5lJ237IiBMGYMQMdw== Join now
11 Aug 2025, 02:07 UTC26 viewsread 12 August 2026
https://t.me/proxy?server=World-press.Online-shop.speeker-voice.avadox-zhoan.info&port=144&secret=7gAA8A8Pd1VV____9QBuLmltZWRpYS5zdGVhbXBvd2VyZWQuY29t Join now
11 Aug 2025, 02:04 UTC2 viewsread 12 August 2026
Forwarded from @proxymtproto
Server: Unknown Port: 443 Secret: 7gAAAAAAAAAAAAAAAAAAAAB0Z2p1Lm9yZw%3D%3D @ProxyMTProto
11 Aug 2025, 02:02 UTCviews —
Channel photo updated
11 Aug 2025, 01:57 UTCviews —
Channel created
Showing the 8 most recent of 8 posts we hold for @ProxyBMProto. 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.
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
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.
“Proxy BMProto” (@ProxyBMProto), 7 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/ProxyBMProto.
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.