Telegram RegisterThe public register of Telegram
Telegram profile photo for 泡沫公益改文件交流群(和平/三角洲/暗区)

Supergroup

泡沫公益改文件交流群(和平/三角洲/暗区)

@POMO666

Has discussion group

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

5,377members

+1,501 since we began measuring on 12 August 2026

315 online right now

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002267443787
TypeSupergroup
Username@POMO666
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded5 September 2026
Last confirmed live10 November 2026
Measurements held24
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/POMO666

Topic

Gaming — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 70% 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

3,8765,3774,626.512 August 2026 — 3,876 members13 August 2026 — 3,882 members16 August 2026 — 3,902 members19 August 2026 — 3,958 members23 August 2026 — 3,977 members26 August 2026 — 3,986 members29 August 2026 — 3,984 members1 September 2026 — 4,003 members5 September 2026 — 4,001 members5 September 2026 — 4,001 members10 September 2026 — 4,025 members14 September 2026 — 4,044 members18 September 2026 — 4,014 members5 October 2026 — 4,069 members12 October 2026 — 4,217 members15 October 2026 — 4,326 members18 October 2026 — 4,516 members21 October 2026 — 4,644 members25 October 2026 — 4,795 members28 October 2026 — 4,873 members31 October 2026 — 5,041 members3 November 2026 — 5,187 members6 November 2026 — 5,269 members10 November 2026 — 5,377 members12 August 202610 November 2026
24 measurements spanning 89 days, net +1,501. 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 3,651–5,602 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 24
Measured (UTC)MembersChange
10 Nov 2026, 00:455,377+108
6 Nov 2026, 08:315,269+82
3 Nov 2026, 10:015,187+146
31 Oct 2026, 00:445,041+168
28 Oct 2026, 04:474,873+78
25 Oct 2026, 03:144,795+151
21 Oct 2026, 23:054,644+128
18 Oct 2026, 11:504,516+190
15 Oct 2026, 07:274,326+109
12 Oct 2026, 13:054,217+148
5 Oct 2026, 16:564,069+55
18 Sept 2026, 12:404,014-30
14 Sept 2026, 06:194,044+19
10 Sept 2026, 07:004,025+24
5 Sept 2026, 20:224,001no change
5 Sept 2026, 08:574,001-2
1 Sept 2026, 17:284,003+19
29 Aug 2026, 22:053,984-2
26 Aug 2026, 19:033,986+9
23 Aug 2026, 10:123,977first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind 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 10 November 2026 — this entry's latest reading, not the date you are reading this.

“泡沫公益改文件交流群(和平/三角洲/暗区)” (@POMO666), 5,377 members as measured 10 November 2026. Telegram Register, tgregister.com/channel/POMO666.

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.