Telegram RegisterThe public register of Telegram
Telegram profile photo for Rules Mistral Service

Channel

Rules Mistral Service

@MistralRules

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

9subscribers

+1 since we began measuring on 12 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003422290155
TypeChannel
Username@MistralRules
Created16 November 2025 — measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live4 October 2026
Measurements held3
Confirmed unchanged1 time, most recently 4 October 2026
On Telegramt.me/MistralRules

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 4 October 2026 and assigned it the closest of 31 fixed categories, at 98% 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

898.512 August 2026 — 8 subscribers12 August 2026 — 8 subscribers4 October 2026 — 9 subscribers12 August 20264 October 2026
3 measurements spanning 53 days, net +1. 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 8–9 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Oct 2026, 09:379+1
12 Aug 2026, 15:328no change
12 Aug 2026, 11:038first reading

Engagement

2 posts held, back to 16 November 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 2 posts for this entry, the most recent from 16 November 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

16 Nov 2025, 20:27 UTC160 viewsread 12 August 2026
Photo

⚙️Правила Mistral Service: *Относится ко всем группам по скупке какого-либо материала нашего проекта ➡️Пункт 1.0: - Запрещается принимать какой-либо материал не имея на это разрешения администрации [БАН] ➡️Пункт 1.1: - Запрещается предлагать какие либо услуги в чате/лс не имея разрешения от администрации [БАН/-РЕП] ➡️Пункт 1.2: - Запрещается перегонять трафик в иные чаты/каналы [МУТ/БАН] ➡️Пункт 1.3: - Запрещаетс…

Showing the 2 most recent of 2 posts we hold for @MistralRules. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

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 4 October 2026 — this entry's latest reading, not the date you are reading this.

“Rules Mistral Service” (@MistralRules), 9 subscribers as measured 4 October 2026. Telegram Register, tgregister.com/channel/MistralRules.

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.