Telegram RegisterThe public register of Telegram
Telegram profile photo for Frontend Developer Indonesia

Supergroup

Frontend Developer Indonesia

@FrontEndID

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

5,135members

-199 since we began measuring on 7 August 2026

222 online right now

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

Register entry

Telegram ID-1001087100147
TypeSupergroup
Username@FrontEndID
CreatedBetween 1 September 2016 and 30 September 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded31 August 2026
Last confirmed live4 November 2026
Measurements held24
Confirmed unchanged1 time, most recently 4 November 2026
On Telegramt.me/FrontEndID

Topic

Job listings — 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 99% 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

5,1355,3345,234.57 August 2026 — 5,334 members11 August 2026 — 5,327 members14 August 2026 — 5,328 members17 August 2026 — 5,323 members21 August 2026 — 5,319 members25 August 2026 — 5,307 members28 August 2026 — 5,302 members31 August 2026 — 5,295 members31 August 2026 — 5,295 members2 September 2026 — 5,290 members7 September 2026 — 5,275 members12 September 2026 — 5,264 members15 September 2026 — 5,254 members27 September 2026 — 5,229 members5 October 2026 — 5,206 members11 October 2026 — 5,192 members14 October 2026 — 5,190 members18 October 2026 — 5,176 members21 October 2026 — 5,166 members23 October 2026 — 5,163 members26 October 2026 — 5,161 members29 October 2026 — 5,153 members31 October 2026 — 5,146 members4 November 2026 — 5,135 members7 August 20264 November 2026
24 measurements spanning 88 days, net -199. 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 5,105–5,364 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 24
Measured (UTC)MembersChange
4 Nov 2026, 02:005,135-11
31 Oct 2026, 22:455,146-7
29 Oct 2026, 04:495,153-8
26 Oct 2026, 10:585,161-2
23 Oct 2026, 18:185,163-3
21 Oct 2026, 00:365,166-10
18 Oct 2026, 07:205,176-14
14 Oct 2026, 20:415,190-2
11 Oct 2026, 18:185,192-14
5 Oct 2026, 15:595,206-23
27 Sept 2026, 16:425,229-25
15 Sept 2026, 15:375,254-10
12 Sept 2026, 03:415,264-11
7 Sept 2026, 12:005,275-15
2 Sept 2026, 18:435,290-5
31 Aug 2026, 21:255,295no change
31 Aug 2026, 02:585,295-7
28 Aug 2026, 01:545,302-5
25 Aug 2026, 01:245,307-12
21 Aug 2026, 05:195,319first 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 4 November 2026 — this entry's latest reading, not the date you are reading this.

“Frontend Developer Indonesia” (@FrontEndID), 5,135 members as measured 4 November 2026. Telegram Register, tgregister.com/channel/FrontEndID.

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.