Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝖋𝖚𝖗𝖗𝖎 𝖘𝖙𝖎𝖐𝖊𝖗𝖞 🎱

Channel

𝖋𝖚𝖗𝖗𝖎 𝖘𝖙𝖎𝖐𝖊𝖗𝖞 🎱

@Fur1ry

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

4,093subscribers

+402 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-1003366399072
TypeChannel
Username@Fur1ry
CreatedBetween 1 November 2025 and 31 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live30 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/Fur1ry

Growth

3,6917,1325,411.57 August 2026 — 3,691 subscribers7 August 2026 — 3,691 subscribers8 August 2026 — 3,698 subscribers11 August 2026 — 7,132 subscribers14 August 2026 — 3,909 subscribers17 August 2026 — 4,013 subscribers20 August 2026 — 4,031 subscribers24 August 2026 — 4,038 subscribers27 August 2026 — 4,054 subscribers30 August 2026 — 4,093 subscribers4,0937 August 202630 August 2026
10 measurements spanning 23 days, net +402. 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 3,175–7,648 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 12:164,093+39
27 Aug 2026, 08:374,054+16
24 Aug 2026, 10:584,038+7
20 Aug 2026, 15:184,031+18
17 Aug 2026, 15:174,013+104
14 Aug 2026, 13:543,909-3,223
11 Aug 2026, 00:417,132+3,434
8 Aug 2026, 10:343,698+7
7 Aug 2026, 18:023,691no change
7 Aug 2026, 17:513,691first reading

Engagement

21 posts held, back to 1 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 3 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
68.6%
avg views ÷ 4,093 subscribers
Avg views / post
2,810
20 posts measured
Reaction rate
7.82%
reactions ÷ views · ER floor
Posts in window
21
of 21 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 11 August 2026
Posts held21 (1 August 202611 August 2026)
Views total56,150
Reactions total4,389
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 02:20 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.

Reaction mix

4,389 reactions across 21 posts, in 31 distinct kinds. The most used accounts for 33.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1,48633.9%
custom 52763397150862558431,27028.9%
custom 52089071394011615163127.11%
custom 54068205080061305433046.93%
custom 53029934832613195762154.90%
❤‍🔥2154.90%
🌭1373.12%
custom 53885963046392036811272.89%
custom 5206274500542370458651.48%
custom 5388977513051494177491.12%
custom 5206405999556070974471.07%
custom 5334767866065489472300.684%
💔190.433%
🔥190.433%
custom 5443138072856275387150.342%
custom 5303146349737315571120.273%
😡110.251%
😨80.182%
🥰80.182%
custom 543846049698864684870.159%
11 further kinds330.752%

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

Measured over the 21 most recent posts we hold, published 1 August 2026 to 11 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
125
across the posts below
Posts paid on
6
of 21 we hold a reading for · 29%
Most on one post
100
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @Fur1ry. 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 21 most recent posts we hold for this entry, published 1 August 2026 to 11 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

11 Aug 2026, 11:59 UTC≈1,210 views155 reactionsread 12 August 2026
Photo

Улыбнулся значит добрый 😊 🌟

100custom 540682050800613054321custom 538859630463920368110custom 52062745005423704587custom 52089071394011615165custom 53029934832613195765🌭2🔥2

11 Aug 2026, 05:58 UTC≈1,500 views157 reactionsread 12 August 2026
Photo

😊 🤩

113custom 527633971508625584319🔥12❤‍🔥4custom 52089071394011615164🍌2🌭1💘1

10 Aug 2026, 11:34 UTC≈1,770 views155 reactionsread 12 August 2026
Photo

❤❤

107custom 527633971508625584333custom 53029934832613195768custom 53031463497373155714❤‍🔥1🌭1custom 52089071394011615161

10 Aug 2026, 04:57 UTC≈1,890 views219 reactions1 Starread 12 August 2026
Photo

Акулка 😼 🤩

custom 5276339715086255843159custom 52062745005423704582216custom 53885963046392036818custom 52089071394011615165custom 53889775130514941774❤‍🔥3🌭2

8 Aug 2026, 11:40 UTC≈2,380 views180 reactionsread 12 August 2026
Photo

Интересный артик Chaz 😏😳😜 Фул в 𐌿ρᥙʙᥲᴛκᥱ 🌟

🌭107custom 520890713940116151633custom 5206274500542370458129custom 53029934832613195766💔4custom 53885963046392036814custom 52763397150862558433

7 Aug 2026, 14:19 UTC≈2,660 views197 reactionsread 12 August 2026
Photo

🤩Ножки из предложки 🌟

custom 5406820508006130543129custom 52763397150862558433817custom 53885963046392036815custom 53029934832613195763🌭2custom 53889775130514941772❤‍🔥1

6 Aug 2026, 13:39 UTC≈3,040 views196 reactions100 Starsread 12 August 2026
Photo

Интересный артик Riley🥹 Фул в 𐌿ρᥙʙᥲᴛκᥱ 🤩

132custom 530299348326131957625custom 538859630463920368110custom 52763397150862558437custom 52062745005423704586💔5custom 52089071394011615165❤‍🔥2

6 Aug 2026, 09:06 UTC≈2,810 views216 reactions7 Starsread 12 August 2026
Photo

😁 ❤️

151custom 538897751305149417743custom 538859630463920368110custom 52089071394011615164custom 54068205080061305434❤‍🔥1🌭1🤔1

5 Aug 2026, 18:01 UTC≈3,030 views567 reactionsread 12 August 2026
Photo

Акулка застрял 🤩 🤩 Осеменить - 👅

custom 5276339715086255843476custom 52089071394011615164216custom 53029934832613195769custom 53885963046392036819💔5❤‍🔥4custom 53865459387917001484

5 Aug 2026, 05:19 UTC≈3,120 views243 reactionsread 12 August 2026
Photo

❤❤Доброе утро🤩

❤‍🔥16739custom 520627450054237045818custom 53885963046392036817custom 52763397150862558435custom 53031463497373155713🌭2custom 52089071394011615162

4 Aug 2026, 17:18 UTC≈3,280 views170 reactionsread 12 August 2026
Video

Video, posted without a caption

100custom 527633971508625584337custom 540682050800613054314custom 53029934832613195768custom 53885963046392036814🌭3❤‍🔥2🤯1

4 Aug 2026, 05:50 UTC≈3,390 views137 reactionsread 12 August 2026
Photo

😊 🎸

custom 5276339715086255843104custom 5443138072856275387159custom 52089071394011615165custom 53885963046392036812🌭1🍓1

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

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.

“𝖋𝖚𝖗𝖗𝖎 𝖘𝖙𝖎𝖐𝖊𝖗𝖞 🎱” (@Fur1ry), 4,093 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/Fur1ry.

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.