Telegram RegisterThe public register of Telegram
Telegram profile photo for weHost.gg

Channel

weHost.gg

@wehosts

On this record: Growth · Engagement · Posts · Polls · Cite this entry

266subscribers

+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-1002046303235
TypeChannel
Username@wehosts
CreatedBetween 1 November 2023 and 4 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live24 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 24 August 2026
On Telegramt.me/wehosts

Growth

2662682677 August 2026 — 266 subscribers8 August 2026 — 266 subscribers16 August 2026 — 268 subscribers24 August 2026 — 266 subscribers7 August 202624 August 2026
4 measurements spanning 17 days. 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 266–268 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 18:08266-2
16 Aug 2026, 08:06268+2
8 Aug 2026, 09:01266no change
7 Aug 2026, 12:37266first reading

Engagement

4 posts held, back to 4 May 2024the 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 4 posts for this entry, the most recent from 23 April 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

8 Jan 2026, 22:45 UTC272 viewsread 8 August 2026

Hello, The upstream issue has now been fully resolved. The fix was implemented several hours ago, and we have been closely monitoring the situation since then. All services have been operating normally and remain stable. All affected customers will be compensated for the downtime. The appropriate credit will be added to your plan shortly. Thank you for your patience and understanding.

8 Jan 2026, 15:08 UTC281 viewsread 8 August 2026

Hello, We have identified an issue affecting the USA nodes. Our upstream providers are currently experiencing difficulties with propagating our IP prefixes to the global routing tables. The upstream providers have been contacted and are in the process of refreshing the prefix lists to resolve this issue. We will provide a further update as soon as we receive additional information from them. Thank you for your pat

4 May 2024, 22:19 UTC≈4,800 viewsread 8 August 2026
Poll

What do you mostly buy?

  1. RDP56%
  2. VPS30%
  3. Dedicated Server23%
  4. Web Hosting (Cpanel)13%

The shares total 122%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

Showing the 4 most recent of 4 posts we hold for @wehosts. 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.

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

4 May 2024, 22:19 UTCAnonymous Poll232 voters

What do you mostly buy?

  1. RDP56%
  2. VPS30%
  3. Dedicated Server23%
  4. Web Hosting (Cpanel)13%

The shares total 122%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 4 most recent posts we hold, published 4 May 2024 to 23 April 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

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

“weHost.gg” (@wehosts), 266 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/wehosts.

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.