Telegram RegisterThe public register of Telegram
Telegram profile photo for h1kar1

Channel

h1kar1

@prikoluhaaaa

On this record: Growth · Engagement · Reactions · Posts · Cite this entry

42subscribers

-1 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-1001288474877
TypeChannel
Username@prikoluhaaaa
CreatedBetween 1 April 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live24 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 24 August 2026
On Telegramt.me/prikoluhaaaa

Growth

424342.57 August 2026 — 43 subscribers10 August 2026 — 43 subscribers24 August 2026 — 42 subscribers7 August 202624 August 2026
3 measurements spanning 17 days, net -1. 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 42–43 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 00:5542-1
10 Aug 2026, 16:3143no change
7 Aug 2026, 11:5843first reading

Engagement

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

Reaction mix

20 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 60.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53595564888576595271260.0%
custom 5361929222065494120840.0%

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 5 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 20reactions 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 19 June 2026 to 14 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

14 Jul 2026, 13:40 UTC48 views4 reactionsread 10 August 2026
Photo

Photo, posted without a caption

custom 53595564888576595272custom 53619292220654941202

Signed hikari

9 Jul 2026, 13:14 UTC60 views4 reactionsread 10 August 2026
Photo

йоу мы в уфе

custom 53595564888576595272custom 53619292220654941202

Signed hikari

2 Jul 2026, 14:11 UTC58 views6 reactionsread 10 August 2026
Photo

ура

custom 53595564888576595276

Signed hikari

20 Jun 2026, 11:45 UTC71 views4 reactionsread 10 August 2026
Photo

ми крутые

custom 53595564888576595272custom 53619292220654941202

Signed hikari

19 Jun 2026, 18:18 UTC57 views2 reactionsread 10 August 2026
Photo

Photo, posted without a caption

custom 53619292220654941202

Signed hikari

Showing the 5 most recent of 5 posts we hold for @prikoluhaaaa. 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 24 August 2026 — this entry's latest reading, not the date you are reading this.

“h1kar1” (@prikoluhaaaa), 42 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/prikoluhaaaa.

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.