Telegram RegisterThe public register of Telegram
Telegram profile photo for TWIZF

Channel

TWIZF

@twizffk

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

6,037subscribers

+8 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002069315738
TypeChannel
Username@twizffk
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live30 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/twizffk

Previous handles

@twizffk was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@twiizkaa
held 7 August 20267 August 2026

Growth

5,9086,0375,972.57 August 2026 — 6,029 subscribers7 August 2026 — 6,029 subscribers8 August 2026 — 6,027 subscribers10 August 2026 — 6,005 subscribers13 August 2026 — 5,989 subscribers27 August 2026 — 5,908 subscribers27 August 2026 — 5,912 subscribers30 August 2026 — 6,037 subscribers7 August 202630 August 2026
8 measurements spanning 23 days, net +8. 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 5,889–6,056 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 12:546,037+125
27 Aug 2026, 07:355,912+4
27 Aug 2026, 04:315,908-81
13 Aug 2026, 18:185,989-16
10 Aug 2026, 16:376,005-22
8 Aug 2026, 03:216,027-2
7 Aug 2026, 19:326,029no change
7 Aug 2026, 19:196,029first reading

Engagement

31 posts held, back to 6 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 9 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
48.8%
avg views ÷ 6,037 subscribers
Avg views / post
2,940
17 posts measured
Reaction rate
4.32%
reactions ÷ views · ER floor
Posts in window
17
of 31 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 26 August 2026
Posts held31 (6 July 202626 August 2026)
Views total50,039
Reactions total2,160
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Aug 2026, 04:31 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

Video runtime
44s
Average length
11s

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

5,561 reactions across 31 posts, in 2 distinct kinds. The most used accounts for 70.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52043583223580947473,91170.3%
custom 54408745348969539881,65029.7%

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 31 of the 31 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 5,561reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 31 most recent posts we hold, published 6 July 2026 to 26 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.

Telegram Stars

Stars received
1,177
across the posts below
Posts paid on
16
of 31 we hold a reading for · 52%
Most on one post
404
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @twizffk. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 31 most recent posts we hold for this entry, published 6 July 2026 to 26 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

26 Aug 2026, 22:36 UTC480 views11 reactionsread 27 August 2026
Photo

🤍всем привет, меня зовут Аня и я живу в Германии 🌟🤩 лайф, покупки, немного меня и просто красивые фото. 🔫🌸 буду рада вашей подписке👁️‍🗨️ https://t.me/kosmohapka2014

custom 520435832235809474711

26 Aug 2026, 20:39 UTC999 views68 reactions2 Starsread 27 August 2026
Video

Video, posted without a caption

custom 520435832235809474768

24 Aug 2026, 23:20 UTC≈2,190 views114 reactionsread 27 August 2026
Photo

смотрем

custom 5204358322358094747114

23 Aug 2026, 18:40 UTC≈2,300 views48 reactionsread 27 August 2026

скоро буду в мск и мне нужно сделать ногти🙏🏻

custom 520435832235809474748

21 Aug 2026, 21:24 UTC≈2,880 views66 reactionsread 27 August 2026
Forwarded from @watakaeone

Геля меня заставила смотреть колобка..

custom 520435832235809474766

17 Aug 2026, 23:18 UTC≈4,590 views253 reactions22 Starsread 27 August 2026
Photo

crybaby

custom 5204358322358094747253

16 Aug 2026, 17:35 UTC≈4,030 views91 reactions60 Starsread 27 August 2026

почему у меня в реках какие то сальмонеллеозники едят сырое мясо

custom 520435832235809474791

16 Aug 2026, 14:35 UTC≈3,840 views238 reactions102 Starsread 27 August 2026
Photo

бум

custom 5204358322358094747238

15 Aug 2026, 21:08 UTC≈3,740 views140 reactionsread 27 August 2026
Video

Video, posted without a caption

custom 5204358322358094747140

14 Aug 2026, 11:12 UTC≈3,530 views67 reactionsread 27 August 2026
Photo

Photo, posted without a caption

custom 520435832235809474767

14 Aug 2026, 06:19 UTC≈3,520 views144 reactionsread 27 August 2026
Photo

прив это ты <3

custom 5204358322358094747144

11 Aug 2026, 20:39 UTC850 views69 reactionsread 12 August 2026
Video

Video, posted without a caption

custom 520435832235809474769

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

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

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

“TWIZF” (@twizffk), 6,037 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/twizffk.

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.