3 Aug 2026, 13:11 UTC35 viewsread 13 August 2026
Video
Video, posted without a caption
Channel
LORVEXSI’s PLAYLIST.
@LorvexLogs
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
6subscribers
+1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003951361144 |
|---|---|
| Type | Channel |
| Username | @LorvexLogs |
| Created | Between 1 April 2026 and 16 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 3 times, most recently 15 September 2026 |
| On Telegram | t.me/LorvexLogs |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 07:56 | 6 | +1 |
| 13 Aug 2026, 00:03 | 5 | no change |
| 6 Aug 2026, 22:25 | 5 | first reading |
Engagement
16 posts held, back to 16 July 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 16 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 1m 51s
- Average length
- 1m 51s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Recent posts
3 Aug 2026, 12:54 UTC35 viewsread 13 August 2026
File
File, posted without a caption
19 Jul 2026, 18:14 UTC44 viewsread 13 August 2026
Forwarded from @enchantian
https://t.me/Lorvexsi read the whisper
19 Jul 2026, 18:14 UTC44 viewsread 13 August 2026
Forwarded from @enchantian
suka poster opmemb nya, keren tapi simple terus Seonghyeon banget gitu loh. simple but effortless cool
19 Jul 2026, 18:14 UTC45 viewsread 13 August 2026
Forwarded from @enchantian
seapa-adanya, suka deh. isinya juga banyak yang funny, naturally funny maksudnya. tapi ada swag juga dah heeh, BALANCE
16 Jul 2026, 12:27 UTC16 viewsread 13 August 2026
Forwarded from @LorvexsiSticker
Sticker, posted without a caption
16 Jul 2026, 12:27 UTC19 viewsread 13 August 2026
Forwarded from @Lorvexsi
ㅤGerald @naonsenah @ahnmoire. read the whisper
16 Jul 2026, 12:27 UTC25 viewsread 13 August 2026
Forwarded from @LorvexsiSticker
Sticker, posted without a caption
16 Jul 2026, 12:27 UTC28 viewsread 13 August 2026
Forwarded from @Lorvexsi
Savero @jzSeonghyeon read the whisper
16 Jul 2026, 12:27 UTC45 viewsread 13 August 2026
Forwarded from @LorvexsiSticker
Sticker, posted without a caption
16 Jul 2026, 12:27 UTC16 viewsread 13 August 2026
Forwarded from @LorvexsiPhoto
If Elsie @leeamn were a dessert, she would be lemon tart—bright, elegant, and refreshingly charming. She carries a lively warmth that instantly lifts the mood, balancing sweetness with just the right touch of zest. Effortlessly delightful and impossible to forget, she's the kind of dessert that leaves you smiling long after the last bite.
16 Jul 2026, 12:27 UTC27 viewsread 13 August 2026
Forwarded from @LorvexsiPhoto
If Gerald @naonsenah were a dessert, he would be classic New York cheesecake—steady, timeless, and quietly dependable. He doesn't rely on extravagance to stand out; instead, his charm comes from a comforting presence that feels familiar from the very beginning. Rich without being overwhelming and effortlessly satisfying, he's the kind of dessert people return to time and time again because it never disappoints.
Showing the 12 most recent of 16 posts we hold for @LorvexLogs. 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
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
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 29 August 2026 — this entry's latest reading, not the date you are reading this.
“LORVEXSI’s PLAYLIST.” (@LorvexLogs), 6 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/LorvexLogs.
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.