Telegram RegisterThe public register of Telegram
Telegram profile photo for 3D Model & CG-News

Supergroup

3D Model & CG-News

@model3dsky

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

2,300members

+175 since we began measuring on 7 August 2026

104 online right now

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

Register entry

Telegram ID-1002230570880
TypeSupergroup
Username@model3dsky
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 live25 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.me/model3dsky

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 18 September 2026 and assigned it the closest of 31 fixed categories, at 64% 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,1252,3002,212.57 August 2026 — 2,125 members8 August 2026 — 2,126 members10 August 2026 — 2,137 members13 August 2026 — 2,156 members16 August 2026 — 2,165 members20 August 2026 — 2,193 members24 August 2026 — 2,168 members27 August 2026 — 2,186 members30 August 2026 — 2,198 members2 September 2026 — 2,203 members8 September 2026 — 2,227 members12 September 2026 — 2,240 members15 September 2026 — 2,260 members18 September 2026 — 2,260 members25 September 2026 — 2,300 members7 August 202625 September 2026
15 measurements spanning 49 days, net +175. 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,099–2,326 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
25 Sept 2026, 03:192,300+40
18 Sept 2026, 01:002,260no change
15 Sept 2026, 17:412,260+20
12 Sept 2026, 06:162,240+13
8 Sept 2026, 03:202,227+24
2 Sept 2026, 17:462,203+5
30 Aug 2026, 23:382,198+12
27 Aug 2026, 13:382,186+18
24 Aug 2026, 03:432,168-25
20 Aug 2026, 06:082,193+28
16 Aug 2026, 21:252,165+9
13 Aug 2026, 23:242,156+19
10 Aug 2026, 19:442,137+11
8 Aug 2026, 02:422,126+1
7 Aug 2026, 12:002,125first 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 25 September 2026 — this entry's latest reading, not the date you are reading this.

“3D Model & CG-News” (@model3dsky), 2,300 members as measured 25 September 2026. Telegram Register, tgregister.com/channel/model3dsky.

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.