Telegram RegisterThe public register of Telegram
Telegram profile photo for ︎︎ ︎ ︎ ︎ ︎ ︎ ︎ ︎

Channel

︎︎ ︎ ︎ ︎ ︎ ︎ ︎ ︎

@FELIH1K

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

67subscribers

-21 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-1003147176315
TypeChannel
Username@FELIH1K
Created30 September 2025measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live23 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 23 August 2026
On Telegramt.me/FELIH1K

Growth

678877.57 August 2026 — 88 subscribers9 August 2026 — 88 subscribers15 August 2026 — 73 subscribers23 August 2026 — 67 subscribers7 August 202623 August 2026
4 measurements spanning 16 days, net -21. 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 64–91 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 20:5767-6
15 Aug 2026, 05:2473-15
9 Aug 2026, 15:3388no change
7 Aug 2026, 19:4088first reading

Engagement

4 posts held, back to 30 September 2025the 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 4 posts for this entry, the most recent from 26 February 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

428 reactions across 3 posts, in 6 distinct kinds. The most used accounts for 20.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52445877477164029698720.3%
custom 52468406513366843868118.9%
custom 59650345856737019877317.1%
custom 52468890255533369776715.7%
custom 52446814896726062236515.2%
custom 52309715503368425555512.9%

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 3 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 428reactions 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 30 September 2025 to 26 February 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

26 Feb 2026, 17:20 UTC≈1,210 views158 reactionsread 9 August 2026

My value does not depend on the opinions of others

custom 524458774771640296934custom 524684065133668438632custom 524688902555333697729custom 596503458567370198726custom 523097155033684255519custom 524468148967260622318

22 Jan 2026, 17:01 UTC≈7,360 views154 reactionsread 9 August 2026
Photo

✅ No one is too busy, you're just not a priority

custom 524684065133668438636custom 524458774771640296932custom 524468148967260622330custom 523097155033684255522custom 524688902555333697717custom 596503458567370198717

30 Sept 2025, 20:21 UTC≈7,830 views116 reactionsread 9 August 2026
Photo

✅ OWNER - Värion 💲 Fel Hans Channel ✨ Private MyPlaylist 🔵IMessage 🔒Online: 12:00 - 01:00 One day the darkness will embrace you from head to toe 🤩

custom 596503458567370198730custom 524458774771640296921custom 524688902555333697721custom 524468148967260622317custom 523097155033684255514custom 524684065133668438613

Showing the 4 most recent of 4 posts we hold for @FELIH1K. 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.

“︎︎ ︎ ︎ ︎ ︎ ︎ ︎ ︎” (@FELIH1K), 67 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/FELIH1K.

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.