Channel
@Foxxienyan
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
591subscribers
+104 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002495202505 |
|---|---|
| Type | Channel |
| Username | @Foxxienyan |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/Foxxienyan |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 21 September 2026 and assigned it the closest of 31 fixed categories, at 54% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 22:19 | 591 | -7 |
| 10 Sept 2026, 17:41 | 598 | -1 |
| 1 Sept 2026, 08:14 | 599 | -2 |
| 19 Aug 2026, 20:42 | 601 | +81 |
| 13 Aug 2026, 14:06 | 520 | +33 |
| 6 Aug 2026, 18:48 | 487 | no change |
| 6 Aug 2026, 11:47 | 487 | first reading |
6 posts held, back to 28 July 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 6 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
217 reactions across 6 posts, in 5 distinct kinds. The most used accounts for 27.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5972035704488727309 | 60 | 27.6% | |
| custom 5974350657501533316 | 47 | 21.7% | |
| custom 5974350185055130699 | 38 | 17.5% | |
| 💘 | 37 | 17.1% | |
| custom 5972233019581273283 | 35 | 16.1% |
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 6 of the 6 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 217 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 28 July 2026 to 6 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.
💙 💙💙 🤩🤩🤩🤩🤩 🤩 ✨ Make it! ✨ ドキドキするとき無敵でしょ 💕Make up! 💕 キラキラ未来で決まりでしょ 🌈🌈🌈🌈🌈🌈🌈 Cos / ph #Mirei #pripara
custom 597203570448872730915custom 597435065750153331613custom 597223301958127328311custom 59743501850551306992💘1
Posted without readable text
custom 597203570448872730914custom 59743501850551306998💘6custom 59743506575015333161
💦 💙💙💙💙💙💙💙💙💙 🌊 Пару дней назад фоткали любимую акулу - Ринчика из вольного стиля🦈 Несмотря на плохую погоду день прошел очень весело и в суперской компании)) Спасибо большое Фокси за помощь, и Роме за фотосъемку и крутой новый опыт 💙 И конечно же суперской базе «Pro Veter» и ребятам с электросерфами ( сайт / inst ) что так тепло приняли 💙 #фотобэк
custom 59743506575015333167custom 59720357044887273093💘2
💙💙💙🧡🧡🧡🧡🧡🧡 ❤️My name is Shōyō Hinata. I'm going to thrash your team and go to Nationals! ➿➿➿➿➿➿➿➿➿➿➿ #Hinata #Volleyball
💘24custom 597203570448872730917custom 597435018505513069913custom 59743506575015333164
✨ Это очень гениальный фотос Мива
custom 597435018505513069914custom 59743506575015333168custom 59722330195812732836💘1
✨ Впервые у меня есть красивые фото со сцены не с тупым лицом, пхехех 🐈 Ph #Doll #blackbutler
custom 597223301958127328318custom 597435065750153331614custom 597203570448872730911💘3custom 59743501850551306991
Showing the 6 most recent of 6 posts we hold for @Foxxienyan. 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.
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.
Named by 19 registered channels — 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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“Foxxie | キツネ ~” (@Foxxienyan), 591 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/Foxxienyan.
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.