Telegram RegisterThe public register of Telegram
Telegram profile photo for Candles Crusher (CC)πŸ“Š

Supergroup

Candles Crusher (CC)πŸ“Š

@liqudity883

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

2,984members

-308 since we began measuring on 7 August 2026

160 online right now

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

Register entry

Telegram ID-1001934960797
TypeSupergroup
Username@liqudity883
CreatedBetween 1 April 2023 and 31 October 2023 β€” estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 September 2026
Last confirmed live27 October 2026
Measurements held22
Confirmed unchanged1 time, most recently 27 October 2026
On Telegramt.me/liqudity883

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

2,9843,2923,1387 August 2026 β€” 3,292 members8 August 2026 β€” 3,288 members11 August 2026 β€” 3,286 members15 August 2026 β€” 3,272 members18 August 2026 β€” 3,255 members22 August 2026 β€” 3,259 members25 August 2026 β€” 3,249 members28 August 2026 β€” 3,238 members30 August 2026 β€” 3,229 members3 September 2026 β€” 3,202 members8 September 2026 β€” 3,176 members10 September 2026 β€” 3,176 members12 September 2026 β€” 3,150 members15 September 2026 β€” 3,152 members28 September 2026 β€” 3,108 members5 October 2026 β€” 3,069 members12 October 2026 β€” 3,039 members15 October 2026 β€” 3,025 members18 October 2026 β€” 3,015 members21 October 2026 β€” 3,006 members24 October 2026 β€” 2,997 members27 October 2026 β€” 2,984 members7 August 202627 October 2026
22 measurements spanning 81 days, net -308. 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 2,938–3,338 and does not start at zero.
Measurement log β€” every members count we have recorded, most recent 20 of 22
Measured (UTC)MembersChange
27 Oct 2026, 16:402,984-13
24 Oct 2026, 07:542,997-9
21 Oct 2026, 01:063,006-9
18 Oct 2026, 03:493,015-10
15 Oct 2026, 07:413,025-14
12 Oct 2026, 14:313,039-30
5 Oct 2026, 20:363,069-39
28 Sept 2026, 11:573,108-44
15 Sept 2026, 15:373,152+2
12 Sept 2026, 06:173,150-26
10 Sept 2026, 00:493,176no change
8 Sept 2026, 03:143,176-26
3 Sept 2026, 08:583,202-27
30 Aug 2026, 23:353,229-9
28 Aug 2026, 00:333,238-11
25 Aug 2026, 05:423,249-10
22 Aug 2026, 11:363,259+4
18 Aug 2026, 23:423,255-17
15 Aug 2026, 16:553,272-14
11 Aug 2026, 20:483,286first 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 27 October 2026 β€” this entry's latest reading, not the date you are reading this.

β€œCandles Crusher (CC)πŸ“Šβ€ (@liqudity883), 2,984 members as measured 27 October 2026. Telegram Register, tgregister.com/channel/liqudity883.

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.