^ Ad for friend, good proxies!

Channel
BluGo 2.0
@shopsblugo
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
535subscribers
+10 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 | -1001921001358 |
|---|---|
| Type | Channel |
| Username | @shopsblugo |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 1 October 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 1 October 2026 |
| On Telegram | t.me/shopsblugo |
Topic
Other / unclassifiable — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 33% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Oct 2026, 14:00 | 535 | +6 |
| 17 Sept 2026, 01:20 | 529 | -1 |
| 8 Sept 2026, 09:22 | 530 | +2 |
| 29 Aug 2026, 09:53 | 528 | +3 |
| 8 Aug 2026, 04:01 | 525 | no change |
| 7 Aug 2026, 12:47 | 525 | first reading |
Engagement
20 posts held, back to 28 April 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 20 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 1m 03s
- Average length
- 1m 03s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Recent posts
🟢🟢🟢🟢🟢🟢🟢🟢🟢🟢🟢 Enjoy the best proxy experience with our service, designed by former proxy users who understand the need for quality and reliability. 🚀 What they offer - Over 40M undetected IPs - Fast proxy speeds - Stable connections - UDP supported - HTTP/3 available 💵 Pricing - From 1 GB - $1.20/GB - From 25 GB - $1.10/GB - From 50 GB - $1.00/GB - From 100 GB - $0.90/GB - From 250 GB - $0.80/GB - From 500 GB - $0.7…
GMX.com accounts (Imap Enabled) Wont die good for all tasks Mail.com Accounts (mixed) are both available message me @blugoshop
https://t.me/multimailgen
Ran for 24 hours 15.7k GMX made CPM is pretty decent right now I just started mailcom at the start of this hour and will update in next few hours A few spots to buy licenses are ready if anyone wanting just give me a message. @blugoshop
Got 3.6k GMX.com spare not on preorder right now Message me if you need them @blugoshop
Channel for updates https://t.me/multimailgen If you have any questions or want to buy @blugoshops
MultiMail - GMX + Mail.com Generator GMX Features Free CaptchaFox Solver (will be paid later down the line, cheap) IMAP Enabler (Comes with Free Solver, paid later down line, will be much cheaper than captchafox) Thread Settings (Up to 75 threads, Will be increased as we test more) GMX Checker (Check accounts very fast) Auto Pause (Gens much better at start of hour and to save proxies the gen pauses after 25 minutes…
Lots of Mail.com in stock right now if anyone needs. @blugoshops
Have 10k + GMX.com ready to go right now message me if you need @blugoshop
Can generate Mail.com accounts again quite fast. And gmx.com also being created but its much slower so let me know how many you need in advance. In the next week or so i will be selling licenses for GMX, Mail.com generator. this will come with a free solver for the first month or so they will be paid per k (very cheap tho) Give me a message if you need anything or have any questions! @blugoshop
Got some captcha solvers if anyone needs theM friendlycap/capfox also some new domains @firemail.de (quite a few domains for this, imap enabled good for email sending @mailbox.org (has imap, cant send emails good for verifying accs) can make any script for email sending if needed @blugoshop
Showing the 12 most recent of 20 posts we hold for @shopsblugo. 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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@shopsblugo named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 9 August 2026 – 9 August 2026
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 1 October 2026 — this entry's latest reading, not the date you are reading this.
“BluGo 2.0” (@shopsblugo), 535 subscribers as measured 1 October 2026. Telegram Register, tgregister.com/channel/shopsblugo.
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.