да не могла эта какашка делаться 5 часов. 😢
custom 54066011511414205895custom 53368398098286810362custom 54069141855378251781

Channel
@fkalln
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
74subscribers
-1 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004380484034 |
|---|---|
| Type | Channel |
| Username | @fkalln |
| Description | артики от никчёмного художника. ((18+))!!! я не отвечаю за вашу психику, вы тут находитесь добровольно. |
| Created | Between 1 June 2026 and 24 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 3 |
| On Telegram | t.me/fkalln |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 21:32 | 74 | no change |
| 9 Aug 2026, 02:36 | 74 | -1 |
| 8 Aug 2026, 09:34 | 75 | first reading |
19 posts held, back to 24 July 2026 — 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.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 18 of 19 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 8 August 2026 |
|---|---|
| Posts held | 19 (24 July 2026 – 8 August 2026) |
| Views total | 2,669 |
| Reactions total | 277 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 21:32 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 9 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.
277 reactions across 18 posts, in 12 distinct kinds. The most used accounts for 20.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5208862905532975291 | 56 | 20.2% | |
| custom 5197659990147495276 | 38 | 13.7% | |
| custom 5400224086779524773 | 33 | 11.9% | |
| custom 5442733873484030143 | 30 | 10.8% | |
| custom 5208817151246371747 | 29 | 10.5% | |
| custom 5438151521336332618 | 27 | 9.75% | |
| custom 5445240128635169597 | 20 | 7.22% | |
| custom 5397614211247405060 | 15 | 5.42% | |
| custom 5406601151141420589 | 14 | 5.05% | |
| custom 5336839809828681036 | 6 | 2.17% | |
| custom 5406914185537825178 | 5 | 1.81% | |
| custom 5321224605820543819 | 4 | 1.44% |
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 18 of the 19 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 277reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 24 July 2026 to 8 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.
да не могла эта какашка делаться 5 часов. 😢
custom 54066011511414205895custom 53368398098286810362custom 54069141855378251781
закончила с кастомом для победителя. было очень приятно работать по мудборду. 🥹
custom 54066011511414205899custom 53212246058205438194custom 53368398098286810364custom 54069141855378251784
ой ребята, вроде что-то рисуется. но я хочу ей ещё окрас какой-нибудь придумать блен 😢
custom 54452401286351695976custom 54381515213363326183custom 54427338734840301432
ух ты что это, я ему ноги сломала, доигрался. 😨
custom 54452401286351695975custom 54427338734840301433custom 53976142112474050602custom 54381515213363326182
🌟🌟🌟🌟🌟🌟🌟 0.2 • условия: 1. репост поста в тгк/чат репостов/двум друнам 2. отправить пруф и желаемый номер под этот пост 3. реакция по желанию 1 - 2 - 3 - 4 - @Diloshki52 5 - 6 - 7 - 8 - @DeeLora 9 - 10 - @Nikulich0 11 - @KikoFoxice 12 - @bano4k0 (я) 13 - @HA7N11 14 - @nastxxyaa 15 - 16 - каждый рисует ❗️самостоятельно❗️и в течении двух недель скидывает мне в лс - @bano4k0
💋💋💋💋💋💋💋🤩 давно её не было, поэтому вот. к сожалению в этот раз поняшки не такие крутые, но может кто-то да и поучаствует. условия: репост в свой тгк/репост чаты. подписка на мой канал, кинуть пруффы репоста и свой порядковый номер. призы: 1 место: кастом на платной базе. 2 место: морячка. 3 место: гусеница. количество участников: 25. актуально до 7 августа, могу закончить раньше, если наберётся 25 участников. в…
custom 544273387348403014318custom 53976142112474050606custom 54381515213363326186custom 54452401286351695975
вот такая простенькая морячка получилась 😇
custom 54381515213363326187custom 54427338734840301434custom 53976142112474050603custom 54452401286351695973
последний спойлер, дальше иду работать с заказом и потом продолжу дрочить адопта 🥺
custom 54381515213363326189custom 53976142112474050604custom 54427338734840301433custom 54452401286351695971
ребята тише без отписок, я работаю над заказами и стараюсь на расслаблне провести оставшееся лето 😭
custom 51976599901474952767custom 52088171512463717474custom 52088629055329752914custom 54002240867795247732
это не достойно быть ючиком. как тени то ставить бля 😭
custom 51976599901474952764custom 52088171512463717473custom 52088629055329752912
улыбаемся и пашем. в первые переносила пт на канон базу, думаю это хороший опыт, вообще пиратик чудо. ❤️
custom 52088629055329752918custom 51976599901474952762custom 52088171512463717472custom 54002240867795247731
опять купила двух доходяг на эмоциях. потратила на них 450р, первому делается крутой референс от моей любимки. что с ними делать не знаю. заблокируйте мне карту 🥺
custom 52088629055329752916custom 51976599901474952763custom 54002240867795247731
Showing the 12 most recent of 19 posts we hold for @fkalln. 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 — 392,236 of 1,183,361entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“#F’KKALN.k” (@fkalln), 74 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/fkalln.
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.