Telegram RegisterThe public register of Telegram
Telegram profile photo for CODING BUGS COMMUNITY

Supergroup

CODING BUGS COMMUNITY

@Coding_Bugs

Has discussion group

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

1,415members

-114 since we began measuring on 7 August 2026

30 online right now

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

Register entry

Telegram ID-1001969481007
TypeSupergroup
Username@Coding_Bugs
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded28 September 2026
Last confirmed live17 November 2026
Measurements held28
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/Coding_Bugs

Topic

Technology — 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 29 September 2026 and assigned it the closest of 31 fixed categories, at 76% 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

1,4151,5291,4727 August 2026 — 1,529 members8 August 2026 — 1,528 members11 August 2026 — 1,522 members14 August 2026 — 1,512 members17 August 2026 — 1,508 members20 August 2026 — 1,506 members23 August 2026 — 1,504 members26 August 2026 — 1,497 members1 September 2026 — 1,490 members4 September 2026 — 1,485 members10 September 2026 — 1,479 members14 September 2026 — 1,477 members18 September 2026 — 1,471 members28 September 2026 — 1,462 members28 September 2026 — 1,462 members5 October 2026 — 1,454 members11 October 2026 — 1,448 members14 October 2026 — 1,446 members18 October 2026 — 1,440 members21 October 2026 — 1,438 members24 October 2026 — 1,436 members27 October 2026 — 1,434 members30 October 2026 — 1,430 members3 November 2026 — 1,428 members5 November 2026 — 1,426 members8 November 2026 — 1,424 members12 November 2026 — 1,420 members17 November 2026 — 1,415 members7 August 202617 November 2026
28 measurements spanning 102 days, net -114. 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,398–1,546 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 28
Measured (UTC)MembersChange
17 Nov 2026, 18:191,415-5
12 Nov 2026, 11:571,420-4
8 Nov 2026, 17:441,424-2
5 Nov 2026, 15:261,426-2
3 Nov 2026, 01:341,428-2
30 Oct 2026, 17:041,430-4
27 Oct 2026, 22:161,434-2
24 Oct 2026, 14:491,436-2
21 Oct 2026, 10:171,438-2
18 Oct 2026, 07:491,440-6
14 Oct 2026, 22:381,446-2
11 Oct 2026, 14:381,448-6
5 Oct 2026, 14:201,454-8
28 Sept 2026, 23:301,462no change
28 Sept 2026, 05:561,462-9
18 Sept 2026, 11:171,471-6
14 Sept 2026, 07:551,477-2
10 Sept 2026, 10:151,479-6
4 Sept 2026, 22:171,485-5
1 Sept 2026, 15:381,490first 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 17 November 2026 — this entry's latest reading, not the date you are reading this.

“CODING BUGS COMMUNITY” (@Coding_Bugs), 1,415 members as measured 17 November 2026. Telegram Register, tgregister.com/channel/Coding_Bugs.

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.