Telegram RegisterThe public register of Telegram
Telegram profile photo for Info Event Teknologi

Supergroup

Info Event Teknologi

@eventteknologi_id

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

5,601members

-164 since we began measuring on 6 August 2026

60 online right now

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

Register entry

Telegram ID-1001132125206
TypeSupergroup
Username@eventteknologi_id
CreatedBetween 1 June 2017 and 30 September 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded30 August 2026
Last confirmed live1 November 2026
Measurements held24
Confirmed unchanged1 time, most recently 1 November 2026
On Telegramt.me/eventteknologi_id

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 12 September 2026 and assigned it the closest of 31 fixed categories, at 80% 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,6015,7655,6836 August 2026 — 5,765 members10 August 2026 — 5,760 members13 August 2026 — 5,756 members16 August 2026 — 5,751 members19 August 2026 — 5,745 members23 August 2026 — 5,746 members27 August 2026 — 5,738 members30 August 2026 — 5,727 members30 August 2026 — 5,727 members2 September 2026 — 5,722 members6 September 2026 — 5,712 members11 September 2026 — 5,700 members14 September 2026 — 5,708 members19 September 2026 — 5,707 members28 September 2026 — 5,673 members6 October 2026 — 5,655 members12 October 2026 — 5,639 members15 October 2026 — 5,630 members18 October 2026 — 5,628 members20 October 2026 — 5,625 members23 October 2026 — 5,620 members26 October 2026 — 5,612 members30 October 2026 — 5,604 members1 November 2026 — 5,601 members6 August 20261 November 2026
24 measurements spanning 87 days, net -164. 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,576–5,790 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 24
Measured (UTC)MembersChange
1 Nov 2026, 21:315,601-3
30 Oct 2026, 03:165,604-8
26 Oct 2026, 20:095,612-8
23 Oct 2026, 20:165,620-5
20 Oct 2026, 15:555,625-3
18 Oct 2026, 00:075,628-2
15 Oct 2026, 09:205,630-9
12 Oct 2026, 15:405,639-16
6 Oct 2026, 08:025,655-18
28 Sept 2026, 22:395,673-34
19 Sept 2026, 12:165,707-1
14 Sept 2026, 21:015,708+8
11 Sept 2026, 13:205,700-12
6 Sept 2026, 14:385,712-10
2 Sept 2026, 12:045,722-5
30 Aug 2026, 11:585,727no change
30 Aug 2026, 05:025,727-11
27 Aug 2026, 07:045,738-8
23 Aug 2026, 21:055,746+1
19 Aug 2026, 23:435,745first 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 1 November 2026 — this entry's latest reading, not the date you are reading this.

“Info Event Teknologi” (@eventteknologi_id), 5,601 members as measured 1 November 2026. Telegram Register, tgregister.com/channel/eventteknologi_id.

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.