3 Apr 2026, 21:37 UTC165 views18 reactionsread 11 August 2026
анон🖕🖕🖕 http://t.me/anonaskbot?start=iupywdl
custom 54201322566288993629custom 54609177514030039729
Signed 𝐿𝑎𝑝𝑖𝑠 𝐿𝑎𝑧𝑢𝑙𝑖.^🦪
Channel
૮Ꮚ 𝐼𝓃𝒻𝑜 — 𝓗𝓲𝓴𝓾𝓼𝓱𝓪 ᡴꪫ
@lapissinfo
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
19subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003124355213 |
|---|---|
| Type | Channel |
| Username | @lapissinfo |
| Created | 15 October 2025 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/lapissinfo |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 17:31 | 19 | no change |
| 8 Aug 2026, 03:50 | 19 | first reading |
Engagement
5 posts held, back to 15 October 2025 — 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 pageof 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 5 posts for this entry, the most recent from 3 April 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 2
- Links
- 1
Lifetime counters from Telegram’s own channel header, read 11 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.
Reaction mix
135 reactions across 4 posts, in 9 distinct kinds. The most used accounts for 23.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5420132256628899362 | 31 | 23.0% | |
| custom 5422556048407951038 | 26 | 19.3% | |
| custom 5422606965245247848 | 20 | 14.8% | |
| custom 5422604048962453627 | 19 | 14.1% | |
| custom 5328036930758143075 | 12 | 8.89% | |
| custom 5271805204579248174 | 9 | 6.67% | |
| custom 5460917751403003972 | 9 | 6.67% | |
| custom 5422682247432010020 | 5 | 3.70% | |
| custom 5305347052325069613 | 4 | 2.96% |
Custom emoji. Every row above is a 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 areTelegram’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 4 of the 5 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 135reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 15 October 2025 to 3 April 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.
Recent posts
13 Nov 2025, 12:50 UTC329 views28 reactionsread 11 August 2026
File
File, posted without a caption
custom 542260696524524784810custom 54225560484079510389custom 54226040489624536279
Signed 🍫〢𝓛𝔂𝓪𝓹𝓲𝓼. ♅ั ( ?? ) #𝐣𝐮𝐬𝐭𝐮𝐫𝐚𝐧𝐞𝐩.
24 Oct 2025, 23:56 UTC414 views28 reactionsread 11 August 2026
Photo
➿➿ [🤩'r 0pin!on about m€⚪️] ➿➿➿ ➖➖➖➖➖➖➖➖➖➖➖➖➖➖ 🤩🤩😻💬➖➖ — Под этим постом Вы м_жете высказать @бсолютно любое мнение обо мне, каким бы он0 ни было.🌟➖➖➖➖➖➖➖➖ ➖➖➖➖➖➖➖➖➖➖➖➖➖➖ Сообщения с флудов будут удаляться. Напишите его компактно в одном предложении.💭
custom 54225560484079510389custom 52718052045792481747custom 54226069652452478487custom 54226040489624536275
Signed 𝓛𝔂𝓪𝓹𝓲𝓼. #𝑰𝑵𝑭𝑷
22 Oct 2025, 10:52 UTC362 views61 reactionsread 11 August 2026
Photo
🌟✨✨✨🔤то Вы мне ⭐️🤩 😻😻🤩😻— Пр0хож4й. (-ая) 😻😻🤩😻— Хотите с0 мной подружиться. 😻😻⛓️😻— Вы влюбл€ны в меня. 😻😻🌟😻— Друг/подруг@. 😻😻🐾😻— Ненав#дите меня. 😻😻⚖️😻— Бывший друг/подруга. 😻😻🔫😻— Сталкер. 😻😻🩸😻— Зн@комый.
custom 542013225662889936222custom 532803693075814307512custom 54225560484079510388custom 54226040489624536275custom 54226822474320100205custom 53053470523250696134custom 54226069652452478483custom 52718052045792481742
Signed 𝓛𝔂𝓪𝓹𝓲𝓼. #𝑰𝑵𝑭𝑷
15 Oct 2025, 10:24 UTCviews —
Channel created
Showing the 5 most recent of 5 posts we hold for @lapissinfo. 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.
Citation-graph rank
Citation-graph rank — 1,021,379 of 1,481,217entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Mentions
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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“૮Ꮚ 𝐼𝓃𝒻𝑜 — 𝓗𝓲𝓴𝓾𝓼𝓱𝓪 ᡴꪫ” (@lapissinfo), 19 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/lapissinfo.
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.