Telegram RegisterThe public register of Telegram
Telegram profile photo for 支付宝洗口令红包

Channel

支付宝洗口令红包

@DG23GFH15156

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

2subscribers

+1 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-1003633544907
TypeChannel
Username@DG23GFH15156
Created27 December 2025 — measured — dated from the channel’s first post
First recorded14 August 2026
Last confirmed live13 November 2026
Measurements held3
Confirmed unchanged3 times, most recently 13 November 2026
On Telegramt.me/DG23GFH15156

Topic

Hacking & security — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 27 October 2026 and assigned it the closest of 31 fixed categories, at 67% 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 the other topics.

Growth

121.57 August 2026 — 1 subscribers14 August 2026 — 1 subscribers27 October 2026 — 2 subscribers7 August 202627 October 2026
3 measurements spanning 81 days, net +1. 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 1–2 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Oct 2026, 11:212+1
14 Aug 2026, 23:461no change
7 Aug 2026, 19:141first reading

Engagement

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

Recent posts

27 Dec 2025, 15:39 UTC120 viewsread 14 August 2026

🔥都给我看过来!看过来!看过来! 🔥全网唯一做单现结算且无压的像目。 🔥有支付宝就能做,安全无风险洗金! 🔥单人日赚2000+ 无需压金0风险 🔥联系客服: https://t.me/hxzhifu8 如果你无法向我发消息,请发消息给机器人 : @hxzhifubot

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

“支付宝洗口令红包” (@DG23GFH15156), 2 subscribers as measured 27 October 2026. Telegram Register, tgregister.com/channel/DG23GFH15156.

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.