Telegram RegisterThe public register of Telegram
Telegram profile photo for CONFIG HTTP CUSTOM SGP

Supergroup

CONFIG HTTP CUSTOM SGP

@httpcustomsanggar

Has discussion group

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

2,245members

-45 since we began measuring on 7 August 2026

94 online right now

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

Register entry

Telegram ID-1002220391973
TypeSupergroup
Username@httpcustomsanggar
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded18 September 2026
Last confirmed live10 October 2026
Measurements held16
Confirmed unchanged1 time, most recently 10 October 2026
On Telegramt.me/httpcustomsanggar

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 18 September 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 why it has no browse page of its own yet.

Growth

2,2412,2932,2677 August 2026 — 2,290 members11 August 2026 — 2,289 members14 August 2026 — 2,293 members18 August 2026 — 2,290 members21 August 2026 — 2,284 members25 August 2026 — 2,276 members28 August 2026 — 2,275 members31 August 2026 — 2,270 members4 September 2026 — 2,264 members10 September 2026 — 2,262 members13 September 2026 — 2,257 members17 September 2026 — 2,256 members18 September 2026 — 2,256 members25 September 2026 — 2,241 members4 October 2026 — 2,249 members10 October 2026 — 2,245 members2,2457 August 202610 October 2026
16 measurements spanning 64 days, net -45. 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,233–2,301 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
10 Oct 2026, 15:202,245-4
4 Oct 2026, 21:202,249+8
25 Sept 2026, 10:362,241-15
18 Sept 2026, 01:102,256no change
17 Sept 2026, 08:012,256-1
13 Sept 2026, 18:412,257-5
10 Sept 2026, 07:202,262-2
4 Sept 2026, 16:182,264-6
31 Aug 2026, 22:272,270-5
28 Aug 2026, 11:572,275-1
25 Aug 2026, 03:362,276-8
21 Aug 2026, 21:582,284-6
18 Aug 2026, 07:322,290-3
14 Aug 2026, 21:462,293+4
11 Aug 2026, 07:312,289-1
7 Aug 2026, 15:062,290first 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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 October 2026 — this entry's latest reading, not the date you are reading this.

“CONFIG HTTP CUSTOM SGP” (@httpcustomsanggar), 2,245 members as measured 10 October 2026. Telegram Register, tgregister.com/channel/httpcustomsanggar.

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.