Telegram RegisterThe public register of Telegram
Telegram profile photo for .πŸŒͺ α·‚Ψ£Ω†ΨͺΩΩ€Ω€Ω€Ω€ΩƒΨ§β”Šπ—”π—‘π—§π—œπ—žπ—”

Channel

.πŸŒͺ α·‚Ψ£Ω†ΨͺΩΩ€Ω€Ω€Ω€ΩƒΨ§β”Šπ—”π—‘π—§π—œπ—žπ—”

@di_mosa

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

5,403subscribers

-210 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-1001289694741
TypeChannel
Username@di_mosa
CreatedBetween 1 April 2018 and 31 July 2021 β€” estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 September 2026
Last confirmed live2 November 2026
Measurements held13
Confirmed unchanged1 time, most recently 2 November 2026
On Telegramt.me/di_mosa

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

5,4035,6135,5089 September 2026 β€” 5,613 subscribers9 September 2026 β€” 5,613 subscribers11 September 2026 β€” 5,599 subscribers15 September 2026 β€” 5,575 subscribers26 September 2026 β€” 5,568 subscribers12 October 2026 β€” 5,531 subscribers15 October 2026 β€” 5,516 subscribers18 October 2026 β€” 5,503 subscribers21 October 2026 β€” 5,481 subscribers24 October 2026 β€” 5,460 subscribers27 October 2026 β€” 5,440 subscribers30 October 2026 β€” 5,421 subscribers2 November 2026 β€” 5,403 subscribers9 September 20262 November 2026
13 measurements spanning 54 days, net -210. 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,372–5,645 and does not start at zero.
Measurement log β€” every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Nov 2026, 11:405,403-18
30 Oct 2026, 21:305,421-19
27 Oct 2026, 23:165,440-20
24 Oct 2026, 17:185,460-21
21 Oct 2026, 14:105,481-22
18 Oct 2026, 09:445,503-13
15 Oct 2026, 04:405,516-15
12 Oct 2026, 06:415,531-37
26 Sept 2026, 13:165,568-7
15 Sept 2026, 11:005,575-24
11 Sept 2026, 20:425,599-14
9 Sept 2026, 13:015,613no change
9 Sept 2026, 12:475,613first 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 2 November 2026 β€” this entry's latest reading, not the date you are reading this.

β€œ.πŸŒͺ α·‚Ψ£Ω†ΨͺΩΩ€Ω€Ω€Ω€ΩƒΨ§β”Šπ—”π—‘π—§π—œπ—žπ—”β€ (@di_mosa), 5,403 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/di_mosa.

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.