Channel
@ulikpikmelife
On this record: Growth · Engagement · Reactions · Posts · Cite this entry
437subscribers
-14 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002542416574 |
|---|---|
| Type | Channel |
| Username | @ulikpikmelife |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 6 September 2026 |
| On Telegram | t.me/ulikpikmelife |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 16:58 | 437 | -7 |
| 28 Aug 2026, 08:37 | 444 | -2 |
| 21 Aug 2026, 03:02 | 446 | -2 |
| 14 Aug 2026, 03:13 | 448 | -2 |
| 8 Aug 2026, 05:02 | 450 | no change |
| 7 Aug 2026, 18:00 | 450 | -1 |
| 7 Aug 2026, 17:11 | 451 | first reading |
4 posts held, back to 3 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 4 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
112 reactions across 4 posts, in 11 distinct kinds. The most used accounts for 32.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5244653452126096872 | 36 | 32.1% | |
| custom 5287411758523251463 | 20 | 17.9% | |
| custom 5258230810116400744 | 16 | 14.3% | |
| custom 5465602998082241794 | 10 | 8.93% | |
| custom 5438342243654065221 | 8 | 7.14% | |
| custom 5240063626735291361 | 6 | 5.36% | |
| custom 5442696322584975725 | 6 | 5.36% | |
| custom 5237930647191850476 | 5 | 4.46% | |
| custom 5418014068952805770 | 3 | 2.68% | |
| custom 5418117805297932468 | 1 | 0.893% | |
| custom 5465142092256808084 | 1 | 0.893% |
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 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 4 of the 4 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 112 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 4 most recent posts we hold, published 3 August 2026 to 6 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.
Новгородский кремль 🌟
custom 528741175852325146314custom 52400636267352913615custom 52582308101164007445custom 52379306471918504761custom 52446534521260968721custom 54180140689528057701custom 54383422436540652211custom 54656029980822417941
Video message, posted without a caption
custom 54656029980822417949custom 52379306471918504764custom 52446534521260968723custom 54180140689528057701custom 54181178052979324681custom 54426963225849757251custom 54651420922568080841
На пару дней приехала в 🤩🤩🤩 иииии угадайте, что? Правильно - опять уехала, до пятницы я в 🤩овгороде смурфятки🍵 🎭🎭🎭
custom 524465345212609687217custom 52582308101164007449custom 54383422436540652216custom 52874117585232514631custom 54180140689528057701custom 54426963225849757251
после 🤩еверодвинска у нас была пересадка на один день в 🤩оскве. Очень хорошо провела время 🙏Встретилась с другом и посетила всё самое любимое ☝️ 🤩🤩 🤩🤩
custom 524465345212609687215custom 52874117585232514635custom 54426963225849757254custom 52582308101164007442custom 52400636267352913611custom 54383422436540652211
Showing the 4 most recent of 4 posts we hold for @ulikpikmelife. 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.
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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“𝓤𝓵𝓲𝓴𝓢” (@ulikpikmelife), 437 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/ulikpikmelife.
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.