Telegram RegisterThe public register of Telegram
Telegram profile photo for فیگزی چکار کرد؟

Channel

فیگزی چکار کرد؟

@figsymade

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

17subscribers

+1 since we began measuring on 7 October 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002157808372
TypeChannel
Username@figsymade
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 October 2026
Last confirmed live18 October 2026
Measurements held3
Confirmed unchanged2 times, most recently 18 October 2026
On Telegramt.me/figsymade

Growth

161716.57 October 2026 — 16 subscribers7 October 2026 — 16 subscribers10 October 2026 — 17 subscribers7 October 202610 October 2026
3 measurements spanning 4 days, 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 16–17 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Oct 2026, 22:3817+1
7 Oct 2026, 03:2216no change
7 Oct 2026, 02:4716first reading

Engagement

15 posts held, back to 2 September 2025 — 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 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
52.9%
avg views ÷ 17 subscribers
Avg views / post
9.0
2 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
3
of 15 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 5 October 2026
Posts held15 (2 September 2025 – 5 October 2026)
Views total18
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Oct 2026, 03:22 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

7 reactions across 4 posts, in 5 distinct kinds. The most used accounts for 42.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🍓342.9%
❤‍🔥114.3%
🍾114.3%
🔥114.3%
🤩114.3%

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

Measured over the 15 most recent posts we hold, published 2 September 2025 to 5 October 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

3 Dec 2025, 15:35 UTC82 views3 reactionsread 7 October 2026

" کد رهگیری ۱۲ آذر" 193650425800653840009101 عمادی 193650425800652640036101 اولادی 193650425800651330034101 آشوری ها

🍓3

24 Nov 2025, 16:26 UTC93 views2 reactionsread 7 October 2026

"کد رهگیری ۱ آذر " 193650424700004200078101 رمضانی 193650424700003990049101 عقیلی

🍾1🤩1

29 Oct 2025, 15:35 UTC122 views1 reactionsread 7 October 2026

کد رهگیری "۷ آبان" : 193650422300386180079114 مالکی مقدم 193650422300385810067114 مرادی

🔥1

23 Oct 2025, 07:14 UTC956 views1 reactionsread 7 October 2026
Photo

سلام شیلوم جان 🥹 ممنونم از دستان هنرمندتون بابت این جاسوویچی زیبا یکساله که همراهمه و آخ نگفته تمیزی بافت هاتون قابل ستایشه 😭🩷

❤‍🔥1

23 Oct 2025, 07:13 UTC97 viewsread 7 October 2026

سلام به موقع به دستم رسید 😍 ممنون از هنر دستتون که دقیقا همونی که میخواستم رو برام درست کردین. فکر نمی‌کردم اینقد باکیفیت باشه. امیدوارم همیشه با هنرتون به زندگی آدما خوشحالی و لبخند بیارین و حال دل خودتون هم خوب باشه 🌷 مرسی

23 Oct 2025, 07:13 UTC816 viewsread 7 October 2026
Photo

این جوجه نرمالو قراره رو لبای یکی که ازم دوره لبخند بیاره و خوشحالش کنه :)

20 Oct 2025, 13:14 UTC72 views0 reactionsread 7 October 2026

" کد رهگیری ۲۸ مهر " 193650421400166714394101 صالحی 193650421400165817564101 فرحناکفر 193650421400164590044101 سماک

23 Sept 2025, 17:37 UTC76 viewsread 7 October 2026

کد رهگیری ۱ مهر: 193650418700150880646111 نادر لطیف 193650418700151950089111 غفوری بیداخویدی

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

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

“فیگزی چکار کرد؟” (@figsymade), 17 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/figsymade.

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.