Channel
@MiroFoxy
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Telegram's recommendations · Cite this entry
477subscribers
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001894581950 |
|---|---|
| Type | Channel |
| Username | @MiroFoxy |
| Description | 🎨 Turning your ideas into colorful art — from sketch to final piece. 📩 DM to order: @Miro_foxy 🔗 Links & prices: mirofoxy.carrd.con My Game - https://t.me/yournumber_game https://yournumbergame.carrd.co/ |
| Created | Between 1 November 2022 and 31 August 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 18 September 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 1 |
| On Telegram | t.me/MiroFoxy |
Growth history is still building. We hold one measurement for this entry. A trend needs at least two, taken days apart — so this will fill in on its own rather than being estimated. We do not publish numbers we have not measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 10:22 | 477 | first reading |
18 posts held, back to 8 April 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 page of 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 26 August 2026 |
|---|---|
| Posts held | 18 (8 April 2026 – 26 August 2026) |
| Views total | 429 |
| Reactions total | 36 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 18 Sept 2026, 10: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.
Lifetime counters from Telegram’s own channel header, read 18 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 5 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.
417 reactions across 18 posts, in 10 distinct kinds. The most used accounts for 50.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 209 | 50.1% | |
| 🔥 | 79 | 18.9% | |
| custom 5456522406426318492 | 45 | 10.8% | |
| custom 5456571158600096647 | 41 | 9.83% | |
| custom 5456157600494131627 | 16 | 3.84% | |
| 🎉 | 10 | 2.40% | |
| 💯 | 10 | 2.40% | |
| 🥰 | 4 | 0.959% | |
| 😍 | 2 | 0.48% | |
| custom 5375560194132569806 | 1 | 0.24% |
Custom emoji. 4 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 are Telegram’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 18 of the 18 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 417 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 8 April 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @MiroFoxy. 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 18 most recent posts we hold for this entry, published 8 April 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.
Since I’m much more of a 2D artist than a 3D artist, I decided to lean into that and make Your Number as a pre-rendered 2.5D game like an old horror game.
custom 545652240642631849219custom 54565711586000966477🔥1
Hi everyone! I decided to separate my personal art from my game project. This channel will stay focused on my personal posts, thoughts, commission artwork, and other things I want to share. For everything related to Your Number, I created a separate channel. There I’ll post game updates, artwork, development progress, characters, locations, gameplay, and other news about the project. So if you’re interested in the ga…
custom 54565711586000966479
Photo, posted without a caption
custom 545615760049413162714❤8💯1
Биомеханоид
🔥19❤7custom 54565711586000966471
Хоба! 🤸♀️
❤12custom 54565711586000966474
Базовый завтрак художника
🔥17❤11
Делаю кости для хвостика))
custom 545657115860009664711🔥6custom 54565224064263184924custom 54561576004941316272
Карта 3д уровня
🔥19custom 54565711586000966479❤8
Awww
❤15
Уж простите. Но этот матч очн странный. Испанцы играли хорошо, не спорю. Я бы даже сказал лучше . Но меня сука бесит , что у них был доп игрок в виде судьи. Направо и налево накидал нам карточек. Наш упал в лужу и ему же желтая. Испанец сам врезался и крутанул сальто нам красная. Даже тренеру дали жёлтую! Только у наших мяч и они бегут к воротам противника, сразу свисток. Я в шоке. Судья конч P.s Мартинес красавчик ❤…
💯9
Video, posted without a caption
🔥12❤2
Photo, posted without a caption
🎉8❤2
Showing the 12 most recent of 18 posts we hold for @MiroFoxy. 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.
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.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“MiroFox” (@MiroFoxy), 477 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/MiroFoxy.
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.