Telegram RegisterThe public register of Telegram
Telegram profile photo for DINO

Channel

DINO

@dino_ediit

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

4,189subscribers

+80 since we began measuring on 9 September 2026

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

Register entry

Telegram ID-1002528731212
TypeChannel
Username@dino_ediit
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 September 2026
Last confirmed live6 November 2026
Measurements held15
Confirmed unchanged2 times, most recently 6 November 2026
On Telegramt.me/dino_ediit

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 29 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

4,0964,1924,1449 September 2026 — 4,109 subscribers9 September 2026 — 4,109 subscribers11 September 2026 — 4,102 subscribers14 September 2026 — 4,096 subscribers19 September 2026 — 4,101 subscribers29 September 2026 — 4,098 subscribers6 October 2026 — 4,104 subscribers12 October 2026 — 4,103 subscribers15 October 2026 — 4,116 subscribers18 October 2026 — 4,129 subscribers22 October 2026 — 4,161 subscribers24 October 2026 — 4,187 subscribers28 October 2026 — 4,192 subscribers31 October 2026 — 4,191 subscribers3 November 2026 — 4,189 subscribers4,1899 September 20263 November 2026
15 measurements spanning 55 days, net +80. 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 4,082–4,206 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Nov 2026, 16:354,189-2
31 Oct 2026, 14:554,191-1
28 Oct 2026, 08:044,192+5
24 Oct 2026, 23:154,187+26
22 Oct 2026, 00:464,161+32
18 Oct 2026, 13:214,129+13
15 Oct 2026, 11:054,116+13
12 Oct 2026, 16:384,103-1
6 Oct 2026, 10:014,104+6
29 Sept 2026, 12:174,098-3
19 Sept 2026, 05:164,101+5
14 Sept 2026, 14:404,096-6
11 Sept 2026, 09:194,102-7
9 Sept 2026, 13:044,109no change
9 Sept 2026, 12:474,109first 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 3 November 2026 — this entry's latest reading, not the date you are reading this.

“DINO” (@dino_ediit), 4,189 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/dino_ediit.

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.