Channel
@l0lkl0lo
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
106subscribers
+0 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002385781387 |
|---|---|
| Type | Channel |
| Username | @l0lkl0lo |
| Description | owner: t.me/TWINXXI |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/l0lkl0lo |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 02:45 | 106 | no change |
| 13 Aug 2026, 02:33 | 106 | first reading |
10 posts held, back to 7 June 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 10 posts for this entry, the most recent from 31 July 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 13 August 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.
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.
82 reactions across 10 posts, in 19 distinct kinds. The most used accounts for 18.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 15 | 18.3% | |
| 🍓 | 11 | 13.4% | |
| 💔 | 11 | 13.4% | |
| custom 5280714762047486935 | 7 | 8.54% | |
| 🆒 | 6 | 7.32% | |
| 💋 | 4 | 4.88% | |
| custom 5280689172632342858 | 3 | 3.66% | |
| custom 5282969297755341395 | 3 | 3.66% | |
| custom 5296422380866924987 | 3 | 3.66% | |
| custom 5299034829084457047 | 3 | 3.66% | |
| custom 5280886938696447325 | 2 | 2.44% | |
| custom 5283119351027759735 | 2 | 2.44% | |
| custom 5287267151269361518 | 2 | 2.44% | |
| custom 5294075765355214047 | 2 | 2.44% | |
| custom 5298755308317866848 | 2 | 2.44% | |
| custom 5312342879740392720 | 2 | 2.44% | |
| custom 5318779270485539531 | 2 | 2.44% | |
| custom 5280819975861338676 | 1 | 1.22% | |
| custom 5287649278804650261 | 1 | 1.22% |
Custom emoji. 14 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 10 of the 10 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 82 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 7 June 2026 to 31 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
File, posted without a caption
custom 52964223808669249872custom 52990348290844570472custom 52872671512693615181custom 52987553083178668481custom 53123428797403927201custom 53187792704855395311
Photo, posted without a caption
custom 52940757653552140472custom 52872671512693615181custom 52876492788046502611custom 52964223808669249871custom 52987553083178668481custom 52990348290844570471custom 53123428797403927201custom 53187792704855395311
ну тупа мы🫰
💔4❤2🍓2🆒1custom 52807147620474869351custom 52829692977553413951
3 день подряд ходим с евой на ночевки🫰
custom 52807147620474869355❤2🍓1💔1🆒1custom 52829692977553413951
File, posted without a caption
❤1🍓1💔1
File, posted without a caption
❤1🍓1💔1🆒1custom 52806891726323428581custom 52831193510277597351
File, posted without a caption
❤2🍓1💋1💔1🆒1custom 52808869386964473251
name: vika/riya 📈 19.09.08(17 y.o) 🎶 intp 🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 anon ; boost ; side ; me ; tiktok ; insta ; pin
❤2🍓1💋1💔1custom 52806891726323428581
🎁
🍓3❤2💋1💔1🆒1custom 52806891726323428581custom 52808199758613386761
ТУПА МЫ С ЕВИКОМ🙂
❤3🍓1💋1💔1🆒1custom 52807147620474869351custom 52808869386964473251custom 52829692977553413951
Showing the 10 most recent of 10 posts we hold for @l0lkl0lo. 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.
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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“шеина” (@l0lkl0lo), 106 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/l0lkl0lo.
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.