Telegram RegisterThe public register of Telegram

Channel

TetrraFox | cosplay

@tetrrafox

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

689subscribers

+1 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001848122325
TypeChannel
Username@tetrrafox
Created19 April 2023measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live7 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 7 August 2026
On Telegramt.me/tetrrafox

Growth

688689688.56 Aug 2026, 16:04 — 688 subscribers6 Aug 2026, 16:38 — 688 subscribers7 Aug 2026, 10:30 — 689 subscribers6 Aug 2026, 16:047 Aug 2026, 10:30
3 measurements taken within a single day, 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 688–689 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 10:30689+1
6 Aug 2026, 16:38688no change
6 Aug 2026, 16:04688first reading

Engagement

16 posts held, back to 26 July 2026the 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 · 30 days
55.1%
avg views ÷ 689 subscribers
Avg views / post
379
16 posts measured
Reaction rate
13.3%
reactions ÷ views · ER floor
Posts in window
16
of 16 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 6 August 2026
Posts held16 (26 July 20266 August 2026)
Views total6,069
Reactions total809
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 16:38 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

809 reactions across 16 posts, in 17 distinct kinds. The most used accounts for 16.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
13716.9%
❤‍🔥11013.6%
custom 544939532910542329610613.1%
💘789.64%
custom 5404385888614512817728.90%
custom 5384581102922916085658.03%
💋566.92%
🥰425.19%
🔥374.57%
custom 5404762776289685683313.83%
🤩313.83%
custom 5413540753139854584202.47%
🤝172.10%
custom 589318694252210569020.247%
💯20.247%
😍20.247%
🍓10.124%

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

Measured over the 16 most recent posts we hold, published 26 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.

Recent posts

6 Aug 2026, 14:05 UTC174 views50 reactionsread 6 August 2026
Photo

Мои котики 💘 Дариус & Леди

❤‍🔥2512custom 54043858886145128178💋3💘1🥰1

4 Aug 2026, 11:55 UTC431 views91 reactionsread 6 August 2026
Photo

𝓐𝓹𝓱𝓻𝓸𝓭𝓲𝓽𝓮, 𝓬𝓪𝓷 𝔂𝓸𝓾 𝓰𝓾𝓲𝓭𝓮 𝓶𝓮? 𝓣𝓮𝓵𝓵 𝓶𝓮 𝔀𝓱𝓪𝓽 𝓼𝓱𝓮 𝔀𝓪𝓷𝓽𝓼 𝓽𝓸 𝓱𝓮𝓪𝓻.

❤‍🔥38💋24custom 544939532910542329621custom 538458110292291608551💘1custom 54043858886145128171

4 Aug 2026, 11:49 UTC226 views2 reactionsread 6 August 2026

Больше никаких вариантов?🥲

💘2

4 Aug 2026, 07:06 UTC151 views25 reactionsread 6 August 2026
Forwarded from @dariusfairyPhoto

Ехал Грека через реку, а там боги в игры играют…😘 CON.Версия 2026. 1 день Сценическая постановка № 8 Welcome to the God Games🏛️ Zeus | Hera | Dionysus | Apollo | Athena | Aphrodite | Ares | Calypso | Odysseus #cosplay #EPIC

13custom 53845811029229160855💘4custom 58931869425221056902custom 54047627762896856831

4 Aug 2026, 05:46 UTC270 views15 reactionsread 6 August 2026

Считаю, отличный повод расписать длинный пост со всеми готовыми фуллами, процессами и планами, а также хотелками, куда меня можно тащить в проекты 🤩 Думала об этом на выходных Потом увидела пост Иры Потом этот интерактив Все знаки сходятся!

custom 540476277628968568310💘41

4 Aug 2026, 03:50 UTC75 views4 reactionsread 6 August 2026
Forwarded from @lunamoonshade

👽🧦™️🦄🛼🥑🐈™️🪀🍷 Представь, что мы делаем с тобой парный косплей. Кого будем делать и почему? 👁 Или кем ты меня видишь в пару к уже своему сделанному образу? 😇

💘4

3 Aug 2026, 04:37 UTC478 views83 reactionsread 6 August 2026
Photo

🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 🤩🤩🤩🤩🤩Фото: @AkioCato

29custom 540476277628968568319🔥17❤‍🔥4custom 54135407531398545844custom 53845811029229160853custom 54493953291054232963🥰2

2 Aug 2026, 11:59 UTC452 views82 reactionsread 6 August 2026
Photo

🤩🤩🥺☹️🥺😕😕😀🥳🥺😕 Фото от @cris_photoarchive (босиком, потому что так надо))

🥰30custom 538458110292291608519💘177custom 54493953291054232964❤‍🔥2custom 54043858886145128172🔥1

1 Aug 2026, 16:29 UTC447 views84 reactionsread 6 August 2026
Photo

На AltParty впервые вывела в свет свою Нин Гуан. Рада была со всеми увидеться и почиллить!! Ждём новых мероприятий ✨

custom 54043858886145128173218custom 544939532910542329618custom 53845811029229160856💋4💘3❤‍🔥2🥰1

30 Jul 2026, 06:40 UTC475 views54 reactionsread 6 August 2026
Photo

Напоминаю про свой лайф-канал 🐦‍🔥 https://t.me/+7WUMZC4OyCU4NjYy Там пишу больше о жизни, кидаю рандомные фото и истории, чуть-чуть спойлерю новые проекты

custom 544939532910542329625custom 541354075313985458414💘10💋3🥰2

30 Jul 2026, 04:25 UTC456 views72 reactionsread 6 August 2026
Photo

Очень хочу спойлерить образ, но нельзя. Держусь как могу! Ловите вот фотографию кошечки с примерки готового фулла. Я впервые сама полностью уложила парик! Позже покажу-расскажу подробнее :3 Ну а теперь остался только крафт декораций, сегодня жду доставку материалов

custom 544939532910542329622🔥19custom 5404385888614512817167💋3❤‍🔥2🥰2💘1

29 Jul 2026, 13:11 UTC435 views62 reactionsread 6 August 2026
Photo

Не мем, а жизнь

🤩31🤝17custom 54493953291054232969💘2💯21

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

Citation-graph rank — 199,370 of 1,169,250entries 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.

Forward network

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.

Mentions

Named by 9 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.

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.

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

“TetrraFox | cosplay” (@tetrrafox), 689 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/tetrrafox.

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.