Channel
@lapshiff
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
399subscribers
+13 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001782554022 |
|---|---|
| Type | Channel |
| Username | @lapshiff |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/lapshiff |
Sports — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 15 Sept 2026, 19:57 | 399 | +3 |
| 7 Sept 2026, 16:17 | 396 | +5 |
| 29 Aug 2026, 04:28 | 391 | +1 |
| 15 Aug 2026, 01:43 | 390 | +5 |
| 7 Aug 2026, 16:27 | 385 | -1 |
| 7 Aug 2026, 07:15 | 386 | first reading |
20 posts held, back to 6 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 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 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
246 reactions across 19 posts, in 18 distinct kinds. The most used accounts for 35.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤣 | 88 | 35.8% | |
| 🤡 | 32 | 13.0% | |
| 💯 | 24 | 9.76% | |
| ❤ | 20 | 8.13% | |
| custom 5217716040015836620 | 19 | 7.72% | |
| 🔥 | 14 | 5.69% | |
| custom 4997125622045082667 | 10 | 4.07% | |
| custom 5269430018945095944 | 8 | 3.25% | |
| 👏 | 8 | 3.25% | |
| custom 5222257572794351907 | 4 | 1.63% | |
| 🖕 | 4 | 1.63% | |
| custom 5219789083290650011 | 3 | 1.22% | |
| 💩 | 3 | 1.22% | |
| 🤬 | 3 | 1.22% | |
| 👍 | 2 | 0.813% | |
| 🤯 | 2 | 0.813% | |
| 👀 | 1 | 0.407% | |
| 😈 | 1 | 0.407% |
Custom emoji. 5 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 19 of the 20 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 246 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 6 August 2026 to 7 August 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.
Замечательное: судя по сервисам с публичной статистикой, точность передач «Шерифа» в домашнем матче составила 60%. 4 из 10 передач шли мимо. Про то, что у соперника владение в 2 раза больше, и говорить не приходится. Уже привыкли.
🤣4custom 52694300189450959443custom 52177160400158366202
Sticker, posted without a caption
Прислал подписчик. Народное творчество!
🤣11❤2🔥2
Video, posted without a caption
🤡13🖕4🤣2custom 52222575727943519072
Охренеть, говорящий календарь!
🤣15custom 52177160400158366206❤2🤡1custom 52694300189450959441
Вам и темп лиги мамалыги, судя по результатам за последние годы, тяжело держать. Деятель, ебт.
🤣11💯5custom 52177160400158366203👍2🤡1
Наблюдательный подписчик заметил: все три мяча швейцарцев забили футболисты, вышедшие на замену! У «Шерифа» тоже забил игрок с замены. Хотя у обоих команд и в первом тайме моментов хватило бы на 5-6 забитых мячей.
custom 49971256220450826676❤4💩1🤡1
Азы копиума от местных профессионалов: если не сообщить о третьем пропущенном мяче, жизнь станет слаще.
🤣10custom 52197890832906500113💯1🤡1
«Шериф» МихВика-Кучука в матчах еврокубков: 5 матчей Общий счёт 2:9 1 победа, 1 ничья (обе — против «Алюминия»), 3 поражения Дайте поработать!
🤣7custom 52177160400158366206custom 52694300189450959444🤯2🤡1
Как обычно, я пророк. Как же приятно был пророком!
👏8❤2🤣2🤡1
Но у швейцарцев есть исполнители посильнее
❤4🔥3🤡2
Вернувшийся на поле Пинеда вколачивает мяч в сетку ворот соперника, 1:2!
🔥9❤2🤡1
Showing the 12 most recent of 20 posts we hold for @lapshiff. 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.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“Иван Лапшин | Тираспольский «Шериф» и молдавский футбол” (@lapshiff), 399 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/lapshiff.
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.