22 May 2026, 17:40 UTC844 viewsread 10 August 2026
I recommend NO further use on the @automullvadbot & anything associated with @B4Unetwork DO NOT USE THESE BOTS
Channel
Mullvad B4U
@MullvadB4U
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
51subscribers
+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 | -1003942299229 |
|---|---|
| Type | Channel |
| Username | @MullvadB4U |
| Created | Between 1 April 2026 and 22 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 3 October 2026 |
| On Telegram | t.me/MullvadB4U |
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 29 September 2026 and assigned it the closest of 31 fixed categories, at 56% 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 |
|---|---|---|
| 3 Oct 2026, 04:00 | 51 | +2 |
| 17 Sept 2026, 16:20 | 49 | +2 |
| 9 Sept 2026, 01:17 | 47 | -2 |
| 24 Aug 2026, 17:24 | 49 | +1 |
| 16 Aug 2026, 20:26 | 48 | +2 |
| 10 Aug 2026, 14:30 | 46 | no change |
| 7 Aug 2026, 16:46 | 46 | first reading |
Engagement
1 post held, back to 22 May 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 1 post for this entry, the most recent from 22 May 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Showing the 1 most recent of 1 post we hold for @MullvadB4U. 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 3 October 2026 — this entry's latest reading, not the date you are reading this.
“Mullvad B4U” (@MullvadB4U), 51 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/MullvadB4U.
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.