Channel
@FIIMA444
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
157subscribers
+0 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002877020376 |
|---|---|
| Type | Channel |
| Username | @FIIMA444 |
| Created | Between 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 10 August 2026 |
| On Telegram | t.me/FIIMA444 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 16:28 | 157 | no change |
| 9 Aug 2026, 17:32 | 157 | first reading |
14 posts held, back to 7 May 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.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 14 (7 May 2026 – 7 August 2026) |
| Views total | 761 |
| Reactions total | 179 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 17: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.
463 reactions across 13 posts, in 10 distinct kinds. The most used accounts for 19.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5343572944159264129 | 90 | 19.4% | |
| custom 5318834868837191834 | 86 | 18.6% | |
| custom 5368418531102700925 | 56 | 12.1% | |
| custom 5377692177243581560 | 49 | 10.6% | |
| custom 5197361163502901705 | 45 | 9.72% | |
| custom 5400105571451967857 | 44 | 9.50% | |
| custom 5343819720095192544 | 35 | 7.56% | |
| custom 5231327255233314351 | 31 | 6.70% | |
| custom 5343582594950780695 | 18 | 3.89% | |
| custom 5319287236267642939 | 9 | 1.94% |
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 13 of the 14 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 463reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 7 May 2026 to 7 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.
я выписалась! сладенькая коммишечка, я бы взяла ещё кмм
custom 536841853110270092513custom 53438197200951925446custom 53776921772435815604custom 53188348688371918341custom 53435729441592641291
Камишечко
custom 54001055714519678578custom 53188348688371918344custom 53776921772435815604custom 53438197200951925441
кмм
custom 531883486883719183412custom 54001055714519678576custom 53776921772435815605
Channel photo updated
коммишечкт забыла показать :3
custom 536841853110270092517custom 540010557145196785710custom 53776921772435815608custom 53188348688371918342
коммишка готовенькая
custom 531883486883719183414custom 53776921772435815609custom 53435729441592641296custom 53684185311027009252custom 53438197200951925441custom 54001055714519678571
🔤🦷🦷🦷🦷🦷🦷🦷🦷🦷 🔤🔤🙈😎 гифт на день 🔤 рождения @chiiii7777 буду очень благодарна фитбеку!!
custom 534357294415926412920custom 536841853110270092511custom 53776921772435815609custom 53188348688371918342custom 54001055714519678572
₊˚⊹🤩🤩🤩🥛🤩🤩🤩🤩🤩🤩
custom 534357294415926412922custom 534381972009519254410custom 53776921772435815606custom 54001055714519678574custom 53188348688371918342custom 53684185311027009251
🥲🥲 её можна купить тут
custom 534381972009519254416custom 53435729441592641297custom 54001055714519678574custom 53776921772435815602custom 53188348688371918341
наконец-то закончили кмм! заказчик: @ARKbutan теперь коммишки снова открыты!! прайс лист >тут< пишите в любое время
custom 534357294415926412919custom 531883486883719183410custom 536841853110270092510custom 53438197200951925441custom 53776921772435815601
маленькая лошадка хочет стать хирургом
custom 534357294415926412915custom 54001055714519678579custom 53188348688371918348custom 53684185311027009252custom 53776921772435815601
!!bark
custom 523132725523331435123custom 51973611635029017059custom 53435825949507806959custom 53188348688371918344
Showing the 12 most recent of 14 posts we hold for @FIIMA444. 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 — 683,594 of 1,340,412entries 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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“[18+] ☕️ fima444” (@FIIMA444), 157 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/FIIMA444.
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.