Telegram RegisterThe public register of Telegram
Telegram profile photo for 红旗广告代发

Channel

红旗广告代发

@erethryjtukiuo

On this record: Topic · Growth · Engagement · Posts · Handles named that no longer answer · Cite this entry

5subscribers

-2 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-1001925873179
TypeChannel
Username@erethryjtukiuo
Created9 April 2024 — measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live2 October 2026
Measurements held4
Confirmed unchanged1 time, most recently 2 October 2026
On Telegramt.me/erethryjtukiuo

Topic

Marketing & affiliate — 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 2 October 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

5767 August 2026 — 7 subscribers12 August 2026 — 7 subscribers17 September 2026 — 6 subscribers2 October 2026 — 5 subscribers7 August 20262 October 2026
4 measurements spanning 56 days, net -2. 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 5–7 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Oct 2026, 06:595-1
17 Sept 2026, 03:166-1
12 Aug 2026, 17:157no change
7 Aug 2026, 12:327first reading

Engagement

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

Recent posts

11 Apr 2024, 15:43 UTC139 viewsread 12 August 2026

联系: @hqgg999,双向联系: @hqgg999bot,🔥🔥🔥接广告代发,群发,私信,拉人,拉群,出质量群,出飞机号,代开会员,频道(群组)上粉,强拉,帖子浏览,表情代刷等。 🌹另外出群发软件!专业群发不死号🌹

11 Apr 2024, 14:52 UTC139 viewsread 12 August 2026

联系: @hqgg999,双向联系: @hqgg999bot,🔥🔥🔥接广告代发,群发,私信,拉人,拉群,出质量群,出飞机号,代开会员,频道(群组)上粉,强拉,帖子浏览,表情代刷等。🌹另外出群发软件!🌹

10 Apr 2024, 07:26 UTC142 viewsread 12 August 2026

联系: @hqgg999,双向联系: @hqgg999bot,接广告代发,拉群,频道上粉,私信等业务,另外出群发软件

Showing the 4 most recent of 4 posts we hold for @erethryjtukiuo. 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 2 October 2026 — this entry's latest reading, not the date you are reading this.

“红旗广告代发” (@erethryjtukiuo), 5 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/erethryjtukiuo.

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.