Telegram RegisterThe public register of Telegram
Telegram profile photo for fukasi

Channel

fukasi

@fuk1sa

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

75subscribers

+16 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-1003710913913
TypeChannel
Username@fuk1sa
CreatedBetween 1 February 2026 and 30 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live12 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 12 September 2026
On Telegramt.me/fuk1sa

Growth

5975677 August 2026 — 59 subscribers10 August 2026 — 59 subscribers28 August 2026 — 60 subscribers4 September 2026 — 64 subscribers12 September 2026 — 75 subscribers7 August 202612 September 2026
5 measurements spanning 36 days, net +16. 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 57–77 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Sept 2026, 05:1975+11
4 Sept 2026, 03:2064+4
28 Aug 2026, 10:2460+1
10 Aug 2026, 05:3159no change
7 Aug 2026, 03:1459first reading

Engagement

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

Reaction mix

127 reactions across 8 posts, in 8 distinct kinds. The most used accounts for 28.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52446585760220649753628.3%
3023.6%
custom 52466976546955149231814.2%
🍓1713.4%
custom 5235639045916207782107.87%
custom 537543143101302004586.30%
custom 523598383300582715343.15%
custom 538444195027750920143.15%

Custom emoji. 6 of the rows above are 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 8 of the 8 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 127 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 8 most recent posts we hold, published 8 July 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.

Recent posts

6 Aug 2026, 23:04 UTC39 views13 reactionsread 10 August 2026
Photo

Весь отпуск не могу отдохнуть 🧅

custom 52356390459162077826custom 53844419502775092013🍓2custom 52359838330058271532

23 Jul 2026, 23:49 UTC96 views14 reactionsread 10 August 2026
Photo

Опять спойлеры в зины, в августе я уже это закончу и будут дропы по айдлинам 👅 #evezine_wip #KagamineRinLenZINE

custom 52356390459162077824custom 524465857602206497543custom 52359838330058271532custom 53844419502775092011

20 Jul 2026, 20:12 UTC114 views17 reactionsread 10 August 2026
Photo

Привет, пока занимаюсь сдачей всех долгов в зины ☠️ приглашаю в щп. Только если вы хотите! В любом случае это свалка бестолковых мыслей админа данного арт канала.  https://t.me/+H7tZkL6sqvg0NjI6

custom 52446585760220649757custom 537543143101302004562custom 52466976546955149232

17 Jul 2026, 19:56 UTC116 views18 reactionsread 10 August 2026
Photo

Пока опять со скетчами, закрою дедлайны и буду гнить в квартире рисуя полноценки

8🍓4custom 52446585760220649753custom 52466976546955149233

17 Jul 2026, 16:18 UTC113 views20 reactionsread 10 August 2026
Photo

Ещё спойлеры в ив зин, пытаюсь закрыть все дд во время, помогите 🐡 #evezine_wip

custom 524465857602206497576🍓4custom 52466976546955149233

14 Jul 2026, 05:31 UTC127 views10 reactionsread 10 August 2026
Photo

Спойлер в eve зин, будут ещё спойлеры оттуда 🍎 #evezine_wip

🍓4custom 52466976546955149233custom 524465857602206497521

10 Jul 2026, 14:38 UTC143 views21 reactionsread 10 August 2026
Photo

Всякое скетчовое и даже секай

9custom 52446585760220649755custom 52466976546955149234🍓3

8 Jul 2026, 12:40 UTC123 views14 reactionsread 10 August 2026
Photo

Всем привет, хочется поделиться мне уже очень много нарисовали фан артов с моими персонажами и вселенной! Очень приятно спасибо 。⁠:゚⁠(⁠;⁠´⁠∩⁠`⁠;⁠)゚⁠:⁠。 ❤️❤️ Художники: 1. @ikasi3 2. @selkytenmei 3. @riiikaisan 4. @sunnrrie 5. Это старое моё И спасибо за 52 подписчика! Как раз еду в Питер 🐙

custom 52446585760220649758custom 52466976546955149233custom 537543143101302004521

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

Mentions

Named by 2 registered channels — 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 12 September 2026 — this entry's latest reading, not the date you are reading this.

“fukasi” (@fuk1sa), 75 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/fuk1sa.

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.