Telegram RegisterThe public register of Telegram
Telegram profile photo for wielee

Channel

wielee

@wieleechu

On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry

28subscribers

-3 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-1001939232277
TypeChannel
Username@wieleechu
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live9 October 2026
Measurements held5
Confirmed unchanged2 times, most recently 9 October 2026
On Telegramt.me/wieleechu

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 30 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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

283129.57 August 2026 — 31 subscribers11 August 2026 — 31 subscribers20 August 2026 — 30 subscribers11 September 2026 — 29 subscribers29 September 2026 — 28 subscribers7 August 202629 September 2026
5 measurements spanning 53 days, net -3. 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 28–31 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Sept 2026, 00:3728-1
11 Sept 2026, 01:5629-1
20 Aug 2026, 23:0530-1
11 Aug 2026, 03:0131no change
7 Aug 2026, 10:5431first reading

Engagement

19 posts held, back to 20 March 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 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 19 posts for this entry, the most recent from 27 May 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

129 reactions across 19 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🍌129100.0%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 19 of the 19 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 129 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 20 March 2025 to 27 May 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

27 May 2025, 18:52 UTC72 views7 reactionsread 11 August 2026
Photo

Конец мая, а это значит, что я возвращаюсь к любимым камушкам

🍌7

8 May 2025, 09:48 UTC85 views5 reactionsread 11 August 2026

Мне это кажется издевательством

🍌5

8 May 2025, 09:48 UTC79 views5 reactionsread 11 August 2026

Как вы можете праздновать день победы, который подразумевает уважение к жертвам войны, в условиях войны?🥰

🍌5

3 May 2025, 09:29 UTC68 views7 reactionsread 11 August 2026

Ой, какой же сегодня день приятный, захотелось пожелать всем приятной субботы💋

🍌7

29 Apr 2025, 12:42 UTC51 views8 reactionsread 11 August 2026
Photo

Вчерашние намалёвки в тетради 🦶🦶

🍌8

20 Apr 2025, 10:39 UTC56 views7 reactionsread 11 August 2026
Photo

Ребята, давайте помянем мой любимый карандашик ;(

🍌7

11 Apr 2025, 04:43 UTC48 views5 reactionsread 11 August 2026

Я люблю дядюшек с баянами

🍌5

Showing the 12 most recent of 19 posts we hold for @wieleechu. 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.

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

“wielee” (@wieleechu), 28 subscribers as measured 29 September 2026. Telegram Register, tgregister.com/channel/wieleechu.

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.