Telegram RegisterThe public register of Telegram
Telegram profile photo for 3chuj1

Channel

3chuj1

@chujowytest

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

5subscribers

+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-1002529533116
TypeChannel
Username@chujowytest
Created13 May 2025 — measured — dated from the channel’s first post
First recorded13 August 2026
Last confirmed live18 September 2026
Measurements held2
On Telegramt.me/chujowytest

Growth

57 August 2026 — 5 subscribers13 August 2026 — 5 subscribers7 August 202613 August 2026
2 measurements spanning 5 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 4–6 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 01:485no change
7 Aug 2026, 15:565first reading

Engagement

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

Recent posts

13 May 2025, 08:14 UTC12 viewsread 13 August 2026

Connected channels: @chujowytest Status: Active. Pause posting: /channel__pause_chujowytest Disconnect channel: /channel__delete_chujowytest

13 May 2025, 04:26 UTC13 viewsread 13 August 2026

{ "update_id": 937172593, "channel_post": { "message_id": 8, "sender_chat": { "id": -1002529533116, "title": "chuj", "username": "chujowytest", "type": "channel" }, "chat": { "id": -1002529533116, "title": "chuj", "username": "chujowytest", "type": "channel" }, "date": 1747110403, "text": "/socials", "entities": [ { "offset": 0, "length": 8, "type": "bot_comman…

13 May 2025, 03:03 UTC8 viewsread 13 August 2026

{ "update_id": 937172561, "my_chat_member": { "chat": { "id": -1002529533116, "title": "chuj", "username": "chujowytest", "type": "channel" }, "from": { "id": 694008352, "is_bot": false, "first_name": "zarabiajmyrazem", "username": "zarobki24" }, "date": 1747105385, "old_chat_member": { "user": { "id": 285793787, "is_bot": true, "first_name": "Show Json Bot", "…

Showing the 12 most recent of 15 posts we hold for @chujowytest. 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 13 August 2026 — this entry's latest reading, not the date you are reading this.

“3chuj1” (@chujowytest), 5 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/chujowytest.

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.