Telegram RegisterThe public register of Telegram

Channel

Домик Фркфркфрк 🦊

@frk_klok

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

229subscribers

-1 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-1001680735755
TypeChannel
Username@frk_klok
Descriptionты похож на кота, хочу забрать тебя домой😺 фотографии по поиску #фркофото по вопросам и сотрудничеству @klok_buryy мои фотографии: @empty_underground https://vk.com/empty_underground
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held3
On Telegramt.me/frk_klok

Growth

229230229.57 Aug 2026, 15:25 — 230 subscribers8 Aug 2026, 03:31 — 229 subscribers8 Aug 2026, 10:16 — 229 subscribers7 Aug 2026, 15:258 Aug 2026, 10:16
3 measurements taken within a single day, net -1. 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 229–230 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 10:16229no change
8 Aug 2026, 03:31229-1
7 Aug 2026, 15:25230first reading

Engagement

12 posts held, back to 7 August 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
32.0%
avg views ÷ 229 subscribers
Avg views / post
73.3
12 posts measured
Reaction rate
13.9%
reactions ÷ views · ER floor
Posts in window
12
of 12 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 8 August 2026
Posts held12 (7 August 20268 August 2026)
Views total880
Reactions total122
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 10:16 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.

What this channel posts

Photos
11,900
Videos
500
Links
665

Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
1m 05s
Average length
33s

Measured directly from 2 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

122 reactions across 12 posts, in 9 distinct kinds. The most used accounts for 69.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤‍🔥8569.7%
😁86.56%
custom 543401529603157384975.74%
64.92%
custom 537541031265882416843.28%
🔥43.28%
🥰43.28%
👍21.64%
😱21.64%

Custom emoji. 2 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 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 12 of the 12 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 122reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

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

Recent posts

8 Aug 2026, 09:20 UTC50 views6 reactionsread 8 August 2026
Photo

Опять этот же вагон украла👻

❤‍🔥6

8 Aug 2026, 08:10 UTC62 views11 reactionsread 8 August 2026
Photo

Верите, нет, но это мы стоим на Богородском

❤‍🔥92

8 Aug 2026, 06:50 UTC78 views16 reactionsread 8 August 2026
Photo

Так, я решила покататься

❤‍🔥12🥰4

8 Aug 2026, 06:30 UTC80 views13 reactionsread 8 August 2026

Украдем вагон какой-нибудь?

😁8🔥3❤‍🔥1👍1

8 Aug 2026, 05:36 UTC78 views10 reactionsread 8 August 2026
Video message

Video message, posted without a caption

❤‍🔥91

8 Aug 2026, 04:34 UTC78 views10 reactionsread 8 August 2026
Video message

Video message, posted without a caption

❤‍🔥91

8 Aug 2026, 03:50 UTC79 views9 reactionsread 8 August 2026
Photo

Блин, а на чем кататься?

❤‍🔥5custom 53754103126588241684

8 Aug 2026, 02:30 UTC83 views9 reactionsread 8 August 2026
Photo

Нет, ну так ещё Яндекс не пытался меня увести на Буденного. В этот раз он выиграл, и мы постоим на нескольких светофорах. Но это только сегодня.

custom 54340152960315738497❤‍🔥2

7 Aug 2026, 18:50 UTC87 views6 reactionsread 8 August 2026
Forwarded from @mos_sobyaninPhoto

Новая эстакада на шоссе Энтузиастов улучшит транспортное обслуживание жителей районов Ивановское, Новогиреево и подмосковной Балашихи Реализуем одновременно три проекта. Первый — комплексное благоустройство самой магистрали. 🛣 Второй — строительство эстакады на пересечении шоссе Энтузиастов со Свободным проспектом и Большим Купавенским проездом, практически рядом с МКАД, где регулярно возникали пробки. Ввод эстакад

❤‍🔥42

7 Aug 2026, 17:40 UTC99 views12 reactionsread 8 August 2026
Photo

Восторг! Восторг! https://transphoto.org/photo/2314947/

❤‍🔥12

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

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.

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 August 2026 — this entry's latest reading, not the date you are reading this.

“Домик Фркфркфрк 🦊” (@frk_klok), 229 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/frk_klok.

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.