Posted without readable text

Channel
π―πππππ | π©ππ ππππππππ πͺπππππππ
@hunfek
On this record: Growth Β· Engagement Β· What this channel posts Β· Reactions Β· Posts Β· Citations Β· Cite this entry
347subscribers
+0 since we began measuring on 14 August 2026
Risers and fallers across the register Β· movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001670127842 |
|---|---|
| Type | Channel |
| Username | @hunfek |
| Created | Between 1 December 2021 and 30 April 2023β estimated from Telegramβs id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/hunfek |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 19:16 | 347 | no change |
| 14 Aug 2026, 19:06 | 347 | first reading |
Engagement
16 posts held, back to 15 February 2024 β 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 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 16 posts for this entry, the most recent from 24 June 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 36
- Videos
- 190
- Links
- 1
Lifetime counters from Telegramβs own channel header, read 14 August 2026 β not the date at the top of this page, which is when the subscriber count was last read. Below Telegramβs rounding threshold, so these counts are exact.
- Video runtime
- 36m 50s
- Average length
- 2m 50s
Measured directly from 13 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
220 reactions across 15 posts, in 6 distinct kinds. The most used accounts for 73.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| β€ | 162 | 73.6% | |
| β€βπ₯ | 29 | 13.2% | |
| π | 12 | 5.45% | |
| π | 9 | 4.09% | |
| π | 7 | 3.18% | |
| π | 1 | 0.455% |
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 16 of the 16 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 220reactions in total: the kind of figure the paragraph above means by βa reaction total printed elsewhere on the pageβ.
Measured over the 16 most recent posts we hold, published 15 February 2024 to 24 June 2025, 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
ΠΡΠ΅ΠΌ ΠΏΡΠΈΠ²Π΅Ρ. Π― ΠΎΡΠ΅Π½Ρ Π΄ΠΎΠ»Π³ΠΎ Π΄ΡΠΌΠ°Π»Π°, ΠΎΠ±ΡΠ°Π»Π°ΡΡ ΠΌΠ½ΠΎΠ³ΠΈΠΌΠΈ Π»ΡΠ΄ΡΠΌΠΈ, ΠΏΡΠΎΡΠΈΠ»Π° ΡΠΎΠ²Π΅ΡΠΎΠ², ΡΠ°Π·Π±ΠΈΡΠ°Π»Π°ΡΡ Π² ΡΠ΅Π±Π΅. ΠΠ°Π½Π°Π» Π²ΡΠ·ΡΠ²Π°Π΅Ρ Ρ ΠΌΠ΅Π½Ρ ΠΊΠ°ΠΊ Ρ ΠΎΡΠΎΡΠΈΠ΅ Π²ΠΎΡΠΏΠΎΠΌΠΈΠ½Π°Π½ΠΈΡ, ΡΠ°ΠΊ ΠΊ ΡΠΎΠΆΠ°Π»Π΅Π½ΠΈΡ ΠΈ ΠΏΠ»ΠΎΡ ΠΈΠ΅. ΠΡΠΎ ΡΠ°ΡΡΡ ΠΆΠΈΠ·Π½ΠΈ ΠΊΠΎΡΠΎΡΡΡ Ρ Ρ ΠΎΡΡ ΠΎΡΡΠ°Π²ΠΈΡΡ Π² ΠΏΡΠΎΡΠ»ΠΎΠΌ. ΠΡΡΡ Π»ΡΠ΄ΠΈ, ΠΊΠΎΡΠΎΡΡΠ΅ Π½Π°ΠΏΡΡΠΌΡΡ ΡΠ²ΡΠ·Π°Π½Π½Ρ Ρ ΡΡΠΈΠΌ ΠΊΠ°Π½Π°Π»ΠΎΠΌ, Π½ΠΎ ΠΎΠ½ΠΈ Π²ΡΠ·ΡΠ²Π°ΡΡ Π½Π΅ ΠΎΡΠ΅Π½Ρ Ρ ΠΎΡΠΎΡΠΈΠ΅ ΡΠΌΠΎΡΠΈΠΈ. ΠΠ°Π½Π°Π» Π·Π°ΠΊΡΡΡ. Π― Π½Π΅ Ρ ΠΎΡΡ Π²Π΅ΡΡΠΈ Π΅Π³ΠΎ. Π― Π½Π΅ Ρ ΠΎΡΡ Π΄Π°Π²Π°ΡΡ Π²Π°ΠΌ Π»ΠΎΠΆΠ½ΡΡ Π½Π°Π΄Π΅ΠΆΠ΄ ΠΈΠ»ΠΈ Π΅ΡΡ ΡΡΠΎ-ΡΠΎ. Π― ΡΠΎΠ·Π΄Π°ΠΌ Π΄ΡΡΠ³ΠΎΠΉ,β¦
β€11π5β€βπ₯1
β§ β 71 ΡΠ΅ΡΠΈΡ post : @hunfek β‘
β€19π4π1
β§ β 70 ΡΠ΅ΡΠΈΡ ββ 1:51:38, 1:58:10 post : @hunfek β‘
β€22π1π1
π
β€βπ₯27β€7π2π1
β§ β 69 ΡΠ΅ΡΠΈΡ ββ1:33:03 post : @hunfek β‘
β€12π1
β§ β 69 ΡΠ΅ΡΠΈΡ ββ17:05 post : @hunfek β‘
β€13π2
β§ β 68 ΡΠ΅ΡΠΈΡ ββ 1:17:06, 1:21:10, 1:23:42 post : @hunfek β‘
β€10
β§ β 68 ΡΠ΅ΡΠΈΡ ββ 33:44 post : @hunfek β‘
β€11π1
β§ β 67 ΡΠ΅ΡΠΈΡ ββ 1:14:37 post : @hunfek β‘
β€8π2
β§ β 65 ΡΠ΅ΡΠΈΡ ββ 1:51:05 post : @hunfek β‘
β€7π1
β§ β 64 ΡΠ΅ΡΠΈΡ ββ 1:10:39 post : @hunfek β‘
β€7π2β€βπ₯1π1
Showing the 12 most recent of 16 posts we hold for @hunfek. 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.
Citation-graph rank
Citation-graph rank β 1,317,804 of 1,581,209entries in the measured graph. A weighted position computed from the forward and mention edges below β republished posts weigh more than named mentions β and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channelβs name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page β a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
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.
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 14 August 2026 β this entry's latest reading, not the date you are reading this.
βπ―πππππ | π©ππ ππππππππ πͺπππππππβ (@hunfek), 347 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/hunfek.
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.