Sfs 26 account

Channel
LORVEXSI: Until The Horde Passes.
@Lorvexsi
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
1,934subscribers
-11 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1003843436999 |
|---|---|
| Type | Channel |
| Username | @Lorvexsi |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/Lorvexsi |
Topic
Gaming — 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 16 September 2026 and assigned it the closest of 31 fixed categories, at 65% 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 |
|---|---|---|
| 17 Sept 2026, 00:01 | 1,934 | -18 |
| 13 Sept 2026, 04:19 | 1,952 | -44 |
| 9 Sept 2026, 12:01 | 1,996 | -20 |
| 4 Sept 2026, 07:57 | 2,016 | +28 |
| 31 Aug 2026, 17:15 | 1,988 | -42 |
| 29 Aug 2026, 02:19 | 2,030 | -1 |
| 26 Aug 2026, 08:17 | 2,031 | -22 |
| 23 Aug 2026, 08:38 | 2,053 | +43 |
| 19 Aug 2026, 18:42 | 2,010 | +45 |
| 16 Aug 2026, 08:45 | 1,965 | +15 |
| 12 Aug 2026, 20:53 | 1,950 | -6 |
| 9 Aug 2026, 20:12 | 1,956 | +3 |
| 7 Aug 2026, 03:08 | 1,953 | +8 |
| 6 Aug 2026, 09:37 | 1,945 | first reading |
Engagement
31 posts held, back to 5 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 2 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 31 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Main yuk
Cilok
Loci
What's up, obcy! We're doing a quick headcount for Cortis' 1st Anniversary, kindly send the format below to @ObscortRobot! Hey, Obscort! I'm [name + usn], and my muse is Ahn Keonho/Kim Juhoon/Park Martin/Eom Seonghyeon/James Zhao. Count me in for the anniversary project. Thanks! One more thing: make sure your name and username are written in MONOSPACE before you send it. Heads up at the anniversary! ꫂ᭪݁
Yang kurtis absenn ~
(Help Forward) Hi, everyone! Here I am opening a roll call for all CORTIS PORTRAYERS who will be participating in the celebration of CORTIS ANNIVERSARY, to be held on August 18th, 2026! If you're interested in joining this special celebration, please use the format below: PERSONAL : Hi, there. I (full name @.usn + in MONO) as (your muse), wishing to join the Cortis Mensiversary on August 18th. Please include me in …
ㅤㅤㅤㅤ (HELP FORWARD) ㅤㅤㅤㅤ As we commemorate the magnificent milestone of CORTIS, we are opening our registry to gather every sanctuary standing under its celebratory banner. We summon you to step into the light and be officially recorded within the @AHNORB central archives. Use The Following Template: USERNAME DORM + DORM MUSE Example: @AHNORB + KEONHO EVENT CORTIS’ Ann…
. • 🐈⬛🩷︙HFW! Enthralling Presence Fractures of Static-LACES / 1st EP. Enter a realm of Roseatte Entwine ༯ CORTIS 1st Anniversary! Blending in with the confident intensity of dazzling miracles. 🔝 My fellow, REBELEOM. Here, We are, from [your dorm username + JAMES/JUHOON/MARTIN/SEONGHYEON/KEONHO] ready to make some noise with yall. Please dial us in. ➤ Carve your presence through @rebeleombot / @rebeIeom
︎︎ ︎︎ ︎︎ ︎︎ ︎︎ ︎︎︎ ︎︎ ︎︎ ︎︎ ︎︎ ︎︎ ︎︎ ︎︎ ︎︎ ︎︎ ︎︎ A YEAR’S WORTH OF COLORING OUTSIDE THE LINES: CORTIS. Let us celebrate every persona who turned every red to green. MARTIN, JAMES, JUHOON, SEONGHYEON, & KEONHO potrayers, please send us: Well met, Hospectre! I, (name @username + MARTIN/JAMES/JUHOON/SEONGHYEON/KEONHO), am checking in within the echo. Monospaced name & username would be very much appreciated. Shout yo…
ㅤㅤ HELP FORWARD. Hey! we're calling for all CORTIS RP-ers. We're gonna celebrate in celebration of CORTIS'S Anniversary on August 18 2026. To participate, send to @SEONDRUXBOT Thank you to everyone who has already joined! Format: Hi! I’m [Your Full Name], @[Your Username] and im using [Your Muse]. Count me in. Thank you and have an amazing day! Hello! We are [@.Dorm], and we are using [Muse]. Count in please. Tha…
(HFW) Cortis absen @SeanFTWBot kirim nama, username, sama muse wajib mono ya
Showing the 12 most recent of 31 posts we hold for @Lorvexsi. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Mentions
Named by 10 registered channels — 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.
@voerux · 112 posts儲存空間••TDV Archive
@tdvarsip · 1810 postsSEONDRUX : ハイキュー!!
@SEONDRUX · 4,0433 postsREBELEOM ARCHIVE
@rebeleoms · 432 postsCORTOWN’s Downstairs!
@cortowns · 291 postDUNKSEAN [HOLD SFS]
@DUNKSEAN · 1,5511 postJUHOTZ.ZIP 🗂️
@JUHOTZIP · 181 post𝙹𝚄𝙿𝙰𝚆𝚂 🐈 @VAORUE
@Jupaws · 2,0131 postLORVEXSI’s PLAYLIST.
@LorvexLogs · 61 postYinsvelour arsip
@Yinsvelourr · 101 post
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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“LORVEXSI: Until The Horde Passes.” (@Lorvexsi), 1,934 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/Lorvexsi.
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.