Telegram RegisterThe public register of Telegram
Telegram profile photo for 大日🍎🍎 ϝӄ ϝɾ𖦹ϻ ʝɾʝʂӄα ౿ . .

Channel

大日🍎🍎 ϝӄ ϝɾ𖦹ϻ ʝɾʝʂӄα ౿ . .

@fk_from_iriska

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

114subscribers

+42 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-1002460702922
TypeChannel
Username@fk_from_iriska
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live8 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/fk_from_iriska

Growth

71117947 August 2026 — 72 subscribers9 August 2026 — 72 subscribers16 August 2026 — 71 subscribers24 August 2026 — 90 subscribers31 August 2026 — 117 subscribers8 September 2026 — 114 subscribers1147 August 20268 September 2026
6 measurements spanning 32 days, net +42. 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–124 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 17:00114-3
31 Aug 2026, 04:27117+27
24 Aug 2026, 12:0690+19
16 Aug 2026, 04:1871-1
9 Aug 2026, 23:0072no change
7 Aug 2026, 19:1672first reading

Engagement

4 posts held, back to 4 May 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 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 21 June 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

168 reactions across 4 posts, in 8 distinct kinds. The most used accounts for 17.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54472675378824734673017.9%
custom 53282383303645805102213.1%
custom 54178676792875046192213.1%
custom 54111482759673481022011.9%
custom 54654715634930417162011.9%
custom 54653516952507812711911.3%
custom 52247375942852519151810.7%
custom 53415183606538823611710.1%

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 168 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 4 May 2026 to 21 June 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

21 Jun 2026, 16:46 UTC271 views38 reactionsread 9 August 2026
Photo

⏜⌣ 🪷 ׅ︎ . ✧ׅ͡ ℒ𝒾𝓁𝒶𝒸 🍵 𔓘 ᷼͡꒱𑪍 ݃ 𝅾࿙͝࿚

custom 541114827596734810220custom 522473759428525191518

12 Jun 2026, 17:51 UTC321 views52 reactionsread 9 August 2026
Photo

⏝︶ ུ 🧈 ˖ ᩙ 𑇙𑇙ㅤׅㅤׄㅤ∘ 🔘ㅤ᪤ 𝒻𝓇ℴ𝓂 𝒾𝓇𝒾𝓈𝓀𝒶

custom 544726753788247346730custom 532823833036458051022

26 May 2026, 18:41 UTC326 views42 reactionsread 9 August 2026
Photo

౨ৎ ໒ 🌞꒱ ࿐ .⠀. 🌅 Sɕⴙ゙⃞𑄜꯭𑄜Ɩ ˙ 𝒻𝓇ℴ𝓂 𝒾𝓇𝒾𝓈𝓀𝒶

custom 541786767928750461922custom 546547156349304171620

4 May 2026, 15:59 UTC383 views36 reactionsread 9 August 2026
Photo

⵰ ܵ ₊ 🧄 ꕀ ' 彡 .🌂]] ぼ . ྀ 𝒻𝓇ℴ𝓂 𝒾𝓇𝒾𝓈𝓀𝒶

custom 546535169525078127119custom 534151836065388236117

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

“大日🍎🍎 ϝӄ ϝɾ𖦹ϻ ʝɾʝʂӄα ౿ . .” (@fk_from_iriska), 114 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/fk_from_iriska.

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.