Telegram RegisterThe public register of Telegram
Telegram profile photo for ASIAFORCE / ТЮНИНГ-АТЕЛЬЕ

Supergroup

ASIAFORCE / ТЮНИНГ-АТЕЛЬЕ

@asiaforce_studio

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

2,000members

+414 since we began measuring on 7 August 2026

57 online right now

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

Register entry

Telegram ID-1003204653803
TypeSupergroup
Username@asiaforce_studio
CreatedBetween 1 October 2025 and 31 January 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded23 September 2026
Last confirmed live1 November 2026
Measurements held24
Confirmed unchanged1 time, most recently 1 November 2026
On Telegramt.me/asiaforce_studio

Topic

Automotive — 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 23 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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,5862,0001,7937 August 2026 — 1,586 members8 August 2026 — 1,589 members11 August 2026 — 1,605 members13 August 2026 — 1,612 members16 August 2026 — 1,624 members20 August 2026 — 1,640 members24 August 2026 — 1,652 members27 August 2026 — 1,662 members30 August 2026 — 1,667 members2 September 2026 — 1,723 members7 September 2026 — 1,757 members11 September 2026 — 1,786 members15 September 2026 — 1,802 members23 September 2026 — 1,802 members25 September 2026 — 1,862 members4 October 2026 — 1,909 members11 October 2026 — 1,928 members14 October 2026 — 1,936 members17 October 2026 — 1,953 members20 October 2026 — 1,957 members23 October 2026 — 1,970 members27 October 2026 — 1,990 members30 October 2026 — 1,999 members1 November 2026 — 2,000 members7 August 20261 November 2026
24 measurements spanning 86 days, net +414. 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,524–2,062 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, 23:592,000+1
30 Oct 2026, 01:381,999+9
27 Oct 2026, 00:411,990+20
23 Oct 2026, 17:001,970+13
20 Oct 2026, 11:571,957+4
17 Oct 2026, 08:151,953+17
14 Oct 2026, 08:051,936+8
11 Oct 2026, 00:381,928+19
4 Oct 2026, 20:411,909+47
25 Sept 2026, 15:211,862+60
23 Sept 2026, 02:501,802no change
15 Sept 2026, 12:381,802+16
11 Sept 2026, 14:221,786+29
7 Sept 2026, 07:181,757+34
2 Sept 2026, 17:081,723+56
30 Aug 2026, 05:151,667+5
27 Aug 2026, 01:531,662+10
24 Aug 2026, 03:291,652+12
20 Aug 2026, 05:041,640+16
16 Aug 2026, 21:431,624first 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.

“ASIAFORCE / ТЮНИНГ-АТЕЛЬЕ” (@asiaforce_studio), 2,000 members as measured 1 November 2026. Telegram Register, tgregister.com/channel/asiaforce_studio.

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.