6 May 2025, 17:06 UTC223 viewsread 12 August 2026
The teamspeak proxy website will be terminated today. Read above why.
Channel
Beanes Teamspeak Proxy
@beanesproxy
On this record: Growth · Engagement · Posts · Citations · Cite this entry
72subscribers
-2 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001523392789 |
|---|---|
| Type | Channel |
| Username | @beanesproxy |
| Created | 13 November 2021 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 3 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 3 September 2026 |
| On Telegram | t.me/beanesproxy |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Sept 2026, 12:42 | 72 | -1 |
| 27 Aug 2026, 16:04 | 73 | -1 |
| 12 Aug 2026, 10:15 | 74 | no change |
| 12 Aug 2026, 10:04 | 74 | first reading |
Engagement
11 posts held, back to 13 November 2021 — 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 11 posts for this entry, the most recent from 6 May 2025. An engagement rate over an empty window would be a number about nothing.
Recent posts
30 Apr 2025, 22:24 UTC643 viewsread 12 August 2026
Teamspeak wants me to properly monitor proxies for illegal activities. However they do not want to provide any documentation / access to resources that would allow me to do this (like checking if a target server is blacklisted) Unfortunately due to this not being possible for me I will no longer pay for the hosting services of the proxy and it will be shut down. For the time being you can use the blacklist bypass b…
24 Apr 2025, 19:27 UTC312 viewsread 12 August 2026
File
Teamspeak Blacklist The proxy has been blacklisted by teamspeak, I'm waiting for my support ticket to be resolved. If you wish to still use the proxy you can use the following bat script to disable the teamspeak blacklist services.
20 Sept 2024, 19:27 UTC≈1,690 viewsread 12 August 2026
Teamspeak proxy is back There should no longer be certificate errors as its now a certificate of 15 years 🙏 Apparantly people still use this so heres the link: https://proxy.beanes.xyz
4 Feb 2024, 19:47 UTC≈1,490 viewsread 12 August 2026
Teamspeak proxy is back online If you still play (after all these years) you can create a teamspeak proxy on proxy.beanes.xyz
27 Dec 2022, 19:38 UTC912 viewsread 12 August 2026
Teamspeak proxy is back online. https://proxy.beanes.xyz/
17 Feb 2022, 09:44 UTC≈1,260 viewsread 12 August 2026
The site is back online.
20 Jan 2022, 17:55 UTC≈1,360 viewsread 12 August 2026
The site has been moved to https://proxy.beanes.xyz/
25 Nov 2021, 16:04 UTC≈1,420 viewsread 12 August 2026
If you get the error: Maximum number of connections with the same identity exceeded. Tell the server owner to set the permission for guest server group i_client_max_clones_uid to 75
13 Nov 2021, 17:48 UTC≈1,300 viewsread 12 August 2026
» Link: https://proxy.beanes.xyz » For any issues contact @Beaness » Version: stable You can also use ips like "teiko" (you do not need a numerical ip)
13 Nov 2021, 17:42 UTCviews —
Channel created
Showing the 11 most recent of 11 posts we hold for @beanesproxy. 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
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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
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 3 September 2026 — this entry's latest reading, not the date you are reading this.
“Beanes Teamspeak Proxy” (@beanesproxy), 72 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/beanesproxy.
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.