[𐌹𐌽𐍆𐌏] ⋅ . ˚ 𐙚 ℒυсья 𝒩 σρα 🦴 ꒱ ‧ ₊ pinned «໒🫙꒱ 𝒩 αɞυⲅαʯυя .. (≧▽≦) – вп/вл – набор в админы – параметры ос/код – администрация»
![Telegram profile photo for [𐌹𐌽𐍆𐌏] ⋅ . ˚ 𐙚 ℒυсья 𝒩 σρα 🦴 ꒱ ‧ ₊](https://cdn.tgregister.com/av/96/96d87461ece57e37f7bead0b516e5b6f15673fdd93a0e16979fe5b2728abd156.jpg)
Channel
[𐌹𐌽𐍆𐌏] ⋅ . ˚ 𐙚 ℒυсья 𝒩 σρα 🦴 ꒱ ‧ ₊
@mevixx_fox_info
On this record: Topic · Growth · Engagement · Posts · Cite this entry
2subscribers
+0 since we began measuring on 26 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1004405769573 |
|---|---|
| Type | Channel |
| Username | @mevixx_fox_info |
| Created | 26 August 2026 — measured — dated from the channel’s first post |
| First recorded | 26 August 2026 |
| Last confirmed live | 6 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 6 October 2026 |
| On Telegram | t.me/mevixx_fox_info |
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 6 October 2026 and assigned it the closest of 31 fixed categories, at 74% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Oct 2026, 16:36 | 2 | -2 |
| 3 Sept 2026, 10:12 | 4 | +2 |
| 26 Aug 2026, 23:15 | 2 | no change |
| 26 Aug 2026, 23:00 | 2 | first reading |
Engagement
8 posts held, back to 26 August 2026 — 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 8 posts for this entry, the most recent from 26 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
✩ 🍥 . 𝒜∂ɱυʜυсτραʯυя 𓂃 – влд @mevixx_1 – адм по вп @Apple_AsperJuice – адм по вл [пока что пишите влд] – адм по играм @qwertyfemboy @Napoleon_I_Bonaparte – адм по постам @MOLLYQWXX – адм по творчеству ❌
≧﹏≦ 𝒫 αραɱϱτρы 𝒪с/𝒦σ∂ . 🫧 ୨୨ – параметры на фото!! – кода пока что нету
ᜊᜊ 🍰. 𝒩 αɓσρ 𝒱 𝒜∂ɱυʜы ੭୧ [зп нету!!] – по вп/вл [0/8] – по играм [1/2] – по постам [1/10] – по творчеству [0/10] ᯓ хотите стать админом?? пишите в лс @mevixx_1
໒໒ . 𝒱η/𝒱 ⲗ ꒰ 🍨 ꒱ – вл 80+ [5-30 мест] – вп 20+
໒🫙꒱ 𝒩 αɞυⲅαʯυя .. (≧▽≦) – вп/вл – набор в админы – параметры ос/код – администрация
Channel photo updated
Channel created
Showing the 8 most recent of 8 posts we hold for @mevixx_fox_info. 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 6 October 2026 — this entry's latest reading, not the date you are reading this.
“[𐌹𐌽𐍆𐌏] ⋅ . ˚ 𐙚 ℒυсья 𝒩 σρα 🦴 ꒱ ‧ ₊” (@mevixx_fox_info), 2 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/mevixx_fox_info.
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.