Channel
@sololeveling7
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Polls · Citations · Cite this entry
23,059subscribers
-647 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001431196218 |
|---|---|
| Type | Channel |
| Username | @sololeveling7 |
| Description | Uniquement les scans de Solo Leveling en Français (VF) |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 35 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/sololeveling7 |
Film & TV — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 32% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Oct 2026, 17:45 | 23,059 | -58 |
| 8 Oct 2026, 02:01 | 23,117 | -51 |
| 3 Oct 2026, 13:41 | 23,168 | -102 |
| 24 Sept 2026, 21:16 | 23,270 | -41 |
| 18 Sept 2026, 15:20 | 23,311 | -18 |
| 16 Sept 2026, 08:58 | 23,329 | -12 |
| 14 Sept 2026, 18:00 | 23,341 | -14 |
| 13 Sept 2026, 07:22 | 23,355 | -18 |
| 11 Sept 2026, 09:17 | 23,373 | -13 |
| 8 Sept 2026, 15:39 | 23,386 | -30 |
| 5 Sept 2026, 10:38 | 23,416 | -3 |
| 3 Sept 2026, 10:03 | 23,419 | -13 |
| 2 Sept 2026, 05:28 | 23,432 | -17 |
| 1 Sept 2026, 05:25 | 23,449 | -10 |
| 31 Aug 2026, 07:17 | 23,459 | -8 |
| 30 Aug 2026, 08:44 | 23,467 | -8 |
| 29 Aug 2026, 07:15 | 23,475 | -8 |
| 28 Aug 2026, 03:42 | 23,483 | -9 |
| 27 Aug 2026, 06:58 | 23,492 | -5 |
| 26 Aug 2026, 09:53 | 23,497 | first reading |
20 posts held, back to 21 October 2021 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 85 pages 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 20 posts for this entry, the most recent from 9 January 2022. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 13 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
C'est comme ça que ça se termine Solo Leveling 😭❤️vraiment, on remercie l'auteur🙏 pour ce chef d'oeuvre Mais il nous a quand même fait du lourd😁🔥. Nouveau Manwha du studio de solo Leveling enfin disponible qui s'appelle : Return of the disaster-class hero .. lien du canal 👇https://t.me/thedisasterclasshero
File, posted without a caption
Le groupe a été créé 👇 https://t.me/thedisasterclasshero
dois-je créer un autre groupe pour publier le nouveau manwha du studio de solo Leveling
The shares total 109%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Un autre manhwa du studio de Solo Leveling ! Qui est : 👉Return of the Disaster-Class Hero
J'espère qu'il n'y a pas de problème avec les scans s'il y en a vous pouvez m'indiquer
Joyeux Noël à tous même à ceux qui ne la fêtent pas
File, posted without a caption
File, posted without a caption
Excusez moi pour mon absence
https://t.me/sololeveling7
https://t.me/sololeveling7
Showing the 12 most recent of 20 posts we hold for @sololeveling7. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
dois-je créer un autre groupe pour publier le nouveau manwha du studio de solo Leveling
The shares total 109%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 20 most recent posts we hold, published 21 October 2021 to 9 January 2022. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“Solo Leveling Scan VF” (@sololeveling7), 23,059 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/sololeveling7.
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.