Telegram RegisterThe public register of Telegram
Telegram profile photo for Лампасник media. Челябинск

Channel

Лампасник media. Челябинск

@LampasnickTeam

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

856subscribers

-6 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001593290472
TypeChannel
Username@LampasnickTeam
CreatedBetween 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live23 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 23 August 2026
On Telegramt.me/LampasnickTeam

Growth

8568628597 August 2026 — 862 subscribers8 August 2026 — 862 subscribers15 August 2026 — 860 subscribers23 August 2026 — 856 subscribers7 August 202623 August 2026
4 measurements spanning 16 days, net -6. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 855–863 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 11:45856-4
15 Aug 2026, 19:59860-2
8 Aug 2026, 01:17862no change
7 Aug 2026, 12:34862first reading

Engagement

19 posts held, back to 18 April 2026the 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 19 posts for this entry, the most recent from 16 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
2m 57s
Average length
20s

Measured directly from 9 videos 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.

Reaction mix

950 reactions across 19 posts, in 23 distinct kinds. The most used accounts for 28.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥26928.3%
custom 542734209367463014819120.1%
19020.0%
custom 5427124875703630216747.79%
❤‍🔥414.32%
373.89%
🤣373.89%
custom 5426954133573745247353.68%
👍222.32%
😍212.21%
💯70.737%
🏆60.632%
🤝60.632%
👏30.316%
💘20.211%
🦄20.211%
custom 523140662622894826510.105%
🆒10.105%
👎10.105%
🕊10.105%
3 further kinds30.316%

Custom emoji. 4 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 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 19 of the 19 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 950reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 18 April 2026 to 16 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.

Recent posts

16 Jul 2026, 00:02 UTC628 views72 reactionsread 8 August 2026
Photo

Встретили наших парней🤩 Пахать за упущенный год будут вдвойне😈🥊

🔥25custom 54273420936746301482210😍9👍3custom 54271248757036302163

12 Jul 2026, 12:27 UTC≈1,370 views58 reactionsread 8 August 2026
Video message

Video message, posted without a caption

custom 542734209367463014828🤣139💯4🔥2custom 54271248757036302162

27 Jun 2026, 01:48 UTC≈1,340 views52 reactionsread 8 August 2026
Video

Четкая поездка, четкая атмосфера, видео не четкое по соображением безопасности. Отличное утро

custom 5427342093674630148259custom 54271248757036302166custom 54269541335737452475❤‍🔥4🏆3

11 Jun 2026, 05:56 UTC≈1,620 views44 reactionsread 8 August 2026
Video

А кто то ведет каналы ? Давайте в комменты скинем ?

custom 542734209367463014820118custom 54269541335737452472custom 54271248757036302162👍1

7 Jun 2026, 20:08 UTC≈1,620 views55 reactionsread 8 August 2026
Video

Всем будем рады 🥊

🔥2916🤝6👍2custom 54271248757036302162

7 Jun 2026, 12:16 UTC≈1,260 views53 reactionsread 8 August 2026
Video

Кто сколько весит ?

custom 5427342093674630148349custom 54269541335737452477custom 54271248757036302162🔥1

5 Jun 2026, 11:36 UTC≈1,390 views92 reactionsread 8 August 2026
Video

Video, posted without a caption

custom 54273420936746301483825🔥16custom 54271248757036302167🏆3custom 54269541335737452473

2 Jun 2026, 10:32 UTC≈1,830 views73 reactionsread 8 August 2026
Video

Наша поезда к соседям, в Екатеринбург😈 Дважды одержали победу🥊 Дольше ехали, чем длились столкновения🫠

🔥4318custom 54269541335737452479👎1custom 54271248757036302161custom 54273420936746301481

31 May 2026, 11:19 UTC≈1,930 views37 reactionsread 8 August 2026
Video message

Video message, posted without a caption

16👍8custom 54271248757036302167🔥4💯1custom 54273420936746301481

31 May 2026, 11:14 UTC≈1,380 views39 reactionsread 8 August 2026
Video message

Video message, posted without a caption

🔥247custom 54271248757036302166💯1custom 54273420936746301481

29 May 2026, 15:26 UTC≈1,410 views44 reactionsread 8 August 2026
Video message

Video message, posted without a caption

🔥23custom 542734209367463014811custom 542712487570363021682

29 May 2026, 15:25 UTC≈1,320 views41 reactionsread 8 August 2026
Video message

Video message, posted without a caption

🔥20custom 542734209367463014810custom 542695413357374524792

Showing the 12 most recent of 19 posts we hold for @LampasnickTeam. 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.

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 23 August 2026 — this entry's latest reading, not the date you are reading this.

“Лампасник media. Челябинск” (@LampasnickTeam), 856 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/LampasnickTeam.

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.